Article ID: K00000217
Last Updated: June 25, 2015
The adTempus service fails to start as described in article K00000222. The adTempus diagnostic log contains a line with the following error message:
Error -2147467259: Login failed for user 'adtempus_XXX'. Reason: Not associated with a trusted SQL Server connection. (source=Microsoft OLE DB Provider for SQL Server; native error=18452; SQL state=42000)
adTempus may also report the following error in the Application log in the Event Viewer:
adTempus is trying to connect to the SQL Server database using SQL Server (password) security, but SQL Server security has not been enabled on the database server.
To resolve this issue you may use any of the following approaches:
- Enable enable SQL Server (password) security for SQL Server. See "Security Setup" section of the Using a Standalone SQL Server Instance topic in the online help for more information.
- Give the adTempus server account the necessary permissions in SQL Server as described in article K00000397.
- Change the adTempus service to run under a user account and use integrated (Windows) security. See "Security Setup" section of the Using a Standalone SQL Server Instance topic in the online help for more information. Note: This approach is no longer recommended, and is not supported beginning with adTempus version 4.
If adTempus was previously working correctly on this computer but you are now encountering this error, there are two likely causes:
- The remote SQL Server has been reconfigured to no longer allow SQL Server security and only allow Integrated security. In this case, you will need to change the SQL Server settings to again allow SQL Server security, or reconfigure adTempus to run under a user account.
- adTempus was reinstalled and the database settings for the existing database were not specified correctly during installation. In this case you need to reconfigure adTempus to run under a user account.