Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Service created with Wise Express times-out on start

Updated: 31 Aug 2010 | 2 comments
dlowerymcse's picture
0 0 Votes
Login to vote

Every service I create with Wise installation Express starts then stops with an "Error 1053: The service did not respond to the start control or request in a timely fashion." 

As a test, I built a simpler msi that only installs a service that starts calc.exe.  The service does start, and the calculator runs but then the service stops immediately throwing the timeout error.
I tested this on multiple computers with differing Operating systems(XP, Win 7) with the same result.

Surely there is a simple flag or setting that I am missing.

Comments

EdT's picture
09
Feb
2010
0 Votes 0
Login to vote

Need more information

1. How are you defining the service?  If you can take us through the steps you are using to create your "simpler" MSI then perhaps we can spot what is wrong. Or you can attach your simpler MSI to your original posting as a ZIPPED file.
2. Are you setting the service to run in system context or as a specific user?
3. Have you looked at the service parameters using the MMC to see how it has been set up?
4. Have you tried creating the same service manually, and checked that this works OK?

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

dlowerymcse's picture
26
Feb
2010
0 Votes 0
Login to vote

Service timeout issue post update


Attached to the original post is an example test MSI I created to start the actual exe I want to run as a service

I set the service to run in the system context. Ultimately i plan to run this at boot automatically but for testing I have it set to run manual

In services.msc it is set up just as I defined it and looks OK

The only way I am currently capable of creating a service manually is to use the srvany  process from the Windows Server toolkit.  I have used this method and my executable runs fine.