• 

  Isabel Messore

  • 13 de octubre de 2026 17:32

  Hi Caroline Maria Saint Yves, 

  The Exit Code 2 from the HFM connector specifically means "Invalid Credentials." Even though the HFM admin confirmed the credentials are correct, the most likely root cause is the type of user being used for the connector.

   

  The Oracle HFM connector requires two distinct users, and they serve different purposes:

  - Connector Properties (authentication to HFM) → Must use a Native Directory user (local to HFM's own authentication service)
  - GroundRunner service → Must use an MSAD (Microsoft Active Directory) user

   

  "HFM has its own authentication service. While that service can hook into AD and use AD accounts, the best practice for the HFM connection is to use a native account because the password doesn't need to be updated every time the AD user's password changes."

   

  If an MSAD user is entered in the Connector Properties instead of a Native Directory user, HFM will reject it with an authentication error — even if the credentials themselves are technically correct.
  
  Steps to Resolve

  1. Confirm with your HFM admin that the user entered in the Connector Properties is a Native Directory user, NOT an MSAD/AD user
  2. Ensure that Native Directory user has access to Reporting and Extended Analytics in HFM
  3. Ensure the GroundRunner's integration user (MSAD user) has Execute privileges to the HFM home directory
  4. Also verify the GroundRunner is installed on the EPM server hosting the HFM Application Service — Workiva cannot support troubleshooting if it's on a different server/network

   

  If the GroundRunner is installed across multiple servers, check the logs for this line:

  INFO: The file reg.properties could not be found.

  If found, copy reg.properties from:

   

  Oracle\Middleware\user_projects\config\foundation\11.1.2.0
  → to:
  Oracle\Middleware\user_projects\epmsystem1\config\foundation\11.1.2.0

  0

Iniciar sesión para dejar un comentario.