This content has been marked as final. Show 4 replies
It is obvious there is some type of communication issue with MSAD and your Hyperion environment. As an user equivalent to the internal admin log into shared services and review the MSAD configuration. If it is setup to use multiple servers try to use a known good MSAD server and then get IT to look at why the existing configuration is not working.1 person found this helpful
If you are very desperate you could hit my blog and send me an email.
John A. Booth
Thank you for the response. I'm not sure if we do have multiple MSAD servers, so I've forwarded the question on to my IT department and I'm waiting for their response.
During my call with Oracle support, they suggested turning off the MSAD group configuration and restarting Hyperion to see if that would help. The only area that it seemed to help is in searching for users in MSAD. That works a lot faster now, but it didn't fix the problem with the users logging into Hyperion. I've sent Oracle the shared services logs for Admin, Hub and Security as they requested and I'm waiting for their response.
Once groups were disabled did you have all Hyperion services restarted?
You may also want to review the following KB articles which also can affect stability and performance of MSAD.
Using User Filter to Reduce the Number of Users Retreived from Microsoft Active Directory (MSAD) [ID 1227144.1]
Increase Essbase Server Java heap size [ID 1473163.1]
John A. Booth
I did have IT restart all Hyperion services and only saw the user search function improve after the restart.
After reading the Using User Filter to Reduce the Number of Users Retreived from Microsoft Active Directory (MSAD) [ID 1227144.1], I have a quick question: Would using the generic sample query statement for "Object is a user" (&(objectCategory=person)(objectClass=user))
suffice, or do I have to modify the statement?