RegSvr32 error - Techist - Tech Forum

Go Back   Techist - Tech Forum > Computer Software > Microsoft Windows and Software
Click Here to Login
Closed Thread
 
Thread Tools Display Modes
 
Old 03-06-2005, 10:38 AM   #1 (permalink)
Banned
 
Join Date: May 2003
Posts: 105
Default RegSvr32 error

When I register or unregister a dll/ocx I get this message
DLLRegisterServer in FileName failed Return code 0x80004005
http://www.sonomaenterprises.us/regsvr32.gif

I get this message no matter what dll or ocx I attempt to register. The
platform is Windows 2000 SP4 Build 2195.
__________________

_Jack is offline  
Old 03-07-2005, 09:14 AM   #2 (permalink)
Super Techie
 
Join Date: Dec 2003
Posts: 324
Default

If the .dll is a replacement, you should unregister the existing version, then replace it, then register the new version.
__________________

sunsider is offline  
Old 03-07-2005, 10:37 AM   #3 (permalink)
Banned
 
Join Date: May 2003
Posts: 105
Default

I get the same result from both the unregister and register.
_Jack is offline  
Old 03-07-2005, 10:48 AM   #4 (permalink)
Super Techie
 
Join Date: Dec 2003
Posts: 324
Default

Are you using M$ IIS? If so, the only other info I could drag up was this link on the M$ knowledge base.

http://support.microsoft.com/default...b;en-us;307495
sunsider is offline  
Old 03-07-2005, 11:06 AM   #5 (permalink)
Banned
 
Join Date: May 2003
Posts: 105
Default

Unfortunately that is not the case. The DLL is a COM Add-in, I also tried to register simple Active X controls and get that message. Also, I have this application deployed on several hundred other machines and they register without a problem. I am thinking it could be caused by some other application running on the machine???
_Jack is offline  
Old 03-07-2005, 11:18 AM   #6 (permalink)
Super Techie
 
Join Date: Dec 2003
Posts: 324
Default

It's possible that it could be a software glitch, but I am assuming since it is on a mass network that they all have the same config. It could more likely be some obscure security setting on that pc that won't let it register the file. I'll poke around the msdn boards and see if anyone there has any ideas.
sunsider is offline  
Old 03-07-2005, 11:45 AM   #7 (permalink)
Banned
 
Join Date: May 2003
Posts: 105
Default

Thanks!
_Jack is offline  
Old 03-07-2005, 01:20 PM   #8 (permalink)
Super Techie
 
Join Date: Dec 2003
Posts: 324
Default

Here's what I was able to scrape up from the msdn boards. Of course, the first thing they asked was are you sure it was unregistered and removed before re-registering ..

An MFC ActiveX control that subclasses any of the window classes implemented by Comctl32.dll causes the error to be thrown. What they advise you to check on your.dll is the following :

Inside the InitInstance of your ActiveX control, make a call to:InitCommonControls(void)
or InitCommonControlsEx(LPINITCOMMONCONTROLSEX lpInitCtrls)
This ensures that Comctl32.dll is loaded and initialized, regardless of the container the control is running in.

Instead of calling InitCommonControls from the control's code, you can also call it directly from the Visual Basic client application:
• Make a General declaration for the corresponding Form; for example:Private Declare Sub InitCommonControls Lib ".dll filename" ()

• Add a call to:InitCommonControls in the Form_Load method.

That should clear up the issue, other than that, the only other reference they gave me was to the following link, which shoud help narrow down the issue further if the above doesn't help you out.

http://support.microsoft.com/?scid=h...%2fdllinfo.asp
__________________

sunsider is offline  
Closed Thread

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off




Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -5. The time now is 12:19 PM.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.