Knowledgebase : Enterprise


"Not Enough Space for Row Title and at Least One Data Row" Trying to Print or Preview a Journals Report

 Modified 13-OCT-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 6.5.0.0.00 and later   [Release: 6.5 and later ]
Information in this document applies to any platform.

Symptoms

In the Journals module, doing a Print or Preview of the "Journals Report" gives the following error: "Not enough space for row title and at least one data row".

Cause

The cause of the problem seems to be an issue with the German version of Hyperion Enterprise. 

Unpublished bug 10133736 has been created to report this issue to development.

Solution

  • As a workaround, install the software in English.
  • A permanent solution will be available when the bug is addressed. 


Back to topBack to top


Error: "Unable to Load Proper Application Module" when Opening Enterprise Application

 Modified 11-FEB-2011     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 4.3.2.0.00 and later   [Release: 4.3 and later ]
Microsoft Windows (32-bit)
This knowledge document is a replacement for 593297.1 and 591662.1 which have been deleted.

Symptoms

Error: "Unable to load proper application module" when opening enterprise application.


Cause


  1. Hypent.ini and/or other user specific .ini files needed to run Enterprise and Enterprise Reporting cannot be located.

  2. The system path for Hyperion Enterprise is incorrect

Solution

  1. The hypent.ini and other user specific .ini files should be located in one of two places when using Terminal Server or Citrix:
1. If a home directory is defined in Terminal Server, the .ini files will be located in this home directory

2. Otherwise they will be located in the users' profile\WINDOWS directory


Note:  Occasionally the hypent.ini does not write properly.  If this should happen, copy the file from an existing user to the appropriate location


     2.  Check that the path has the reference for Hyperion Enterprise Reporting in the front of the path, followed by Hyperion Enterprise and 
          then everything else.
E.G: PATH=C:\Programs Files\Hyperion Solutions\Reporting;C\Program Files\Hyperion Solutions\Enterprise;C:\WINDOWS;C:\WINDOWS\COMMAND;

'Invalid Pointer' Message' On Hyperion Enterprise Database Converstion to 6.5.1

 Modified 15-OCT-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 6.5.1.0.00 and later   [Release: 6.5 and later ]
Information in this document applies to any platform.

Symptoms


When converting an application to version 6.5.1, at the start of the conversion an error box appears stating 'Invalid Pointer' ..When 'OK' is clicked the conversion process continues and the resulting 6.5.1. application contains all expected data elements

Cause

There is an unpublished bug logged 9131586 - INVALID POINTER MESSAGE IS DISPLAYED WHILE HE APP CONVERSION to correct this message in a future release.

Solution

Development have confirmed that in the circumstance where the error is seen but the conversion proceeds and all categories of data are present. The error can be ignored.



"Add-in" Disappears from Excel 2007 Menu When in Retrieve for Hyperion Enterprise

 Modified 12-MAR-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 6.5.0.0.00 - Release: 6.5
Information in this document applies to any platform.

Symptoms

When working in retrieve within Microsoft Excel 2007, the retrieve addin disappears when you perform a print operation from a review screen.

Cause

Microsoft has confirmed that this is a problem in the Microsoft Excel 2007. Please refer the below link.


<<http://support.microsoft.com/kb/933787>>

Solution

To work around this problem, click a tab other than the Add-Ins tab to make the other tab active before you print the workbook from the print preview.

See other suggestions in the link below.


<<http://support.microsoft.com/kb/933787>>


"Error sending message. Winsock error code 10038" when Attempting to Run Server Based Consolidation

 Modified 12-JAN-2011     Type PROBLEM

Applies to:

Hyperion Enterprise - Version: 4.3.2.0.00 and later   [Release: 4.3 and later ]

Microsoft Windows (32-bit)

Symptoms

When attempting to run server based consolidation on an enterprise application the following error occurs: "Error sending message. Winsock error code 10038" 

Cause

The enterprise application is not listed in the hypent.ini on the enterprise application server

Solution

To add the application to the hypent.ini on the application server launch enterprise from the application server and refer to document 580746.1

A Report Displays a Blank Column When Previewed in Enterprise but Shows Data in Enterprise Reporting

 Modified 22-DEC-2010     Type PROBLEM n

Applies to:

Hyperion Enterprise Reporting - Version: 3.6.0.0.00 to 6.5.0.0.00 - Release: 3.6 to 6.5
Information in this document applies to any platform.
Issue when Reports are run from within Core Enterprise. Reports are fine within HER.

Symptoms


A specific report when previewed in HER shows data in a Category column but no data when the same report is run from Reports Module within Enterprise.

Cause


The report used the Period @cur function which failed when the point of view (POV) category was set to one with a different year setting to the category on the Report.

Solution


There are two date functions which can be used to define a period in a report.

CUR returns the current month from the POV including year.

CMO  returns the current month only and so works when the POV Category is a different year.

The columns definition was such that it hard coded the category but used an @CUR to define the period from the POV. The columns were changed to use @CMO and then they returned the data correctly regardless of the POV category year in both Enterprise and HER.


An entity loses its data when adding a substructure to it

 

Changes:

A substructure has been added to an entity

Solution:

In order to keep the data you need to follow these steps:

Before adding the substructure to the entity:

1. In the Journals module unpost and extract any journals that are posted to the entity for all organisations, categories and periods

2. In the Database module extract all data from the entity for all organisations, categories and periods

After attaching the substructure to the entity:

1. Modify the data extracts and journal extracts by changing the entity to one of the subentities which has been added

In the following examples of data extract and journal extract files, the entity TEST would need to be changed to the correct subentity TEST.INP

Example of a data extract:

ACTUAL
1
3
TEST,100000,100,200,300

Example of a journal extract:

[JOURNAL=TESTJOURNAL!B!J!R!P!ACTUAL!APR 00!MAXIMUM! ! !P]
DESC=test journal
TEST!100000!10!
TEST!104000! !10

2. Load the amended data extracts and journal extracts via the Database module and Journals module respectively


AutoPilot Fails to Start With Error "Unexpected error; quitting"

 Modified 31-MAR-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 5.1.1.0.00 to 6.5.0.0.00 - Release: 5.1 to 6.5
Information in this document applies to any platform.

Symptoms


Hyperion AutoPilot fails to start with the error  "Unexpected error; quitting" on a newly installed computer.

Changes

The install was run using a "Run As" command and specifying a user with local Administrator rights on the target machine as opposed to running the install while logged on as a user with local Administrator privileges.

Cause


Enterprise needs to be installed, logged on as a user with full administrator rights.

If the install is not made with a user with full Administrator rights, the required registry entries will not be made and the software will not function correctly.

.

Solution


The installation must be run as an Administrator user logged onto the machine.  
Re-install while logged on suitably and re-test Hyperion AutoPilot. 

Can only change the ownership values for one period in the category
One period ownership is 100% but all other periods are blank
Ownership grid is blank except for one period
Application is Organization By Period (OBP)

Changes:

Changes were made to the organization structure in one period.Added a new entity

 

Cause:

Organization has not been pasted to the other periods in the category

 

Solution:

1. Select EDIT -> PASTE ORGANIZATION
2. Select radio button CURRENT PERIOD ONLY
3. Select required category from the drop-down menu
4. Highlight the required period(s) in the box below
5. Click OK


Cannot Add a currency to the Currency Subaccount Table in Oracle's Hyperion Enterprise

 Modified 18-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Enterprise
Hyperion Enterprise - Version: 5.0.1.0.00 and later    [Release: 5.0 and later]

Symptoms

Cannot add a currency to the Currency subaccount table in Hyperion Enterprise.
Can not add currencies into the application.
CURRENCY subaccount table is Read Only in the Accounts module.

Cause

The CURRENCY subaccount table is automatically created when an application is created. It is set up in the Entities module and will appear as Read Only in the Accounts module and cannot be modified directly from the Accounts Module.

Solution

Edit the CURRENCY subaccount table via the NAVIGATE->CURRENCIES option in the Entities module.




Cannot Change The Default Location of ‘Common Logon’ While Installing Hyperion Enterprise Reporting

 Modified 13-JAN-2010     Type PROBLEM

Applies to:

Hyperion Enterprise Reporting - Version: 6.1.0.0.00 to 6.5.0.0.00 - Release: 6.1 to 6.5
Information in this document applies to any platform.

Symptoms


Cannot Change The Default Location of ‘Common Logon’ While Installing Hyperion Enterprise Reporting?

Changes

Installed Hyperion Enterprise Reporting to one location but unable to change the location of common logon.

Cause

It is normal behavior in Hyperion Enterprise Reporting and unpublished BUG 8241704 has already been created.

Solution


It is not possible to change the default location of 'Common Logon' location and there are no current plans to change it to custom location. 

Unpublished BUG 8241704



Cells with No Data display as NA instead of a value of zero in a Hyperion Retrieve for Reporting (CDA Retrieve) spreadsheet

 Modified 08-JUL-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise

Symptoms

Cells with No Data display as NA instead of a value of zero in a Hyperion Retrieve for Reporting (CDA Retrieve) spreadsheet
CDA Retrieve returns # value when there is no data in the database
Formula cells in CDA Retrieve display #N/A instead of zeros

Cause

Hyperion Enterprise Reporting Configuration ,ini file settings missing or not set correctly.

Solution

Add the MissingValues=1 statement to the [MAIN] section of the HDCDARET.ini.
1. Open the HDCDARET.ini file in Notepad and create a [MAIN] section. 
2. Add the MissingValues=1 and save the file to display 0 for cells with no data. 
If an HDCDARET.ini does not already exist, change the POV in the Hyperion Retrieve for Reporting (CDA Retrieve) spreadsheet. This will create the HDCDARET.ini file. (This file is located in the Windows operating system directory.) 

Other Entries:

MissingValues=0 Displaying an N/A for cells for which there is no data, and ERR for cell errors in the worksheet.
MissingValues=1 Displaying a 0 for no data, and ERR for cell errors in the worksheet.
MissingValues=2 Displaying a 0 in cells for which there is no data, and a 0 for cell errors in the worksheet.


The documents attached to this article explain best practices and environmental changes for the avoidance of CHAPP errors.

Connection Error: Domain is Missing" When Attempting to Integrate With Hyperion Enterprise

 Modified 02-FEB-2009     Type PROBLEM  

Created from <SR 3-854437321>

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 - Release: 9.3

Information in this document applies to any platform.

Symptoms

When trying to make a connection to Hyperion Enterprise from FDM an error occurs with the following message:  "Error: Connection Error: Domain is Missing"

Cause

Hyperion Enterprise does not support native NTLM style authentication, but by default other Hyperion products that FDM integrates with do.  Since the scripting/coding for the Enterprise adapter has to conform to the other standards, it has a field for 'domain' but isn't populated/required.

Solution

Simply place the servername from the 'Source Machine' into the domain field of the Machine Profile.  Since the coding requires the Domain to be populated, but the Enterprise software doesn't require it.  It will not harm/change anything and provide a solution to the issue. 


1.       Ensure everybody is out of all areas of the Enterprise application. This applies to all associated products including Retrieve Excel and Reporting.

2.       Go to the route of the application (Usually the Label is the parent folder in the windows folder structure, under which would be Inbox, Outbox, Data etc etc including some system files.

3.       Right click on the route folder and select copy. This will have the effect of copying everything under the route inclusive.

4.       Then paste the folder to a local directory.

5.       It is better to do this twice to ensure against failure.

N.B. ENSURE EVERYBODY IS OUT OF THE SYSTEM INCLUDING ALL ASSOCIATED PRODUCTS BEFORE COPYING.


Creating a new GL Template- Unable to drag the file record into the sample record box to populate.

 Modified 22-JAN-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 6.3.1.0.00 - Release: 6.3
Information in this document applies to any platform.

Symptoms


Unable to see sample record in Ledgerlink GL Temple Wizard. 

The Sample record field appears blank.

Cause


This is an issue  with Microsoft Windows XP machines

Solution

 

Set the Windows theme to 'Windows Classic': 

  • On the machine's Desktop background right click with the mouse and select Properties.
  • Select the Appearance Tab.
  • Change the 'Windows and buttons' drop down box to  setting to 'Windows Classic Style'
  • Select Apply.
  • The issue should be resolved.


Data is Appearing in the Incorrect Entity Within Hyperion Enterprise

 Modified 16-FEB-2010     Type PROBLEM   

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 to 6.5.1.0.00 - Release: 5.0 to 6.5
Information in this document applies to any platform.

Symptoms


Data is being incorrectly referenced by Database and DataEntry Modules . The data shown for Entity X was acually from Entity Y.

Cause


Entities had been added to the application with Live users on the System. 
At some point a file contention issue has arisen and caused the application's internal referencing to become corrupt.

Solution

Avoid making Metadata Changes while users are live on the system. Ensure that such changes are made in an offline application copy. Then update the live application with an extract from the test copy while no users are active within the live application.


If corruption is already present. Perform the following steps.

  1. Ensure that no users are logged into the application.
  2. Extract the Metadata changes made via TASK, EXTRACT APPLICATION in the Application Module of the Corrupt Application.
  3. Extract a recent data or journal changes if possible.  (This is done via the Database Module and Journal Module respectively). 
  4. Manually check the integrity of any data extracted as the application damage may have rendered this data incorrect.
  5. Restore a clean verified back-up which does not exhibit the problem seen.
  6. Load the Metadata and Data and Journal Extracts taken above. (Ensure no other users are connected to the restored application when the Metadata is loaded).
  7. Verify the data in the restored application is correct. 
  8. Back this application up.
  9. While there are no users on the Corrupt Application Delete the corrupted application folder and replace with the corrected restored application files. 

Hi David,

Ok great thanks.

Kind Regards
Ben

 

Hi Ben, I called your office on Friday to catch up. I’ve managed to find where the issue was/is.

 

With vWorkspace disabling printer pass through isn’t as simple as with Citrix.

 

Once that had been sorted individually to the Hyperion RDSH and we relied just on the printers on the server the selection works and all printers are fine.

 


Enterprise Issue When Validated Sub-Accounts Are In Use Not All Validated Data Is Extarcted 

 Modified 02-DEC-2010     Type PROBLEM

Applies to:

Hyperion Enterprise - Version: 6.3.0.0.00 and later   [Release: 6.3 and later ]
Information in this document applies to any platform.

Symptoms

Extract of Data does not include All validated Sub accounts.

An extract is attempted using a name list and an account list. The account list contains validated sub accounts which only contain certain data for certain members of the entity list in use. Dependent on the order in which the Account List and Entity List are selected in the DataBase module and the Entity Point of View (POV) in the Database Module . Varying amounts of data are extracted, i.e. not all validated sub accounts which contain data for all the entities in the chosen entity list are extracted.

Cause

As with all validated sub accounts, the sub accounts which display data very entity to entity. When data is extracted from various POV the data available to extract will very depended on how the list used to extract data are chosen and which accounts are available to the POV Entity.

A setting is available to force Oracle Hyperion Enterprise to evaluate all validated sub accounts for all the entities in the selected lists.



Solution

There is a setting which forces Oracle Hyperion Enterprise (Enterprise) to evaluate ALL validated sub accounts for ALL entities in the chosen Account and Entity List.. 

To Resolve the issue 

Log out of Enterprise and all related modules (Retrieve, Reporting etc)

Add the line below into the default section of Hypent.ini for an affected user..

This file in located in the Windows folder a fat client machine for versions prior to 6.5.1, The hypent_home folder for version 6.5.1 and later. If citrix/terminal server is in use, the file will be located in either the PROFILE folder of the user or their HOME folder. The file can be edited using Notepad or similar text editor. Before making changes, take a back-up of the file first


Add the line below into the default section of the file at the TOP after the line [DEFAULT]

APP_PRE_DATA_EXTRACT_VIEW_VALIDATED_ACCOUNT_CHECKBOX=1

Then re-start Enterprise to force a read of the hypent.ini file.
Once in place the setting should force an extract of all Validated Accounts for all Entities in chosen lists.

Error 'Cannot Create Device context' When Printing to HRPRINTER From Hyperion Enterprise Or Hyperion Enterprise Reporting

 Modified 17-MAR-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 6.5.0.0.00 - Release: 6.5
Information in this document applies to any platform.

Symptoms


Error 'Cannot create device context error' when printing to the HRPRINTER from Hyperion Enterprise or Hyperion Enterprise Reporting

Cause

GhostScript has not been installed

As per the release documentation, GhostScript 8.54 (or later) is a required component for HRPRINTER functionality.

Solution


Download and install GhostScript version 8.54 or later.



Error 'Cannot Create Device context' When Printing to HRPRINTER From Hyperion Enterprise Or Hyperion Enterprise Reporting

 Modified 17-MAR-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 6.5.0.0.00 - Release: 6.5
Information in this document applies to any platform.

Symptoms


Error 'Cannot create device context error' when printing to the HRPRINTER from Hyperion Enterprise or Hyperion Enterprise Reporting

Cause

GhostScript has not been installed

As per the release documentation, GhostScript 8.54 (or later) is a required component for HRPRINTER functionality.

Solution


Download and install GhostScript version 8.54 or later.



Error 'ERROR DISPATCH 101#' When Loading A Formula Extract Into Hyperion Enterprise 6.5 Or Above

 Modified 17-MAR-2010     Type PROBLEM    

Applies to:

Hyperion Enterprise - Version: 6.5.0.0.00 - Release: 6.5
Information in this document applies to any platform.

Symptoms


Receiving "IDispatch Error 101# " when loading a formula extract from a version prior to 6.5 into 6.5 or later

Cause

This occurs when a line in the source file contains a comment (shown by the exclamation ! sign) followed later by an ampersand (&). The ampersand is used to wrap the comment onto the next line due to its length. It is the & which throws the error.

Solution


When attempting to load the file, the error log should list the lines which are erroring.
Open the formulas file in a text editor and navigate to those lines.

Pre-correction the line will appear as:
#account=Formula ! a long comment which is wrapped &
onto the next line

Correct the line to appear as:
#account=Formula ! a long comment which is wrapped onto the next line


Only the & which appear after a comment (!) need to be removed



Error "Print Engine Error – Cannot Create Driver" when Printing from Hyperion Enterprise

 Modified 04-FEB-2009     Type PROBLEM  

Created from <SR 3-842320141>

Applies to:

Hyperion Enterprise - Version: 4.3.2.0.00 to 6.5.0.0.00 - Release: 4.3 to 6.5

Information in this document applies to any platform.

Symptoms

Unable to print to an HP LaserJet 2420 printer from Hyperion Enterprise and Hyperion Enterprise Reporting.
Error: "Print Engine Error – Cannot Create Driver"

Cause

The HP LaserJet 2420 uses a PCL6 printer driver

The latest PCL6 printer driver was not being used

Solution

Download the latest compatible printer driver from

http://h20000.www2.hp.com/bizsupport/TechSupport/Product.jsp?lang=en&cc=us&taskId=135&prodTypeId=18972&prodCatId=236252



Error when viewing the Ledgerlink Error Log, "HPPLINK.ERR Could Not Be Found"

 Modified 13-OCT-2010     Type PROBLEM   

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 and later   [Release: 5.0 and later ]
Information in this document applies to any platform.

Symptoms


When trying to view Ledgerlink error file, An error "HPPLINK.ERR could not be found" is given.

Issue occurs after data has been loaded and errors generated while trying to view the LedgerLink error file thus produced.


Cause


When the error log is viewed in Ledgerlink, the program uses the Windows file Association with the file type .ERR to open a suitable editor to display the file.

If this association is not to a text editor, an error can be generated. 





Solution


In order to open the HPLINK.ERR file, Oracle Hyperion Ledgerlink requires a suitable text editor to be associated with the .ERR file extension.

To achieve this perform the following steps.

1.  Run Windows Explorer.
2.  Browse to the Application\ Inbox  folder for one of the applications in use.
3.  Locate the HPLINK.ERR file.
4.  Right mouse click on the file.
5.  Select OPEN WITH.
6.  Select CHOOSE PROGRAM.
7.  Select ALWAYS USE THE SELECTED PROGRAM TO OPEN THIS KIND OF FILE...
8.  Browse for your preferred text editor. (Notepad or WordPad work well.)
9.  Select OK.

Test the association by double clicking on the HPLINK.ERR in Windows Explorer file and ensuring the editor associated with the .ERR file extension opens the file.

Once Windows has associated a suitable program with the file type, when the error log is viewed from the Ledgerlink POP up box, the editor will open the file..


Note: These steps will need to be taken on all machines where Legderlink is RUN including Citrix/Windows Terminal Servers if used.





Error: "Access to entity denied" when clicking on a Data Entry module
The category .dat file size is large indicating that there is data
Application is on a server
Error only occurs in one category
Cannot consolidate
Database module shows status NO DATA

Solution:

1. After checking that no users are logged in to the application, in Application Module, select TASK -> RUN USERS IN APPLICATION REPORT

2. Test by copying the entire application directory on a local machine

3. Launch Hyperion Enterprise and at the login screen select ADD APPLICATION from the drop-down menu

4. Browse to the local copy of the application and login

If local copy of the application is accessible as normal, reboot the server housing the Hyperion Enterprise application.


Error: "Class not registered" when Going into Database and Data Entry Module

 Modified 18-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Enterprise

Symptoms

Error: "Class not registered" when going into Database and Data Entry modules.

Changes

  • Installed new version of Hyperion Enterprise.
  • Changed path variable for workstation.
  • Moved Hyperion Enterprise program files to a different folder.

Cause

A compatible version of the HELOGENG.DLL file cannot be found or has not been registered properly with the Microsoft Windows operating system.

Solution

To fix this error, find where the HELOGENG.DLL is located (should be in the Hyperion Enterprise programs directory) and register it with the Microsoft Windows operating system. 



References

NOTE:585946.1 - Information About the HELOGENG.dll File For Oracle's Hyperion Enterprise



Error: "Component Transfer Error" While Performing a Workstation Installation of Hyperion Enterprise [ID 1067861.1]

 Modified 17-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 and later   [Release: 5.0 and later ]
Information in this document applies to any platform.

Symptoms


Error: "Component Transfer error"  received while performing a workstation installation of Hyperion Enterprise.

Cause

The shared target folder (Hyperion Solutions ) in the server has not been given FULL CONTROL for the user who is performing a workstation installation of Hyperion Enterprise.


Solution

The installer should have FULL CONTROL over the executable folder:

1) Navigate to the target folder (Hyperion Solutions folder) in the server.This folder is generally shared.
2) Right Click on target folder and click properties.
3) Click on the sharing tab
4) Click on Permissions
5) Add the installing user and Assign FULL CONTROL .
6) Also make sure the user has FULL CONTROL clicking on the security tab.



Error: "Could not get Operating System info" When Installing Hyperion Enterprise Reporting

 Modified 07-APR-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise

Symptoms

Error: "Could not get Operating System info"
Error occurs when trying to install Hyperion Enterprise Reporting.

Cause

The operating system is not compatible with the version of Reporting being installed

Solution

Check the installation guide to find a compatible operating system for the version being installed



(checked for currency on 7 April 2010)



Error: "Could not load wizard specified in /wizard.inf(104)" When Doing a Complete Installation of Oracle's Hyperion Enterprise on a Citrix Server 

 Modified 17-JAN-2011     Type PROBLEM

 

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 to 6.5.1.0.00 - Release: 5.0 to 6.5
Information in this document applies to any platform.

Symptoms

Error: "Could not load wizard specified in /wizard.inf(104)" When Doing a Complete Installation of Oracle's Hyperion Enterprise on a Citrix Server.

Cause

The local user profile path is incorrect.

Solution

In the Environment Variables, the Temp location for the user variables needs to be changed.

Default would be %USERPROFILE%\Local Settings\Temp 

This change has to be done to the drive location where the Hyperion Enterprise installation files reside.


Example: If the user is installing to D Drive , then the location would be as D:\Temp


Show Attachments Attachments


 HE_InstallError.rtf (3,844.03 KB)



Error: "Error occurred while attempting to compress and then add a file to c:\program files\HyperionSolutions\Hyperion Enterprise\Enterprise\SITES\work\DAT~HQ_.ZIP"

 Modified 25-MAY-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise

Microsoft Windows (32-bit)

Symptoms

Error: "Error occurred while attempting to compress and then add a file to c:\program files\Hyperion Solutions\Hyperion Enterprise\Enterprise\SITES\work\DAT~HQ_.ZIP"
Error: "sites.exe has encountered an error and needs to be closed"

Cause

DFS (Distributed File System) is installed on the server on which the application folder is located

Solution

DFS Technology was introduced by Microsoft to facilitate WAN management of data and server locations.  DFS uses a generic form to reference the location of the application in the hypent.ini file.  This generic form is not recognised by the SITES module and the data transmission fails.  The workaround is to reference the application path in the hypent.ini file using either unc or a drive letter



Error: "failed to initialize FrontPage" When Using Hyperion Enterprise Reporting Web Server Web Site Wizard [ID 597350.1]

 Modified 26-JAN-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise Reporting

Symptoms

error: "failed to initialize FrontPage" when using Hyperion Enterprise Reporting Web Server Web Site Wizard.

Cause

Microsoft FrontPage is not installed or incorrect version is installed.

Solution

Check the Add-in Applications in the system requirements section of the Hyperion Enterprise Reporting Installation Guide for compatibility information on Microsoft FrontPage.




Error: "failed to initialize FrontPage" When Using Hyperion Enterprise Reporting Web Server Web Site Wizard

 Modified 26-JAN-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise Reporting

Symptoms

error: "failed to initialize FrontPage" when using Hyperion Enterprise Reporting Web Server Web Site Wizard.

Cause

Microsoft FrontPage is not installed or incorrect version is installed.

Solution

Check the Add-in Applications in the system requirements section of the Hyperion Enterprise Reporting Installation Guide for compatibility information on Microsoft FrontPage.




Error: "Instruction at "x024332b2?" to reference memory in "0x2667d50". The memory cannot be "read"." Occurs when Opening an Application

 Modified 15-JUN-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 4.3.2.0.00 to 6.5.1.0.00 - Release: 4.3 to 6.5
Information in this document applies to any platform.

Symptoms


Error:" Instruction at "x024332b2?" reference to memory in "0x2667d50". The memory cannot be "read"." appears when attempting to open an application.

Changes

Hypent.ini file copied from another machine or edited manually.

Cause


Corrupt hypent.ini file.

Solution

Create a new hypent.ini file by performing the following steps:

  1. Rename the corrupt hypent.ini  fie located in the local windows folder of the machine or, if using Terminal Services or Citrix, in the user profile folder or Home folder.
  2. Launch Enterprise.
  3. From the Hyperion Enterprise Login dialog box, select Add Application from the Application drop-down list box.
  4. Select the database driver for the application you want to add, then click OK.
  5. To add an application stored on a file server or a stand-alone PC, specify the drive and directory where the application is stored.
  6. Select OK.
  7. To open the application, select OK.
  8. Set a Point of View by selecting a category, period, organisation, entity and account.  This will create a new hypent.ini file in which these settings will be saved.
  9. Exit enterprise to save the new point of view settings to the new hypent.ini file.



Error: "No MODAPPDLL Parm: OpenAppp error" When Logging Into An Enterprise Application

 Modified 11-FEB-2011     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 to 6.4.1.0.00 - Release: 5.0 to 6.4
Hyperion Enterprise - Version: 5.0.1.0.00 and later    [Release: 5.0 and later]
Hyperion Enterprise Reporting - Version: 3.6.0.0.00 and later    [Release: 3.6 and later]
Hyperion Enterprise - Version: 4.3.2.0.00 to 6.5.1.0.00   [Release: 4.3 to 6.5]
Information in this document applies to any platform.
This knowledge document is a replacement for 591925.1, 592870.1, 593198.1, 590371.1 which have been deleted.

Symptoms

When logging on to an Enterprise application receiving the error: "No MODAPPDLL Pam: OpenAppp error" is received.

Cause

This error means that Enterprise can not find the listed application at the application path defined, therefore it is unable to open it. Enterprise needs to be directed to the correct path.

Common causes of this are:

  • The physical application has been moved to a new location
    E.g. the application was located on C:\Hyperion\Applications and has been moved to D:\EnterpriseApps
  • User rights to the application location have been changed (restricted)
    E.g the user has no rights to the folder where the application is and therefore can not read and write to the files.
  • The application has been renamed.
    E.g. the application was called Demo6 but has been renamed to Demo7. Enterprise will still be looking for Demo6.

Installation of the security update 917422 (MS06-051) on a computer that is running Windows 2000 Service Pack 4 and that has Terminal Services enabled:

  • These programs cannot read their initialization (.ini) files. Therefore, the settings or parameters for these programs may not be correct when these programs start.
  • These programs cannot write to their initialization (.ini) files. Therefore, these programs cannot save their settings or parameters.
  • These programs cannot create temporary (.tmp) files.


Retrieve specific:

  • The application name in the HPAPP.DAT does not have the exact spelling of the application name as defined in the <Application>.ini.


Hyperion Enterprise Reporting Web specific:

  • Enable Distributed COM on this computer" is not selected.


Enterprise Sites specific:

  • The name of the application at the site and the name at the HQ don't match


Solution

 

Firstly ensure the user has full rights to the application folder and sub-directories:

1) Launch Enterprise and from the logon drop-down select Add Application. 

2) Select File-based (or SQL if an SQL Application).

3) Browse to where the application is located.
 
4) Select the ApplicationName.exa file. 

5) Select Open.
 
6) A warning will appear that the current application will be overwritten. This is not overwriting the data just the path to where the application is. Select Yes.
 
7) Log into the application as normal.


Note: This will need to be done on each machine that gets the issue.


If the error is received when using Retrieve:

HPAPP.DAT does not show the exact application

1. In a text editor, open the <Application>.ini, where <Application> is the name of the Enterprise database.

2. Highlight the application name excluding the brackets on 1st row of this file and select EDIT->COPY or Ctrl+C to add to the clipboard.

3. Open the HPAPP.DAT file and paste over the Application Name and save changes.

Using this method will ensure that the application name defined in the HPAPP.DAT precisely matches the [APPNAME] in the <Application>.ini.


If the security update 917422 (MS06-051) has been installed:

Please check the following on Microsoft's knowledgebase: http://support.microsoft.com/kb/924066

Additional workaround:

Copy a user's hypent.ini file that includes all desired applications and paste it into the C:\WINNT directory of the Terminal Services / Citrix server.


If the error is received when  using Hyperion Enterprise Reporting Web:

1. Access the Distributed COM Configuration Properties: START -> RUN -> type 'dcomcnfg' -> ENTER

2. On the DEFAULT PROPERTIES tab select "Enable Distributed COM on this computer". (This should be enabled by default).

3. Recycle internet services.


If this error is received when using Sites (This option has been removed from version 6.5 onwards):

The applications must have the same name at sites and HQ

1. Send a new copy of the application to the Site/HQ or rename the application using a supported method.



Error: "No numerical value exists for the MISC field of the Component Definition of : CSS" During Installation of Oracle's Hyperion Enterprise 

 Modified 18-JAN-2011     Type PROBLEM     Status PUBLISHED 

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 and later   [Release: 5.0 and later ]

Microsoft Windows (32-bit)

Symptoms

Error: "No numerical value exists for the MISC field of the Component Definition of : CSS"

Cause

The "Modify Selectable Components" option was selected when installing the software for the first time.  This option should only be selected when re-running an installation.

Solution

  1. Delete the *.TAG file created when the "Modify Selectable Components" is selected from the installation directory
  2. Re-install the software again but this time select "Complete Setup " select the components you want to install




References

NOTE:589094.1 - Reversing the Effects of Having Selected the Option "Modify Selectable Installation Components" During Installation of Hyperion Enterprise
NOTE:591363.1 - Error: "Component selection has not been modified. Operation unsuccessful" Occurs During Installation of Oracle's Hyperion Enterprise



Error: "None of the drivers specified in the .ini file were loaded. Driver hpred32.dll. Error code 0126L" When Launching Hyperion Enterprise Reporting

 Modified 30-JUL-2010     Type PROBLEM   

Applies to:

Hyperion Enterprise

Symptoms

Error: "None of the drivers specified in the .ini file were loaded. Driver hpred32.dll. Error code 0126L"
Error when launching Hyperion Enterprise Reporting
New installation of Hyperion Enterprise
New Installation of Hyperion Enterprise Reporting

Cause

In the Path statement in the System Environment Variables the paths to the directories where the executables for Hyperion Enterprise Reporting and Hyperion Enterprise are stored were not placed at the beginning of the path.
The client had two paths to reporting specified in the Path statement in the System Environment Variables.

Solution

The path statement must contain only one reference to the Hyperion Enterprise Reporting folder, and this should be at the beginning of the path. 

If there was an earlier version on the same machine in a different folder then it is vital that references to the old programs be removed completely.



Error: "Prior period not in OK, Changed or NODATA State"
Some entities are locked in the prior period
Some entities are inactive in the prior period
Ownership by Period and Category is selected

 

Changes that have been made:

New dependents have been added to the organization

Reason for Problem:

The prior period has IMPACTED entity or entities which cannot be consolidated because entities above are LOCKED

Solution:

Calculate formulas on the dependent of the locked entity

If there is no data in the new dependent select TASK -> ERASE

The dependent should also be locked. There should be no unlocked dependents if the parent is locked.


Error: "The application or the dll C:\Program Files\Hyperion Solutions\HERES.dll is not a valid windows image. Check help in your installation program" When Installing an Enterprise Patch

 Modified 07-FEB-2011     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 and later   [Release: 5.0 and later ]

Symptoms

Error: "The application or the dll C:\Program Files\Hyperion Solutions\HERES.dll is not a valid windows image. Check help in your installation program"
Error occurs when trying to install Enterprise patch
Note this is a generic error that can occur with multiple product/patch versions where the patch install is supported by a Install Shield program and the patch is released in multiple language versions.

Changes

A patch installation was attempted.

Cause

The language version of the patch does not correspond to the language version of the Enterprise installation.

Solution

The heres.dll is a language specific dll so the language version of the heres.dll needs to match the language version of the Enterprise installation.

Refer to the Patches and Updates Tab on the My Oracle Support Portal to obtain the correct language version of the patch you are attempting to install.


Error: "VERGETFILEVERSION API FAILED" During Uninstall of Oracle's Hyperion Enterprise

 Modified 18-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 to 6.5.1.0.00 - Release: 5.0 to 6.5
Information in this document applies to any platform.
Regedit

Symptoms

When uninstalling Hyperion Enterprise by [Add or Remove Programs] in Control Panel, it gives Error: "VERGETFILEVERSION API FAILED" and fails to uninstall.

Cause

Possible Causes:
1.Lack of Heapi.dll in Hyperion Enterprise installed folder.
2.Hyperion Enterprise uninstallation file broke or parts of registry keys for Hyperion Enterprise broke.

Solution

Solution1:

1. Copy Heapi.dll from other machine to the problem machine, then uninstall the old version enterprise.

Solution2:

Delete the old version enterprise manually.
1. Delete the related registry keys: uninstall registry
a. Hyperion Enterprise:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A713F236-6F27-4779-AD70-C1290CBC99B6}]

b. Hyperion Common Logon:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{D337768B-4627-11D5-9953-00500466E4ED}]

c. Hyperion Enterprise Reporting Windows Client:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EDDBB48A-3A68-11D5-992D-00500466E4ED}]

2. Backup the Hyperion Solutions folder, then delete the folder.
for example:
C:\Program Files\Hyperion Solutions
->
C:\Program Files\Hyperion Solutions_bak

3. Reboot the machine.
Postscript: if you use messenger server or application server, you also need to delete the service from registry by command: [sc delete]






Error:" Component 'MoveData Error Number: XXXXXXXX'" When Installing Hyperion Enterprise

 Modified 07-FEB-2011     Type PROBLEM 

Applies to:

Hyperion Enterprise
Hyperion Enterprise - Version: 5.0.1.0.00 and later ]

Symptoms

Error:" Component 'MoveData Error Number: XXXXXXXX'" when installing Hyperion Enterprise

Where XXXXXXXX may be any numeric value.

This error may occur at any stage of the installation.

The installation aborts.

Changes

An installation is run from downloaded media or legacy CD ROM.

Cause

The installation media is corrupt or the installation process cannot write files to the target machine.

Solution

  1. Verify file integrity of source media (can this media be installed on a different machine).
  2. Download the media again if integrity issues suspected.
  3. Check the user identity running the install has Administrator rights on the target machine.
  4. Ensure all users are out of the systems on the client or server machine being installed to.

If the above does not resolve the issue contact Oracle Support.




Error:"Hyperion Enterprise Backup/ Restore is in progress , please try again later" When Logging Into Hyperion Enterprise Application

 Modified 08-JUL-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 6.5.0.0.00 and later   [Release: 6.5 and later ]
Information in this document applies to any platform.

Symptoms

Unable to login to Hyperion Enterprise application due to Error:" Hyperion Enterprise Backup/ restore is in progress, please try again later".

Cause

The application is locked due to a backup running, access will be restored when the backup is complete.
If the backup has completed or is not running, then it is possible the server was rebooted during the backup and the application.ini file is still indicating that the backup is running when it has in fact finished.


Solution

Ensure the backup process is not still running. Check the back-up schedule and check the back up file set is not still growing.

When a back up is running the application.ini file will state.

APP_BACKUP_ISRUNNING="1"

If the backup process has stalled and not finished, then this line is NOT reset to 

APP_BACKUP_ISRUNNING="0"

Make this change manually, if  the line in the application.ini file is reflecting the wrong status.



Error:"Record Translation Error. Continue with translation?"

 Modified 13-OCT-2010     Type PROBLEM

Applies to:

Hyperion Enterprise

Symptoms

Error: "Record Translation Error. Continue with translation?"

Cause

Possible Causes:

A.  External Entity list in lower case
B.  Coma missing from the source file when selecting coma delimiter

Solution

Solution A

Change the External file entity list to uppercase before translation is undertaken.

Solution B

Add coma after the field which needs it.





Extracted Data Lines are not all Converted correctly by Selected Entity Conversion Table

 Modified 13-OCT-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 5.1.1.0.00 and later   [Release: 5.1 and later ]
Information in this document applies to any platform.

Symptoms

When a Data Extract is made using an old Entity Conversion Table not all lines of  the extract are converted properly i.e. they are not converted at all. Some lines do convert correctly.

During past maintenance of the application entities within the Entity conversion tables were deleted. Prior to deletion of Entities, the Entity Conversion Tables were not purged of the redundant Entities.

Cause


The Entity Conversion Tables contain Entities that are no longer in the Application and which were never purged for the Conversion Tables.


Solution

The cause of the instability of the Entity conversion table showed that there were previously deleted entities in some Conversion tables that were not visible in the Oracle Hyperion Enterprise GUI but manifested themselves as 'Invalid Enterprise Entity' messages when the extract of Conversion Tables was loaded.

Two solutions to this problem are available.

Before proceeding ensure no users are working in the application and you have a valid back-up.

Solution A delete and re-create existing conversion tables


A1, Navigate to the Application Module from the Oracle Hyperion Enterprise Desktop.
A2, Select TASK
A3, Select EXTRACT APPLICATION.
A4, Deselect the 'ENTIRE APPLICATION Check Box of the Extract Application Window.
A5, Under the ENTITIES tag Select ENTITY CONVERSION.
A6, Back at the FILE tag , give the file a suitable name.
A7, Select OK and allow the extract to run.
A8, Access the Extract file and open in a suitable TXT file editor (Notepad.exe  or similar)
A9, The format of the file will be as follows for an extract conversion table . 
NOTE  For an import conversion table the External/Internal conversion is reversed.


[Econv=conversion table name   !Description

External Entity  !Enterprise Entity 
External Entity2 !Enterprise Entity2

etc etc.


The second column after the delimiter contains the entities that MUST be available in the Application. If they are not the error is produced.

Each of these 'Missing Enterprise Entities' need to be corrected and changed to valid Enterprise Entities or removed.

Hint :- To test the file for non existed Entities, load the Extract file of Conversion Tables file and trap the errors that are generated from the error.log file.


A10, Once the extract file is cleaned proceed as follows.
A11, From the Entities Module
A12, Select NAVIGATE
A13, Select Entity Conversion Tables.
A14, Open Any Table by highlighting it and pressing OK
A15, From the File Menu , Select and delete all Entity Conversion Tables. (Removing them from Database Formats they are attached to if needed)
A16, Return to the Application Module 
A17, Select Task,  Load Application 
A18, Re-load the  corrected extract file of Conversion tables to re-create the Conversion Tables.
A19, If the Conversion Table names were removed form Database Formats..Re-add them at this point.

Verify the Conversion Tables are working by running an Extract or Load of Data using the Formats that apply them.

Solution B  Create New Entity Conversion Tables


Follow the same steps as solution path A but

B1 While editing the Conversion Table Extract, Adjust the conversion table NAME field to a new desired name.
B2, Negate step A15, the deletion step.

If new Conversion Tables are created, the Database Formats calling these tables Must to changes to the NEW Conversion Table Names.

B3, Enter the Database Module
B4, Select FILE
B5, Select OPEN FORMAT
B6, Open each Format in turn and change the Entity Conversion Table to the newly created appropriate Entity Conversion Table.
B7, Again as in Solution A, verify the Conversion Table works as expected.


When extracting data from the Database module, data is extracted multiple times and is incorrect when reloading

Data Extract is showing values multiple times

 

Reason:

 

Extracting data using an Entity List that has duplicate entries

Solution

When creating the Dynamic Entity List, do not check the box "Duplicate Entries" under the "Allow in list" section. This will prevent duplicate entities from being added to the dynamic list.


FDM Check Report Returns Periodic Values in Hyperion Enterprise When Requesting YTD 

 Modified 06-MAY-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms


   When attempting to retrieve a value for a target intersection from Hyperion Enterprise for the FDM Check Report, the value that is returned is always the Periodic value and not the CAT/YTD value in Enterprise.  Hard coding the view in the validation rule to CAT or YTD still returns periodic values.

Cause


   The cause of the issue is a unpublished bug (6578866) in the HE6x-G4-D adapter.  This version of the adapter contains a bug which only retrieves Periodic data from Enterprise, no matter what view is specified in the validation rule builder.  The issue has been resolved in the HE6x-G4-E adapter which is supported for use with FDM 9.3.1-11.1.1.3


Solution


   A) Download the Adapter Suite for FDM version 11.1.1.3 from E-Delivery
B) Extract the contents of the adapter suite to extract the HE6xG4E.zip file, extract the contents of the .zip file
C) Import the HE6xG4E.xml file into the FDM application using the File/Import functionality in the workbench client.
D) Choose File/Register Adapter and copy the upsHE6xG4E.exe file to the Hyperion/Products/FinancialDataQuality/SharedComponents folder and open the file to register it.
E) Sync the adapter with the current HE6xG4D adapter
F) Choose Administration > Application Settings and set the system code to HE6xG4E



FDM Error Integrating with Hyperion Enterprise "Error 2509 Hyperion application named not found in hypent.ini."

 Modified 19-APR-2010     Type PROBLEM  

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.0.0.00 and later   [Release: 9.3 and later ]

Generic Windows

Symptoms

When attempting to perform any integration with Hyperion Enterprise from within FDM by browsing for a target value in the mapping table or browsing for a target value in the period/category table, end users receive an error.  The error message states:

"Error 2509 Hyperion application named <appname> not found in hypent.ini."

Cause

The message indicates that the Hyperion Enterprise application that FDM is currently set to integrate with, is not found in the hypent.ini file on the FDM application server.  In order for Enterprise to successfully open the application, it must be listed in the hypent.ini file on the FDM application server.  Currently the application listed in the Administration/Integration Settings/App Name field is not contained in the enterprise hypent.ini file on the FDM application server for the FDM service account.

Solution

1) Login to the FDM application server as the FDM service account

2) Launch the Hyperion Enterprise win32 client

3) Currently the Enterprise Application name listed in the Integration Settings menu is not an available application to login.  The application will need to be added.

4) Choose <Add Application> and login with a valid enterprise user and click OK

5) Choose File - based Application and click OK

6) Browse to the location of the Application folder for the enterprise application and select the applications .EXA file.  (C:\Program Files\Hyperion Solutions\Hyperion Enterprise\<Appname>\<Appname.exa>)  Click Open

7) The application will now be listed in the hypent.ini file on the server.  Verify the ability to login to the Enterprise application.



Figures imported from CDA retrieve into the database are not being scaled

 Modified 15-NOV-2010     Type PROBLEM     Status PUBLISHED 

Applies to:

Hyperion Enterprise

Symptoms

Figures are being imported from CDA retrieve into the database and are not being scaled
The issue seems to be only with certain Citrix Metaframe users
In Hyperion Database module Figures are not being scaled

Cause

Every Citrix user has their own HECDAREP.ini, if not they use the default HECDAREP.ini. In the HECDAREP.ini the option to set scales in CDA retrieve is stored

Solution

Copy the HECDAREP.ini file from a Citrix user who is not experiencing the problem to one that is. Alternatively open the HECDAREP.ini file on the Citrix server in the user profile directory. For the particular user on Citrix modify or add the line:


ScaledValues=0 Displays worksheet values in non-scaled format, even if the values are scaled in the Hyperion product.
ScaledValue=1 Display worksheet values in a scaled format if the values are scaled in the Hyperion product.


Treasury in Greencore is held in two categories.

Current year, consisting of 65 weeks, being weeks 1 to 53 in current year, and then periods 54 to 65 being week 1 to 12 in the next year, And TreasuryLY (last year) consisting of 53 weeks.

We cannot simply use the rollover function as Treasury Last Year has fewer periods than current year. 

Please ensure that after the Rollover function has completed the category "Treasury" contains "WK1" within the "Start Period" field. If not please run through the following steps:

locked all users out and closed all enterprise instances.. (we had Extracted the data as a backup.)

Navigated through explorer to the application/data folder, renamed treasury relaunched hyperion, changed the start of the category to wk1, saved and closed.

Renamed category in explorer, re-opened enterprise and checked dates.

Then launched schedules and checked data was intact and reports were correct.

Once the Rollover has been completed and the "Treasury" category has the correct start week. Please continue with the following:

 

 

So we have to move the data manually. Set POV to Treasury, set organisation and Top company, select entity list all input.

Highlight all periods, select include calculated and global and set decimals to 5 , extract.(this is a backup) Repeat for periods 1 to 53, and then a separate extract for periods 54 to 65.

Open the extract file for weeks 1 to 53 and change the category to TreasuryLY, save Open the extract file for weeks 54 to 65 and change the Periods to 1 to 12, save Navigate to desktop/application/task/run rollover Ensure all users are out of the system Select the Treasury rollover set and run. this will zero both categories and increment the years by 1 Now load the two extract files to recreate TreasuryLY, and the first 12 weeks of this year.

consolidate all orgs for the treasury categories, lock periods as required.

 

How to Configure and Setup DrillBack from Hyperion Enterprise (HE) into Hyperion Financial Data Quality Management (FDM)

Configure Enterprise 6.5.1

  • Enable FDM Settings
  • Populate FDM Server URL
  • Populate FDM Adaptor Key
  • Populate FDM Application Name

Configure FDM 11.1.1.3.00

  • Add VBScript Authentication to FDM LoadBalance Manager
  • Add VBScript SSO Authentication to FDM LoadBalance Manager
  • Enable DrillBack Integration Option

Test Functionality

  • Ensure POV in Enterprise is Blank
  • Import file into FDM
  • Validate file in FDM
  • Export file from FDM into Enterprise
  • Test Drillback from Enterprise

How to create/Define Entity Conversion Tables in Hyperion Enterprise

 

Solution:

Entity conversion tables are used to translate external entities into Hyperion entities and vice versa when loading or extracting data via the Database module.

Considerations:

1. Can create and label new tables or modify information in existing tables.
2. Each entity conversion table must have a unique ID.
3. An entity conversion table can be defined as load only, extract only, or both load and extract.
- A load only table can be defined so that many external accounts can be loaded into one Hyperion Enterprise account. (Many to One)
- An extract only table can be defined so that many Hyperion Enterprise accounts are converted into one external account. (One to Many)
- A table that can be used to either load or extract data can only be defined with one to one relationships.
4. Once a table has been created, its description and security class can be changed by selecting FILE->TABLE ATTRIBUTES. However, the load and/or extract selection cannot be changed.

To define an entity conversion table:
1. From within the ENTITIES module, select NAVIGATE->ENTITY CONVERSION TABLES and do one of the following:
a. To create a new table, select FILE -> NEW TABLE
b. To edit an existing table, highlight the desired table and hit the OK button and then select FILE->TABLE ATTRIBUTES.

2. If a new table, specify the ID, description, security class, and table type, then select OK. If an existing table, changes can only be made to description and security class.

3. Add or change the entities in the table:
a. To insert a row in table, highlight the cell above which the new row is to be inserted. Then select EDIT->INSERT ROW.
b. To paste a Hyperion Enterprise entity:
- Select EDIT->PASTE ENTITY - Select an entity from the dialog box - Then select OK.
c. New rows can be added to the end of the table by simply entering information.

4. Select FILE->SAVE to save changes.

How to delete an Account List in Hyperion Enterprise.

 

Solution:

  1. Click on Accounts Module.

  2. Go to Navigate->Account Lists.

  3. Choose the Account Lists to keep.

  4. Go to File->Delete List.

  5. Choose the Account Lists to delete and hit OK.

Please note these steps are specifically for Applications that DO NOT use Active Directory for user Access. It is only for Native user access.

1. Locate the recently replace application.

2. Make sure that the following files as well as the application folder itself are the same name. For example the application folder is called Spark2_210814 Spark2_210814.EXA Spark2_210814 - This is the .ini Config file. It does not display a file type like the others. However make sure the first 4 lines have been updated with the application name and path. Spark2_210814.LOK Spark2_210814.mdb Spark2_210814.USE

3. Log into Entperise(current Live application - Spark2). Alternatively from the Enterprise logon screen, select Add Application and go to point 6.

4. Go to Open Application.

5. Click on Add

6. A Window will pop-up asking the type of applicaiton to add. Please select "File-based Application". Click OK.

7. Browse to find the application (Spark2_210814) folder you want to add.

8. Select the Spark2_210814.EXA file and click Open.

9. You should see the application "Spark2_210814" in the application list.

10. Click OK.

11. Enter your credentials.

12. From the menu select File, Preferences, Application and check that you are correctly pathed to the application, Spark2_210814.

13. Go to Edit - Point Of View.

14. Just simply click on all tabs then click OK.

15. Go to Database

16. Select the POV that contains the data you require.

17. Extract the Data. Note: enter "9" in the decimal field.

18. Saved the .DAT file into the current Live application Inbox.

19. Log into the current Live application (Spark2).

20. Go to Database - Task - Load Data. Note: Tick the "Calculate Formula" option.

21. Check numbers.

22. Once all users have confirmed data is correct go to File - Open Application - Highlight the old application (Spark2_210814) NOT the current Live application. Click on Remove. This only removes the application from the application list in the HYPENT.INI file. It does NOT delete the application. 

Please note these steps are specifically for Applications that DO NOT use Active Directory for user Access. It is only for Native user access.

 

1. Make sure you have the relevant backup restored.

2. Make sure all users are logged off the current Live application.

3. Go to the Folder path location where the application resides. For example: Server\Hyperion65\Spark2

4. Rename the Application. For example: Spark2 changed to Spark2_210814

5. Make sure the backup copy is in the same location as the Live application. For example: Server\Hyperion65\

6. Rename the backup copy, if required, as the Live application. For example: Spark2_190814 change to Spark2

7. Make sure that the permissions on the Live application folder are correct. Users will need to have read and write access. Compare this with the recently renamed Live application.

8. Log into the application and test the consolidations, etc that were giving you the errors.

9. If all is successful please request users to check data, if necessary.

Note: depending on how recent the backup is the users may need to reload their data.

 

Email discussion:

Keith, Tanya, the issue today where no users were able to access the restored Spark2 application is caused by permissions to the restored Spark2 folder. During live operation when users are using the application they have modify permission to the Spark2 folder. When a restore is done, admin users have modify permission to the folder but the other users do not. The other users are all contained within a group and it is a simple change to give them the modify permission they need, just by applying modify to the group. Ryan is going to build this into the restore process notes for any future restores. You should also note this, as we will, because it may not be Ryan who does a restore. Regards Frank

 

 

How to sort accounts in subaccount table

Accounts must be sorted manually as there is no automated tool for this.
Use Insert Row and add the account where needed.

The default Intercompany table cannot be sorted the same way as others.
1.  Extract all data for the Intercompany accounts
2.  Deselect the Intercompany box for the affected entities
3.  Select the Intercompany box for the affected entities in the order you would like them, saving after each one
4.  Load the data back into the Intercompany accounts.


HOWTO : Error: "Cannot delete, category in use" When Trying to Delete a Category in Hyperion Enterprise

 Modified 24-JUN-2010     Type HOWTO      

Applies to:

Hyperion Enterprise

Goal

Deleting a category in Hyperion Enterprise.

Solution

Prior to deleting a category ensure that this category is not mentioned in a rollover.
It is also important that no other users is logged onto this application during the deletion.




Hyperion Enterprise Client Crash In Windows XP

 Modified 31-JAN-2011     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 6.5.1.0.00 and later   [Release: 6.5 and later ]
Information in this document applies to any platform.

Symptoms

Repeated and sudden Client crashes / hangs with newly deployed Oracle Hyperion Enterprise (Enterprise) version 6.5.1

Data vanishes or disappears from the application.

Variants or the error ChappFile Readfrom SysFile returned (followed by a reason string i.e Reached the end of the file): Terminating Current Session.

Note, the reason string may very.

a. The error happens at various times and with various client operations. Data Entry , Consolidation, Reporting,  Database operations such as Locking etc.

b. The system has recently been upgraded and after an event an of the ChappFile message, if the application is restored from back-up, after a short while the issue may return immediately.

c. Data Loss is also seen after some of the noted events and then can re-occur again if the fix for this issue is not applied.

Changes

Recent Upgrade to Oracle Hyperion Enterprise 6.5.1.

Cause

A code issue with File locking was identified in version 6.5.1 which causes the Chapp|File file errors and potentially data corruption/data loss.

The issue can occur under various scenarios where multiple users and or connection are at present.



Solution

In order to resolve the issue of sudden and unexpected ChappFile messages appearing in Oracle Hyperion Enterprise (Enterprise) 6.5.1 the follow software upgrade needs to be applied. 

Patch 9685920  Oracles Hyperion Enterprise Release 6.5.1.0.03 Service Fix...

Please refer to the patch Readme file for full instructions of installing this patch but please note the following.

Once installed if Enterprise is run, from Help menu > About Hyperion Enterprise, the version 6.5.1.0.03.001 is displayed. 

The patch will address the cause of the issue and prevent the error re-occurring on a clean application.

The patch will NOT repair an application which has suffered Data Loss during an incident of the error prior to the patch being installed.

ALL machines running Hyperion Enterprise 6.5.1 need to be patched...Including Citrix/Terminal Servers , Client workstations and Application Servers. Note: Citrix/Terminal Server Workstations which do NOT have a local installation of Enterprise, do not need to be patched.

If the application in question has suffered data loss , then a back-up which was taken prior to the incidents of data loss must be restored or the application re-built in 6.5.1.0.03. if use of 6.5.1 is early it deployment an application conversion from the prior release can also be performed.

Note Chappfile Error Messages may also appear for reasons other than the issues addressed in the patch above. This Patch 9685920: Oracles Hyperion Enterprise Release 6.5.1.0.03 Service Fix is only designed to address ChapFile messages and Data Loss in version 6.5.1. 


This patch is not applicable to prior versions of Enterprise and if these errors persist after the installation of the patch , please contact Oracle Support.



Hyperion Enterprise crashes when an Account Conversion Table is loaded from an text file
No error produced

 

Changes:

Application recently converted from an older version.

Cause:

The account conversion tables have become corrupted.

Solution:

Ensure you have a valid application back-up before following the procedure below.

1. From within the Enterprise Application make an extract of all Account Conversion Tables to a text file.
2. From with the Account module delete all Account Conversion tables in the failing application.
3. Re-load the Account Conversion extract and verify that further loads can then be made.


 


Hyperion Enterprise Crashes When Trying to Load an Account Conversion Table

 Modified 31-MAR-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 5.1.1.0.00 - Release: 5.1
Information in this document applies to any platform.
Loading an Account Conversion Table.

Symptoms


Hyperion Enterprise crashes when an Account Conversion Table is loaded from an text file.

No error produced.

Changes

Application recently converted from an older version.

Cause


The account conversion tables have become corrupted.

Solution

Ensure you have a valid application back-up before following the procedure below.

1. From within the Enterprise Application make an extract of all Account Conversion Tables to a text file.
2. From with the Account module delete all Account Conversion tables in the failing application.
3. Re-load the Account Conversion extract and verify that further loads can then be made.




Hyperion Enterprise Event Logging Database Should Not Contain Special Characters [ID 1222156.1]

 Modified 13-OCT-2010     Type PROBLEM   

Applies to:

Hyperion Enterprise - Version: 3.9.0.0.00 to 6.5.1.0.00 - Release: 3.9 to 6.5
Information in this document applies to any platform.

Symptoms

Getting Error -ORA Error 00911 OR IDispatch error #3902

If the Event log is enabled in the application for Database logging -Data,Meta Data,Security and reports. Then this error comes up. 

Cause

This can be seen from Enterprise server administration-> advanced settings ->APP_TABLE_LOG_NAME->DATABASE LOGGING OPTIONS will start with symbol "_" (Underscore) 

Solution

Removing the special character in the Database name will fix the issue.


Note:This will also occur due to & (Ampersand Symbol) 



Hyperion Enterprise Event Logging Database Should Not Contain Special Characters [ID 1222156.1]

 Modified 13-OCT-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 3.9.0.0.00 to 6.5.1.0.00 - Release: 3.9 to 6.5
Information in this document applies to any platform.

Symptoms

Getting Error -ORA Error 00911 OR IDispatch error #3902

If the Event log is enabled in the application for Database logging -Data,Meta Data,Security and reports. Then this error comes up. 

Cause

This can be seen from Enterprise server administration-> advanced settings ->APP_TABLE_LOG_NAME->DATABASE LOGGING OPTIONS will start with symbol "_" (Underscore) 

Solution

Removing the special character in the Database name will fix the issue.


Note:This will also occur due to & (Ampersand Symbol) 




Hyperion Enterprise Integration With FDM 11.1.2 Fails on Web

 Modified 13-SEP-2010     Type PROBLEM 

Applies to:
Hyperion Financial Data Quality Management - Version: 11.1.2.0.00 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

Enterprise Adapter Returns "Unable to Create Active X Control"
In FDM Workbench, under Integration settings for the Hyperion Enterprise adapter, the Test connection button returns a successful connection to Enterprise. The NameCat tab will successfully allow for setting the base level entity and category.  When clicking on the Dimension Cache Tab and attempting to update the Dim cache the error message

-2147217887 Multiple-step operation generated errors. Check each status value

In FDM Web selecting activities > maps and attempting to browse for a target member returns "ActiveX component can't create object: 'upsHE6xG4F.clsHypeWindow' At Line: 51"


Cause


In order for FDM to establish a connection with Hyperion Enterprise, it first launches the connect action contained within the HE6xG4F adapter, the connect action first looks for a machine profile within the adapter that matches the NETBios name of the FDM application server that the connection is occurring on, it then attempts to launch an instance of the Adapter DCOM object on the machine referenced in the "Target machine" field of the machine profile.  Currently this value is the Enterprise Server name and not the FDM application server name where the adapter .exe is registered.  When the process attempts to establish an instance of the com object it fails because the adapter has not been registered on the Enterprise Server, but is registered on the FDM application server.


Solution

Solution Delivered
A) Login to the FDM application using the workbench client
B) Expand Target System Adapters > HE6x-G4-F > Machine Profiles
C) Open the current machine profile
D) Update the target machine field to the FDM Application server and click OK to save the change



Hyperion Enterprise Retrieve Displays #VALUE with HPVAL Formula

 Modified 11-AUG-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 and later   [Release: 5.0 and later ]

Symptoms

Hyperion Enterprise Retrieve displays #VALUE with HPVAL formula.

The POV settings in Retrieve appear correct

Cause

The actual value in the period option is not the displayed value due to Excel formatting.
Although it appears to be MAR 03 in the formula bar it is really 3/3/04 as an example.

Solution

From within Excel, in the cell which references the period, either enter the period number (i.e.1 for Jan Etc) or use the CHANGE PERIOD option from the RHXL menu to populate the period cell with a correctly formatted period value.

Once done refresh the sheet and ensure the values are now displaying as expected.

Applies to:

Hyperion Enterprise - Version: 6.4.1.0.00 to 6.5.0.0.00 - Release: 6.4 to 6.5
Information in this document applies to any platform.
Regedit

Symptoms

When uninstalling Hyperion Enterprise by [Add or Remove Programs] in Control Panel, it gives [VerGetFileVersion API failed] error and fails to uninstall.

Cause

Possible Causes:
1.Lack of Heapi.dll in Hyperion Enterprise installed folder.
2.Hyperion Enterprise uninstallation file broke or parts of registry keys for Hyperion Enterprise broke.

Solution

Solution1:

1. Copy Heapi.dll from other machine to the problem machine, then uninstall the old version enterprise.

Solution2:

Delete the old version enterprise manually.
1. Delete the related registry keys: uninstall registry
a. Hyperion Enterprise:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A713F236-6F27-4779-AD70-C1290CBC99B6}]

b. Hyperion Common Logon:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{D337768B-4627-11D5-9953-00500466E4ED}]

c. Hyperion Enterprise Reporting Windows Client:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EDDBB48A-3A68-11D5-992D-00500466E4ED}]

2. Backup the Hyperion Solutions folder, then delete the folder.
for example:
C:\Program Files\Hyperion Solutions
->
C:\Program Files\Hyperion Solutions_bak

3. Reboot the machine.
Postscript: if you use messenger server or application server, you also need to delete the service from registry by command: [sc delete]

Hyperion Enterprise Web Logon Fails with "Error: Module not Found in He.hecontainer"

 Modified 19-JAN-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 6.4.1.0.00 - Release: 6.4
Information in this document applies to any platform.

Symptoms


When logging on Hyperion Enterprise Web the following error occurs:  "Hyperion Enterprise Error: Module not Found He.hecontainer".


Cause

This is a coding issue and started to occur after the 1st  of January 2010.

This is unpublished BUG 9259234.

Solution

1. Shutdown Hyperion Enterprise Web and reset IIS.

2. Locate locFuncs.asp at the following locations:

where % denotes your installation drive.

 a. %Hyperion Solutions%\Hyperion Enterprise\HEWeb 
 b. %Hyperion Solutions%\Hyperion Enterprise\HEWeb\modules\com\hyperion\bpm\web\desktop 
 c. %Hyperion Solutions%\Hyperion Enterprise\HEWeb\modules\com\hyperion\he\web\hecontainer 
 d. %Hyperion Solutions%\Hyperion Enterprise\HEWeb\modules\com\hyperion\he\web\hedesktop 
 e. %Hyperion Solutions%\Hyperion Enterprise\HEWeb\modules\com\hyperion\he\web\helogoff 
 f. %Hyperion Solutions%\Hyperion  Enterprise\HEWeb\modules\com\hyperion\he\web\helogon 
 g. %Hyperion Solutions%\Hyperion @ Enterprise\HEWeb\modules\com\hyperion\he\web\hestartup 

3. Take a backup of the original locFuncs.asp.

4. Locate the line: 

Response.Cookies("DisplayLanguage").Expires = #January 01, 2010# 

5.  Replace 2010 with 2030 for the year field: 

i.e., Response.Cookies("DisplayLanguage").Expires = #January 01, 2030# 

6. Perform this change inside locFuncs.asp, located in the folders mentioned in step 2. 

7. Re-boot the server.

8. Retry logging onto Hyperion Enterprise Web to confirm it works as expected. 



Hyperion Enterprise: When Consolidating, Data in an Account Does Not Roll Up to the Parent Level

 Modified 02-AUG-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise

Symptoms

The value in an account at the child level is not rolling up to the parent level when consolidation is run.


Cause

In the method CHART this account has the formula NOINP. This prevents input against this account.
The value is instead coming from another account as per a formula in the TRANS method

Solution

Remove the NOINP from the CHART method and normal consolidation will then apply.



Hyperion Retrieve Appears Twice in Microsft Excel Add-Ins.

 Modified 13-JAN-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 6.0.0.0.00 to 6.5.0.0.00 - Release: 6.0 to 6.5
Information in this document applies to any platform.

Symptoms

Hyperion Retrieve add-in appears twice in the Microsoft Excel > Tools > Add-Ins.

Cause

Hyperion Retrieve appears twice in Excel > Tools > Add-ins if both Retrieve add-ins are selected.

Solution

  • Open an Excel Sheet and go to Tools Add-ins and confirm both Add-ins have been selected.
  • Decide which add-in is needed either rhxll32.xll or heretrv.xla
  • Deselect the undesired add-in 
  • The add-in will be cleared and now only the needed add-in will be listed

Issues Unlocking the Periods within Hyperion Enterprise

 Modified 29-JUL-2009     Type PROBLEM 

Created from <SR 3-868760416>

Applies to:

Hyperion Enterprise - Version: 5.0.0.0.00 - Release: 5.0

Information in this document applies to any platform.

Symptoms


Unable to unlock the data.

Cause


Determined the cause to be a parent entity lock issue.We can unlock the base entity only after unlocking the parent.

As per procedure we have to unlock the parent and then the base entity.

Solution

To resolve this take the following steps.


1) Create a parent entity list .

2) Create a base entity list.

3) Unlock the data using the parent entity list and then unlock using the base entity ilst.



Logging on to a Oracle Hyperion Enterprise Application With a Password Set Gives Error "Invalid Password for user USERNAME on Application APPNAME"

 Modified 20-SEP-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 6.5.0.0.00 to 6.5.1.0.00 - Release: 6.5 to 6.5
Information in this document applies to any platform.

Symptoms

A previously created application  which has a password set, is not accessible from a machine experiencing this fault. The error message 'Invalid Password for user USERNAME on application APPNAME' appears when you try to log on via Oracle Hyperion Enterprise Client. The password being entered is correct. 

Non affected machines allow access to the same application with the correct password.

A knock on affect of this issue is that the application cannot be accessed via Oracle Smartview or Oracle Hyperion Enterprise Web if the affected machine is an HEWeb Server.


Changes

The AES.DLL file has been removed from the Oracle Hyperion Enterprise Installation folder.

Cause

This issue is be caused by the AES.DLL file not being present on the machine running Enterprise.





Solution

The solution is to replace the AES.DLL file which has been deleted from the Enterprise Installation folder.

This can be achieved by one of the following methods:

1. Repair of the installation by running the original SETUP.EXE supplied with the software and choosing the REPAIR OPTION.
2. Re-installation of Enterprise
3. Copying the AES.DLL from a back-up or another machine with the same Enterprise version installed


AES stands for Advanced Encryption Standard also famously known as Rijndael after its developers

This algorithm is specifically used in Hyperion Enterprise for Password Encryption and Decryption. 
This DLL is not attached with any File Version, as it is a pure C DLL with no GUI components there-in



Multiloads From FDM to Hyperion Enterprise Do Not Kick Off the Logic/Calculations

 Modified 19-APR-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: 8.0.5.0.00 to 11.1.1.1.00 - Release: 8.0 to 11.1

Generic Windows

Symptoms

When importing a multiload file into FDM which then exports and loads to Enterprise, the logic/calculations are not being executed in Enterprise.

Cause

The target system load tags within the multiload file were not set correctly.

Solution

1) Open the Multiload Template file

2) Update the Target System Load Tags as outlined in the FDM Web Client Admin guide.  These tags are outlined in Chapter 15 (Importing Other Data Files) under the section "Multiload Files", Hyperion Enterprise Load Control Tags (multiload).

3) Update the Target System Load Tags as appropriate and save the template. 

Reload the template into FDM and Export/Load the data to Enterprise.  Verify the load is correct in Enterprise.




Multiple Product Versions are Listed in Drop Down when Logging into Hyperion Enterprise Reporting

 Modified 11-FEB-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise

Symptoms

Multiple product versions listed in drop down when logging into Hyperion Enterprise Reporting.

Changes

Recently upgraded from one version of Hyperion Enterprise to another.

Cause

The REPENG.INI has not been cleared of references to prior versions.

Solution

The DRIVERS32 section of the REPENG.INI file is updated with each new install of Hyperion Enterprise.  Prior entries are not automatically removed.  Simply remove the older version drive references or comment them out.  They will then no longer appear to users in the dropdown options of the login screen.

The REPENG.INI file can be found on each user's PC in the WINNT directory or in their home directory on a Citrix server.

[DRIVERS32]
Enterprise6=HPRED32.DLL /ADDIN=odbcad32.dll /HsProdId=3 /HsProdVer=
Enterprise=H4RED32.DLL /ADDIN=odbcad32.dll



No Entities Can be Seen via RHXL -> CHANGE ENTITY in Hyperion Retrieve

 Modified 18-AUG-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 and later   [Release: 5.0 and later ]

Symptoms

No entities can be seen via RHXL -> CHANGE ENTITY in Hyperion Retrieve

Changes

Application has been reshelled

Cause

The new application has been added incorrectly

Solution

1. Remove application details from the hypent.ini file, either manually or in Hyperion Enterprise via FILE -> OPEN APPLICATION -> highlight the issue application and click REMOVE
2. Launch Hyperion Enterprise and re-add the application via the <ADD APPLICATION> option
3. Set all the POV items in Hyperion Enterprise, ensuring being able to see the desired entities
4. Launch Hyperion Retrieve and verify that entities now can be seen via RHXL -> CHANGE ENTITY



No Error Message Is Saved In Hyperion Enterprise Event Log

 Modified 01-MAR-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 6.4.0.0.00 to 6.5.1.0.00 - Release: 6.4 to 6.5
Information in this document applies to any platform.

Symptoms

No error message is saved in Hyperion Enterprise(HE) Event log, if 'Logging Options' is enabled.

Instructions to reproduce the issue -

1. Logon to the application with valid user id and password.

2. Select 'Application' module.

3. Select check box for 'Logging Options' to enable the Event log.

4. Click on 'Save' icon from the HE toolbar.

5. To reproduce the error message, stop the 'Hyperion Application Server' services from the services.msc (Start > Run > services.msc).

6. Try to do the server based consolidation and it will throw a error message 'Error on socket connect. WinSock error 10061.' which would not be logged Event log.

NOTE:
All information other than ERROR is included in Event log.
All information including ERROR is logged in the Error log.

Cause

This is a known issue in Hyperion Enterprise which is a unpublished Bug 9355898 for v6.4, v6.4.1, v6.5 and v6.5.1.

Solution


This issue would be fixed in future release. Fixable version is yet to decide and its subject to change.

Workaround :

Use HE Error log option to capture error related information.



No Groups Show Up After Selecting Refresh Key When Trying to Import Users for External Authentication in Hyperion Enterprise

 Modified 07-JUL-2010     Type PROBLEM

Applies to:

Hyperion Enterprise

Symptoms

Setting up External Authentication in Hyperion Enterprise.
No groups show up after selecting the Refresh key when trying to import external users.

Cause

Incorrect syntax for the APP_CSS_CONFIG_FILE line in the <ApplicationName>.INI file

Solution

Open the <ApplicationName>.INI file and change the following line:


FROM: APP_CSS_CONFIG_FILE="file:///D:/hyperion/Enterprise/msad.xml"


TO:   APP_CSS_CONFIG_FILE="file:///\\D:/hyperion/Enterprise/msad.xml"


Note the direction of the slashes. The information in double quotes is the location of the XML file configured for External Authentication for the Enterprise application

Opening Balances Pull Through

Please create a Entity list of the BASE LEVEL components access this list in the Database by selecting:-
1/ VIEW
2/ Entity List
3/ Highlight the first period of the grid by selecting the period from the top part of the Grid EG JAN
4/ Then activate formulas. The BF's will follow through.

Oracle Hyperion Ledgerlink Prompts For A Folder For The ERR Files When Profile Is Run

 Modified 31-MAR-2010     Type PROBLEM 

Symptoms

When a Load Profile is run from Ledgerlink the user is prompted for a path to a location in which to save the various .ERR files generated.

The load profile is still working but the prompt is not desired.

Changes

The Application Inbox path has been changed manually from @APP\Inbox  to a defined path, and the Application has been moved to a different Server.

Cause

The prompt is produced if the application Inbox folder, defined in the Application settings,  does not exist or if the user running Legerlink does not have access to the folder.




Solution


The Application Inbox needs to be defined as folder that exists and which users have write access to.

To set the Inbox path

1. Logon to Enterprise
2. Select the Application Module.
3. Select the menu File-> Application Attributes
4. Press Next at the Application Setup Window
5. At the Window which shows the Driver Setup locate the Inbox Path field
6. Set this field to point to an existing location that the users have access to. 
7. Select Next several times and select Finish when Prompted.
8. Log out of Enterprise.
9. Verify the prompt is gone from Ledgerlink by running a Load Profile.



Plug Account Shows a Different Value Compared to the Intercompany Matching Report in Hyperion Enterprise

 Modified 07-JUL-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise

Symptoms

Plug account shows a different value compared to the Intercompany Matching Report

Cause

An entity has an intercompany transaction entered against itself in a sub entity

Solution

If an entity has ah  intercompany transaction against itself in a subentity, the balance will eliminate within the substructure as this is where the first common parent is found.  The fact that it eliminates is fine however the elimination will not show up in the Intercompany Matching Report as you cannot create an elimination entity within a substructure

In order to match the Intercompany Matching Report to the plug account, remove the transaction and rerun the consolidation





Prompted To Log On Twice When Launching Hyperion Retrieve From A Shortcut.

 Modified 19-JAN-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 - Release: 5.0

Symptoms

Prompted to log on twice when launching Hyperion Retrieve From a shortcut.

Cause

The shortcut references Hyperion Retrieve and the Hyperion Retrieve Addin has been selected in Excel.
This will result in the prompt to log in twice.

Solution

Either remove the reference to Hyperion Retrieve in the Microsoft Excel shortcut or remove the Hyperion Retrieve from the Microsoft Add-Ins:


Refreshing a Large Spreadsheet in Hyperion Retrieve is Very Slow

 Modified 10-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 4.3.2.0.00 to 6.5.0.0.00 - Release: 4.3 to 6.5

Symptoms

Refreshing a Large Spreadsheet in Hyperion Retrieve is Very Slow.

Cause

When a Retrieve Sheet is developed there are several factors that can affect performance.

1. Size of the Spreadsheet.

2. Technical Environment.

3. The complexity of the spreadsheet and the data dimensions being retrieved.

Large Retrieve spreadsheets can be slow to refresh as Retrieve will query the database to retrieve the data for each cell on a cell by cell basis. Other reporting tools can be more efficient in retrieving larger amounts of data If the sheet is large another reporting tool should be considered such as Hyperion Enterprise Reporting.

Solution

Possible solutions for this include the following:

1. Reduce the size of the spreadsheet. Consider splitting the spreadsheet into several smaller spreadsheets within the same workbook. Spreadsheets within a workbook refresh individually.

2. Consider the use of another reporting tool.

3. Review the Technical Environment using a performance monitoring tool. Resources may be an issue.  Check available memory and network connections. Ensure Application file Server and machine running Excel are located on same sub-net as the client or Citrix server.

4. Consult Oracle Support for more information or consider engaging Consulting for a technical review of the Enterprise environment.



See NOTE 593517.1 for Slow performance when using Refresh All Linked Cells 
See NOTE 1210143.1 for Slow Retrieve Performance Using Microsoft Excel 2007 and Enterprise 6.5.0 or 6.5.1.

References

NOTE:593517.1 - Slow performance when using Refresh All Linked Cells
NOTE:1210143.1 - Slow Retrieve Performance Using Microsoft Excel 2007 and Enterprise 6.5.0 or 6.5.1.


The attached document shows how to set the filters to be able to see all relevant entities when using Schedules.

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Troubleshooting Details

  1. Log into the converted application
  2. Open the Application module
  3. Click on the Sever Tab (3rd one in from left)
  4. The Application Server ID is blank

article.jpg

Checking Server Administration

  1. Log into the converted application.
  2. Open the Application module.
  3. Go to Navigate-Server Administration.
  4. On the left Pane highlight Application server.
  5. On the right side of the window the server id is blank again, and the name of the server or IP address cannot be typed in.

article.jpg

Migrating server information from the HSvrCtrl.dat file to the HEServers.xml file, perform these actions:

  1. From Server Administration highlight Server Management, right click and choose Migrate Servers.
  2. Browse to the HSvrCtrl.dat on the old server (previous version).
  3. Once that file is found highlight it and select open.
  4. In the left corner select Migrate.
  5. The message the that database was migrated successfully will appear.
  6. Select ok.
  7. On the left Window Pane select Application Settings.
  8. On the right side for the database path using the drop down arrow, go to browse and select the HEServers.xml file on the 6.5.1 install.
  9. Now the Server Name is filled in in both Server Administration and on the Server tab.

article.jpg


This change was done because...

1. The HSvrCtrl.dat was a binary file and needed HAdmin.exe to view all server information. After moving the server information to HEServers.xml it has become readable and easy to maintain.
2. Hyperion Enterprise HAdmin utility was responsible to only depict Application Server information. The new Enterprise Server Admin module has to maintain server information about App Server, DataServer, Message Server etc… To make this easy to maintain in a single place, we have the concept of HEServers.xml.


Migrate Process: When we click the Migrate button, the server information from HSvrCtrl.dat is read and populated as XML entries into the HEServers.xml. All application server entries for every unique AppServer from the HSvrctrl.dat are written to the HEServers.xml.


Server Based Processing is No Longer Working After Upgrading to Enterprise 6.5.1

 Modified 24-MAY-2010     Type TROUBLESHOOTING 

Applies to:

Hyperion Enterprise - Version: 6.5.1.0.00 to 6.5.1.0.00 - Release: 6.5 to 6.5
Information in this document applies to any platform.

Purpose

This document describes post installation steps for migrating your server in order for sever based processing to work after converting an application to Enterprise 6.5.1.

Last Review Date

May 17, 2010

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Troubleshooting Details

  1. Log into the converted application
  2. Open the Application module
  3. Click on the Sever Tab (3rd one in from left)
  4. The Application Server ID is blank

Checking Server Administration

  1. Log into the converted application.
  2. Open the Application module.
  3. Go to Navigate-Server Administration.
  4. On the left Pane highlight Application server.
  5. On the right side of the window the server id is blank again, and the name of the server or IP address cannot be typed in.



Migrating server information from the HSvrCtrl.dat file to the HEServers.xml file, perform these actions:

  1. From Server Administration highlight Server Management, right click and choose Migrate Servers.
  2. Browse to the HSvrCtrl.dat on the old server (previous version).
  3. Once that file is found highlight it and select open.
  4. In the left corner select Migrate.
  5. The message the that database was migrated successfully will appear.
  6. Select ok.
  7. On the left Window Pane select Application Settings.
  8. On the right side for the database path using the drop down arrow, go to browse and select the HEServers.xml file on the 6.5.1 install.
  9. Now the Server Name is filled in in both Server Administration and on the Server tab.



This change was done because
...

1. The HSvrCtrl.dat was a binary file and needed HAdmin.exe to view all server information. After moving the server information to HEServers.xml it has become readable and easy to maintain.
2. Hyperion Enterprise HAdmin utility was responsible to only depict Application Server information. The new Enterprise Server Admin module has to maintain server information about App Server, DataServer, Message Server etc… To make this easy to maintain in a single place, we have the concept of HEServers.xml.


Migrate Process: When we click the Migrate button, the server information from HSvrCtrl.dat is read and populated as XML entries into the HEServers.xml. All application server entries for every unique AppServer from the HSvrctrl.dat are written to the HEServers.xml.





Set Password Expiration causes user's passwords to expire immediately

 Modified 06-OCT-2009     Type PROBLEM 

Applies to:

Hyperion Enterprise

Symptoms

"Set Password Expiration" causes user's passwords to expire immediately.
For example, the Administrator has set the password expiry to 60 days from now but the user's password expires as soon as they log out and log back in.

Cause

The user was logged in the system when the administrator was setting the password expiry.

Solution

It is not recommended that any changes are made in the Security module while users are in the system. Use the Users in Application Report to determine if this is the case before making any changes, and once everyone is logged out ensure they don't log back in until the changes have been completed. If no users are logged in the system when the administrator sets the password expiry, the passwords will expire at the correct time.

To view the Users in Application Report:
In APPLICATION MODULE select TASK -> RUN USERS IN APPLICATION REPORT

To set the Password Expiration date:

  1. Log into Application
  2. Select Application Module
  3. Select Navigate - Security
  4. Select Task - Set Password Expiration
  5. Select Password Age in Days and then OK



Slow Retrieve Performance Using Microsoft Excel 2007 and Enterprise 6.5.0 or 6.5.1.

 Modified 10-JAN-2011     Type PROBLEM     Status PUBLISHED 

Applies to:

Hyperion Enterprise - Version: 6.5.0.0.00 and later   [Release: 6.5 and later ]
Information in this document applies to any platform.

Symptoms

When using Microsoft Excel Version 2007 (with or without service packs) The following symptoms are seen when using HP Retrieve (RHXLL32.XLL)

Slow performance calculating HPVAL formulas ( RHXLL | REFRESH).

Performance is lower than with Excel 2003.

Retrieve workbooks take a long time to open when compared to Microsoft Excel 2003

Changes

Oracle Hyperion Enterprise  has been updated to version 6.5.x
Microsoft Excel has been updated to version 2007 (with or without service packs)

Cause

To enable backward compatibility the addins for Excel use the Excel SDK version 5 and are hence not optimized for Excel 2007 Multi-Threading is in place. Multi-Threading can have an adverse effect on performance





Solution


Four areas of configuration to consider to optimize performance.

Saving  the spreadsheet as an XLSX extension file to avoid Excel converting the spreadsheet each it is opened.

Disable Multi-Threaded Calculation in the Excel Spreadsheet.

Select the Office 2007 Symbol at the top left of the Excel screen whilst the spreadsheets is open
Select the "Excel Option" button
Select Advanced
Deselect...Enable-Multi-Threaded Calculations.
Save the workbook.

Turn Off Auto Calculation.

Select the Office 2007 Symbol at the top left of the Excel screen whilst the spreadsheets is open
Select the "Excel Option" button
Click Formulas
Set the Work Book Calculation Radio Button to Manual
Save the workbook

Tune the HACCESSDATATABLECACHECOUNT parameter in Hypent.ini default section.

Use the HACCESSDATATABLECACHECOUNT option in the hypent.ini to specify the number of Hyperion Enterprise data tables that are cached by Hyperion Enterprise.

A data file contains all data for the combination of a category, entity, and consolidation detail. For best performance, you should set this number to be equal to or greater than the number of data files used in an Enterprise Retrieve spreadsheet. However, if you use a large number, it may increase your RAM requirements.

If you do not enter this setting, the system uses a default value of 20.

Example:
If data is retrieved from three categories for 20 entities, the setting would be HACCESSDATATABLECACHECOUNT=60

The maximum setting for this option is 100.

This setting has no effect on any other add-on modules performance. It only needs to be in the hypent.ini file of users who access large spreadsheets.

Save the Hypent.ini file and close and restart Microsoft Excel/Retrieve.

With these settings in place an improvement in performance will be seen.














References

NOTE:1181603.1 - Tuning Hyperion Enterprise to Improve Performance
NOTE:585549.1 - Using the HACCESSDATATABLECACHECOUNT Option in the Hypent.ini File to Improve Retrieve Spreadsheet Performance
NOTE:593517.1 - Slow Performance When Using Refresh All Linked Cells In Retrieve
NOTE:591404.1 - Refreshing a Large Spreadsheet in Hyperion Retrieve is Very Slow



Smart View Formula Becomes Invalid When Sharing Workbooks from Another User

 Modified 26-MAR-2010     Type PROBLEM 

Applies to:

Hyperion Essbase - Version: 9.2.0.0.00 to 11.1.1.3.00 - Release: 9.2 to 11.1
Hyperion Enterprise - Version: 6.5.0.0.00 to 6.5.1.0.00 - Release: 6.5 to 6.5
Hyperion Financial Management - Version: 4.1.0.0.00 to 11.1.1.3.00 - Release: 4.1 to 11.1
Hyperion BI+ - Version: 9.0.0.0.00 to 11.1.1.3.00 - Release: 9.0 to 11.1
Hyperion Planning - Version: 9.2.0.0.00 to 11.1.1.3.00 - Release: 9.2 to 11.1
Information in this document applies to any platform.
Excel2003, Excel 2000, Excel 2007

Symptoms

SmartView functions contain the full path of the Smart View Addin when opened. The contents of some particularly complex cells may become invalid when this occurs.

Cause

Excel saves the location of the SmartView Add-in with each function. If the stored SmartView add-in location is different from the client's SmartView installation location, the original full path name appears in front of every Smart View formula in the workbook. For example, if a workbook is created on a machine where SmartView is installed to C:\Hyperion\SmartView and the workbook is opened on a machine where it is D:\Oracle\SmartView, Excel will display C:\Hyperion\SmartView\bin in front of each SmartView function.

This can cause the formulas to exceed the maximum character length of the cells (255 in Office 2003 and earlier).

Normally SmartView will automatically remove the unwanted path name, but the corruption of very long cells may still occur. If SmartView does not automatically remove the path, refer to Note 827523.1.

Solution

As a best practice, it is recommended that Smart View be installed in the exact same location on all machines to prevent this issue from occurring.
Secondly, ensure all cells are less complex. You should ensure that cells are less than 250-(length of pathname of SmartView Add-in).

Suggestions:
- Do not specify all members in every function but rely on the background Point of View (as defined in POV Manager) for most dimensions. Only include dimensions that differ from the background Point of View. This will also improve performance.
- Use cell references rather than hardcoded member names.
- Do not have more than one SmartView function in each cell.
- Split complex calculations over more than one column. Intermediate calculations can be hidden.

Example:
=If(HsGetValue("MyConnection","Scenario#Actual;Year#2010;Entity#Wolverhampton;Account#Sales;...")=0,"Zero",HsGetValue("MyConnection","Scenario#Actual;Year#2010;Entity#Wolverhampton;Account#Sales;..."))
Avoid repeating the function (which will hit performance) by placing the function in, say, C2 and in D2 have:
=If(D2=0,"Zero",D2).
Hide column C.

References

NOTE:827523.1 - SmartView functions are preceded by the full path to HsTbar.xla
NOTE:745097.1 - Functions Saved in a SmartView Worksheet Include the Path of the File HsTbar.xla of the original machine.



Smart View Formula Displays #VALUE! Instead of Expected Value

 Modified 07-MAY-2010     Type PROBLEM 

Applies to:

Hyperion Financial Management - Version: 9.2.0.0.00 to 11.1.1.3.00 - Release: 9.2 to 11.1
Hyperion Essbase - Version: 9.2.0.0.00 to 11.1.1.3.00   [Release: 9.2 to 11.1]
Hyperion Enterprise - Version: 6.5.0.0.00 to 6.5.1.0.00   [Release: 6.5 to 6.5]
Hyperion Planning - Version: 9.2.0.0.00 to 11.1.1.3.00   [Release: 9.2 to 11.1]
Hyperion BI+ - Version: 9.0.0.0.00 to 11.1.1.3.00   [Release: 9.0 to 11.1]
Microsoft Windows (32-bit)
Microsoft Excel 2003 and Microsoft Excel 2007

Symptoms

When attempting to refresh a Smart View sheet that contains formulas(not Ad Hoc), the cell displays #VALUE! instead of the expected value.  This is an Excel message, not a Smart View message.

Cause

This is caused by an issue with the Excel formula.  Specifically, the #VALUE! error value occurs when the wrong type of argument or operand is used, or if the Formula AutoCorrect feature cannot correct the formula.  The most common cause is trying to to use a math operand on a non-numeric value.

If a simple Smart View formula would return #MISSING, #NOACCESS, or some other non-numeric value and the more complex Smart View formula has additional operands on the end like /1000 or *.1, this will occur.




Solution

  1. Remove all other Excel functions from the Smart View formula.
  2. Address the underlying issue by either correcting the formula or by changing the Smart View Replacement values under Smart View Options, Display.


Smart View Users are not Listed in the Users in Application Report

 Modified 20-SEP-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 6.5.0.0.00 to 6.5.1.0.00 - Release: 6.5 to 6.5
Information in this document applies to any platform.

Symptoms

When the Users in Application Report is run from the Application module any users logged into the Smart View addin do not appear in the report

Cause

This feature is currently not available 

Solution

Enhancement request 10045199 has been raised for Smart View users to be listed in the Users in Application Report and will be implemented in a future version.  This enhancement request is unpublished



The Application Server ID Option is Greyed Out In Application Module Of Hyperion Enterprise

 Modified 13-JAN-2011     Type PROBLEM   

Symptoms

After logging in to Hyperion Enterprise, cannot select the Application Server ID to run any server based processing .The drop-down arrow to make this selection is grayed out.

Changes

New installation of Hyperion Enterprise

Cause

There are several possible causes

1. Application server component has not been installed during the Hyperion Enterprise Installation.

2. The component is installed but in the Application.ini file in the Hyperion Application folder the following parameter has been set to zero.
                       APP_USE_SERVER="0"

This has to be set to 1 for turning on the Application Server options in the Application Module.

Solution

Ensure that following is done to resolve this.

1.During the Hyperion Enterprise installation, select the components, make sure the Enterprise Application Server is selected and installed.

2. If it is installed, in Application.ini file in the Application folder,  make sure that APP_USE_SERVER="1" set.  While performing this step make sure that all the users are logged out from Hyperion Enterprise.

The procedure for changing the substructure attached to an entity is as follows:

 

Example:
Entity TEST has the substructure REGION attached.
This substructure has REGION as the top entity and EAST, WEST, NORTH, and SOUTH as its dependents.
A new substructure called PRODUCT needs to replace REGION.
PRODUCT has GOLF, TENNIS, and SKATING attached as dependents.

1. Extract data from each of the entities: TEST.EAST. TEST.WEST, TEST.NORTH, and TEST.SOUTH for all categories and periods.
2. If the subentities have been attached to any parent independent of the main entity TEST, these need to be deleted from those organizations.
3. Turn off the option 'SHOW SUBENTITIES'.
4. Select the entity TEST and set the substructure to NONE.
5. Make a note of the Entity attributes of TEST and then delete the entity TEST from all organizations. (Be sure to note all parents for re-adding entity later.)
6. Select TASK->UNOWNED ENTITIES->PURGE UNOWNED ENTITIES and purge the entity TEST.
7. Save your changes and shut down Hyperion Enterprise.
8. Re-launch Hyperion Enterprise and open the Entities module.
9. Add the new entity and call it TEST. Set all attributes as before and set the substructure to PRODUCT.
10. Re-add the new entity TEST to all organizations as appropriate and add the new sub-entities to the appropriate organizations if applicable.

NOTE: Failure to follow these steps will result in the original subentities still being available in select entity dropdown lists. Also, if flagged for journals, users will still be able to post journal entries to these deleted entities.


Troubleshooting Hyperion Enterprise Client Published with Citrix

 Modified 31-JAN-2011     Type TROUBLESHOOTING 

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 to 6.5.1.0.00 - Release: 5.0 to 6.5
Information in this document applies to any platform.

Purpose

To aid in troubleshooting issues publishing Hyperion Enterprise with Citrix.

Last Review Date

May 21, 2010

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Make sure that the application was installed using the “install mode” on the server.

1. Go to the server where application will be installed and published on Citrix.

2. Physically put the server into "Install Mode" by issuing the following from a 'cmd' window: 
 

change user /install

DO NOT CLOSE this window; minimize it for now if you wish.

3. Install the application normally.

4. Back at the 'cmd' window, issue the following command: 
     

change user /execute

5. Close the command window.

6. Go to Citrix as normal and publish the application. 


Test with user-class and administrative accounts directly at the server.

This test will take the “published” aspect out of the equation and give insight as to whether this issue is related to the application being published with Citrix, or if it could be permissions or security policy related that could prevent the application from running correctly as a specific user.

Test directly on the server: 

1. Go directly to the Citrix server. 

2. Open the Citrix Metaframe Presentation Server Management Console. 

3. Click on Farm where the published application resides.

4. Find the Published application in question.

5. Right Click the published application - click Properties. 

6. Click on Application Location - look at Command Line to see where the actual executable is on the server. 

7. Close the Management Console. 

8. Go directly to the executable of the application in question to test locally on the Citrix server itself (not using the "published" application). 

9. Right click on the executable and click "run as". 

10. First test with the Administrator ID to test that the application itself is working properly. 
      This will show us if the issue is user specific or security related.


Check that “Memory Optimization” setting is turned off on the Hypent.exe file located in Hyperion Solutions\Hyperion Enterprise 

For Citrix Presentation server 4 and 4.5, the Memory Optimization exclusion list is located in the Presentation Server Console under the farm properties in the Memory Optimization section. 
It is best to configure the optimization to run daily at an off peak time. You can configure this in the Presentation Server Console under Farm properties > Memory Optimization. 

To exclude additional applications from memory optimization in Citrix XenApp

1. Depending on the version of XenApp you have installed, from the Start menu, select All Programs > Citrix > Management Consoles and choose Access Management Console or Delivery Services Console. 

2. In the left pane, select the farm on which you want to exclude additional applications from memory optimization. 

3. From the Action menu, select Modify farm properties > Modify all properties. 

4. In the Farm Properties dialog box, choose Farm-wide > Memory/CPU > Exclude Applications. The Exclude Applications page appears. This page lists the applications that memory optimization ignores.

5. Click Add. The Browse Files dialog box listing all servers in the farm appears. 

6. Navigate to the applications from each server that you would like memory optimization to ignore, clicking OK to add each executable to the Exclude Applications page. 

7. Click Apply to implement your changes and then OK to close the Farm Properties dialog box. 


If users do not see the Enterprise application at first log on:

For NEW users: (have not previously logged in via Citrix)

1. Create the database normally in a network directory accessible to the Citrix/Terminal server. 


2. Switch the Citrix/Terminal Server box to INSTALL mode – from cmd prompt 

change user /install 

3. While physically logged into Citrix/Terminal server, log into the Enterprise application, add the new database, open it and set all dimensions of the point of view. 

4. Log out of Enterprise. 

5. Switch Citrix/Terminal server back to EXECUTE mode – from cmd prompt 

change user /execute

6. As users log into Citrix/Terminal Server sessions the updated HYPENT.INI for Enterprise should copy to their individual home directories. 

For CURRENT users: (already have a HYPENT.INI in home directory)

 

1. From any user's Citrix/Terminal Server session, log into Enterprise, add the new database, open it, and set all dimensions of the point of view. 

2. Log out of Enterprise. This causes the HYPENT.INI (for Enterprise) file to be updated. 

3. Copy the updated HYPENT.INI file from the home directory of the user in step 1, to all other users' individual home directories. 


If Enterprise Retrieve is not working for some users.

It's possible that some users get the error “Cannot open HPAPP.DAT.” 

Setting up Hyperion Retrieve with user specific or multiple HPAPP.DAT files in a Citrix Environment.:

1.The admin must log in as the user and set up a user variable pointing to the path for the HPAPP.DAT to the user's home directory. The admin must set this up for each user and have the copy of the specific HPAPP.DAT in the users home directory. If a system environment variable has already been set up for the HPAPP.DAT, it would need to be removed since it will take precedence over a user variable that is set up. 

1. An HPAPP.DAT file with desired data application references needs to be created/copied for every user to his/her personal Metaframe home directory. 


Home Directories contain any user specific files in the Metaframe environment. For Enterprise, these include the HYPENT.INI, REPENG.INI, etc...


2. Create a User Variable 
Go to -> Control Panel ->System ->Environment with the following attributes: 
Variable: HPAPP.DAT 
Value: drive\home directory path\HPAPP.DAT 

For example, if the user home directories are all set up on the Z drive with each user folder named after the user's ID (this is another Citrix recommendation), then your User Variable would be "Z:\username\HPAPP.DAT"


It may also be necessary to leave the default file location in Excel blank

 

Citrix Published Retrieve has different default file location

Citrix published version of Hyperion Enterprise Retrieve has a different Default file location then the one specified in the Tools / Options / General (TAB) / Default file location in Excel.

The use of Excel startup switch /p folder path\folder name when publishing the application will set the default file location to the specified folder in the startup switch. This switch will override the folder location shown in the Default file location in Excel.

An example of the issue:

Client's publishing Enterprise Retrieve with the following
"c:\Program Files\Microsoft Office\Office10\EXCEL.EXE" /p "c:\PROGRAM
FILES\Enterprise 651" "c:\PROGRAM FILES\Enterprise 651\RHXLL32.XLL"

You can remove this switch from the command line used to publish Retrieve in Citrix.

@ Note:
 This is a consolidated document made from the following articles which have now been removed:



References

NOTE:1128334.1 - Points to Consider when Installing Oracle's Hyperion Enterprise Release 6.5.1 on a Windows/Citrix 64-bit Platform
NOTE:580746.1 - Adding An Applications To Oracle's Hyperion Enterprise
NOTE:581499.1 - How To Set Up Hyperion Retrieve With User Specific Or Multiple HPAPP.DAT Files In A Citrix Environment.



Security for the Hyperion Enterprise Backup Utility [ID 1073807.1]

 Modified 17-MAY-2010     Type TROUBLESHOOTING 

Applies to:

Hyperion Enterprise - Version: 6.5.0.0.00 and later   [Release: 6.5 and later ]
Information in this document applies to any platform.

Purpose

This document describes how to diagnose the back up utility if it does not run.

Last Review Date

May 17, 2010

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Components to review to ensure a backup runs

Checking the Enterprise User ID:

  1. Launch the Applications Module
  2. From the menu bar select Navigate - Security
  3. Click on Maintain Tasks and check the security class attached to the option of Application Backup
  4. Navigate to the upper right corner and using the drop down arrow under Show Task for Module and  choose Applications.
  5. Scroll down until you come to the tasks of Application Backup & Application Restore and check the security class assigned to these tasks.
  6. On the left side of the screen choose Maintain Classes and find the security class that has been assigned to the task of Application Backup and Application Restore.
  7. Highlight that security class and navigate to the top of the screen and choose the option Assign Class Rights
  8. Highlight the security class and on the second tab on the bottom choose Assign Rights making sure this security class has Modify rights assigned
  9. On the left side of the screen choose Maintain Groups
  10. Highlight the group that the user is assigned.
  11. At the top of the screen, Choose Assign Group Rights
  12. Select the group and click on the Assign rights Tab at the bottom of the window pane making sure that the class assigned to the group is one that has modify rights.
  13. On the left side of the screen choose Maintain Users
  14. At the top of the screen choose Assign User Rights
  15. Find the user and highlight them and then at the bottom of the Window choose the tab Assign Rights
  16. Verify the security class for this user

Verify that the Windows User ID is a local Administrator.  This User ID will be used within the backup module

  1. Right Click on My Computer on the desktop or from the start menu
  2. Go to Manage
  3. Expand Local Users and Groups
  4. Highlight Groups
  5. Double click Administrators
  6. Make sure the Windows id is in the Administrators Group


Configuring the Backup

  1. Open Application module and launch Application Backup module through Task -  Backup Application(s) .
  2. ‘Application Backup’ module will be launched.
  3. On the Backup Profile Tab select a ‘New Profile’, enter a new profile name in the pop up dialog.
  4. Select application(s) to take backup from ‘Available Applications’ list box.
  5. Select the path where the application backup files will be stored in ‘Archive applications backups to ’.
  6. Select the ‘Run as’ user and provide the appropriate password with respect to selected user.
  7. By selecting ‘Run only if logged on’ enables only the windows logged on user to run the backup.
  8. Select ‘Enabled (Scheduled task runs at specified time)’ to take application backup at scheduled time (default it will be checked).
  9. Enabling ‘Messaging’ options will let user send a broadcast message to users in the backed up application at a specified interval.
  10. From the Methods Tab choose the Profile
  11. Make sure the option of Full Application is checked
  12. Provide the user ID and Password (Hyperion ID & Password)
  13. Move to the Schedule Tab
  14. Choose when you want the back up to run and the Start time
  15. Schedule the task (How often this must run everyday or once a week)
  16. Choose the Duration time which means the Start & End dates
  17. Now the back up is scheduled to run.


If the Back up does not run check the following:

Create a Manual Backup task creation: (Verification for Microsoft Task Scheduler)
  1. Windows Explorer - Control Panel - Scheduled Tasks
  2. Right-click and create New Scheduled task with a unique Task Name
  3. Specify the following command for the Run box (Enterprise install path): (ex.) "C:\Program Files\Hyperion Solutions\Hyperion Enterprise\HeAutoBackup.exe" <Scheduled_Task_Name_Goes_Here>
  4. Specify the following in the Start in box: (ex.) "C:\Program Files\Hyperion Solutions\Hyperion Enterprise"
  5. Specify the correct user credentials to run the scheduled task
Notes:
  • The Network user ID should be able to create any other non-Hyperion tasks like for example running Notepad, Calculator etc… If the Non Enterprise user ID cannot create such tasks then Hyperion Application Backup task will also not get created.
  • The Hyperion Enterprise user ID that you use to set up a backup must have a password.  Using a user ID with a blank password to setup backup will cause the backup to fail.
  • “Interact with Desktop” needs to be checked for the Task Scheduler service in the Start - Run - 'Services.msc' panel.









Unable to Configure Internal Oracle Hyperion Enterprise Back-Up

 Modified 26-APR-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 6.5.1.0.00 and later   [Release: 6.5 and later ]
Information in this document applies to any platform.

Symptoms


When an Enterprise back-up is initialized the system window appears and then closes a few seconds later. No error messages are displayed but the 'create back-up folder' is empty.

When navigating through the back-up tabs the settings are not saved and are lost when exiting the back-up window.

Cause

The user configuring the back-up has insufficient Windows and/or Enterprise Rights to perform the back-up configuration.

Solution

When logging into the Enterprise application and creating a back-up profile certain rights as below are required:

  • Admin rights to Enterprise Application so that all application areas and task are accessible.
This is achieved by granting the admin user MODIFY rights to all the security classes within the application.

In terms of windows security, a user with admin rights to the machine running Enterprise is recommended as the user rights required will have to include the following:

  • Write access to the Back-up_configuration.dat file in the windows folder of the desktop or citrix/terminal server running the back-up.
  • Full control to the application folder where the application is stored.
  • Full control to the back-up folder where the back-up is to be stored to.
  • The ability to create Windows Scheduled tasks.

Unable To Locate Component in Hyperion Enterprise Reporting

 Modified 16-NOV-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 6.3.1.0.00 to 6.3.1.0.00 - Release: 6.3 to 6.3
Information in this document applies to any platform.

Symptoms

Unable to open the Hyperion Enterprise Reporting Application and getting the error,

"The application has failed to start because hsutl132.dll was not found.Re-installing the application may fix the problem. "

Cause

Hsutl132.dll is one of the .dll files that helps in running the Hyperion Enterprise Reporting Application.

The File is either lost or damaged or corrupted.


Solution

There are 2 solutions to this error message,
"The application has failed to start because hsutl132.dll was not found.Re-installing the application may fix the problem"

Solution 1: Full re-install

1.Perform a Uninstall of the Hyperion Enterprise Reporting  from the Add/Remove programs in the control panel(ensuring no users are logged in to the system)
2.Re-boot the system to ensure that no files related to the old installation is running.
3.Re-install the Hyperion Enterprise Reporting as an admin.
4.Re-boot the system.

Solution 2: Repair the installation.

1.Go to the control panel and perform a Repair-install of the Hyperion Enterprise Reporting.
2.Re-boot the system




Unable to Post Journal Even Though User Has Modify Rights to Post Journal Security Class

 Modified 17-SEP-2010     Type PROBLEM     Status PUBLISHED 

Applies to:

Hyperion Enterprise

Symptoms

Unable to post journal.
User created a journal but cannot post that same journal even though user has Modify rights to post journal security class.

Cause

User has only VIEW access to a security class attached to one or more application elements (accounts and entities) in the journal entry.

Solution

To create a journal entry, the user needs MODIFY access to the journal module but needs only VIEW access to all application elements selected in the entry.


However, to post that same journal the user needs MODIFY access to the Post Journal task as well as MODIFY access to all application elements selected in the journal entry. 

For example, User1 created the following journal entry:


Entity1, Account1, 1000
Entity2, Account1, -1000
Entity3, Account2, 1000
Entity4, Account2, -1000


All journal tasks have the MAXIMUM class attached. 
All entities have the MAXIMUM class attached excepting Entity4 which has the CHANGE class attached. 
All accounts have the MAXIMUM class attached excepting Account1 which has the OPTION class attached. 
If User1 has MODIFY access to all three of these classes, he can create and post this journal entry. 
However, if User1 has MODIFY to MAXIMUM and CHANGE but only VIEW to OPTION, he can create this entry but will not be able to post it. 
Also, if User1 has MODIFY to MAXIMUM and OPTION but only VIEW to CHANGE, he can create but cannot post. 
Finally, if User1 has less than MODIFY to MAXIMUM, he will not be able to create nor post a journal.



Unable to Print or Preview Any Reports

 Modified 30-JUL-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise

Symptoms

Print option is greyed out.

Cause

Causes may be that a default printer has not been selected or Software has not been installed or set in the path correctly.

Solution


1. Check Hyperion Enterprise Reporting is installed.

2. Check Hyperion Enterprise and Hyperion Enterprise Reporting have been set in the PATH statement properly.

3. Ensure a default printer has been selected.



Unable To Print Or Preview In Hyperion Enterprise And Hyperion Enterprise Reporting

 Modified 06-AUG-2010     Type PROBLEM  

Applies to:

Hyperion Enterprise - Version: 5.0.1.0.00 to 6.5.1.0.00 - Release: 5.0 to 6.5
Information in this document applies to any platform.

Symptoms

1) Nothing happens clicking on print or preview in Hyperion Enterprise and Hyperion Enterprise Reporting even if the print option is enabled. 

2) Nothing happens clicking on printer select option. 


Cause


The location of the Hyperion Enterprise Reporting directory should appear first in the environment variables PATH followed by the location of the Hyperion Enterprise directory.

Solution


1. Right-click on "My Computer" 
2. Choose Properties 
3. Choose the ADVANCED tab 
4. Choose the ENVIRONMENT VARIABLES button 
5. In the SYSTEM VARIABLES highlight the variable named PATH and click on the EDIT button 
6.Make sure the PATH starts with the first entry pointing to the location of the Hyperion Enterprise Reporting directory, followed by the location of the Hyperion Enterprise directory 
7. Click OK to apply all changes 

Here is an example of path statement: 

C:\Program Files\Hyperion Solutions\Hyperion Enterprise Reporting;C:\Program Files\Hyperion Solutions\Hyperion Enterprise. 




Unable to the Change Background Colour of the Hyperion Enterprise Desktop

 Modified 24-JAN-2011     Type PROBLEM 

Applies to:

Hyperion Enterprise - Version: 6.5.0.0.00 and later   [Release: 6.5 and later ]
Information in this document applies to any platform.

Symptoms

 When selecting any background color defined in FILE -> PREFERENCES -> USER -> COLOURS, closing Enterprise and logging back in again the changes are not saved.


Cause

This is known issue specific to Enterprise 6.5.0 and has been resolved in Enterprise 6.5.1.

@This is BUG 6533606


Solution

Upgrade to Enterprise 6.5.1


Hyperion Enterprise - Version: 5.1.1.0.00 - Release: 5.1
Information in this document applies to any platform.

Purpose

This document has been written to guide customers through resolving issues of reoccurring CHappfile and LockfileEx error messages; it covers Hyperion Enterprise 5\6 File-Based applications without Hyperion Data Server Service. Readers of this document should familiarize themselves with the Hyperion Enterprise Release Notes Release 5.x/6.x This document should be read first and fully understood before proceeding.

Questions and Answers

What is a CHappfile Error? 
CHappfile errors, which are recorded in the Hyperion Enterprise application's error.log file, are written by Hyperion Enterprise whenever a file access problem occurs, either for Read or Write. For example, in the event the server or the server service is restarted and workstations are connected with open files, all files opened by the workstation on the server are closed. In this situation, the workstation still has file handles associated with files on the server, but the server has lost its associated file handles. The file handles on the workstation are now invalid and can no longer be used to update files on the server. Error messages can only be written to the error.log if the client is able to re-establish connection to the server and open the error.log. 

Causes of CHappfile Errors 
CHappfile error messages can be traced back to various environmental factors. CHappfile messages do not always indicate the application has integrity issues, but they do indicate some type of disconnects are occurring. CHappfile messages are normally written to the application Error.log file, provided that the client can still connect to the server. If the client cannot connect to the server to write the message, then a pop up message may appear on the client or no message is recorded. The location of the Error.log is based on the User_Path setting in the HYPENT.INI file. It is possible to have multiple Error.log files if users have modified their HYPENT.INI file. 

Examples of CHappfile Errors 
The following are examples of CHappfile errors: 
CHappfile::ReadFromSysFile returned: Reached end of file. 
Error reading free blocks : CPropFileIO::GetFreeArea This is not a CHappfile message but this message has been found in the midst of other CHappfile messages. 
CHappfile::WriteToFile returned: Reached end of file. 
CHappfile::ReadFromSysFile returned: The handle is invalid. 
CHappfile::WriteToFile returned: The process cannot access the file because another process has locked a portion of the file. 
CHappfile::ReadFromSysFile returned: The operation completed successfully. 
CHappfile::ReadFromSysFile returned: The specified network name is no longer available. 
CHappfile::ReadFromSysFile returned: Cannot create a file when that file already exists. 

Possible messages written to client workstation System Event logs: 
Event ID 3009 "The redirector failed to unlock part of a file on server Hyperion_Enterprise_Server_Name." 
Event ID 26 Application popup: System Process - Lost Delayed-Write Data : The system was attempting to transfer file data from buffers to \\Hyperion_Enterprise_Server_Name\Share\551demo\551demo.EXA. The write operation failed, and only some of the data may have been written to the file. 

Windows clients, or Terminal Server RDP clients, don't write events to the event logs. There is currently no way to determine if these clients have experienced these types of issues based on the event logs. 

Interpreting Error.log entries 
When reviewing the Error.log file, it is important to understand this file is an event log as well as an error log. Not all events in the application are logged, but some informational events like consolidation start and complete times, data load and extract start and complete times, report previews and retrieve refreshes are logged. When reviewing the Error.log file, here is a sample of what may be found: 

(User: admin ) An unrecoverable error occurred. 
LockFileEx returned: Time=8:30:11 PM 3/5/02, OS Error Code=0x6, OS Error Message= The handle is invalid. , Module=N:\Hyperion Solutions\Hypent.exe Terminating current session. 

This sample comes from version 5.x\6.x, which includes additional error logging information. The key items to note are the OS Error Code and the OS Error Message. The OS Error Code is what has been returned to the Hyperion Enterprise application. The OS Error Message gives the text meaning of that OS Error Code (Prove this to yourself :on Windows machines open a Command prompt and type net helpmsg 6™. The text return should be The handle is invalid) These are not Hyperion program errors but are OS errors being reported to Enterprise. Prior to 5.x\6.x, here is a sample of the same event: 

(User: admin ) An unrecoverable error occurred. 
LockFileEx returned: The handle is invalid. 
Terminating current session. 

The additional information provided by 5.x\6.x and later versions also includes the Module the user was in and the time the error was reported to the Enterprise program. The time listed does not necessarily mean that the underlying problem occurred at this time. For example, if a user is logged into Enterprise and steps away from their computer and the Enterprise file server is rebooted for some reason, no error will be reported by that user Enterprise program until they return to the workstation and attempt to access the application files. The time stamp of the error could be several hours after the server reboot caused the disconnect. 

What is a LockFileEx Error? 
Like CHappfile errors, LockFileEx Errors recorded in the Hyperion Enterprise application's error.log file indicate that Hyperion Enterprise experienced a problem reading or writing to a file. LockFileEx messages are normally written to the application Error.log file provided that the client can still connect to the server. If the client cannot connect to the server to write the message, then a pop up message may appear on the client or no message is recorded. Also, like CHappfile messages, LockFileEx messages do not always indicate the application has integrity issues, but they do indicate some type of network disconnects happening. 

Examples of common LockFileEx messages found in the Error.log: 
LockFileEx returned: The session was cancelled. 
LockFileEx returned: The handle is invalid. 
LockFileEx returned: An unexpected network error occurred. 
LockFileEx returned: The specified network name is no longer available. 

Possible messages written to client workstation System Event logs: 
Event ID 3013. The redirector has timed out a request to Hyperion_Enterprise_Server_Name. 

Windows clients, or Terminal Server RDP clients, don't write events to the event logs. There is currently no way to determine if these clients have experienced these types of issues based on the event log. 


Current Recommendations 


Please refer first to the Hyperion Enterprise 5\6 Release Notes. The release notes for version 5.5 and later include Appendix A, which listed Suggested Network Guidelines for Hyperion Enterprise. The following information should be considered to complement those sections. Before making any changes to your production environment it is recommended that the changes be fully tested on a non-production system that closely matches the production environment. 

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall. Use this tool at your own risk. 
Basic environmental recommendations 
These are standard recommendations that should apply to all environments: 
Network Interface Cards (NIC) and switch ports should not be set for Auto Sensing of Speed and Duplex method. These devices should be configured to match both speed and duplex method. 
Running Hyperion Enterprise on Domain Controllers is not recommended 
Clustering technologies like MSCS should not be used in Active mode 
Backups and file copies should not be made with users in an application 
Virus scanning should not be configured to scan the Enterprise application data files in Real-time mode 
All Windows servers and workstations should be on the same Service pack level. 
Hyperion Enterprise Servers Windows and Windows (file servers) 
Disable Opportunistic Locking at the server service level 
Add the following Value: 
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters 
Value Name: EnableOplocks 
Data Type: REG_DWORD 
Value (decimal): 0 

Disable Remote File Control Blocks (RFCB) caching 
Add the following Value: 
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters 
Value Name: CachedOpenLimit 
Data Type: REG_DWORD 
Value (decimal): 0 

Windows Terminal Services (with or without Citrix) 
For Windows servers running Terminal Service, the article Q299603 was found to list a few registry modifications to help resolve redirector problems. Although the error mentioned Error reading file is not seen in Enterprise, the registry changes are being recommended as part of the standard troubleshooting process. 
From Q299603: 

Disable Opportunistic Locking at the workstation/redirector level 
Add the following Value: 
\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Mrxsmb\Parameters 
Value Name: OpLocksDisabled 
Data Type: REG_DWORD 
Value (decimal): 1 

Disable File caching 
Add the following Value: 
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters 
Value Name: UtilizeNTCaching 
Data Type: REG_DWORD 
Value (decimal): 0 

Note: entry has been reported to impact performance. Test this modification in your environment to determine the impact. 

Disable Remote File Control Blocks (RFCB) caching 
Add the following Value: 
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters 
Value Name: CachedOpenLimit 
Data Type: REG_DWORD 
Value (decimal): 0 

Windows 2000
For the specific errors CHappfile::ReadFromSysFile returned: An unexpected network error occurred. or LockFileEx returned: An unexpected network error occurred when Windows Terminal servers are involved, apply the hotfix Q320310 if using SP1 or SP2. Service Pack 3 for Windows also includes the fixes to address the œunexpected network error. Q320310 is a Pre-SP3 Hotfix Q320310 includes the updated files from Q272582. 

If any Windows machines are found to be Blue Screening, you must address those machines first. The proper way to handle Blue Screening workstations is to contact Microsoft. You can determine the type of Stop error from the System Event Log. Common errors on Profession machines are Stop 0x1E and Stop 0xA. These are Kernel level Microsoft driver issues and not the result of a Hyperion Enterprise process. Search Microsoft Knowledge database for the specific stop error being reported for an applicable Hotfix(s). 

For Windows servers running Terminal Services, Dr. Watson errors occurring while navigating the Enterprise desktop may be resolved by disabling Dr. Watson. The œAdvanced Concepts MetaFrame XP has a section on Dr. Watson were it states you should either run the application compatibility scripts or you can disable Dr. Watson all together. Q188296 list the registry keys. To disable Dr. Watson totally, clear the following value: 

\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug 

Value Name: Debugger 
Data Type: REG_SZ 
Value: (blank) 

What happens with a data Load using entity conversion table which has multiple external entities for one Enterprise entity?

 

Solution:

If an entity and account combination appears more than once in a load file, those values are added together before they are loaded into the database.


When Previewing or Printing Any Reports Hyperion Enterprise Reporting Crashes. 

 Modified 17-AUG-2010     Type PROBLEM 

Applies to:

Hyperion Enterprise

Symptoms

When previewing or printing any reports the software crashes.
Error: ""0x0012d4cd" referenced memory at "0xfffffffff" the memory could not be read.".

Cause

A bad syntax is used in the  reports. The reports were using a command "Expand @ALL" after defining the sub-accounts.
This Expand @ALL command should only be used in Hyperion Enterprise Web Reporting.

Solution

Remove the "Expand @ALL" syntax from the affected reports and replace with #Account @ALL.



Applies to:

Hyperion Enterprise - Version: 4.7.0.0.00 to 6.5.0.0.00 - Release: 4.7 to 6.5

Information in this document applies to any platform.

Symptoms


When running a consolidation getting the error 'Lost network connection to Application Files'

Changes

The category producing the error had been manually edited by renaming the Category .DAT file. This is not a recommended procedure.

Cause


The category.dat files had been manually renamed in Windows Explorer to allow editing and then named back. Afterwards the consolidation would fail

Files should not be manually edited. If changes to the category settings are required follow the process to rebuild a cateory.

Solution


Restore the database from backup


Hi Tanya,

This update is just info only.

Make backup copy of application
Add new category for prior year (date specific eg 2013)
Edit formulae to include new category in "Category" statements (7 logic files to amend)
Lock all users out of the system
Update rollover sets to include new category (change in Rollset - LastYear)
Order of rollover most important, run lastyear/actuals/budget/fullclear
Check dates in categories (pay attention to categories in full clear rollover set....previously dates have NOT incremented (?))
Unlock users

Client to then unlock all periods/all categories and reconsolidate all, then relock all

After completing the rollover, go into data-entry for the category last year. Set to Global, then Re-enter the closing exchange euro rates which should be 1.00000 for each period. Calc and save.

This will force the opening exchange rates to recalculate. Then consolidate all impacted in the usual way.