asked on

DCOM Component failure "Class not registered"

How do I ensure a COM component is registered for use? Are there any checks we can make to ensure it? This error is coming from a vendor product which uses DCOM to communicate to a backend system. We have other servers which are working fine, but we have two servers which are not. Checking the configurations on dcomcnfg.exe has resulted in the same settings for both the working and non-working systems. If I use a working system and connect to the backend of the non-working system - it also works so it points directly to the non-working servers. Any help would be great!
PS: The two servers in question have been recently rebuilt using standard scripts.
I would like to request since I haven't received any responses to this query if anyone knows of any tools for DCOM based sniffing or a known network tool and how to identify the communications for DCOM within it. Wish I could raise the points but it is at the max.
Thanks, In Advance,

ASKER CERTIFIED SOLUTION

barnesd1

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

spinewr

ASKER

Thanks Barnesd1, you are the first to at least review the question. I actually have Microsoft working on the problem wth us now. We have tested SQL connectivity using a test UDL flle, ODBC connectivity using SQL and done a trace in ODBC which is not giving us much information. I will accept your answer because it is now a vendor problem. The UDL file and ODBC connecitivity tests are working and the connect string from the application is throwing an SSL error (which the company swears they have not done any SSL implementation. We are next going with a NetMon trace to see if that gives us more information.

DCOM Component failure &quot;Class not registered&quot;

DCOM Component failure "Class not registered"