SQL Server Version:

Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)  Dec 10 2010 10:56:29  Copyright (c) 1988-2005 Microsoft Corporation  Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

Issue : Maintenance Plan - DB backup plan & TRN Log backup plan skipped / some times not deleting the old backup files.

Error : Failed to retrieve date for this request (Microsoft.SqlServer.SmoEnum)

Additional Informaiton

An exception occurred while executing a Transact-SQL statement or batch.

(Microsoft.SqlServer.ConnectionInfo)

A Server error occurred on the current command.

The results, if any should be discarded (Microsoft Sql Server)

Any experts can help me to resolve this issue.

Thanks

drmrpush

Hello,

Same issue reported here:

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/601fd83c-c49f-4bf8-b69d-95431197652d/maintenance-plan-is-not-opening-on-sql-server-2005-sp2?forum=sqlkjmanageability

Please check solution on :

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/3e53ba8b-ea23-4629-98db-43c80ba9888e/cannot-save-maintenance-plans?forum=sqltools

This problem occurs if some of the stored procedures while installing SP2 has not been applied successfully. So manually run the script below and it may resolve your issue. It resolved ours and we went throught exact same process of re-installing several times.

                1)       First go to the folder Install . The default location is this = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install .

Please post back still your issue not resolves.

 

2)      Then in this folder find this sysdbupg.sql .

3)      Please open this script with a nodepad.

4)      Then copy the whole script and then paste it in the Query window of the Management studio.

5)      Then execute this script.

6)      Once this script has been successfully executed, The issue should be resolved.

MP is not that reliable specially that of SQL Server 2005. You also cannot complain much because MS has officially put SQL Server 2005 in completely unsupported list.

You can use Ola Hallengen solution for backup it works quite well it would take database backup and would make sure backup is deleted after days specified. Do read FAQ section before proceeding.

I got the below error message - in the mid of the job running.

TITLE: Microsoft.SqlServer.ConnectionInfo

------------------------------

An exception occurred while executing a Transact-SQL statement or batch.

------------------------------

ADDITIONAL INFORMATION:

A severe error occurred on the current command.  The results, if any, should be discarded. (Microsoft SQL Server, Error: 0)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.5000&EvtSrc=MSSQLServer&EvtID=0&LinkId=20476

------------------------------

BUTTONS:

OK

The issue still persists:

The db backup plan skipped

errorlog

Msg 22004, Level 16, State 1, Line 0
Failed to open loopback connection. Please see event log for more information.
Msg 22004, Level 16, State 1, Line 0
error log location not found
 

@ event log

 298] SQLServer Error: 10060, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]

Experts - suggest please

The issue still persists:

The db backup plan skipped

errorlog

Msg 22004, Level 16, State 1, Line 0
Failed to open loopback connection. Please see event log for more information.
Msg 22004, Level 16, State 1, Line 0
error log location not found
 

@ event log

 298] SQLServer Error: 10060, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]

Hi MRVSFLY,

Based on my research, the above error could occur because either the firewall on the server has refused the connection or the server is not configured to accept remote connections. Please use one of the following actions to troubleshoot this issue.

Make sure that you have configured the firewall on server instance of SQL Server to accept connections.
Use the SQL Server Surface Area Configuration tool to allow SQL Server to accept remote connections.

There are some related articles for your reference.
MSSQLSERVER_10060
SQL Server Error: 10060 \ SQL Server Error: 10061
Resolving could not open a connection to SQL Server errors



Thanks,
Lydia Zhang