|HFM users cannot open application with error :Application [%0] is not contained in a Hyperion SharedServices Project. Please contact your administrator|
| ||Modified 21-SEP-2010 || |
Applies to:Hyperion Financial Management - Version: 18.104.22.168.00 to 22.214.171.124.00 - Release: 4.1 to 11.1
Hyperion Financial Management - Version: 126.96.36.199.00 to 188.8.131.52.00 [Release: 4.1 to 11.1]
Microsoft Windows (32-bit)
Users are not able to open a Consolidation (Financial Management) application with the error :"Application [%0] is not contained in a Hyperion SharedServices Project. Please contact your administrator" via Win32 client and Web client.
Also when they open the application from SharedServices, they receive "Application [APP_NAME] is not contained in a Hyperion SharedServices Project. Please contact your administrator".
Some application registration information in Shared Services is lost or corrupted.
This can happen when the SharedServices relational database and OpenLDAP are not in a consistent state, resulting (for example) by restoring one of the two from backup; which is why it is recommended to always restore both at the same time, using backups taken on the same date.
The SharedServices relational database stores information related to projects and product registration. The Native Directory OpenLDAP database contains provisioning data for all products. Data inconsistencies between the two will impact standard operations as seen in the Symptoms.
The following solution applies to "Classic" Consolidation applications only.
If you are experiencing this on an application created with EPMA, contact Oracle Support.
Recommended SolutionRun the SyncOpenLDAP utility to synchronize the two repositories.
Whenever version conflicts arise during synchronization, it is the data from the relational repository that is taken as reference. This means that if a project exists in OpenLDAP but not in the relational repository, all information about it and all provisioning info WILL BE DELETED.
For such reason, it is strongly recommended that you take a backup of your OpenLDAP before proceeding. Refer to Note 763771.1
for how to do it.
To synchronize the Native Directory repository with the Shared Services database:
Launch the SharedServices User Management Console, either navigating directly to http://your_hss_server:your_port/interop/ , or selecting the following menu item:
- 11.1.1 and above: Navigate ("the wheel") -> Administer -> SharedServices Console
- 9.3.x: Navigate -> Administer -> User Management Console
- 9.2.x, 9.0.x and 4.0.5: File -> User Management Console
- Select Administration -> Sync Native Directory.
- The Sync Native Directory tab displays the status of the synchronization operation.
- Optional: Click Refresh to update the status.
- Optional: Click View Log to display a log file that details the operations that were performed during the synchronization process.
Emergency solutionThis procedure should be attempted only if the above technique fails. It will manually remove the registration information about the HFM Application in the relational repository.
It is strongly recommended to backup your relational repository before attempting this procedure. Note also that all provisioning information about the application will be deleted.
- Open Microsoft Word (version 2003 or later). This is the most common tool that can be used for this operation, but any other WebDAV-enabled tool will also work.
- Select File -> Open.
- Enter the following URL: http://your-hss-server:your-port/interop/content
The port is usually 28080 in version 11.1.1 and above, and 58080 in other versions.
- When challenged for user/password, use credentials for the admin account. A file repository will appear.
- Browse to Files->Products->HFM 9.3.1 ->Published
- Delete the file containing the name of the corrupted application.
- Browse to Files -> AdminProjects -> Applications and delete the application file from there too.
- Restart the Shared Services Web Application service.
- Perform the abovementioned Recommended Solution. This will remove any info about the application from the OpenLDAP repository as well.
- Re-register the application, as described in the Financial Management Administration Guide, and re-provision users.