The adTempus service fails to start as described in article K00000222. adTempus logs the following error message in the Application log in the Event Viewer:
The adTempus service cannot be started due to a database problem: adTempus is unable to connect to SQL Server using the user ID (userID) and password specified for the database connection. Login failed for user 'userID'. (-2147217843; native error=18456; SQL state=42000) (DBERROR353).
Additionally, the adTempus diagnostic log contains a line with the following error message:
Database error -2147217843: Login failed for user 'userID'. (source=Microsoft OLE DB Provider for SQL Server; native error=18456; SQL state=42000)
Note: If the user identified in the error message is "NT AUTHORITY\SYSTEM" see article K00000221 instead.
adTempus is unable to connect to the SQL Server database using the account specified in the error message ("userID" in the example above).
Check to make sure the account being used by adTempus is created and enabled in SQL Server, and has full access to the adTempus database.
If the account is present and permissions are correct, the problem may occur if adTempus somehow has the wrong password for the account. You cannot determine what password adTempus is using for the account, but you can reset the password to ensure that adTempus and SQL Server are using the same value.
After changing the password for the account in SQL Server, locate the database connection information being used by adTempus. This information is found in the Registry key "HKEY_LOCAL_MACHINE\Software\Arcana Development\adTempus\Database".
The Password value under this Registry key is an encrypted binary value that stores the password. Delete this value, then create a new "Password" value as a String (REG_SZ) value. Set the new value to the new password for the SQL Server logon account.
Delete the "EncryptedPassword" value, then create a new "Password" value as a String (REG_SZ) value. Set the new value to the new password for the SQL Server logon account.