Hyperion Planning Error: "Failed to sync with user provisioning.

Hyperion Planning Error: "Failed to sync with user provisioning. Check planning log for details."

Applies to:

Hyperion Planning - Version: 1.0.0.0.00 to 11.1.1.3.00 - Release: 1.0 to 11.1
Information in this document applies to any platform.

Purpose

The purpose of this document is to provide three different solutions to the error message "Failed to sync with user provisioning. Check planning log for details."

Last Review Date

June 18, 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

I . Error syncronizing planning users: "Failed to sync with user provisioning. Check planning log for details"
   Error: "Single sign on function call [css_getUser] Failed".

   There is a problem with how the users have been provisioned.

SOLUTION

  To resolve this issue take the following steps:
  1. In the folder .../UTILS
  2. Run PROVISIONUSERS.cmd
  3. Open userprovsionsync.log from the same folder
  4. Single sign on function call [css_getUser] Failed
  5. You will need to either delete all the planning users (underscore and non) and re-add with a 
     planning refresh or go into each (non-underscore) user and check the external auth box

NOTE: To remove all underscore users in 4.1.1.1 you can use HyperionPlanning\Utils Usermigrutil

II. When attempting to log on to Planning you receive this error:  "Failed to sync with user provisioning.
    Check planning log for details"

    The planning application was de-registered from shared services but has failed to re-register. 
    Deleting the application from the Shared Services project has lost the application provisioning.

SOLUTION

  To resolve this issue take the following steps:
  1. Delete the application from 'Unassigned Applications' in Shared Services (HSS).
  2. Re-register Planning with Shared Services from the Configuration Utility
  3. Log into the Planning AppWizard - http://PlanningServer:8300/HyperionPlanning/AppWizard.jsp - and
      re-register the application with HSS.
  4. De-provision the 'admin' user in Shared Services
  5. Run ProvisionUsers.cmd in %HYPERION_HOME%\Planning\bin folder
  6. Re-provision 'admin' in HSS
  7. Log into Planning application.
  8. Re-import (CSSImport) all the other provisioning.

NOTE: The steps above are done with the application owner, in this example, 'admin' user is the Planning application owner

III.When attempting to log on to Planning you receive this error: "Failed to sync with user provisioning.
     Check planning log for details"

     In the Planning log: "An error occurred while adding user to Essbase. Please check the Essbase log for
     details."

    Essbase has a character limitation that will not permit names longer then 30 and this effects all other
    applications that use Essbase. The limitation still exists in Oracle Hyperion Fusion Edition 11.1.1.1.

    This limitation only affects Essbase, not Shared Services, so you are allowed to create and provision a
    user with a user name of more than 30 characters for a Planning role. However, when you try to log into
    Planning an error occurs, as the user cannot be created in Essbase.

    In the Essbase log (Essbase.log) there is no record of the user with a 31 character user name being
    granted access, whereas a 30 character user name user was granted access. The client request for the 31
    character user to be added appears to simply be ignored.

Note:  The 30 character limitation actually reflects an underlying limitation of 8 bytes. This can result in small variations in the maximum number of characters supported (e.g. 31 characters may work in some cases, and 29 may not in others).

This issue is most commonly seen in environments where Shared Services is set up to use a login attribute other than sAMAccountName, such as an email addresses which are typically longer.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/7477027/viewspace-668084/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/7477027/viewspace-668084/