June 14, 2010 at 9:57 pm
Hi,
I am running SQL 2005 SP2 on a server (production.) The Operating System is Windows 2003 SP 2. I have set up Maintenance plans to take a full backup of all databases and also to take a backup of the transaction log for certain selected databases.
My problem is that the maintenance plans start but never end. They appear to freeze. The jobs are shown to be running in the job activity monitor but though they run for several days, they don't provide a result. Manual backup of both the database and the transaction log happens without a fault.
One clue is that when I try to edit the maintenance plan, the connection field is grayed out and if I try to add a new connection, then I get the following error:
"Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.
Object reference not set to an instance of an object."
I have several other servers operating under the same specifications that work just fine. The only difference in this case is that SP2 was installed after the server became in production as opposed to the others where SP2 was installed before the server went into production.
How can I get my maintenance plans to work in this server? Any assistance would be appreciated. Thanks in advance.
sarma
June 20, 2010 at 2:58 pm
One additional piece of information. This server was renamed after SQL 2005 was installed. I then dropped the sql server and recreated it using the following commands
sp_dropserver <old_name>
GO
sp_addserver <new_name>, local
GO
Could this be related to this issue. However, before upgrading to SP2 (Done some time after renaming) the backup jobs were running smoothly even after renaming the server.
Any help on this would be appreciated. I have tried google and am not yet able to find a solution.
Sudarshan.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply