Errors and messages
Needs dev input: remove before publishing
TODO: Confirm that each knowledge base article in this list still applies at 26.09.1. Evidence: none; the articles date from 2023 to 2024.
Use this page to find the article for an error or message that you see in the web UI, in the Access History, or in an API response. Each link text is the exact text of the error. For errors that don't have their own article, see Common UI errors.
Sign-in and authentication
- Invalid Token: The Google Authenticator token is incorrect or out of sync.
- SAML assertion not yet valid: Single sign-on fails because the clocks of the identity provider and the product host differ.
- Password Expired: The Active Directory account that the product uses to bind to the domain controller has an expired password.
- Invalid Request: The web UI sign-in fails and file copies stop at the start of the copy.
Scanning and access requests
- 4Domain only applies with name: An error on the Grant Access page caused by an invalid local group member.
- 9999 Mismatch in service account username when attempting to rotate service password: An error during a scan of an endpoint.
- 'module' object has no attribute 'MODE_CCM': An error in the Access History or during a rescan, caused by Server Message Block (SMB) encryption.
- Offline Access Management (OAM) alternate administrator account is locked and the local Administrator (RID 500) account is disabled: The system left the domain or lost trust.
Linux registration
- Invalid SSH Credentials Authentication Failed: Registration fails because of the registration account or the sudoers configuration.
- Unhandled error: MODULE FAILURE See stdout/stderr for the exact error: An error with code 1779 when you scan or register a Linux system.
- SSH connection error: encountered RSA key, expected OPENSSH key: An
UnprocessableEntityErrorduring registration. - Missing Result for Task checkAdminPrivilege. Code: 9999: An
UnprocessableEntityErrorwhen you register a rebuilt system. - 'ascii' codec can't encode character: A registration error caused by a non-ASCII character in the sudoers file.
Errors in this documentation
Common UI errors explains the following errors:
rpc_s_access_denied- 403 Error: Forbidden from viewing this resource
STATUS_NONE_MAPPEDSTATUS_SPECIAL_ACCOUNT- Your request is taking longer than usual to process
- Unable to connect to system: Host is offline
STATUS_LOGON_FAILURE,STATUS_ACCOUNT_LOCKED_OUT, andSTATUS_LOGON_TYPE_NOT_GRANTEDSTATUS_ACCESS_DENIEDSTATUS_NOT_SUPPORTEDSTATUS_NO_LOGON_SERVERS- Connection timed out, connection refused, and no route to host
Your configuration is not valid. (ECONNRESET)Remote script exited with error: see details in log- The file doesn't have a header with value "Name"
Related articles
The following articles explain how a feature or a check works: