I'm having a lot of occurrences of this error when running my application. Thousands of people have successfully installed without any error -- but hundreds have gotten this error with respect to one OCX/DLL or another. At least six OCX/DLLs have triggered the error for different users but there is no discernible pattern based on OS or other environmental factors. In almost every case, my OCX/DLLs are autoregistered with "self register native library".
In almost every case, manually unregistering the OCX/DLL and registering it again (with regsvr32 and a command window) fixes the problem -- but that's a lot of tech support for hundreds of users!
Why is this registration process so unreliable and what can I do to fix it? Again, the current process has worked for thousands of installations but roughly 5% are getting registration failures.
In one case, I'm running a custom action to register an EXE with /regserver and I don't have any reports of that processing failing. Should I be doing the same thing with every other OCX/DLL that needs to be registered? Is that process more reliable across XP->Vista and 32/64bit?
Very frustrating.
FOLLOW US
Get the latest news in Application Packaging