Why... Why... Why?
This blog is dedicated to documenting error resolution and other tidbits that I discover while working as a Consultant in the Oracle EPM (Hyperion) field. As much of my job revolves around issue resolution, I see an opportunity to supplement the typical troubleshooting avenues such as the Oracle Knowledgebase and Oracle Forums with more pinpointed information about specific errors as they are encountered. Beware, the information found in this blog is for informational purposes only and comes without any warranty or guarantee of accuracy.

EPMVirt: Create your own Oracle Hyperion Virtual Environment:

Sunday, February 26, 2012

FDM - "Object variable or With block variable not set"

This error can be common in Financial Data Manatement (FDM). 
Error Message:
"Object variable or With block variable not set".
The easiest way to reproduce this message is to open an FDM application via the web, Click Activities -> Maps. Click the export to excel option.

 There are two reasons I have seen for this message. The first deals with Microsoft Excel. It must be correctly installed on the FDM application server. It also must be a supported version. This error can come up if you have installed Office 2007 where only 2003 was supported. It can also pop up if a Office service pack is applied which is not supported. Such as installing Office 2007 SP3 when SP2 is only supported. Additionally, Oracle recommends uninstalling or disabling any plugins. If this error occurs, disable or uninstall any Office plugins like Smartview, Excel Add-In or 3rd party extensions. It is worth carefully going over the Excel install, reviewing any recent updates that may have been applied by Windows Update.

If an inadvertant service pack was applied, Microsoft has a tool which can uninstall Office Service Packs, called the "Service Pack Uninstall Tool". This knowledge-base article explains the syntax

The second reason for this message can be due to permissions on the FDMData folder. The folder must be mounted. If it is a shared drive, open the share and try to write to it. Make sure the folder is set to to read/write and the access permissions allow the DCOM user to write to the folder.

Check the Windows Event Viewer for any permissions or DCOM related messages, typically in the Security tab.

No comments:

Post a Comment