If you are not able to register a DLL file and you end up getting an error message saying that the attempt to register the DLL file failed, you might want to disable UAC (User Account Control) in Windows.
Turning off UAC has been known to fix the issue of failed attempts to register DLLs. Other issues could be that you need to right-click on the command prompt and choose Run as Administrator. Sometimes if the command prompt does not have administrator privileges, the register DLL command will fail.
register dll windows 2008 64 bit
Welcome to Help Desk Geek- a blog full of tech tips from trusted tech experts. We have thousands of articles and guides to help you troubleshoot any issue. Our articles have been read over 150 million times since we launched in 2008.
Sometimes, running lodctr /R may not recover all counters. If you notice this happening, verify the file c:\windows\system32\PerfStringBackup.INI contains the proper information. You can copy this file from an identical machine to restore the counters. There may be slight differences in this file from machine to machine. But if you notice a drastic difference in size, it may be missing information. Always create a backup copy before replacing. There's no guarantee that copying this file from another machine will restore all counters. If possible, compare the file to backups of the machine to see if the file size has reduced at some point in time.
There's a hotfix for known issues with PerfDisk.dll on Windows Server 2008 and Vista systems. This hotfix has been rolled into Service Pack 2 for these operating systems. If you're at Service Pack 1 or below, apply the hotfix 961382.
Sometimes "application extension" files (.DLL or .OCX) must be manually registered to properly support functions in a program such as CTI Navigator. A variety of ActiveX, Automation, or "Run-time" type errors can result when associated application extension files (also called ActiveX controls) are not registered in Windows for use by the requesting program. Click on the appropriate topic in the list below to go directly to information relevant to that topic: Register dll or ocx file in Windows Vista, 7, 8.1, or 10
Register dll or ocx file in Windows XP (or earlier Windows)
Un-register dll or ocx files
Security and Active X Controls Enable ActiveX Specifically for CTI Navigator
To register an ActiveX control (dll or ocx) file in Windows Vista, 7, 8.1 or 10:
Note 3: If you are using Windows Vista, you can add a file to the Windows Vista registry that will allow you to right-click on any DLL file and simply select Register or Unregister (without going through the detailed commands). To add the Register and Unregister command to your right-click menu, go to www.ctimls.com/Downloads/Windows/Vista/VistaDll.reg > click Save > right-click on the saved file in your Vista > select Merge > accept the registry change notice. To also add a file to the Windows Vista registry that will allow you to right-click on any OCX file to register or unregister it, go to www.ctimls.com/Downloads/Windows/Vista/VistaOcx.reg > click Save > right-click on the saved file in your Vista > select Merge > accept the registry change notice. Warning: Before making any registry changes, Microsoft highly recommends that you make a backup of your registry (see related article below).
In versions of Windows prior to Vista, or with User Account Control (UAC) turned off in Windows Vista, 7, or 8, ActiveX files (such as .dll or .ocx) can be registered by double-clicking on the filename in Windows Explorer ("File Explorer" in Windows 8). If opening, running, or double-clicking on a file with a .dll extension (Dynamic Link Library) or an .ocx extension (OLE Control Extension) brings up an "Open With" screen: click "Select the program from a List" and click OK > click the "Browse" (or "Other") button on the lower right of the screen > progressively select directories and change the "Look-in" box on the next screen to C:\Windows\System32\regsvr32.exe > double-click on regsvr32.exe (or click the Open button) > verify that "Microsoft Register Server" is highlighted in the Programs list > verify that a check mark is in the "Always Use" box on the lower left of the Open With screen > click the OK button on the "Open With" screen. A message should appear indicating that the registration succeeded. Click the OK button on the RegSvr32 message screen.
Sometimes files need to be un-registered and then re-registered tooperate properly. To un-register a 32-bit Windows system file and then re-register it in a version of Windows without User Account Control (prior to Vista) or with UAC turned off (in a 32-bit version of Windows Vista, 7, or 8):
Note 5: To register or unregister a file not in the Windows system folder using the Windows Run command, youmust enter the full path to the file enclosed by quotation marks after the Regsvr32or Regsvr32 /u command. For example, to register the Announcement file in CTI Navigator run Regsvr32"C:\Program Files\Cti Navigator\CtiAnnouncement.dll". Ensure that you type the correct drive letter and the correct folder (Program Files or Program Files (x86)) in the path.
Try copying any of these two executables, along with the OCX or DLL file to register.Run in administrator mode, or change the properties of the executable in compatibility tab to "run this program as an administrator."Register the ActiveX (ocx) or DLL or running RegSvr32.exe nombre_dll nombre_activeX RegSvr32.exe.
(I apologize, if this is not the correct forum for my question, but I did not find another one.)Here is my question:We have developed à COM dll server.This latter is compiled in 32 bits AND 64 bits (without any changes). On Windows 64 bits, the two versions may be ran at the same time by a 32 bits and a 64 bits process clientI can't figure out if we need to change the CLSID of our COM objects for each "bit model". I would prefer not changing them, otherwise that would mean a lot of changes in our clients.I tried to search these CLSID in the registry and found that they are existing in both the 64 bits and 32 bits section (under Wow6432Node). I know that Windows copies some registry keys from one section to the other, but I'm not sure in which direction (maybe only when the server is 64 bits, and so on...)I wonder also if the registration order is important (i.e. do we need to register the 64 bits version before or after le 32 bits one?). It seems that it may change the way registration informations are stored in the registry. Also, sometimes, we get the "Class is not registered" error. If we register again our server, the error disappears.So, what is the best practice to resolve this issue?Any help in this area will be appreciated.Best regards,Olivier.
All you need to take care of is that you register your COM server DLL's using the right version of regsvr32.exe.The 32-bit DLL must be registered with the 32-bit version of regsvr32 (%windir%\syswow64), while the 64-bit version must be registered with the 64-bit version (%windir%\sytem32).Willy.
They are two different hives - a 32-bit and a 64-bit. You must register themas different using the respective versions of Regsvcs.exe. The order makesno difference.The "copying" you are seeing is actually the result of different 'views'.That is, the 'hives' themselves don't actually exist as physical entities -'hives' are the product of a query to the underlying registry store.[Take a peek at the InprocServer32 key sometime.]As they have different names storage is irrelevant. If you add additionalcomponents to your stable, you might find it more convienent in the long run(and helpful to your sanity ) to separate them into different folderswith different LibIDs, and manage similar code with conditional compiles.But it really doesn't matter.-ralph
Hello Willy,Thank you for your comment, but I'm not sure of this.I tried to register the 32 bits version of our dll, using the regsvr32.exe located in C:\Windows\System32, and it worked without any problem.I tried also to regsister the 64 bits version, using the regsvr32.exe located in C:\Windows\SysWow64, and it worked also without problem.In fact, both versions of regsvr32 seems to work with both versions of our dll.I don't know how this works, but it works!Here are informations about regsvr32.exe found on our 64 bits test machine:C:\Windows\System32\RegSvr32.exe: 15 872 bytes, version 5.2.3790.1830 (srv03_sp1_rtm.050324-1447)C:\Windows\SysWOW64\RegSvr32.exe: 12 800 bytes, version 5.2.3790.1830 (srv03_sp1_rtm.050324-1447)Best regards,Olivier.
Humm... from our experience, it seems that this assertion is also false. FYI, we use the ATL Registrar component to make registration (using .rgs resources)We have tried the following:We have registered Server32.dll then Server64.dll and have searched for Server32.dll and Server64.dll in the registry:Server32.dll:HKEY_CLASSES_ROOT\Wow6432Node\CLSID\2FD8F665-77A0-11D5-BDD1-0050BAAE12A3\InprocServer32HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\2FD8F665-77A0-11D5-BDD1-0050BAAE12A3\InprocServer32HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\2FD8F665-77A0-11D5-BDD1-0050BAAE12A3\InprocServer32Server64.dll:HKEY_CLASSES_ROOT\CLSID\2FD8F665-77A0-11D5-BDD1-0050BAAE12A3\InprocServer32HKEY_CLASSES_ROOT\TypeLib\2FD8F657-77A0-11D5-BDD1-0050BAAE12A3\1.0\0\win32HKEY_CLASSES_ROOT\Wow6432Node\TypeLib\2FD8F657-77A0-11D5-BDD1-0050BAAE12A3\1.0\0\win32HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\2FD8F665-77A0-11D5-BDD1-0050BAAE12A3\InprocServer32HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\2FD8F657-77A0-11D5-BDD1-0050BAAE12A3\1.0\0\win32HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\TypeLib\2FD8F657-77A0-11D5-BDD1-0050BAAE12A3\1.0\0\win32HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\TypeLib\2FD8F657-77A0-11D5-BDD1-0050BAAE12A3\1.0\0\win32Registering in the reverse order, gives the following result:Server32.dll:HKEY_CLASSES_ROOT\TypeLib\2FD8F657-77A0-11D5-BDD1-0050BAAE12A3\1.0\0\win32HKEY_CLASSES_ROOT\Wow6432Node\CLSID\2FD8F665-77A0-11D5-BDD1-0050BAAE12A3\InprocServer32HKEY_CLASSES_ROOT\Wow6432Node\TypeLib\2FD8F657-77A0-11D5-BDD1-0050BAAE12A3\1.0\0\win32HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\2FD8F657-77A0-11D5-BDD1-0050BAAE12A3\1.0\0\win32HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\2FD8F665-77A0-11D5-BDD1-0050BAAE12A3\InprocServer32HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\TypeLib\2FD8F657-77A0-11D5-BDD1-0050BAAE12A3\1.0\0\win32HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\2FD8F665-77A0-11D5-BDD1-0050BAAE12A3\InprocServer32HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\TypeLib\2FD8F657-77A0-11D5-BDD1-0050BAAE12A3\1.0\0\win32Server64.dll:HKEY_CLASSES_ROOT\CLSID\2FD8F665-77A0-11D5-BDD1-0050BAAE12A3\InprocServer32HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\2FD8F665-77A0-11D5-BDD1-0050BAAE12A3\InprocServer32So the result differs.I wonder also why there areHKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432NodeandHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes ?Best regards,Olivier. 2ff7e9595c
Commenti