up vote 0 down vote favorite
share [g+] share [fb]

I want to use an executable-file (which sports only a command-line interface) as a service in Windows 7.

I added it to successfully via:

sc MySVC binPath= "C:\Windows\System32\MyProgram.exe"

but once I try to start it, it times out with an 1053 error.

What am I doing wrong?

link|improve this question
81% accept rate
feedback

3 Answers

up vote 1 down vote accepted

Perhaps you could look at Servify This

Should do what you;re asking for.

link|improve this answer
That does the trick perfectly <3 – Hedge May 29 '11 at 20:06
feedback
up vote 0 down vote

You said "Sports only a command-line interface", this makes no difference what so ever, a service can be run as a command line or a GUI (limits/security depending).

I would personally take a look at the application closer, if it is logging in as a user (service for example) does it have the needed paths and/or are you giving all the necessary calls/arguments in the start?

link|improve this answer
I found out the problem was that Windows didn't get any response from it (it awaits a special response from services). So I had to wrap it with a tool like Servify This which makes the necessary calls for me. – Hedge May 29 '11 at 20:08
feedback
up vote 0 down vote

If the program you're trying to run as a service requires user input, that may be what's causing it to time out. Try executing the program from the command line with the exact same flags and switches you've got the service configured to run with and see what happens. You may need additional flags/switches to make it run without user input whatsoever, or pipe input in from another program/file through a scripted call to the program (batch file, powershell script, etc).

link|improve this answer
It doesn't need user input. – Hedge May 29 '11 at 20:12
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.