>I am running into problems when trying to get a command script to run as a
>scheduled service on ADSM for NT with the SQL Agent. I can get the Central
>Scheduler Service to run normally, but when I try to switch the schedule to
>run as a "Command" the Central Scheduler service starts then ends
>immediately without running the command script.  I can run the command
>script from a DOS prompt and it works fine. My NT service account has Admin
>rights and rights to run as a service.   I have the correct path set in the
>schedules "Action" location, and I have set the "Object" to the path where
>the command script is located.  But for some reason it doesn't launch
>automatically.  I have a hunch I can't see the forest through the trees!
If
>you have any suggestions or need more info, please let me know.
>
>Randy Fenrick
>Network Specialist and All Around Good Guy
>Lab Safety Supply
>r.fenrick@labsafety
>