If you have tried re-configuring Essbase you would notice that it is not able to connect to Shared Service anymore. Authentication error is thrown every time you connect to Essbase from different clients.
Reason: The reason is Essbase is not able to connect with Shared Services. It is unable to create "EssbaseCluster-1" Application group and neither add new application to it as it already exists.
Following error is seen in Essbase_ODL.log files
Failed to create Essbase project [EssbaseCluster-1] at Shared Services with Error [Application group already exist.]
[2013-10-18T05:48:09.953-05:00] [ESSBASE0] [WARNING:1] [AGENT-6822] [] [ecid: 138209328157,0] [tid: 4140] Failed to migrate Essbase to HSS security mode during startup. Check SharedServices_Security_client.log. May need to remove essbase.sec and any of the newly migrated Essbase applications from HSS, then rerun configuration tool.
[2013-10-18T05:48:09.953-05:00] [ESSBASE0] [NOTIFICATION:16] [AGENT-6800] [] [ecid: 138209328157,0] [tid: 4140] Validation of back up file [D:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin\ESSBASETS_1382093289.BAK] completed with status 0
[2013-10-18T05:48:30.96-05:00] [ESSBASE0] [NOTIFICATION:16] [TCP-59] [] [ecid: 138209328157,0] [tid: 3028] Connected from [2002:adcc:7c91::adcc:7c91]
Solution
1. Delete the EssbaseCluster-1 from the application group in shared service.
2. Re configure Essbase (If you already have ignore)
3. Go to this location D:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin (appropriately)
4. Cut the files like Essbase.SEC, ESSBASE.BAK_postUPM, ESSBASE.BAK_preUPM and paste it in some other location
5. Restart Essbase
6. It automatically creates and connects to Shared Service.
Reason: The reason is Essbase is not able to connect with Shared Services. It is unable to create "EssbaseCluster-1" Application group and neither add new application to it as it already exists.
Following error is seen in Essbase_ODL.log files
Failed to create Essbase project [EssbaseCluster-1] at Shared Services with Error [Application group already exist.]
[2013-10-18T05:48:09.953-05:00] [ESSBASE0] [WARNING:1] [AGENT-6822] [] [ecid: 138209328157,0] [tid: 4140] Failed to migrate Essbase to HSS security mode during startup. Check SharedServices_Security_client.log. May need to remove essbase.sec and any of the newly migrated Essbase applications from HSS, then rerun configuration tool.
[2013-10-18T05:48:09.953-05:00] [ESSBASE0] [NOTIFICATION:16] [AGENT-6800] [] [ecid: 138209328157,0] [tid: 4140] Validation of back up file [D:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin\ESSBASETS_1382093289.BAK] completed with status 0
[2013-10-18T05:48:30.96-05:00] [ESSBASE0] [NOTIFICATION:16] [TCP-59] [] [ecid: 138209328157,0] [tid: 3028] Connected from [2002:adcc:7c91::adcc:7c91]
Solution
1. Delete the EssbaseCluster-1 from the application group in shared service.
2. Re configure Essbase (If you already have ignore)
3. Go to this location D:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin (appropriately)
4. Cut the files like Essbase.SEC, ESSBASE.BAK_postUPM, ESSBASE.BAK_preUPM and paste it in some other location
5. Restart Essbase
6. It automatically creates and connects to Shared Service.