Some Services won't start...
-
I've lately been having trouble with services (on win2k) if their ImagePath registry entry has spaces in the path and no quotes around the executable name. Even though the Platform SDK stresses that quotes are needed in ImagePath if the executable name / path has spaces, there are even some Visual Studio services that don't follow this rule. The symptom is a cryptic Message Box showing text such as: Could not start the yadda-yadda service on Local Computer. Error 193: %1 is not a valid Win32 application. We have not been able to determine what caused win2k to suddenly require quotes around service paths. I keep up-to-date with WindowsUpdate patches, but we patched a clean machine and this problem did not occur there. Does anybody have any ideas or suggestions? Thanks, Eric T.
-
I've lately been having trouble with services (on win2k) if their ImagePath registry entry has spaces in the path and no quotes around the executable name. Even though the Platform SDK stresses that quotes are needed in ImagePath if the executable name / path has spaces, there are even some Visual Studio services that don't follow this rule. The symptom is a cryptic Message Box showing text such as: Could not start the yadda-yadda service on Local Computer. Error 193: %1 is not a valid Win32 application. We have not been able to determine what caused win2k to suddenly require quotes around service paths. I keep up-to-date with WindowsUpdate patches, but we patched a clean machine and this problem did not occur there. Does anybody have any ideas or suggestions? Thanks, Eric T.
Eric at Cognos wrote: no quotes around the executable name You must have quotes around any paths in the command line in case they might have spaces. If you don't do this, you'll run into trouble. If other services get away with it, it's only luck. ;)
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi