There have been many workstations that the ActiveX dll registered during the install. There have been many workstations that the ActiveX dll did not register during the installation. A good dozen other ActiveX / COM dll's did register during installation. This CRViewer.dll dated 1/21/2017 is the viewer for Crystal Reports. (not many using it in the VFP world) The one workstation where I've hit this wall is a Windows 7 32-bit machine. IT has it locked down, but we were using a local admin, and later the network admin user. Most of the ActiveX / COM dll's that are part of and needed by our implementation of Crystal Reports work. This Viewer ActiveX dll fails to register.
In an Administrator: Command Prompt running the following command says it is successful. C:\Windows\system32>regsvr32 "\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\common\Crystal Reports 2011\crystalreportviewers\ActiveX Controls\CRViewer.dll"
But the CrystalReports13.ActiveXReportViewer.1 key is not found in the registry where it belongs under HKEY_CLASSES_ROOT.
Running this on other Windows 7 32-bit, Windows 7 64-bit, Windows 10 32-bit, Windows 10 64-bit systems enables the control.
I use the INNO installer for the main installation. The required C++ runtimes are installed successfully during the process. Then I register all the ActiveX / COM dlls after the C++ runtime is completed.
Works on 98 out of 100 machines. Some sites have 1 machine that has a problem and 7 others that don't. Other sites have the problem on every machine, but the manual command above fixes them.
I have not found a "common" factor of all the workstations that presented the problem of the installer failing to register the DLL.
Registering this DLL on a functioning Windows 7 32-bit machine creates 132 keys and sets 61 values in the registry. (according to ProcMon from SysInternals) I have not determined how many registry keys or values are created (if any) on the machine that fails.
This particular customer has had 4 out of 5 workstations fail to register this file on the Install. 1 machine RegSvr32 command fixed it. I have not attempted it on the other 2.
My week is over, and I've been in all sorts of directions today.
Thank you, Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche Sent: Friday, March 23, 2018 6:44 AM To: profoxtech@leafe.com Subject: Re: ActiveX control refuses to register
On Thu, Mar 22, 2018 at 10:53 AM, Tracy Pearson tracy@powerchurch.com wrote:
I have some client workstation that refuse to register an ActiveX control
I
use in my VFP app. Even manually typing the RegSvr32 command. The message that appears states it registered successfully. However, the Registry is never updated.
What ideas can I use to track down this problem?
You could tell us which OS the workstations had, 32-bit or 64-bit.
You could tell us which ActiveX control it is, which version, age, etc.
You could tell us what you know about the workstation, make, model, color, etc. If more than one, anything in common, well, besides color...
You could tell us whether these machines are brand new or are old boxes upgraded from Windows 8.
You could tell us if they were up-to-date on patches.
You mention turning off anti-malware, good, that's often an issue.
Were there any messages in the event log?
I guess these days we can assume much of this stuff, but you know what happens when you ASSuME.
My wild-guess-out-of-the-blue is... something-something-missing-old-VC++-runtime-no-longer-included-in-Windows-1 0...
https://stackoverflow.com/questions/27290154/regsvr32-query-the-module-xxxxx -dll-failed-to-load
https://www.wintertree-software.com/support/wspell/registrationfailure.html
http://www.itninja.com/question/sapgui-7-10-sp-16-some-dll-ocx-files-fail-to -register
Guess #2, if this is only one workstation: Registry is corrupt
Guess #3, some sort of anti-malware protection that prevents Registry entries, like a corporate Policy setting, as many malwares wedge themselves in there good.
Guess #4, the malware's already on the machine, and IT is preventing Registry entries!
That's it, time for more coffee. Happy Friday!