11/22/2024 9:51:41 PM
|
| |
| 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!
Forum to discuss SalesLogix synchronization and remote database management. View the code of conduct for posting guidelines.
|
|
|
|
Synchronization failure. Invalid property value
Posted: 23 Aug 06 9:34 AM
|
fiogf49gjkf0d Hello to all.
On an installation with 1 central office and 4 remote users, after running well for months, we try to synchronize, with the sync service or starting manually the synchronization server, and the following message appears on the log:
[...] Closing current log file.
[...] Refreshing DataDictionary.
[...] Synchronization failure occured.
And a pop-up window appears on the Sync Server with the following message:
Synchronization failure.
Invalid property value.
We had one remote office that we didn't use. We have tried to remove it and the same happens.
We also noticed that the FailedTrans dir on the server had a lot of files, so we renamed that dir and created another one. Also, the SyncErrors.txt was also a 1.2 Gb file, so we also renamed it and created manually an empty one with the same name.
It can be due to that we have this error for nearly two months, with a sync frecuency of 5-10 minutes.
Any ideas, please?
We can't sync our remotes.
Thanks in advance,
Oscar |
|
|
|
Re: Synchronization failure. Invalid property value
Posted: 23 Aug 06 10:05 AM
|
fiogf49gjkf0d Questions:
1. Is there anything in Window's Application Event Log?
2. Is there anything in syncerrors.txt?
3. When was the last time the system was rebooted?
4. How much free space do you have on your drives?
5. What version of SalesLogix are you running? |
|
|
|
Re: Synchronization failure. Invalid property value
Posted: 23 Aug 06 11:22 AM
|
fiogf49gjkf0d Thanks for the response, Frank.
1. On the application event log there's no message related to SalesLogix.
2. Finally we have openned it with UltraEdit, as it was a 1.2 Gb text file. It contained the sync log since September 2004. The last messages are the following (I have translated it to English):
[28/06/2006 21:52:22] The incoming file C:\slxlogs\Infiles\ZIP-FILEX29TA1000LL.LXJ2 appears to be corrupt.
[28/06/2006 21:52:23] The incoming file C:\slxlogs\Infiles\ZIP-FILEX29TA1000LN.LXJ2 appears to be corrupt.
[28/06/2006 21:52:23] The incoming file C:\slxlogs\Infiles\ZIP-FILEX29TA1000LP.LXJ2 appears to be corrupt.
[28/06/2006 21:52:24] The incoming file C:\slxlogs\Infiles\ZIP-FILEX29TA1000LR.LXJ2 appears to be corrupt.
[28/06/2006 21:52:24] The incoming file C:\slxlogs\Infiles\ZIP-FILEX29TA1000LX.LXJ2 appears to be corrupt.
[28/06/2006 21:52:24] The incoming file C:\slxlogs\Infiles\ZIP-FILEX29TA1000LZ.LXJ2 appears to be corrupt.
[28/06/2006 21:52:24] The incoming file C:\slxlogs\Infiles\ZIP-FILEX29TA1000M1.LXJ2 appears to be corrupt.
[28/06/2006 21:52:25] System Error Message: Operation has finished correctly
[28/06/2006 21:52:25] Unable to move/rename attached file \\central\slxlogs\Documents\AttachTemp\FILEX29TA1000AH.LXJ2 to \\central\slxlogs\Documents\!QX29TA1000AGimage001.jpg
Unable to move/rename attached file \\central\slxlogs\Documents\AttachTemp\FILEX29TA1000AH.LXJ2 to \\central\slxlogs\Documents\!QX29TA1000AGimage001.jpg System Error Message: El sistema no puede hallar el archivo especificado
[28/06/2006 21:52:25] System Error Message: System cannot find the specified file
[28/06/2006 21:52:25] Unable to move/rename attached file \\central\slxlogs\Documents\AttachTemp\FILEX29TA1000AJ.LXJ2 to \\central\slxlogs\Documents\!QX29TA1000AIimage003.gif
Unable to move/rename attached file \\central\slxlogs\Documents\AttachTemp\FILEX29TA1000AJ.LXJ2 to \\central\slxlogs\Documents\!QX29TA1000AIimage003.gif System Error Message: El sistema no puede hallar el archivo especificado
[28/06/2006 21:52:25] System Error Message: System cannot find the specified file
[28/06/2006 21:52:25] Unable to move/rename attached file \\central\slxlogs\Documents\AttachTemp\FILEX29TA1000AL.LXJ2 to \\central\slxlogs\Documents\!QX29TA1000AKimage004.gif
3. I have rebooted it some times since we detected the error about 15 days ago. Our team works quite autonomously.
4. On a HDD with 149 Gb, we have 3,94 Gb free.
5. We were running SLX 6.2 SP3. We had it running on SP3 about 3 months before this error occured. Before that, it was a 6.2 installation for about half a year, and a 6.1 installation (with Service Packs) for nearly another year. Yesterday we updated it to SP4 in order to see if it was a bug. But the problem is there.
I have read on a newsgroup (crm toolbox) about a person that had the same problem with 6.1, but nobody answered him for a solution.
Any ideas??
Thanks in advance |
|
|
| |
| |
|
Re: Synchronization failure. Invalid property value
Posted: 19 Jan 07 12:53 PM
|
fiogf49gjkf0d I'd suggest using these tools:
1) SLXProfiler.exe hooked into SyncServer.exe OR
2) Possibly SQL Profiler if SLXProfiler isn't available AND
3) RegMon from SysInternals OR
4) DebugView from SysInternals
I'd have #1 and 3 running regardless. DebugView isn't necessary but there are some instances where it helps. I'd run through a Sync cycle and take a snapshot of everything that happens until it either dies, or processes. Then you can comb through the snapshot for anything that stands out. The problem with that is it's very hard for me to explain exactly what to look for but once you understand the process it becomes easier to focus on what doesn't fit.
"Invalid property value" sounds like an error message you'd get when say SyncServer.exe was looking for a particular settings value of Y but got X. I'm not entirely sure how much of the registry is used for settings so RegMon may not even be necessary for the most part.
The SyncErrors.txt error messages give another problem entirely though. I get those error messages all the time. I thought they were because while the \\ComputerName\Share is short, it really maps to C:\Repository\SalesLogix\Sync Logs\Documents and there's a 256 character limit on file paths. This means that if you have a filename that surpasses 256 characters with the full path, SLX will think it's okay but the filesystem will reject it. Most likely this is not your problem though.
[28/06/2006 21:52:22] The incoming file C:\slxlogs\Infiles\ZIP-FILEX29TA1000LL.LXJ2 appears to be corrupt.
Files with the ZIP-FILE* name are typically attachments. The log is telling you the attachment is corrupt then further down you see that it can't be copied to \\central\slxlogs\Documents\. This is actually normal error behavior for a corrupt file and may be a symptom but is not the root cause. This is also telling me that sync is processing somewhat normally, otherwise you'd get a big fat "CAN'T DO ANYTHING" message or something like that.
I suggest archiving your SyncErrors.txt, trimming it back to when the error started, or deleting it outright. I periodically do this to keep it from growing too much because wading through 2 years of data for a recent problem is supreme overkill. Once you have it down, deleted, or moved then start the sync process again. Your error logs now should point a little more towards the problem.
Hopefully that's enough to get started. This is one of those things you're probably going to have to monitor, poke, and prod until something bubbles up to the surface. It's never quite fun but once you get the hang of it, problems that require monitoring in the future will become easier to spot. |
|
|
|
Re: Synchronization failure. Invalid property value
Posted: 19 Jan 07 3:03 PM
|
fiogf49gjkf0d Jeremy,
What I am seeing is...
1. thousands of messages in syncerrors.txt complaining about not being able to move/rename a file attachment received from a remote user. The attachments are PDF files that were sent out in an email blast to several thousand contacts. The reason for failure is "... the system cannot find the file ..."
2. thousands of files building up in the FailedTrans folder.
3. thousands of files being left behind in the AttachTemp folder.
One more data-point... the attachment files are in the documents folder on the host, and WorkGroup users can see them. So even thought the messages say there was a failure it appears that everything worked.
The issue at the site is that all the error messages and log files are wasting GIGs and GIGs for space.
|
|
|
|
Re: Synchronization failure. Invalid property value
Posted: 19 Jan 07 3:39 PM
|
fiogf49gjkf0d Track an error in syncerrors.txt to the AttachTemp folder. Do the filenames match up? If not, is this an upgraded database from 5.2 or earlier? If so does the syncsequencing table have a composite key for both targetsite and sourcesite (both shown as keys in Enterprise Manager)?
A specific upgrade problem bit me multiple times and the symptoms were sync works from host to remote but not vice versa. I'd also see weird filenamess in AttachTemp like (SITE)(KEY) instead of FILE(SITE)(KEY). This symptom completely identifies the problem because the second it was fixed all of the filenames started showing up correctly. The problem cropped up multiple times because I had fixed remote databases individually but not the host. When I went to cut a new remote database it didn't have the composite key, affecting just that one user.
Have you viewed FailedTrans files with trnViewer? If it's an ongoing problem, you may even be able to get lucky and match up a TEF in Archives for slightly more information I believe. Doesn't the FailedTrans folder on the remote end (the FTP folder) match up with most syncerror entries relating to a remote? The reason I say that is I've had syncerror entries on the host but almost no FailedTrans entries. My remotes are another story.
Last question: Is the problem sporatic or ongoing and consistent? Sporatic problems make SLXProfiler and RegMon almost useless because letting them run for days would take a while to sift through. I don't know of anyone who really has that kind of time anyway. |
|
|
|
Re: Synchronization failure. Invalid property value
Posted: 19 Jan 07 5:13 PM
|
fiogf49gjkf0d | Track an error in syncerrors.txt to the AttachTemp folder. Do the filenames match up? If not, is this an upgraded database from 5.2 or earlier? If so does the syncsequencing table have a composite key for both targetsite and sourcesite (both shown as keys in Enterprise Manager)? |
|
The file names match up.
There are 2 indexes PK_SYNCSEQUENCING which is clustered and SYNCSEQUENCING_PRIMARY which is not clustered.
| A specific upgrade problem bit me multiple times and the symptoms were sync works from host to remote but not vice versa. I'd also see weird filenamess in AttachTemp like (SITE)(KEY) instead of FILE(SITE)(KEY). This symptom completely identifies the problem because the second it was fixed all of the filenames started showing up correctly. The problem cropped up multiple times because I had fixed remote databases individually but not the host. When I went to cut a new remote database it didn't have the composite key, affecting just that one user. |
|
The files are in the format of FILE(SITE)(KEY).
| Have you viewed FailedTrans files with trnViewer? If it's an ongoing problem, you may even be able to get lucky and match up a TEF in Archives for slightly more information I believe. Doesn't the FailedTrans folder on the remote end (the FTP folder) match up with most syncerror entries relating to a remote? The reason I say that is I've had syncerror entries on the host but almost no FailedTrans entries. My remotes are another story. |
|
Attachment TEFs can not be view in the TrnViewer. Note: I know the attachments are there and that they are getting moved because they are showing up in the Documents folder on the host.
| Last question: Is the problem sporatic or ongoing and consistent? Sporatic problems make SLXProfiler and RegMon almost useless because letting them run for days would take a while to sift through. I don't know of anyone who really has that kind of time anyway. |
|
The problem is continuious however it did not start until the customer upgraded to SP4 from SP1. I don't think that SLXProfiler would should anything because it is not SQL commands that are involved... it is file system commands.
It feels like the OS is reporting it can not find the file but in reality it can. |
|
|
|
Re: Synchronization failure. Invalid property value
Posted: 23 Apr 07 1:03 PM
|
fiogf49gjkf0d Good afternoon.
I continue to have this problem. Message showing
M[23/04/2007 19:00:08]Synchronization failure.Invalid property value
on the Monitor Console.
I have traced with SLXProfiler, and the following sentences are executed:
SQL Log:
Time Stamp SQL Type Parse(ms) Prepare(ms) Secure(ms) Execute(ms) GetRows(ms) Log(ms) Rows User ID Process ID Machine Cursor Client SQL
565,0008 USER 0,0805 0,0117 0,0000 0,0000 0,0000 0,0000 0 admin 4012 192.168. 20.104 FORWARD ONLY call slx_RefreshDictionary
565,0026 USER 0,0626 0,0103 0,0000 0,0000 0,0000 0,0000 0 admin 4012 192.168. 20.104 FORWARD ONLY call slx_RefreshLogServer
All messages tab:
Time Stamp Message Type Process ID Machine Message
565,0008 SQL 4012 192.168. 20.104 call slx_RefreshDictionary
565,0026 SQL 4012 192.168. 20.104 call slx_RefreshLogServer
Error log:
(nothing shown)
Any ideas?
Thanks a lot,
Oscar
|
|
|
|
Re: Synchronization failure. Invalid property value
Posted: 09 Nov 07 10:37 AM
|
I guess AttachTemp FailedTrans isssue has been resolved.
If not, here is the solution: We had same problem and both FailedTrans and AttachTemp used to grow into GBs of files [both on Server and Remotes]. We had a tough time in cracking it down. Finally we got rid of these with a hot fix 1 from Sage for version 6.2 with SP6.
It is a defect and the sage support pointed us to this hotfix. Once applied it stopped creating those files and also processed a big bunch of existing AttachTemp files. The hot fix replaces Sync server and Sync Client executable files to version 6.2.6.1009
Hope this helps.
Cheers,
San |
|
|
|
Re: Synchronization failure. Invalid property value
Posted: 06 Jan 09 10:59 AM
|
Hi Oscar. I just ran across your post from a year ago. I am looking for any documentation or procedure for removing an unused Remote Office. Where did you find this, or did you just figure it out on your own? I have not worked with our company's SalesLogix in over a year, and now they are closing a remote office and want me to help get rid of the remote office server without causing sync problems or other issues for the remaining network & remote users. I have searched all of the administrator and implementation guides that i can find, and there is lots of info about creating a remote office but nothing about removing one.
If you or anyone in the slxdeveloper.com community knows where to find steps for removing a remote office I would greatly appreciate a link.
Thanks,
Mark |
|
|
|
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!
|
|
|
|
|
|
|
|