Hello, We have just recently installed our application on a windows 2008 server. My client connects to the server using dcom. On this server only (so far) we get errors saying that we can't find the server. This message is basically a catch all. I have setup a wireshark trace and captured the message using the protocol ISystemActivator with the information stating "RemoteCreateInstance response" . In looking at the message i see an HResult:Unknown (0x80004027) message. I believe that the error messagge is "The component or application containing the component has been disabled". This message is sent from my server IP to the requesting PC. I am not sure what or where I need to make a change to enable it. I have gone through the settings that I know for DCOM. I would appreciate any information you can provide. Thanks. Sunny asked 26 Jul '11, 14:56  sunnystrain |
One Answer:
When I added the Application Server role corrected my issue. The other issue that I said about the HResults error was a different issue isolated to one user. Thanks answered 27 Jul '11, 12:30 sunnystrain |
Have you tried Googling for
dcom "The component or application containing the component has been disabled" ?
I see a number of hits....
I found part of the problem. When windows 2008 was installed they did not add the application server role and install com+ and dtc. I have atleast changed my error. now i am getting Malformed packet (exception occurred)
In Wireshark ? If so: "malformed" is Wireshark's opinion and doesn't necessarily mean there's an actual problem.
The real question: what error message (if any) are you getting from your client ?
Hi Bill, Yes it was in Wireshark that i found the error. What my client gets is an HResults error: (0x800706ba) which I believe is "The RPC server is unavailable." I am trying to see if I have missed another setting in Windows 2008. I have checked and the RPC services is running. Thanks for your help.
My suggestion: :)
First focus on the client error messages rather than Wireshark dissection.
For example: Wireshark showing "malformed" is much more likely to be some Wireshark issue with respect to the capture/decode (rather than an actual protocol error) when looking at a "standard" protocol.