|
|
| Title |
Error 1053: The service did not respond to the start or
control request in a timely fashion |
| Date Updated |
03/24/2006 |
| Versions affected |
Automize 5.x+ |
| OS affected |
Windows |
| Description |
When starting the automize service, User
gets the message:
Could not start automize on the Local Computer, and/or Error 1053: The service did not respond to the start or control request
in a timely fashion |
| Causes |
1) Depending on your system setup, you may
not be able to run the service under Local System or another user
account.
2) On some system setups, it may be required that the Path variable
include the Automize folderWe have tested the service to run under the following
accounts:
* Current user (should have admin privileges)
* Local System (DO NOT select Interact with desktop)
* Administrator or other User account with administrator privileges |
| Solution
|
1) Logon and Start the service using the current
windows user account. You should have administrator privileges.
Remember to enter your user name / password in the Services / Automize / Log On tab and hit apply.
2) If you need to start the service using another user account, make
sure that the other user account has administrator privileges.
3) For starting the service with other user accounts, on some systems
you may have to add the
following entry to the users Path variable:
C:\Program Files\Automize\
i.e. your Automize installation folder. The installation software
automatically adds this Path variable for the windows user that
installed the NT service module)Users Path Variable can be set via - Start Menu / Control Panel / System /
Advanced tab / Environment Variables / User Variables. If the
variable 'Path' does not exist add it here.
Ex: C:\Program Files\Automize\
If the variable 'Path' exists, add the Automize install folder to the
end.
Ex: C:\Program Files\Common Files\InstallShield\;C:\Program Files\Automize\
4) For starting the service with other user accounts, or other user
accounts on a new NT domain, you may have to
* Stop the service from the service control manager
* Remove the service using the Automize NT service module (Service Menu)
* Uninstall the NT service module from control panel
* Log out and log back in as the other user
* Reinstall the NT service module and try again
|
| Output Log |
- |
| Debug Log |
|
|
|