SQL Server 2000 Backup Job Issue

One of our old production servers running SQL 2000 enterprise edition(SP4) suddenly stopped performing backups on 4/1/2010. When I manually start the jobs they do create backup files but the job never ends. It has to be manually stopped. No errors are evident in the SQL error log or in the job history. Also, when I create a new job by creating a new maintenance plan and then run the job, it does not create any backup files and never completes. Suggestions on troubleshooting and/or resolving the issue will be greatly appreciated. Thank you.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee SavidgeCommented:
Besides the obvious answer of upgrading to a SQL version that is not 10 years old, how big is the database? What OS is it running? What changed on or around that date?


Is there any date/time change done on the server? Is there any major change or patch installation done on the server?
rjthomps123Author Commented:
IT guys say no updates done on the server recently, e.g. 30 days. I found another old server running SQL 2000(SP4) where the jobs stopped running on the same date. Both servers are runnning Windows 2003 server(SP2).  Two other SQL 2000 servers running in a different domain are not effected. I also found that only the jobs created by Database Maintenance Plans are effected. Other jobs seem to run ok. Also, the rebuild index and integrity check jobs created through a Database Maintenance Plan work as well. It appears to be isolated to only the actual backup jobs created through Database Maintenance Plans. It seems like a probelm with some update or patch that was applied to these two servers. I am a programmer and not part of the IT group that does the updates. The IT guys say the last updates/patches were done a month or more ago. How can I tell what patches were applied that could have effected SQL? All the SQL servers are on the same version:   8.00.2055(SP4). My experience has been that an applied update would show a different version number. How can I troubleshoot this issue? Is there a way to tell what patches have been applied? Could Windows 2003 server patches be the source of the problem?
rjthomps123Author Commented:
I found that if I log in as 'sa' then I am able to create and run Maintenance Plans as well as run existing jobs created by a maintenance plan. If this were an update problem then changing my login would not affect the issue. My conclusion is that our normal sysadmin logins which are windows logins were somehow changed so that they no longer had the necessary permission to execute Maintenance Plans.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.