How to Troubleshoot DLL that will not Register on VM Server

Hello all,

We are trying to move our In-Proc COM Server DLL written in TD 5.2 from our old server to a new VM server and I cannot get the dll to register.

I have tried using regsvr32 in the SysWow directory, even tried moving the dll to the Syswow directory and had no luck.

I have tried installing older versions of the C++ redistributables, and it was still a no go.

I have tried converting it to TD 6.2.  It registers ok on my Windows 8 VM just fine but it will still not register on my VM server.

Does anyone have some good troubleshooting tips they can give me on how to troubleshoot when a dll  will not register?

Next I'm going to try registering a dll with a minimum amount of code in it, just to see if I can get anything to register.

Thanks in advance for any helpful advice you may have to offer,
~AJ
ajthomas12Asked:
Who is Participating?
 
ajthomas12Connect With a Mentor Author Commented:
Hello All,

I was able to fix my problem with registering my dll by using Dependency Walker, http://www.dependencywalker.com/ , to help me identity the modules or other dlls my dll was dependent upon but could not find.

Good luck,
~AJ
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Is the OS of the Server, 2012 ?
0
 
ajthomas12Author Commented:
Yes Andrew,

It's a VM with Server 2012 on it.

I just finished trying to register a stub of a DLL.

It registered on the development VM Windows 8 machine.

The server returned:

"The module failed to load.

Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent.dll files.

The specified module could not be found."

I know my test dll is there.  

How do I check for problems with dependent.dll files?

Thanks,
~AJ
0
 
ajthomas12Author Commented:
Ok, thanks Andrew.

~AJ
0
 
ajthomas12Author Commented:
Because I was creating the dll on one system and then moving it to another, I needed a way to determine definitively what was needed for my dll to register and work properly.  It was eye opening to me to see the number of dlls my simple dll was dependent upon and looking for.  Dependency Walker was exactly what I needed.  I found a link to it in a comment on a message board for someone who was having a similar problem.
0
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.

All Courses

From novice to tech pro — start learning today.