Expose detailed AD Target Connector error messages in HelloID audit logging | Voters

Expose detailed AD Target Connector error messages in HelloID audit logging

Remco Houthuijzen

Currently, the AD Target Connector in HelloID only shows a generic error message such as:
[Error] Failed to update account for 'Person', details: Failed to update account
However, the internal logging contains much more detailed information, including the underlying (inner) exception. This technical detail is not visible in HelloID, which makes troubleshooting more time-consuming than necessary.
Example 1 – AD account not found
HelloID shows:
[Error] Failed to update account for 'Person', details: Failed to update account
Internal logging shows:
System.Exception: Failed to update account
---> System.Exception: Unable to find AD account with guid guid
The actual root cause (“Unable to find AD account with guid …”) is not visible in HelloID.
Example 2 – Access denied
HelloID shows:
[Error] Failed to update account for 'Person', details: Failed to update account
Internal logging shows:
System.Exception: Failed to update account
---> System.Exception: Internal ad error
---> System.Exception: Access is denied.
The real cause (“Access is denied.”) is not displayed in HelloID.
Requested enhancement:
Please expose the full exception chain or at least the most specific underlying error message in HelloID audit logs and task details
This would significantly improve troubleshooting efficiency and reduce dependency on internal logging or support.

February 16, 2026

Randolf Broer

Hi Rick van den Dijssel, this is especially very handy to have when agent log files are not in reach. For example when an external party manages the server with the agent and where it can take up to days before log files are received when requested for.

Rick van den Dijssel

Thanks for sharing this, Remco Houthuijzen — this is really helpful and I understand how the generic “Failed to update account” message makes troubleshooting unnecessarily hard when the inner exception contains the actual root cause (e.g. “Unable to find AD account with guid …” or “Access is denied.”). We’ll discuss this internally and look into what we can expose in the HelloID audit logs/task details (full exception chain or at least the most specific underlying message), and we’ll come back to you once we have an update.