The name of the service is not important. Here is the most likely cause of that problem: You cannot start a service if it depends on some other service and that service is not running. So first you must call ServiceStart for that service and then call ServiceStart for the main servcie. : I'm running Windows NT 4.0 with SP3 and 24x7 v2.4.1. I need to start/stop a : Windows NT service and I created a simple job with only one JAL statement : for test. This is the statement: ServiceStart : "WorldgroupServer". When I tried to run it with Run Now option, : I got an error message: "Error starting service. Not enough : permissions or invalid service name". The actual name of this service : is "Worldgroup Server" and I tried it (with a space between two : words of the service name) but I got that error message again. I tried to : run a service with only one word name (called "MDaemon") and it : started successfully, so I think there's a problem starting services which : have more than one word in their name. : Am I right, and if yes, what can I do? : Shojaee : P.S: I logged on to server as Administrator so I have full access to any : resources. Also, the "Worldgroup Server" service startup setting : is "Manual", the "Log On As" option is set to : "System Account" and the "Allow Service to Interact with : Desktop" option is not checked.
|