This error is usually self-explanatory — you may have entered the wrong username or password. If you're sure the details are correct, click **Error Details** for a more detailed error from the ADM Client application. Look in the Inner Exception trace for the specific cause. Common Inner Exception errors and their meanings are listed below.
Unable to log in to ADM: Invalid User Details
You have likely entered incorrect login details.
If you are unable to log in due to Invalid User Details, contact your ADM administrator. They may be able to reset your password.
Unable to log in to ADM: The ADM application needs to be upgraded
This is likely because the application version does not match the database version.
If you require a different version of the ADM application, contact the Access support team.
The transaction log for database '<ADMdatabasename>' is full due to 'LOG_BACKUP'
This indicates that the ADM database log files have grown too large, leaving insufficient space on the SQL server system drive to execute queries.
If you are seeing the Inner Exception error The transaction log for database '<ADMdatabasename>' is full due to 'LOG_BACKUP' contact your IT team, as this is an environmental issue that needs resolving internally.