May 3, 2004 at 8:04 am
The other day I noted that one of our SQl 2K Server's refuses to backup its databases at its appointed time. The backup histories were strangely silent about the matter. The event log and sql server logs didn't offer even a hint as to why this was happening. We dump the databases to a local share and there were no files for the time in the dump. So the backup reallt didn't happen. Still the transaction logs were dumping hourly throughout that time period! That server uses a standard Database Maintenance Plan, which I plan to delete and recreate today. It is a Win 2003 Server.
Any idea why this happening?
TIA, Bill
May 3, 2004 at 1:34 pm
Is this through a maintenance plan? Might be hosed up. Check the schedules and be sure everything is enabled.
May 3, 2004 at 8:08 pm
Are you able to run the job associated with the maintenance plan manually?
I would delete the maintenence plan and recreate it. Then go from there.
Cheers,
Angela
May 3, 2004 at 9:38 pm
Are the jobs and Schedule for the job "both" enabled?
May 4, 2004 at 4:47 am
Are the Jobs really ended, or are they running still?
Try stopping and restarting the SQLServerAgent...
Best regards
karl
May 4, 2004 at 5:13 am
May 4, 2004 at 10:12 am
I've had this problem ( but not always with sysmaint.exe plans ) ours is down to excessive handles open on the agent service - check in task manger for the number of open handles.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
May 4, 2004 at 7:10 pm
Thanks to everyone for their replies.
I'm embarassed to tell you what I found out! The sql agent runs under a domain "service account" and, given that auditors visit us often, they enabled pasword aging on all accounts in the domain. In other words, the service account password had expired. Now, I'm using the local System account.
Bill
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply