** Troubleshooting ** "Cannot create ActiveX component" (or ActiveX component can't create object) when running a Consolidation
User launches a consolidation. Looking inside the 'batch queue' user can see that the consolidation has not run successfully. Clicking on the 'details' section, there is an error message.
The error may vary slightly depending on environments:
There are several possible causes for this error/problem:
Scenario #1 - Missing (or incorrectly registered) components in the COM+ application (on the Controller application server):
Scenario #2 - COM+ application
This has been seen with Controller 10.2. From this version onwards, for most environments the following settings are sufficient:
In some customer environments (very rare) these are insufficient.
Scenario #3 - Inaccessible required third-party components
Specifically, in some environments it may be necessary to copy the files "msvcr70.dll" and "msvcr71.dll" to a location inside the PATH variable, which all users have read access of.
Scenario #4 - Incorrect registry key permission(s)
- Specifically, in one environment it was necessary to change the permission of the registry key 'HKCR\Wow6432Node\CLSID'.
- For more details, see separate IBM Technote #1979305.
Resolving the problem
Register the file 'frangovfp.dll' into the relevant COM+ application.
- For more information, see separate IBM Technote #1347488.
Example A: In one real-life customer example, add the group ' Everyone' to the list of 'COM+ users' inside the section 'Controller COM+ roles and users':
Example B: In a different environment, it was necessary to also untick 'Enforce Access checks for the Controller COM+ application":
The following steps are based on Controller 10.2.0 on Windows 2012. The steps may vary slightly for different versions/operating systems.
1. Locate the folder 'server'.
- TIP: By default this is located here: C:\Program Files\IBM\cognos\ccr_64\server
2. Locate the following files:
3. Copy both of those files into this folder: C:\Windows\system32
5. If the above does not solve the problem, then re-register the file 'frangovfp.dll' by following the steps inside Scenario #1.
See separate IBM Technote #1979305.