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.

(T0232) Running ServiceLedger as a Windows Service (NT Service)

Would you like to...

Print this page
Email this to a friend

While running web applications, call centers, and other forms of automation through ServiceLedger, you must normally run ServiceLedger by logging into a computer, running the application, then locking the desktop. This is undesirable in some scenarios. For some skilled users, the preferred method is to run ServiceLedger as a service. A Windows Service runs without any user intervention during startup. Further, no user must log into the system to initiate the automation controller (the application).

There are several caveats to running ServiceLedger as a service:

  • You cannot run the updater while the service is running, you must stop the service to do so. After any update, you must launch the application manually and accept updated files. If you do not do this, the automation controller will appear unresponsive, as if it was not there.
  • You must provide windows login credentials to launch ServiceLedger, you cannot in most cases use the System account.
  • You must have a user created in ServiceLedger with a known password to log into the application. (We use Admin/password in these instructions)

To run ServiceLedger as a service, you must download the relevant "Resource Kit" from Microsoft for your operating system. Please be aware that Microsoft charges for the resource kit on some of the operating systems (home, professional), and provides it freely for others (usually the Server class OS). Once you have acquired the resource kit for your operating system, and installed to the default directory (note: there is more to install than simply unpacking it; you must run a setup program), please follow these instructions to set up your service:

1) Go to Start->Run and type (cut and paste recommended and it is 1 line):
"C:\Program Files\Resource Kit\INSTSRV.EXE" "ServiceLedger Automation" "C:\Program Files\Resource Kit\SRVANY.EXE"

2) Launch ServiceLedger from your desktop and log into the application using your known Admin and Admin password. BE SURE TO ALLOW IT TO UPDATE IF PROMPTED FOR UPDATED FILES.

3) Download the following file and save it to your desktop.

4) If you have modified the admin password in ServiceLedger, please replace the -password password with -password <your_password> using notepad to edit the registry file. If the Admin password is still password, and you accept defaults for other things such as -tpassword, -aport for web application then you may use the file unaltered.

5) Double click the file on your desktop and allow it to import into your registry

6) Go to Start->Run

7) Type services.msc

8) Click run or ok

9) Locate the ServiceLedger Automation service

10) Right click the entry, and select properties

11) Select Logon

12) Select "This Account"

13) Enter in the windows user and password ServiceLedger should run as, please note this is not the Admin account in ServiceLedger.

14) Please enter in your password again in confirm password

15) Click OK.

16) Right click ServiceLedger Automation

17) Select Start

Please note you must shut down this service before updating, if you do not, you will receive errors stating "Could not write ServiceLedger.exe"

Related Questions:


No attachments were found.

ServiceLedger KnowledgeBase Copyright © 2020
Powered by AcitveKB Knowledgebase Software