Summary
When the adTempus service fails to start, the cause of the failure is not immediately apparent, because you only receive a generic error message. This article describes how to determine the problem.
Symptoms
When the adTempus service cannot start due to a configuration problem or other issue, the adTempus service will fail to start, and Windows will return a generic error message:
The adTempus service could not be started. The service did not report an error. More help is available by typing NET HELPMSG 3534.
or
Could not start the adTempus service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, contact your system administrator.
or
The adTempus service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
Troubleshooting
Repairing or reinstalling the adTempus software is almost never useful for resolving startup problems, and is more likely to cause additional problems. If the troubleshooting information below and elsewhere in the Knowledge Base does not help you resolve the problem, contact us for assistance before repairing or reinstalling.
Event Log
When the adTempus service fails to start, you should first check the Application log in the Windows Event Viewer. adTempus usually will log an error message here indicating why the service could not be started. The message in the Event Log may provide the reason for the failure (e.g., a license problem) or it may refer you to a diagnostic log file for more information (see the next section for information on diagnostic log files).
Diagnostic Log File
If adTempus does not report an error in the Event Log, or if the Event Log message refers you to a diagnostic log, the next step is to examine the appropriate log file. To locate the diagnostic log file:
The log files can be viewed using a text file viewer or editor such as Notepad.
If the Event Log message referred you to a specific log file, open that file. If there was no Event Log message, examine the most recent server log file.
Though the information in the log files is generally technical and intended for use by Arcana Development, you may be able to determine the problem from the log. Common error messages are listed in the More Information section below.
Contact Arcana Development
If you are unable to determine the cause of the problem based on the Event Log and diagnostic logs, contact us for support. Be sure to include the following information with your support request:
- The exact wording of any error message(s) in the Event Log.
- A ZIP archive containing all of the adTempus server log files.
Common Problems
The following articles discuss commonly-encountered database problems:
- Login failed for user 'adtempus_XXX'. Reason: Not associated with a trusted SQL Server connection
- adTempus is configured to use SQL Server security (user ID and password), but the SQL Server instance is configured to allow only integrated (Windows) security
- Login failed for user 'NT AUTHORITY\SYSTEM'
- Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
- Login failed for user 'adtempus_XXXX'
- Cannot open database requested in login 'adtempus_XXX'. Login fails
- Cannot open database "adtempus_XXX" requested by the login. The login failed
- SQL Server does not exist or access denied
- Cannot generate SSPI context
- Could not find server in sys.servers
- For adTempus 3: Cannot connect to database after TLS 1.0 is disabled
The following articles discuss non-database issues:
- Problems with adTempus when name of host computer is changed
- adTempus fails to start due to license problem during computer boot-up, but can be started manually
- adTempus fails to start if configured with missing or invalid SSL certificate
- adTempus service fails to start with error "There is already a listener on IP endpoint"
