DCOM 10009

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

DCOM 10009

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> DCOM 10009

Page: [1]

Message

<< Older Topic Newer Topic >>

DCOM 10009 - 11/21/2008 1:33:25 PM

rsharp2124

Posts: 5
Score: 0
Joined: 3/28/2008
Status: offline

I'm periodically get DCOM errors on my SMS 2003 SP3 site server. I get a chunk of about 20 every other day of the below errors in the system logs. It seems like all information on the internet point to the Client Health Tool, which I do not have installed. Can anyone provide any insight it to some other potential causes of this?

DCOM was unable to communicate with the computer XXXXXXX using any of the configured protocols.

Post #: 1

RE: DCOM 10009 - 11/22/2008 12:35:42 AM

SMSExpert

Posts: 193
Score: 39
Joined: 10/28/2008
Status: offline

Cause: DCOM is not configured to allow remote access

It might be failing due to DCOM being configured in a manner that doesn't allow remote applications to run. You must have DCOM configued (on the remote computer that is being accessed) to allow remote launch and remote activation.

Thanks.

(in reply to rsharp2124)

Post #: 2

RE: DCOM 10009 - 11/22/2008 12:40:28 AM

SMSExpert

Posts: 193
Score: 39
Joined: 10/28/2008
Status: offline

Workaround:
Type the command in command prompt:
c:> dcomcnfg.exe
Then:
Click Component Services
Click Computers
Right-click My Computer
Properties
Click on the Default Properties tab
Check "Enable Distributed COM on this computer"
Default Authentication Level: Connect
Default Impersonation Level: Identify
Next:
Click on COM Security tab
Click Edit Limits under "Launch and Acitvate Permissions"
Make sure Remote Launch and Activation permissions are enabled for the Username you are using
Verify that the username (and group) you are using to access the remote machine have both local and remote (activation and launch) capabilities enabled (all 4 boxes should be checked). If DCOM is what is causing the problem, you will typically get an "Authentication Error" from the WMIC command above. If you are getting an "RPC Server Unavailable" error, it is likely that a firewall is blocking access completely.

Thanks.

(in reply to SMSExpert)

Post #: 3

RE: DCOM 10009 - 11/22/2008 12:42:05 AM

SMSExpert

Posts: 193
Score: 39
Joined: 10/28/2008
Status: offline

Hi,
On the remote computer (the one that cannot be accessed), type in a cmd window the following:
c:> netsh firewall set service REMOTEADMIN enable

Thanks.

(in reply to SMSExpert)

Post #: 4

RE: DCOM 10009 - 11/22/2008 12:46:42 AM

SMSExpert

Posts: 193
Score: 39
Joined: 10/28/2008
Status: offline

Hi,

Pls refer to below Microsoft KB Article-
http://support.microsoft.com/default.aspx?scid=kb;en-us;245197

Thanks.

(in reply to SMSExpert)

Post #: 5

RE: DCOM 10009 - 11/24/2008 11:56:23 AM

rsharp2124

Posts: 5
Score: 0
Joined: 3/28/2008
Status: offline

Thanks for the info I will give it a try.