Hi,

We have 4 workstations that connect to remote SQL servers (2000 & 2005)
using SQL Server Management Studio 2005. Whenever we first launch SQL
Management Studio, it will hang for 5 - 10 secs. Additionally, sometimes
when connecting to a different registered server, it will hang again for 5 -
10 secs.

Checking the logs on these workstations, each machine will have around 30
System entries like so...

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

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10009
Date: 18/06/2007
Time: 10:08:11 AM
User: ***\***
Computer: ******
Description:
DCOM was unable to communicate with the computer [**registered SQL server**]
using any of the configured protocols.

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

The connections will always work after these delays, but I would like to
correct this issue so that there is no delay.

I have checked DCOM Config using dcomcnfg, and I believe that each
workstation has the default settings for Default Protocols >

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

Connection-oriented TCP/IP (no port range specified)
Connection-oriented SPX

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

All of the registered servers in SQL Management Studio are configured to use
TCP/IP as the network protocol under Connection Properties.

Our client firewalls have exceptions configured as per this article,
http://support.microsoft.com/kb/287932. Disabling client firewalls does not
correct the DCOM errors either.

If anyone could shed some light on this issue it would be greatly
appreciated.

Thx,
EightBall.

It can be several different things. Check the following list
of possible causes, resolutions:
http://www.eventid.net/display.asp?e...DCOM& phase=1

-Sue

On Mon, 18 Jun 2007 11:16:02 +1000, "EightBall"
<dontbother (AT) withthisone (DOT) com> wrote:

Thanks for the reply Sue, one of those entries was similar...

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

The culprit, in my case, was Microsoft SQL Server Management Studio. Any
registration of an unreachable SQL Server (in my Registered Servers)
produced two of these events on startup. Deleted the dead server
registrations and have had no occurrences of this event since.

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

....however it didn't apply to my case. All of our registered servers in SQL
Management Studio are accurate and can connect ok.

The error is definitely related to SQL Man. Stu., as these DCOM errors never
appear when that software is not being used.

Not sure if it's worth mentioning, but sometimes there are 5 different
server registrations pointing to the one server. Each one having different
login credentials, and connecting to a different database on that server.

Any other feedback would be greatly appreciated.

Regards,
EightBall.

"Sue Hoegemeier" <Sue_H (AT) nomail (DOT) please> wrote