Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Monday, November 25, 2024 
 
slxdeveloper.com Community Forums  
   
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
 Administration Forums - Synchronization
Forum to discuss SalesLogix synchronization and remote database management. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to Synchronization | New ThreadView:  Search:  
 Author  Thread: System Error Message: The system cannot find the file specified
Chris
Posts: 18
 
System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 11 Sep 06 10:45 AM
fiogf49gjkf0d
Hello,

I've got some problem with the synchronization program which displays the following message :
" 10/09/2006 00:05:45] System Error Message: The system cannot find the file specified
[10/09/2006 00:05:45] Unable to delete file: E:\SALSA\Office\Archives\ZIP-QAUY-A100000.QHU0 "

However, Remote User QHU0 seems to synchronize correclty, according to SYNCSEQUECING table dates and files exisiting in Infiles & Outfiles.

How to explain et avoid this message ?

Thanks,

Chris
[Reply][Quote]
Jeremy Brayton
Posts: 491
Top 10 forum poster: 491 posts
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 11 Sep 06 2:20 PM
fiogf49gjkf0d
Check the Archives folder for that file. Does a similar one exist like QAUY-A100000.QHU0 (without the ZIP- in front). If so, it may point to a problem that occured when we upgraded from 5.2 to 6.1 (which I believe is still a "problem" when going straight to 6.2). Do any files exist in the archives folder OTHER than files that are recent?

The remote user should have files dating back to roughly the last time they synchronized. Technically it goes back to 2 syncs ago, the files stay there until the remote client says "Yep, I got those files" during the next sync round-trip.

The filename is VERY IMPORTANT too because A100000 is the very first keybase in a freshly created remote database. To put it simply, that file is the very first file a remote database should receive and synchronize. If either the host or the remote can't find that file, it is likely (though rare) that something is seriously wrong with synchronization. I doubt it's something serious but if this were the 100th file in the sequence it wouldn't be as alarming.
[Reply][Quote]
Chris
Posts: 18
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 12 Sep 06 4:41 AM
fiogf49gjkf0d
In the SyncErrors.txt :
[12/09/2006 00:05:44] System Error Message: The system cannot find the file specified
[12/09/2006 00:05:44] Unable to delete file: E:\SALSA\Office\Archives\ZIP-QAUY-A100000.QHU0
...
[12/09/2006 00:06:05] System Error Message: The system cannot find the file specified
[12/09/2006 00:06:05] Unable to delete file: E:\SALSA\Office\Archives\ZIP-QAUY-A1000B0.QHU0

=> That means 397 files ! (from "00" up to "B0"). No error with other Site Code.

Exacly same error messages for the log part concerning treatment of night 10=>11.

In the Archives folder, the whole files starts with "ZIP-".
But I've got 3 files concerning QHU0 :
ZIP-QAUY-A400019.QHU0 (dated 10/09/2006 during server synchro of night 10=11)
ZIP-QAUY-A40001A.QHU0 (11/09/2006)
ZIP-QAUY-A40001B.QHU0 (12/09/2006)

In the Outfiles folder, I'v got only 2 TEF for QHU0 :
CMDQAUY-A0004E3.QHU0 (dated 12/09/2006)
ZIP-QAUY-A40001B.QHU0 (same date)

In Infiles :
0 file named *QHU0

Strange...

Chris
[Reply][Quote]
Jeremy Brayton
Posts: 491
Top 10 forum poster: 491 posts
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 18 Sep 06 12:18 PM
fiogf49gjkf0d
Outfiles are sent to a remote and then moved to the archive folder. The remote gets the files and then sends an acknowledgement that it got those files. The sync server reads the ack during the next sync cycle and then proceeds to delete the archived files. The error message is the sync server saying it can't find those files to delete, which isn't necessarily bad but may point to something that shouldn't be happening.

There are a couple of things I can think of that may cause this. A custom routine to clear the archive folder periodically and antivirus software's real-time protection isn't set to exclude the sync folders. The sync process is a control-freak when it comes to those directories and as you can see, it is pretty self-contained.

Are you using network or FTP sync? If you use network sync does the person connect through a vpn? I've heard that combination can sometimes cause similar issues.

From what you've posted, the sync process seems fine but the errors will continue until you fix the problem. If this were an event log message it would be informational instead of an error but like the event log you do want to fix informational messages if you can.
[Reply][Quote]
Chris
Posts: 18
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 27 Sep 06 8:26 AM
fiogf49gjkf0d
Hello,

I give you more informations about our problem :

* In the SyncErrors.txt, we have exactely the same messages each day the remote user makes a remote sync (the sync server is launched each night)
* the messages :
"[18/09/2006 00:06:13] System Error Message: The system cannot find the file specified
[18/09/2006 00:06:13] Unable to delete file: E:\SALSA\Office\Archives\ZIP-QAUY-A1000AU.QHU0"
mention the first 397 TEF (A100000 to A1000B0)
* Sync between remote and host is OK : SendIndex = A40001S, ApplyIndex = A40003T

=> According to the log, sync server tries to delete old files in the Archives folder. It means : Host receives ack from the remote user, concering tef A100000 to A1000B0. But these files doesn't exist in Archives.
Am i right ?

=> Is the remote sending out-of-date ack ?

=> Why those 397 TEF and not another ones ?

Thank for you help !

Chris
[Reply][Quote]
Jeremy Brayton
Posts: 491
Top 10 forum poster: 491 posts
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 27 Sep 06 1:14 PM
fiogf49gjkf0d
Quote:
Originally posted by Chris

Hello,
* In the SyncErrors.txt, we have exactely the same messages each day the remote user makes a remote sync (the sync server is launched each night)
* the messages :
"[18/09/2006 00:06:13] System Error Message: The system cannot find the file specified
[18/09/2006 00:06:13] Unable to delete file: E:\SALSA\Office\Archives\ZIP-QAUY-A1000AU.QHU0"
mention the first 397 TEF (A100000 to A1000B0)
* Sync between remote and host is OK : SendIndex = A40001S, ApplyIndex = A40003T

When you first create a remote database for a sitecode, you're given a default keybase (A100000). When you cut a new database for that same sitecode the keybase increments to A200000... up until it runs out of room. The keybase is using a base36 numbering scheme where numbers start at 0 and end at Z (0-9, a=10...z=35). If you are getting errors for every increment from A100000 to A1000B0, that is telling me that EVERY SINGLE TEF shows the same symptom which usually means the problem is easily defined and usually can be fixed.

What stands out from your post is the SendIndex and ApplyIndex. An index of A4 (not A1) suggests they are using the 4th cut database for that sitecode. What this tells me is your sync server thinks you're on a keybase of A1 but the remote (or wherever you're getting the SendIndex from) is telling you that it's on a keybase of A4, which is not good.

The most common cause of an error of this type is when a user gets a new database cut but for whatever reason SalesLogix isn't configured to use it. The AttachRemote utility has been known to have problems upgrading a database that is in use. Because this is fairly common I always use the \admin switch to give you the attach and detach buttons. I then detach an old database, archive it to zip, remove the file entirely or overwrite it with the new database, then use the attach button. This method eliminates the copy routine that the normal mode uses to copy the database to the MSDE data folder, which is the usually the source of the problem. This means that if you attach a database from C:\, MSDE will keep the database there instead of C:\Program Files\Microsoft SQL Server\MSSQL\Data where all of the other databases are normally kept.
Quote:

=> According to the log, sync server tries to delete old files in the Archives folder. It means : Host receives ack from the remote user, concering tef A100000 to A1000B0. But these files doesn't exist in Archives.
Am i right ?

=> Is the remote sending out-of-date ack ?

=> Why those 397 TEF and not another ones ?

Question 1: You're correct. The sync server is looking for files that either never existed or have already been dealt with.
Question 2: I don't think so but it's possible if the user syncs VERY RARELY. Because an ack requires another sync cycle to complete it's round-trip, if your user syncs once every 5 days it would take 10 days before the sync server caught up with the first sync.
Question 3: Those TEFs apply only to that remote and indicates a problem with that person only. I haven't done the math to make sure 397 is the exact number from *00 to *B0 but it's very close, meaning this isn't something that randomly happens for the remote but something that literally occurs every time they sync.

Conclusion:
A mismatched database is the best answer I can come up with. The problem is that if this is the case, your remote has data on their old database that will never make it to the server normally. I believe those more knowledgeable than myself know of ways to "trick" the server into accepting changes without using the "resync remote database" functionality in Administrator.exe. I've used resync remote database before so I know it does work but the major problem with it is that it chokes on large tables like history (70k records). I took the simple approach and deleted everything in those tables but if I needed the data I could have deleted everything but records with a createdate/modifydate after the problem started.
[Reply][Quote]
Chris
Posts: 18
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 27 Sep 06 6:25 PM
fiogf49gjkf0d
Thank you for your answer but it is not very clear for me :

I give you more informations :

* In the Administrator, for the remote user concerned by the errors in SyncErrors.txt (=QHU0), the keybase is "A4"
* In the host database, in the SYNCSEQUENCING table, ApplyIndex and SendIndex are something like "A4000XX" and "A4000YY"
* In the Outfiles and Archives folders on the server, TEF for remote QHU0 are named "A4000.."
* Sync Remote => Host seems to be ok, because recent data written with the remote SLX are found on the host database
* Errors in log concern all TEF from A100000 up to TEF A1000B0 (= 11*36 + 1 = 397 TEF) and there are also exactly 397 rows in SYNCFILETRACKING table with SourceSite = Host and Targetsite = QHU0. And the TranFile column mention TEF from A100000 to A1000B0. FileStatus is "1" for the whole rows

=> Is there a lack of data in the host database or in the remote database ?

=> If the host database is "up to date", can I regenerate a new remote database and attach it again on the remote computer ?

=> Can I "update status"/"delete rows" in the SYNCFILETRACKING to avoid the messages in SyncErrors.txt ?

=> How can I know the keybase used by the remote computer ? (because this computer is used at the opposite place in the country !)

=> Can I use 'resync remote database" ?

Thank you (and sorry for my english) !

[Reply][Quote]
Jeremy Brayton
Posts: 491
Top 10 forum poster: 491 posts
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 27 Sep 06 7:26 PM
fiogf49gjkf0d
Quote:
Originally posted by Chris

* In the Administrator, for the remote user concerned by the errors in SyncErrors.txt (=QHU0), the keybase is "A4"
* In the host database, in the SYNCSEQUENCING table, ApplyIndex and SendIndex are something like "A4000XX" and "A4000YY"
* In the Outfiles and Archives folders on the server, TEF for remote QHU0 are named "A4000.."
* Sync Remote => Host seems to be ok, because recent data written with the remote SLX are found on the host database

All of this suggests the database is correct from the host's perspective.
Quote:

* Errors in log concern all TEF from A100000 up to TEF A1000B0 (= 11*36 + 1 = 397 TEF) and there are also exactly 397 rows in SYNCFILETRACKING table with SourceSite = Host and Targetsite = QHU0. And the TranFile column mention TEF from A100000 to A1000B0. FileStatus is "1" for the whole rows

Do these errors continue to occur or were they a one time event? The precise nature of the "problem" suggests a configuration issue but everything pointed out above makes it appear like everything is fine.
Quote:

=> Is there a lack of data in the host database or in the remote database ?

=> If the host database is "up to date", can I regenerate a new remote database and attach it again on the remote computer ?

=> Can I "update status"/"delete rows" in the SYNCFILETRACKING to avoid the messages in SyncErrors.txt ?

=> How can I know the keybase used by the remote computer ? (because this computer is used at the opposite place in the country !)

=> Can I use 'resync remote database" ?

Answered in order:
1) I don't think there is a lack of information in either database based on what I see, but we haven't ruled out the remote side entirely.
2) Yes you can. If the remote isn't easily accessable I would make 100% sure a recut was necessary before I went this route. This should always be a last resort as it destroys all potential evidence from the database.
3) You can update rows in SYNCFILETRACKING to fool the sync server but generally these types of messages do not cyle through SyncErrors.txt, so you could get away with doing nothing.
4) You could have them look in C:\Documents and Settings\All Users\Application Data\SalesLogix\Sync\Outfiles and have them read the filename to you. The keybase in Sync\Outfiles should match the keybase in Sync\Infiles.
5) It sounds like you don't need to resync the database, as it looks like everything is functioning correctly from what I see but without intimate knowledge of the remote end we can't be 100% sure.

There is one scenario I thought of that could cause this:
Create a remote database but forget to turn off the sync server. The sync server proceeds to process this database and create TEFs (keybase A1). Cut the database 3 more times, most likely because of a configuration error to increment the keybase to A4. The remote syncs up with the keybase of A4 and works as if nothing went wrong. The host continues to process keybase A4 as if nothing's wrong but during one sync event, it tries to reconcile keybase A1 and can't.

The scenario is so specific that I doubt that is what cause the problem. This may only be a very minor issue but because the evidence is still in front of you, it'll be in your best interest to investigate as much as possible. You don't want a similar problem to bite you again later.
[Reply][Quote]
Chris
Posts: 18
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 28 Sep 06 4:03 AM
fiogf49gjkf0d
Quote:
Originally posted by Jeremy Brayton


All of this suggests the database is correct from the host's perspective.

Do these errors continue to occur or were they a one time event? The precise nature of the "problem" suggests a configuration issue but everything pointed out above makes it appear like everything is fine.


Since july, the same 397 error messages are added at the end of SyncErrors.txt each day the remote user synchronizes (once in july, once in august, and four time this month)

Quote:

3) You can update rows in SYNCFILETRACKING to fool the sync server but generally these types of messages do not cyle through SyncErrors.txt, so you could get away with doing nothing.


Sorry, but I don't understand what you mean... I thought the sync server tries to delete the 397 files in Archives (which do not exist) because these files were mentioned in this table (with exactly the same TEF ID A10000 to A1000B0). In other words, I thought some of the data in this table were false, and these data launches a processing which tries to delete files in Archives...
Hum... I am right... My purpose is to avoid this repetitive messages in SyncErrors.txt... That's why I thought an update on this table could cancel the processing of these "old" files... Do you think there is a link between the date in SYNCFILETRACKING and the messages in Errors.txt ?

Quote:

4) You could have them look in C:\Documents and Settings\All Users\Application Data\SalesLogix\Sync\Outfiles and have them read the filename to you. The keybase in Sync\Outfiles should match the keybase in Sync\Infiles.
5) It sounds like you don't need to resync the database, as it looks like everything is functioning correctly from what I see but without intimate knowledge of the remote end we can't be 100% sure.


I agree but do not have the remote with me

Quote:

There is one scenario I thought of that could cause this:
Create a remote database but forget to turn off the sync server.

You mean : create a remote database with Administrator during the sync server is running ?
I don't understand what you mean by this "stop" of the sync server when we create a remote database.

Thank you for you help
[Reply][Quote]
Jeremy Brayton
Posts: 491
Top 10 forum poster: 491 posts
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 29 Sep 06 1:15 PM
fiogf49gjkf0d
Quote:
Originally posted by Chris



Since july, the same 397 error messages are added at the end of SyncErrors.txt each day the remote user synchronizes (once in july, once in august, and four time this month)

Sorry, but I don't understand what you mean... I thought the sync server tries to delete the 397 files in Archives (which do not exist) because these files were mentioned in this table (with exactly the same TEF ID A10000 to A1000B0). In other words, I thought some of the data in this table were false, and these data launches a processing which tries to delete files in Archives...
Hum... I am right... My purpose is to avoid this repetitive messages in SyncErrors.txt... That's why I thought an update on this table could cancel the processing of these "old" files... Do you think there is a link between the date in SYNCFILETRACKING and the messages in Errors.txt ?

Sorry, I was going from my own experience. I have old files in SYNCFILETRACKING that go back to 2000 with filestatus of 1 and 2. These files do not show up in SyncErrors.txt on a consistent basis so I would doubt that this is somehow related to your problem. It's entirely possible that I'm wrong but I've never really had to tweak syncfiletracking even in the height of our sync issues.

Reoccuring sync errors are rare, in fact this is the first time I've heard of them. I would think they indicate a serious problem but everything functioning normally indicates it must not be that serious.
Quote:

I agree but do not have the remote with me

Could you call them on the phone and have them read the filenames off to you? If that's also a problem you could trap the Infiles coming from the remote. You want to compare the TEFs to make sure not only are they named correctly but you may even want to use TrnViewer.exe to peek inside them. You may find one TEF consistently requesting those 397 files and it may point to the problem a little more closely.
Quote:

You mean : create a remote database with Administrator during the sync server is running ?
I don't understand what you mean by this "stop" of the sync server when we create a remote database.

I mean you create the first database and the first sync cycle runs on the server. It creates a couple of TEFs that initialize the new remote database and it'll also queue up all of the attachments if you leave that option checked. You then realize the database was created wrong for whatever reason. You cut a new database 3 more times, most likely due to some configuration quirk to get the keybase A4. I'm not saying this scenario happened exactly but it's one thing I can think of that may bring about the same symptoms.

What bugs me is I really don't have any solutions, I'm just trying to help you troubleshoot what it might be because we haven't even narrowed that down well enough. I did a rough search through the sage knowledgebase and I couldn't find anything even remotely related to the issue.
[Reply][Quote]
Chris
Posts: 18
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 17 Oct 06 3:29 AM
fiogf49gjkf0d
Hello,

=> About the problem :
[14/10/2006 00:06:04] System Error Message: The system cannot find the file specified
[14/10/2006 00:06:04] Unable to delete file: E:\SALSA\Office\Archives\ZIP-QAUY-A1000AO.QHU0

I've tried to update/delete some records in the SYNCFILETRACKING but I think several Remote Sync are needed, so I have to wait in order to check a solution.

=> Moreover I've got a new problem in the syncstatus.txt : during the sync server of this night, we have the messages below (and only these messages) :

" [17/10/2006 00:05:37] System Error Message: The system cannot find the file specified
[17/10/2006 00:05:37] Unable to copy attachment file \\Rdpciteurms059\SALSA\Office\!Q6UJ9A007MLTA6UJ9A0002SR-7729-U6UJ9A00002L-9806.URL for send to XXXX."

We have 10 messages of this kind, for 10 remote users ("XXXX" in the message above) and always the same attchment file.

This file doesn't exist in folder :
\\Rdpciteurms059\SALSA\Office\

And there is no record in the ATTACHMENT table with this file name.

Moreover I can see the attachment file in the SLX Client application : thanks to the name of the file in the syncstatus log, I have the AccountId/ContactId => I can view the attachment file in the "attchament file tab" of the Account/ContactId form.

Has anybody an idea about the reason of these messages ?
How can I know whether this attachment file has been created, has been deleted, will be seeked again ?

Thank you,

Chris

[Reply][Quote]
Dave
Posts: 36
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 24 Oct 06 8:44 AM
fiogf49gjkf0d
Hi Everybody,

I'm currently experiencing the same trouble, having repeatedly the error:
Quote:

System Error Message: The system cannot find the file specified
Unable to delete file: \\ServerName\NetShare\SyncFolder\Archives\ZIP-MAINDB-A800XXX.REMOTE


in the SyncErrors.txt log file.
That for 200 "missing" ones.

Actually, the user Key Base is A9, while the missing files belong to the old A8 key base.

So, the actual attached Remote DB is for sure A9.

On the Remote Log, I can see that the specular error:

Quote:

The file MAINDB-A800XXX.REMOTE was ignored because it is older than your database.

in the SyncStatus.txt file, while I get:

Quote:

System Error Message: Cannot create a file when that file already exists
Unable to move file: C:\Documents and Settings\All Users\Application Data\SalesLogix\Sync\Infiles\MAINDB-A800XXX.REMOTE to C:\Documents and Settings\All Users\Application Data\SalesLogix\Sync\Infiles\Old\MAINDB-A800XXX.REMOTE.


in the SyncErrors.txt file.

So it seems that a ghost of A8 is still around.
Ok, I've understood that maybe I've attached the A9 without synchronizing the last time (twice) the A8.

Anyway, how to get out of there?

Dave.
[Reply][Quote]
Chris
Posts: 18
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 06 Nov 06 4:38 AM
fiogf49gjkf0d
Hello !

I think we have the same problem...
But I can't read the remote logs because our remote users are too far away (moreover, i guess the new remote database has been installed on a new portable, if the former computer has been stolen...)
The first extract of log is the SyncErrors.txt on the server, and the following two extracts are an extract of remote logs, ok ?

Did you try to update the syncfiletracking table ?

Chris
[Reply][Quote]
Don Poggio
Posts: 7
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 07 Nov 06 7:52 AM
fiogf49gjkf0d
I ran into a similar issue with a client. The file starting with "ZIP-" usually references files in the Library and Attachments folder. It turned out that someone had manually deleted some files in one of these two folders on the SLX Server, so every time it tried to synchronize it was attaching a null record to the file, thus corrupting it and making it impossible for the Synch Server to read.
Run the Integrity Checker tests - "Attachment File validation" and "Library Docs file validation", but don't do it in Fix mode. Get the detail and see if you can track down any of the missing docs.

Just one possibility - hope it helps,
Don
[Reply][Quote]
Dave
Posts: 36
 
Re: System Error Message: The system cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 07 Nov 06 10:09 AM
fiogf49gjkf0d
Dan,
we almost do not use the attachments, anyway I'll make a check.
Thanks for the tip.
[Reply][Quote]
Chris
Posts: 18
 
Re: Sytem Error Message : The System cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 23 Nov 06 4:47 AM
fiogf49gjkf0d
Hello,

I've got a new message in the "syncErrors.txt" log ("unable to delete file in \Archives\") concerning a user which appears for the first time in the log.
The file is : ZIP-QAUY-A1000EK.5QPD

In the SyncFiletracking table , i have one record for the tranfile = "QAUY-A1000EK.5QPD" with FileStatus=1.

In the SyncSequencing table, i notice that SendIndex = "A1000ER" and ApplyIndex = "A1000VD"

=> It deals with the same database "A1"

I don't understand what is the problem with this specific file "A1000EK" !

Has someone tried to create an empy file "ZIP-QAUY-A1000EK.5QPD" in the Archives Folder on the server ?

Thank you,

Chris
[Reply][Quote]
Jeremy Brayton
Posts: 491
Top 10 forum poster: 491 posts
 
Re: Sytem Error Message : The System cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 27 Nov 06 2:20 PM
fiogf49gjkf0d
Was this an upgraded database? From 5.x or perhaps 4.x to 6.1 then 6.2? The reason I say this is I had a problem due to an upgrade inconsistency. It produced very odd symptoms compared to the root cause (problems with composite keys).

If memory serves me, attachments are prepended with ZIP-* but it may in fact be every file synchronized. On my host, our files would lose the ZIP-* but contained the same trailing values. The sync server would erroneously try to delete files with the ZIP- prefix but something in the sync process would rename the files (there's way more to it than that).

Take a look at your Archives\ folder. Are all of the files prefixed with ZIP-? If not, do your files go back a while? The Archives folder should cleanse itself as remotes verify they received the data (usually takes 2 full cycles: a send and receive acknowledgement). If you do in fact have these files then chances are you are seeing the exact problem I had.

Reply to this post if you are in fact seeing what I describe. The fix is short but the end result is not very pretty and I don't want to go into length as to why unless I'm certain you're affected.
[Reply][Quote]
Jeremy Brayton
Posts: 491
Top 10 forum poster: 491 posts
 
Re: Sytem Error Message : The System cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 27 Nov 06 2:26 PM
fiogf49gjkf0d
Bah serves me right for not reading. You answered a lot of my questions previously so you could probably discard this.

Actually it wouldn't hurt to check. Go into Enterprise Manager and the table SYNCSEQUENCING go into design mode. Is there a key next to sourcesite AND targetsite? It's important that BOTH columns are keyed. In upgraded databases the clustered index/composite key wouldn't be created correctly. What this would introduce is host changes could be synchronized down to the remote, but no remote changes would be applied to the host. This gave the illusion that sync was working perfectly when in fact it was not for the week it occured.

The fix required me updating the table in every database. If you correct the host, every remote database created after that time would work correctly. If you didn't correct the host, every remote would have to be updated. I believe you could sync down an alter table statement to take care of it, but I was never too bold to try it.
[Reply][Quote]
Dave
Posts: 36
 
Re: Sytem Error Message : The System cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 28 Nov 06 1:42 AM
fiogf49gjkf0d
Jeremy,

my DB was upgraded from 5.4 to 6, and then patched to SP2.
All the Archive files are ZIP-something.
BOTH columns of the SYNCSEQUENCING table are keyed.

There must be something else wrong, because I'm having other users claiming not synchronized data.
I think there's something wrong on extension tables, but this will be another topic...

Thanks anyway!
[Reply][Quote]
Frank Chaffin
Posts: 475
 
Re: Sytem Error Message : The System cannot find the file specifiedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 28 Nov 06 5:47 PM
fiogf49gjkf0d
Dave,
I have not had time to digest all the details of this thread but I have had a lot of experience with syncing. It feels like you are having two seperate issues.

Note: the contents of the SYNCFILETRACKING table is not related to the errors that your syncserver is logging about not being able to delete files from archives. On the hostdb the SYNCFILETRACKING table is used to track missing TEF files coming from the remotes not files going to the remomte. On the remotedb it is used to track missing TEF files coming from the hostdb.

First lets talk about the errors deleting files from archives: As Jeremy has mentioned, at the end of the synccycle the remote creates a special sync file listing all the files that were processed --the name of these special files start with "CMD". When the syncserver process this special CMD file it attempts to delete the acknowledged files from the archives folder.

I can think of some things that might account for your errors:
1. Something is causing the remote to keep reapplying the original files and resending a CMD file that acknowledge the files have been applied.

2. Something is wrong on the remote that is causing it to resend the CMD files that acknowledge the files have been applied.

3. Something is wrong on the host that is preventing it from deleting the CMD file after it processes it.

I have run into all three of these situations. Can you check the contents of the infiles and outfiles folders on the remote, and syncserver.
[Reply][Quote]
 Page 1 of 1 
  You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

   Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 11/25/2024 4:42:19 PM