Error accessing Maintenance Plans

  • When I try to modify or add a Maintenance Plan I get the error:

    "Microsoft SQL Server Management Studio is unable to load this document:

    The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Communication link failure). The SQL statement that was issued has failed.

    In the technical detail it shows:

    Value cannot be null.

    Parameter name: component (System.Design)

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

    Program Location:

    at System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.GetDesigner(IComponent component)

    at Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDesigner(String connectionString, Object connection, String objectUrn)

    at Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()

  • This kind of issue is generally caused by using client tools that are at a lower version than the system you are connecting to.

    Verify the version of the client tools and the version of the server you are accessing. Make sure the client tools are at least the same version - if not a higher version.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • This problem occurs when your network packet size iz above 16k:

    http://support.microsoft.com/kb/2006769

    "To resolve this problem, specify a network packet size that is smaller than 16384 (16K) bytes. You may use the following code to set the network packet size configuration option of the sp_configure system stored procedure:

    [font="Courier New"]EXEC sp_configure 'network packet size', 16383

    RECONFIGURE WITH OVERRIDE

    GO [/font]

    The network packet size can also be altered via the Server Properties page in Object Explorer. Select the Advanced option and type in the new value for Network Packet Size and click OK.

    Note: You do not need to restart SQL Server for the change to be effective. After this setting is changed, all new connections receive the new value."

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply