January 24, 2005 at 5:23 pm
Over 3 years ago I wrote a VBscript that runs as a job under SQL Server 2000. In the last week it has stopped working. The "view history" option shows no runs for the job -- it simply doesn't run. The Windows Event log shows no problems either. When I log in as Admin, I can successfully run the job (right-click in EM and "Start Job") and it works fine. I recreated the job but the new job displays the same problem. (Oh, yes. the SqlAgent is running on that box, the job is enabled, and the nightly backup, run from the same box, starts just fine.)
Any ideas what else to look for?
TIA,
Bill
January 25, 2005 at 1:20 am
- Is the schedule active ?
- who is job-owner ? (and is cmdshell open for non-sysadms (don't if not explicitly needed ! ) ?
- does the sqlagent service account have the needed auth. for the vbs ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
February 1, 2005 at 9:08 pm
What does it show under "Next Run Date" ??
Sometimes I've had the job enabled, but the schedule was not enabled. They both must be enabled.
Perhaps there's an "end date" in the schedule ?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply