Severity: Medium

Description: In SAS^® Metadata Server, when using a direct Lightweight Directory Access Protocol (LDAP) or Active Directory (AD), an access violation can randomly occur that prevents you from logging on.

Potential Impact: Denial of service.

Solution: The only workaround for this issue is to restart SAS Metadata Server until the access violation no longer occurs in the log.

For example, the following error occurs in the SAS Metadata Server log when using a direct LDAP configuration:

2025-06-06T12:01:27,522 TRACE [00002135] :sas - Calling auth provider(5)...
2025-06-06T12:01:27,522 DEBUG [00002135] :sas - Entering ADIR provider for user user@domain
2025-06-06T12:01:27,526 ERROR [00002135] :sas - IOM call failed. Internal server exception: access violation.
2025-06-06T12:01:27,526 ERROR [00002135] :sas - Failed to process peer request.

If the SAS Metadata Server sasv9*cfg config files contain -AD your_ldap_host, you do have a direct LDAP connection.  

Note: Enable the Audit.Authentication DEBUG or TRACE logger if you want to definitely determine what authentication mechanism you use.