Depending on which version of ServiceLedger you use, you should use different directions for updating ServiceLedger to the latest version.

• If you use ServiceLedger 6.0 or earlier, please see (T0160) How do I use the Updater to update ServiceLedger?
• If you use ServiceLedger 2007 or later, please see below.

If you use ServiceLedger 2007 or later, you will generally use the Database Maintenance tab of the Administration window to update ServiceLedger.

Overview of the Update Process

In general, the update process involves the following steps:

1. You follow the steps below to run the update on your server.
2. The next time each workstation logs in, it notices that new files have been downloaded and prompts you to get the latest files from your server.

The only time your computer makes contact with ServiceLedger's download server is during the first step. The second step will happen once for each workstation you have, and occurs entirely within your network.

To run the update (you should only perform these steps on your server):

1. Close ServiceLedger on all computers on your network
2. Double-check to make sure ServiceLedger is not running on this computer
   1. If you are running an automation server (a copy of ServiceLedger running in Server Mode), you should shut it down or stop the service at this point.
   2. If you are using Terminal Server or Windows Server 2003, you should use the Task Manager's processes tab, along with the "Show processes from all users" checkbox, to verify that no one else is running ServiceLedger on this machine
3. Run ServiceLedger and log in (if necessary) as the Administrator
4. Open the Administration window and click on the Database Administration tab
5. Click on the Back up your Database button, change the path if you wish, and click OK. The ServiceLedger Updater will appear and disappear.
6. Click on the Update to the Latest Version button. ServiceLedger will close automatically.
7. Wait while the ServiceLedger Updater performs the update. When finished, the Updater will close automatically.
8. Start ServiceLedger and, when the prompt for updated files appears, click Yes
9. After ServiceLedger and the Updater close, restart your automation server or service if you have one. You may safely log back in to ServiceLedger on other machines now.

At this point, any workstations will notice that you've updated your server and prompt you to get the latest files from your server. All you need to do is click 'Yes' and allow the workstation to get the latest files. Once it has finished doing so, you can open ServiceLedger again.

In some rare cases, a workstation will not get the latest files from the server automatically. If this happens, you may not be able to use ServiceLedger on the workstation due to version conflicts, even though you can run ServiceLedger without any problems on the server. In this situation, you can use the following steps to ensure that the workstation is using the most up-to-date files from your server:

To manually update a workstation: (In general, you do NOT need to do this)

1. Go to Start->(All)Programs->ServiceLedger->Updater
2. Click the Update via Database button
3. When you receive the Update Complete message, close the updater

Scheduling Updates

Updates can be scheduled to run automatically by using the Windows task scheduler. All of the steps described above will still need to be completed when running updates automatically, so it's usually best to put together a batch file that stops your ServiceLedger Automation service, if you use one, and kills any ServiceLedger.exe processes that are currently running; runs the update; and finally restarts the automation service if applicable.

The command line to actually run the update is as follows:

"C:\Program Files\ServiceLedger\ServiceLedger\Updater.exe" -mode AUTO -method INTERNET

Please note that you may need to adjust the path to the updater above. If you use multiple companies and have multiple paths, you will need to run each update separately in its own path.

Note: When setting up any automatic process, it's best to run the same commands manually through a few times to make sure they work.