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,
spinewrAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

barnesd1Commented:
I take it these components are Activex DLLs.  They need to be registered with regsvr32 c:\windows\system32\mydll.dll.  They also need to be setup in component services.  An example of doing this is at http://msdn.microsoft.com/en-us/library/ms878113(EXCHG.65).aspx.  You should also check what user this component needs to run under - compare this with the working servers.  How this helps.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
spinewrAuthor Commented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.