Adlsdk-status-auth-pending 1 Agent Internal Error |top|

This error typically appears in console logs, API debugging tools, or directly within a web application’s user interface when attempting to launch a SCORM or xAPI package, authenticate a learner, or synchronize completion statuses. For system administrators and developers, this message signals a breakdown in the authentication handshake between the client agent (browser, desktop app, or middleware) and the ADLS backend.

Agent reads a partially written file or registry key, finds a “pending” flag without associated context (e.g., missing device code or user code). It doesn’t know how to resolve → internal error.

If the issue persists, the "1:" code can sometimes manifest as related variants like "agent disconnected" or "failed to launch agent." Try these additional steps: : adlsdk-status-auth-pending 1 agent internal error

Understanding your environment is half the battle. This error does not appear in a vacuum. Based on field reports and vendor documentation, here are the most frequent scenarios:

The most common cause is outdated licensing or identity software. For 2024 and Newer Versions: Download and reinstall the latest Autodesk Identity Manager For 2020–2023 Versions: Update the Autodesk Single Sign-On Component (AdSSO) Ensure the Autodesk Desktop Licensing Service is running and updated to the newest version. 2. Reset the Licensing Service This error typically appears in console logs, API

"The license manager is not functioning... ADLSDK_STATUS_AUTH_PENDING 1:Agent internal error" when launching AutoCAD product

For headless agents, the prebuilt binary may be incompatible with your glibc version (common on older RHEL/CentOS). Compile locally: It doesn’t know how to resolve → internal error

Some ADLS SDK versions allow fallback to HTTP polling for auth status. Set:

Security software or specific system files can block the "Agent." "The license manager is not functioning ... - Autodesk