Knowledgebase: FDM
Validate Step of FDM Workflow Fails with "Automation Error: Cannot Create ActiveX Component. At Line: 248" in the FDM Web Interface
Posted by Priya Doyle on 08 February 2011 02:48 PM
Validate Step of FDM Workflow Fails with "Automation Error: Cannot Create ActiveX Component. At Line: 248" in the FDM Web Interface

 Modified 14-SEP-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 to 9.3.1.0.01 - Release: 9.3 to 9.3
Information in this document applies to any platform.

Symptoms

When running the Validate step of the workflow in the FDM Web Interface the following error is returned:

"Cannot create ActiveX component.
At Line: 248"

Cause


Excel is not functioning properly on the FDM application server.  A review of Excel by launching it shows it suffered a critical error and wanted confirmation to start in "SafeMode" or not. Dialog boxes can not be responded to and require user interaction. This failure caused Excel to "hang"




A review of the user error log showed the first entry in the error log to be from the Adapter.
** Begin fdmFM11xG5A Runtime Error Log Entry [2009-12-28-03:54:22] **
-------------------------------------------------------------
ERROR:
Code............ 429
Description..... Cannot create ActiveX component.
Procedure....... clsHPDataAccess.fIntersectionCheckEx
Component....... D:\Hyperion\FDM\Adapters\AdapterComponents\fdmFM11xG5A\fdmFM11xG5A.dll
Version......... 100

The second entry in the error log was from the actual software interface.
** Begin FDM Runtime Error Log Entry [2009-12-28-03:54:22] **
-------------------------------------------------------------
ERROR:
Code......................................... -2146233088
Description.................................. Cannot create ActiveX component.
At Line: 248
Procedure.................................... clsBlockProcessor.ActCheckIntersections
Component.................................... upsWBlockProcessorDM
Version...................................... 931


Solution

1. Kill all "Excel.exe" processes
2. Retest the issue
3. Consider moving to the XML Intersection Check Report using the FM9x-G4-B adapter if Excel continues to have issues.  To use the FM9x-G4-B adapter, an upgrade to FDM 9.3.1.1 or higher is required.


(0 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments: