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 Thread

View: Search:

Author

Thread: Problems in my sync.

Snow Monkey
Posts: 214

Problems in my sync. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 05 Sep 06 12:56 PM

In our 6.2.4 slx system, when an opp is closed-Won, we create a SalesOrders...

One of our Remote user is complaining that at times, when a network user closes an opp , this doesnt update her remote.however she can see the SalesOrder created for that..This is only happening sometimes and not always.I got her remote machines syncerror.txt tru a remote task now and she has no failed update transactions.

In earlier verisons of slx, we would have seen some kinda update transactions which are failed(because of an invalid date or whatever).Now there are no other pointers in this case..Any other place where i should be looking at??

-Nandu

[Reply][Quote]

Frank Chaffin
Posts: 475

Re: Problems in my sync. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 05 Sep 06 1:23 PM

Check and see it there are any SQL Errors in the Window Application EventLog on the remote PC.

Questions:
-Is the remote user subscribed to the Account that the opportunuty is associated with?
-Is the opportunuty in the Remote Database?

BTW, I have seen stuff like this befor and it usually has to do with subscription. When I am tracking stuff like this down I attach a bat file to the before sync and after sync events of the syncserver that will same a copy of all the wglogs, infiles, and outfiles. I then search through the TEF files to see what when wrong. It is not easy but is is doable.

[Reply][Quote]

Snow Monkey
Posts: 214

Re: Problems in my sync. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 05 Sep 06 3:10 PM

Yes this account is subscribed by the remote user. and that opp is in the the remote db.(C'mon Frank............

)

Now the thing which i dont know is about the subscription rule built for this user.My Admin does that and i'd ask him about this.

When I am tracking stuff like this down I attach a bat file to the before sync and after sync events of the syncserver that will same a copy of all the wglogs, infiles, and outfiles.

How do you do that Frank?

[Reply][Quote]

Frank Chaffin
Posts: 475

Re: Problems in my sync. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 05 Sep 06 3:31 PM

Quote:

Originally posted by Nandu

When I am tracking stuff like this down I attach a bat file to the before sync and after sync events of the syncserver that will same a copy of all the wglogs, infiles, and outfiles.

How do you do that Frank?

You will need to launch the SyncServer process interactively. Then select File -> Options from the menu. Then specify a program to Run before and after the syncserver.exe runs. I always check the Wait for Return option.

Here is a sample bat file.

xcopy F:\SlxLogging\Infiles\*.* F:\SlxLogging\_in\*.* /d/s/e/c/y
xcopy F:\SlxLogging\Outfiles\*.* F:\SlxLogging\_out\*.* /d/s/e/c/y
xcopy F:\SlxLogging\WGLogs\*.* F:\SlxLogging\_wg\*.* /d/s/e/c/y

Once you have the files the real fun starts as you explore the files with the SalesLogix Transaction Viewer.

[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 \|

page cache (param): 5/7/2024 7:48:02 PM