Setup:
Windows 2003 R2 64 Bit (SP2 and all recent windows update patches)
SQL 2005 Standard 64 Bit SP2 + Cumulative updates (current build 9.0.3054)

When the server was originally built (just weeks ago), there were 3
maintenance plans created and seemed to be working fine. Now trying to edit
the maintenance plans or create a new maintenance plan we receive the
following errors:

Error 1: Title “Microsoft SQL Server Management Studio�, body of error
“Value cannot be null. Parameter name: component (System.Design)�

Then hitting Ok on that we get a second error: “Microsoft SQL Management
Studio is unable to load this document: the LoadFromSQLServer method has
encountered OLE DB error code 0x80004005 (Communication link failure). The
SQL statement was issued has failed.�

We have done this test from remote workstations plus running the management
studio right from the server itself. We have confirmed that SP2 and update
patches all installed successfully and that the client tools are the up to
date along with the server build. We have double checked all protocol
settings and all settings remain the default setting.

I have found a couple posts on Google discussing this, but no one appears to
have received a final answer to the issue yet that I can find.
Any assistance would be greatly appreciated! Thx!

Ross

Are you gettings error, when you are logged onto the Box or from your
client.
is it possible this SQL Server is engaged in Multi Server
Administation and is either a MASTER or TARGET.
Well, you should have applied Cumulative updates if it were absolute
necessary and you have a typical issue as documented in the
cumulatives updates.

Thx for the post Maninder.

Yes, as stated in the original post, we get the errors regardless if we are
on the box or working on it remotely with a workstation. As for master /
target, we don't have anything like that setup on this server. Its a isolated
box.

As for your "Cumulative updates" comment, I totally agree. Unfortunately, we
(my DBA team) were not involved with the building of the SQL server, we were
just brought in after the original builders had it built and it was already
broken... :-) We are now engaged in attempting to resolve the issue after the
fact.

Thx again!

Ross

"Maninder" wrote:

> Are you gettings error, when you are logged onto the Box or from your
> client.
> is it possible this SQL Server is engaged in Multi Server
> Administation and is either a MASTER or TARGET.
> Well, you should have applied Cumulative updates if it were absolute
> necessary and you have a typical issue as documented in the
> cumulatives updates.
>

try this for now and let me know if this works.
regsvr32 msxml6.dll
regsvr32 msxml3.dll
run this in the RUN box or CMD window,

Both reported "DllRegisterServer in msxml3.dll succeeded" &
"DllRegisterServer in msxml6.dll succeeded".

I tested the editing of the plan again and same errors as before as well.

"Maninder" wrote:

> try this for now and let me know if this works.
> regsvr32 msxml6.dll
> regsvr32 msxml3.dll
> run this in the RUN box or CMD window,
>

Ok last resort is the redo Management Studio.
Reinstall Management Studio and that should Fix your Problems.(Client
Tools)

Can I ask where this report came from?

My hesitation is this "redo suggestion" is that it seems highly unlikely
that this would actually resolve this issue since we would need to reinstall
every Management studio in our environment since we have tried this from both
the server and from various workstations remotely and all in all cases, we
can recreate the issue. It seems very much server side, not client side.

Thx!

"Maninder" wrote:

> Ok last resort is the redo Management Studio.
> Reinstall Management Studio and that should Fix your Problems.(Client
> Tools)
>

Yes My Ignorance, I was counting only one Box and one Direct
connection.
Another approach: Are toy trying to connect as SA or using your Local
admin rights.
try to Login as Local Admin on the Box and Try again saving your
Maintenance Plan.

one more thing, did you restart your Server after you registered the
DLL's.

Question: do you have SSIS installed on the SQL instance as well.
It seems SSIS is required and enabled for the Maintenance Plans to be
Created/Edited.

if none of those things work above, here is one more catcher.

Login to SQL Server as 'sa' and with a server name of '.'