Unsolved
This post is more than 5 years old
26 Posts
0
17287
August 10th, 2003 18:00
DCOM error at each boot after Installing Dell Server Administrato 1.4.0 A03
Hi,
After installed Dell Server Administrator 1.4.0 A03 on my Windows 2000 Server SP4, I receive this error each time I reboot my server. The server is a Dell PowerEdge 2650 with A13 Bios and ESM 2.23.
Error in SYSTEM Log:
Source: DCOM
Event ID : 10010
The server {9B9A80E0-A9C0-11D2-B5E1-006008187232} did not register with DCOM within the required timeout.
After researching the key 9B9A80E0-A9C0-11D2-B5E1-006008187232 in the registry, I found the dcom service: VxVmCmd Command Line Server. This service is for Dell Array Manager. I run the version 3.4.0 of Array Manager installed by Dell Server Administrator 1.4.0.
In the dcomcnfg.exe and registry tool, all permisisons are set correctly.
I have only one server on 4 with this error. All server are the same Windows 2000 version and the hardware is the same including BIOS.
When I remove the Dell Server Administrator 1.4.0 A03, this error is removed. How I can solve this problem ?
Thanks,
Steve
lewisyu
7 Posts
0
September 7th, 2003 05:00
Just want to add a "same here"...
OM Server Administrator 1.4 A03 and 1.5 A00. PE1650/2500/2650/PV750 with latest BIOS/ESM and 3Di firmware.
I found the error is related to the VxCmd (the Array Manager) services.
I have checked with dcomcnfg and removed SPX/IPX protocols. No luck...
Both "NT Authority/INTERACTIVE" and "NT Authority/Authenticated Users" are in the "Users" group....
Hope Dell can solve it soon.
mnh966
2 Posts
0
September 19th, 2003 07:00
Another "Same here"
In my case, I suspect the combination with CA Brightstore (formerly ArcServe) causes the problems.
Once I removed it on one server, everything worked fine. CA uses an RPC portmapper, just as OpenManage, and if this one starts before the OpenManage portmapper, the OpenManage version hangs on starting.
I tried building in a dependency, but this only solved the portmapper startup. Array Manager still doesn't work.
What's extra frustrating, is that while troubleshooting this issue, the server spontaneously rebooted a couple of times.
A solution would be very welcome!
DELL-SeanC
99 Posts
0
September 29th, 2003 12:00
The error message is generated by an array manager manager component (command line interface) on startup of that program.
Array manger works as normal.
I expect the fix will be incorporated with the next array manager 3.5 release.
In the meantime you can safely ignore that particular message.
mnh966
2 Posts
0
September 30th, 2003 04:00
I would love to ignore it, except in my case, it means that Array Manager won't start.
Regards,
Maurice Heine
tnetjpm
37 Posts
0
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 SPX/Netbeui/SPX) then it should be safe to remove all protocols other than "Connection-oriented TCP/IP".