By using this web site, you agree to all terms and conditions for acceptable use.

ServiceLedger KnowledgeBase Knowledgebase Home Page > ServiceLedger > Technical | Contact Us

Search the Knowledge Base Browse by Category

ServiceLedger provides this content as-is for self help support purposes. ServiceLedger assumes no liability for any steps you take based on the directions in our knowledge base, and assumes that you have the knowledge to determine whether a given step is appropriate for your situation. Certain solutions can affect third-party software that ServiceLedger relies on or integrates with; it is your responsibility to consult with the documentation or publishers of such third-party software to understand whether any changes suggested here will have negative effects on other applications.


[D](T0175) How do I run a temporary update code?

Would you like to...

Print this page
Email this to a friend

NOTE: To run a temporary update code, also called a one time custom update, you must be using ServiceLedger 2007 or later. If you use ServiceLedger 6.0 or earlier and have been asked to run a temporary update code, please stop and obtain directions that are appropriate for your version.

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. Type the temporary code you want to run into the Temporary Update Code box.
  7. Click on the Run Custom Update button. ServiceLedger will close automatically.
  8. Wait while the ServiceLedger Updater performs the update. When finished, the Updater will close automatically.
  9. Start ServiceLedger and, when the prompt for updated files appears, click Yes
  10. 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

Related Questions:

Attachments:

No attachments were found.


ServiceLedger KnowledgeBase Copyright © 2019 support.serviceledger.com
Powered by AcitveKB Knowledgebase Software