Actually, I've found that if you look up the executable name in the registry and use that instead, it works fine. For example, to start the "World Wide Web Publishing Service", I just start "ww3svc.exe" and it works fine. However, I agree that support for the service names with spaces should be included. This is just my workaround. : L.s. : On 12/8/2000 Shojaee asked a question about starting and stopping NT : services. The sollutions SysOp gave didn't work. The only thing that : worked is renaming the service you want to start and stop, to a name : without spaces. This has to be done in the registry. : I have the same problem Shojaee has and it is true that 24 X 7 will not stop : a service if there are any spaces in the name of that service. : For example. I want to stop and start exchange services. This has to be done : to be able to automatically delete the exchange log files. One of the 9 : services that must be stopped is "Microsoft Exchange System : Attendant". 24 x 7 won't stop this service and will give you the : error saying that there are not enough permissions or invalid service : name. When I rename the service name in the registry of NT to : "MicrosoftExchangeSystemAttendant" and run the job again, it : stops the service. : When looking at examples for stopping and starting services, all services in : the examples have names without spaces! : Same thing for starting services. : I think this is a bug in 24 x 7 scheduler. Will this be solved soon? It isn't : a verry good idea to rename your services in the registry, because a lot : of help pages (eg MS Technet) rever to the standard names of the services, : not to the names you've entered in the registry. : Please take some time to solve the problem. When this option will work : properly in 24 x 7 scheduler, there will be a lot more happy : systemengineers all over the world. It gives us a lot more possibility's! : Thank you for your attention! : Kind regards, : Martijn de Lange
|