DllRegisterServer in filename.dll failed. Return Code: 0x80004005

[xp8103]

I am at a loss.

I am setting up an isolated client and server pair to send off to a contractor so that they can duplicate our environment here for a specific piece of software support.

I client is WinXP pro, set up as one of our front line user machines. I was able to properly configure it on our LAN, install the production version of the software from the production server and run it without issue.

The standalone server is Win2k. It has a share on the drive that mimics our production environment. It has a copy of the production software on it. It's name is the same as the production machine. The pertinent drive maps are identical.

The next step is to link up the client and the server and get them talking in their own little world. Done. Created a Workgroup and allowed full control for the user. Shared the network drive that contains the software and mapped it on the client. At this point, from a desktop POV, the client looks just like it is connected via our network to the production server.

Next step is to reinstall the software on the client meaning registering a handful of .dll's and an .ocx or two. We have a script that runs to save typing, works every time it's tried. It is run from the network drive and successful registry entries are confirmed. Except, when I run the script on the attached client, failures abound. The only users set up in the workgroup are identical on both machines and both have full control. On the server, the script run and has no problem registering the dlls on it. I even tried copying one of the dlls from the server directly to the client and registering it from the command line with the same error.

Am at a loss.

 

[linney]

xxxxxx.dll was loaded, but the DllRegisterServer or DllUnregisterServer entry point was not found.

xxxxxx.dll may not be exported, or a corrupted version of xxxxxx.dll may be in memory. Consider using Pview to detect the file and remove it."

Interpreted from "Explanation of Regsvr32 Usage and Error Messages"

http://support.microsoft.com/kb/249873

You can chase after that if you think it worthwhile.

Windows Process Viewers

http://www.softpanorama.org/Unixification/windows_process_viewers.shtml

Process Viewer is similar to Pview.exe, but it can view processes on remote computers

http://www.dynawell.com/reskit/microsoft/win2000/pviewer.zip

http://www.microsoft.com/technet/pr...ocess_monitor,_and_event_viewer.mspx?mfr=true

You might like to look at this thread (start at the end and work backward as it is a long and winding road) but it touches on failure to register a dll.

Event ID 1085 Error
thread779-1319110

Also look at the SubInAcl links mentioned here. Adapt and change it to your situation to make sure registry access permissions are correct.

Not Getting a "Save As" dialog
thread779-962708

 

[xp8103]

But I am not sure those messages you list are the same. They both seem to imply that the registration was successful but in my case they aren't even getting registered.

 

[linney]

They are not implying a successful registration only that Windows knows about the .dll but can't register it.

Part of the reason I suggested those other links was from reading threads like this.

DllRegisterServer in <filename.dll> failed. Return Code was: 0x80004005

http://groups.google.com/group/micr...turn+Code:+0x80004005&rnum=1#415597279e1703fe