ActiveX registration problems
Posted: Wed Feb 06, 2013 7:22 pm
I'm just learning IA (migrant from InstallShield). I own a license for Studio but I've tried letting Studio Admin import/convert the existing IS package but with no good results.
I need some guidance on the rules/procedures for packaging ActiveX components. I've built an IA package that includes components that are both made in-house and from 3rd parties, such as ComponentOne & Crystal/Business Objects.
When I install my package on a clean/green XP machine (with current MS updates) I get numerous errors about registering the various ActiveX components. For example:
"Module C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\EnterpriseFramework.dll failed to register. HRESULT -2147023898. Contact your support personnel." Our software doesn't use EnterpriseFramework.dll.
I believe I've extracted the reg info from our own ocx/dlls and included the info in the package but I don't know what to do about the errors that involve the merge modules. I guess there's a general problem of me not understanding the big picture.
I have two general questions:
1) The Crystal components are in merge modules. Did I include the wrong MMs? Is this an IA problem? Do I need to do something extra to tell IA how to handle this? How do I troubleshoot this error?
2) For in-house and 3rd party ActiveX components, should I mark the ActiveX ocx/dll in the IA package as Self-Registering or should I tell IA to import the reg data from the component? One or the other? Both?
I'd appreciate any wise advice.
Jay
I need some guidance on the rules/procedures for packaging ActiveX components. I've built an IA package that includes components that are both made in-house and from 3rd parties, such as ComponentOne & Crystal/Business Objects.
When I install my package on a clean/green XP machine (with current MS updates) I get numerous errors about registering the various ActiveX components. For example:
"Module C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\EnterpriseFramework.dll failed to register. HRESULT -2147023898. Contact your support personnel." Our software doesn't use EnterpriseFramework.dll.
I believe I've extracted the reg info from our own ocx/dlls and included the info in the package but I don't know what to do about the errors that involve the merge modules. I guess there's a general problem of me not understanding the big picture.
I have two general questions:
1) The Crystal components are in merge modules. Did I include the wrong MMs? Is this an IA problem? Do I need to do something extra to tell IA how to handle this? How do I troubleshoot this error?
2) For in-house and 3rd party ActiveX components, should I mark the ActiveX ocx/dll in the IA package as Self-Registering or should I tell IA to import the reg data from the component? One or the other? Both?
I'd appreciate any wise advice.
Jay