thelliez
15th November 2005 20:35 UTC

nsExec and SC.exe syntax problem
I am trying to start the service "Apache Tomcat 4.1" under Windows 2003.

The following worked for services with no spaces in their name, but it fails for Tomcat.

Worked:
nsExec::Exec '"$COMSPEC" /C ("sc" config myService obj= .\$U password= $P)'

Failed:
nsExec::Exec '"$COMSPEC" /C ("sc" config "Apache Tomcat 4.1" obj= .\$U password= $P)'

Any suggestions about this spaces problem?
Thanks,
Thierry

kichik
16th November 2005 18:14 UTC

What are the parenthesis for? Why use $COMSPEC? sc.exe is an executable, not an internal command. If it doesn't work without those two, how about trying one of the other solutions?

thelliez
16th November 2005 19:05 UTC

The COMSPEC might not be needed, but it was an attempt to understand some strange differences between two W2K3 boxes. On one of them $SYSDIR\sc.exe was not found by nsExec, although sc was present in this directory. (I had the same problem with cscript. Sometimes the full path worked, sometimes calling only "sc" or "cscript" worked. I looked at the PATH without finding issues there).

The parenthesis are there to help with too many levels of quotes. Otherwise I would have written something like:

'"$COMSPEC" /C ""sc" config "Apache Tomcat 4.1" obj= .\$U password= $P"'