Application Creator Cannot Create a HFM Application "Error occurred while creating the application" [ID 733566.1] | |||||
|
|||||
Modified 06-APR-2010 |
Applies to:
Hyperion Financial Management - Version: 9.3.1.0.00 to 9.3.1.0.00 - Release: 9.3 to 9.3Information in this document applies to any platform.
Symptoms
A user with the Application Creator role is unable to create an application.
A Native directory user is created and given the rights to create an application, then the user is removed.
If the same user is added back and given the rights to create an application, creating an application fails.
In order to reproduce the issue, do the following:
In Shared Services
- Create a new Native Directory user "newuser" and give the Hyperion Shared Services Global Roles of Dimension Editor and Application Creator
- Exit Shared Services
In Workspace
- Logon as "newuser"
- Select Create Application
- Fill in the dialog box appropriately, attempting to create "newapp1"
- Select Create. Newapp1 is successfully created
- Exit Workspace
In Shared Services
- Delete the Native Directory user "newuser"
- Exit Shared Services
In Shared Services
- Create a new Native Directory user "newuser" and gave the Hyperion Shared Services Global Roles of Dimension Editor and Application Creator (same "newuser" as before)
- Exit Shared Services
In Workspace
- Logon as "newuser"
- Select Create Application
- Fill in the dialog box appropriately, attempting to create "newapp2"
- Select Create. An error message is returned: "Error occurred while creating the application"
Cause
The old user "newuser" is stored as newuser@Native Directory and the newly created user "newuser" is stored as newuser@Native Directory1.
The user id is same as the old user but the CSS Identity is different. Identities are generated randomly by CSS code in OpenLDAP
When the new user is creating the application, the old user's CSS identity (which no longer exists) is passed on to CSS instead of the new user's identity by CMS.
Solution
Apply HSS service fix 9.3.1.0.06
Detailed steps are included in the read me file of the service fix
GKontos
Comments