unable to register 32-bit dll with Win 7 or Win 8/8.1
I have a 32-bit VB 6 dll that runs as a COM add-in to a Microsoft Office application. It's been running for years, including on Win 7 and 8 systems and with all versions of Office since 2003. However, on some systems the dll cannot be registered.
When my installer attempts to register the dll, it fails with this message:
When I try to register the dll from the command line by running regsvr32, I receive this message:
I've researched both error codes and have tried all of the following with no change:
1) Run regsvr32 from C:\Windows\SysWOW64 instead of from C:\Windows\System32
2) Run regsvr32 from an elevated command prompt
3) Turn off UAC
4) Recompile dll after updating references to a newer version of Office (I updated to Office 2010)
Suggestions?
When my installer attempts to register the dll, it fails with this message:
Module xyz.dll failed to register. HRESULT -2147467259. Contact your support personnel.
When I try to register the dll from the command line by running regsvr32, I receive this message:
The module "xyz.dll" was loaded but the call to DllRegisterServer failed with error code 0x80004005.
I've researched both error codes and have tried all of the following with no change:
1) Run regsvr32 from C:\Windows\SysWOW64 instead of from C:\Windows\System32
2) Run regsvr32 from an elevated command prompt
3) Turn off UAC
4) Recompile dll after updating references to a newer version of Office (I updated to Office 2010)
Suggestions?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Its Davis, BTW....
Yes, I have had to repair the permissions on both workstations and servers, hundreds of times.
Yes, I have had to repair the permissions on both workstations and servers, hundreds of times.
ASKER
Sorry about the final letter of your name -- my fingers automatically typed the 'd'.
I will give this a try then, when I have a chance.
I realize now, on rereading my initial question, that I didn't express one thing very well: The bigger issue for me is to find out what is causing the problem in the first place. Assuming your suggestion above solves the problem, I can't expect my customers to use this procedure on their systems after they run my installer. Consequently, I need help figuring out the root cause so I can fix the underlying issue. But first things first, let me see whether this solution solves the local problem.
I will give this a try then, when I have a chance.
I realize now, on rereading my initial question, that I didn't express one thing very well: The bigger issue for me is to find out what is causing the problem in the first place. Assuming your suggestion above solves the problem, I can't expect my customers to use this procedure on their systems after they run my installer. Consequently, I need help figuring out the root cause so I can fix the underlying issue. But first things first, let me see whether this solution solves the local problem.
IMHO, one of the stupidest things M$ implemented were explicit permissions on every single file and registry key, especially since, to this day, they have never provided a utility that really fixes either.
I have a PC here, right now, for example, where the owner let his daughter try to find free TV on the internet and, while the resultant virus/adware was pretty easy to vanquish, the residual damage to Windoze, which now completely refuses to install any updates, may result in a wipe-and-reload being the only possible fix for the PC.
I have seen permissions get gescrewdefay by creating a new user, a defective Windows update, losing the internet in mid-page, a failing hard disk drive, forcing the PC to turn off by holding down the power button, and, of course, any one of the plethora of adware/malware which sometimes accounts for 80+% of my business.
So, determining what caused the problem may not be a productive use of your time.....
I have a PC here, right now, for example, where the owner let his daughter try to find free TV on the internet and, while the resultant virus/adware was pretty easy to vanquish, the residual damage to Windoze, which now completely refuses to install any updates, may result in a wipe-and-reload being the only possible fix for the PC.
I have seen permissions get gescrewdefay by creating a new user, a defective Windows update, losing the internet in mid-page, a failing hard disk drive, forcing the PC to turn off by holding down the power button, and, of course, any one of the plethora of adware/malware which sometimes accounts for 80+% of my business.
So, determining what caused the problem may not be a productive use of your time.....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Good suggestions from Davis for the question I asked, but as I investigated, I realized that they attacked the symptom and not the root problem.
ASKER