Hi,

We've installed with the Sage support the Sync Server on a seperate VM.

We changed everything in the SLX Livesystem wich belongs to the Sync.

We have since that the problem that the Sync Server is not running automaticly. We've created the job in the Admin and changed the Sync Server. But its not working. The job is just not running.

We have to logon to Sync Server VM, login to the SyncServer and hit the Sync button.

Thats not the only Problem. Almost every Tool in the SLX Folder is not running (SLXMonitorConsole, SLXProfiler....)

we get this message from the System Unable to retrieve service file path from the database. The permission is correct.

Since we have the info that sage sells SLX we are not able to get someone on the phone

Regards Dennis

Delete the entry found in SYNCSERVICEFILE table (or multiples if found).

we have just one entry in this table.

This is our main path on the Live System. The Sync Server VM writes everything in there. If we delete this, SLX isn't writing WGLogs and we lose information for the Remote Clients? Is that correct?

That would be terrible. In this case i would have to create new Remote DB's.

I checked everything. Its correct. I have permission, the manuell sync is working correctly.

On both Server the Reg entry is correct.

Back to your answer if I delete the Table entry what should I do after that? Should I set something new?

The manual sync has nothing to do with this section though? If you run it manually - it simply logs in and runs.

When running as a service (which, I'm guessing is started ?) then it picks up the jobs to run from this file (the sync file).

So, when you say they are correct - what are they set to - the old machine ? If so, why?

There's no need to delete the entry - if it is there and correct then, by all accounts, everything should work.

What happens when you run syncmonitorconsole and watch for the job to start/run etc. what does it say - and what happens when it is due to run ?

In SLX Admin - System - Sync Autom. Service the Job is set to the new Service Machine which is the Sync Server. The schedule is every 30 mins.

The shared path to \\NTSG4\Synclogs which is the Live SLX Server. When I open SLXConsoleMonitor and configure the SyncServer i get following.

Current Status: Error in UpdateViewDate - List index out of bounds (1)

Last run was 17.01.2013.

Server Log: SLXSyncService:Unable to retrieve ServiceFilePath from database. But I can when I search for the unc path

Pending Job: Next Run: nothing Enable: N, but  the job is set enable on the SLX Server ?

I'm also in contact with Sage support, they installed the new VM with the SyncServer. We had alsmost a Day Remote Session after the installation. They have noe idea whats going on. Actually the autom. Sync is doing nothing.

If u want I can sent u pictures from the settings via mail?

I suspect the issue is still the registry/permissions.

If the ServiceFilePath points to a folder that is held in a remote location - then the service *cannot* access it (it does not have access to network resources when running as a service). The fact YOU can access is irrelevant - as you have a user context. As a service, it has a service context (local system only by default) and will not be able to access files held on the network share.

Bring that file locally e.g. c:\tmp and re-arrange registry and service file location so that it can be found on the new VM local machine.

OR

Go into services and find the SLX Sync Server and set the Logon As to a specific user or a the Network/System service.

It's working with a special SLXSyncServer Serviceaccount.

Thanks for your Help Mike

Good news! Suspected the latter option was simpler to do !

Although, if the intention is to move sync server from one place to another (i.e. what you are describing you are doing) then probably best to ensure that nothing points to the old sync server. The moment this disappears then you'll get further issues. But, I think the file is pointing to your main sync folder though so you should be fine.

Yes thats true, Thats wy I called Sage support to intsall an configure everything. Next time I ask first here ans save a lot of time and trouble.

No problem. I'll just send you our business bank account details and drop you an invoice

well u know what, we have Sync problems since Sep. 2011. It crashed. Sage wasn't able to fix it. So I'm sure I would get better support from here/you than Sage support and pay the bill to someone who knows whats going on.

Really? It crashed how (error etc) - and what's the issue with it starting up (in other words, what couldn't they fix?)

In one word -  nothing.

We send them a hole Backup of our SLX Server with all Sync file, Remote DB's everything. They told us they would look at it. But i think they never did realy. We found out that one Remote had some faliure attachments somehow. Sage told us to create a new DB for this Remote user. It helpd maybe 2 hours after that serveral other Remotes crashed the Sync. The sync wasn't able to handle the sync file anymore. We coulnd't even open the SLX Sync.exe, somehow there was already a session open. so we killed it and opend the Sync over the command line....etc

At least we don't know 100% what coused the crash.

After one Year they send us an Consultend. He installed the Sync Server on our TestVM ans it worked fine. When i called Sage to install the System on our Live VM it didn't work untill u told me to create this special user.

Right. If the server crashes you cannot reset this (not even a reboot cures it). What you needed to have done (fairly simply when you know how!) is to run syncserver with the /reset option. If you look in syncserver.chm (the help file) you will see this:

/reset

Use ONLY if Sync Server crashes while running and another instance cannot begin. This resets the Synchronization Server.

This resets it internally - allowing it to run again.

Here's a list of all command lines for syncserver.exe (syncclient has cmd line options too - also detailed in help file)

Sync Server Command Line Options

Sync Server Command Line Options
The following parameters can be used to schedule the Synchronization Server and Synchronization Client through the Run command or by using a third party scheduling program. Schedulers, such as WinAT that comes with Windows NT 4.0, System Agent from Microsoft Plus!, or Task Scheduler included with Internet Explorer, use command line options to start the synchronization cycle. A scheduling program with command line options allows the Sync Server to close at the end of a cycle.

To run the Sync Server via command line, you must specify the /B"alias name" and /C parameters. Both the /B and /C parameters are required as the minimum configuration setting.

Parameter
 Default
 Description
 
/A
 True
 Applies changes from remotes and processes network transactions.
 
/B
 "alias name"
 SalesLogix must be used in the command line to set the database alias. This setting is not saved in the registry.
 
/C
 False
 Must be included in a command line to run a custom schedule.
 
/D
 1800(30 min)
 Use with the /I (iterations) parameter to specify the delay time (in seconds) between iterations.
 
/E
 False
 Runs everything. Sends all changes, applies all changes, and runs subscription.
 
/G
 True
 Runs any pending agents at the end of synchronization.
 
/I
 1
 Number of times (iterations) to perform this operation.
 
/L
 False
 Forces the creation of the Server Logs log files.
 
/Q
 True
 Queues synchronization if it detects another instance running.
 
/R
 False
 Runs subscription rules and sends new accounts.
 
/reset
 
 Use ONLY if Sync Server crashes while running and another instance cannot begin. This resets the Synchronization Server.
 
/S
 True
 Sends database changes to remotes.
 
/SF
 
 Used to read the appropriate job from the SyncServiceFile.
 
/SV
 
 Runs Synchronization Server from a service.
 
/TD
 
 Transfer files down from the profile path (usually selected with the Apply parameter).
 
/TU
 
 Transfer files up to the profile path (usually selected with the Send or Subscription parameters).
 
/W
 Wait until time.
 Hold synchronization until a specific time. Set as HHMM in military fashion.
 
/Y
 False
 revent Sync Server from closing until all agents have finished.
 
 

Thanks for all your help Mike.