Unsolved

This post is more than 5 years old

18949

November 24th, 2003 22:00

Event ID 10010 SOURCE: DCOM

Event 10010
SOURCE: DCOM

DESCRIPTION: The server {9B9A80E0-A9C0-11D2-B5E1-006008187232}
did not register with DCOM within the required timeout.

When searching thru my server's registry the GUID (Global Unique Identifier) references
"VxVmCmd Command line Server".

I then ran DCOMCNFG from the command prompt to look at all the applications DCOM was
associated with and found "VxVmCmd Command line Server".  Highlighted that and clicked
on "Properties".  It gave me the message "The operation completed successfully". 
When I hit "Okay", it opened a box "VxVmCmd Command line Server Properties". 
Under the "Location" tab there are two boxes, both unchecked.  I checked the one entitled
"Run application on the computer where the data is located".
(The other one was "Run application on the following computer:" and it gave you a
browse button.  Left that one unchecked.).  Exited out and rebooted. 
Made no difference...still got Event 10010.  Turned it over to Dell Software Support....haven't heard back yet.

Any ideas??

Message Edited by skeeterlogan on 11-24-2003 06:15 PM

37 Posts

November 26th, 2003 17:00

You could try the following :-

Run "dcomcnfg.exe" and click the "Default Protocols" tab.
Remove all of the protocols EXCEPT "Connection-oriented TCP/IP".

NOTE: If other applications on a server require that DCOM use protocols other than TCP/IP, they will no longer function correctly.  If this is the case, the suggested course of action is to leave the DCOM configuration as it is.

If you only have TCP/IP (and not IPX/Netbeui/SPX) then it should be safe to remove all protocols other than "Connection-oriented TCP/IP".

November 28th, 2003 23:00

Found out that the problem is a timing issue between DCOM and Array Manager.  The Event error will occur only once upon boot.  Hopefully it will be corrected when Array Manager 3.5 arrives.  In the meantime, Dell support had me to search the registry for the GUID {9B9A80E0-A9C0-11D2-B5E1-006008187232}.  It should occur only twice.  Delete the key for each instance.  Reboot and Event 10010 is no more.

February 19th, 2004 05:00

I have this showing up four times in my registry - I should delete all four instances of this key?  I'm getting this error steadily now every 31 seconds.  The only change I recently made was adding Backup Exec's 9.1 Advanced File Open Option to the machine.

1 Message

March 3rd, 2004 21:00

I also had four instances of this GUID in my registry.

I deleted all four,. rebooted, and the errors are gone.

March 5th, 2004 16:00

Thanks idratherbe, I ended up nabbing it by installing the latest Array Manager. In its readme file, it mentioned opening up dcomcnfg and removing everything but TCP/IP under "Default Protocols" and that fixed it up for me.  We only use TCP/IP here anyway, so that worked out perfect.

No Events found!

Top