The Service

The adTempus service is the "engine" that does the work of executing adTempus jobs. The adTempus service must be installed on each computer on which jobs are to be executed.

If you have configured more than one instance of adTempus on a computer, there will be a service for each instance.

Managing the adTempus Service

The adTempus service can be started or stopped using the Windows Services tool (found in the Administrative Toolsfolder on the Start menu). Once the service is started, all management of adTempus is done using the adTempus Console.

Troubleshooting Service Problems

If the adTempus service cannot be started, the Application log in the Windows Event Viewer will contain one or more error messages indicating what the problem is. See the Service Startup Troubleshooting topic for more information.

Service Account Requirements

For adTempus to be fully functional, the adTempus service must be configured to run under the Local System account, as this is the only context in which adTempus can fully integrate with Windows.

If you are using a remote database server to host the adTempus data, this restrictions means that you must either use SQL Server security, or grant SQL Server access to the machine account of the computer where adTempus is running (see the Database Credentials topic for more information).

If absolutely necessary, it is possible to run the service under a user account instead, but some adTempus features will not be available (see below).

The account that you use for the adTempus service must meet the following requirements:

• The account must be a member of the Administrators group on the computer.

• The account must have the following rights granted through the Local Security Policy:

  • Log on as a service
  • Act as part of the operating system
  • Create a token object
  • Replace a process level token
  • Adjust memory quotas for a process
  • Restore files and directories

  If any of these rights are missing, the adTempus service will fail to start, and will log a message in the Application log in the Event Viewer indicating which privileges are missing. If they have all been assigned to the user account but you still get the error, you may need to restart the computer or perform a policy refresh to force them to take effect.

• The account must be granted read, write, and backup permissions on the database server.

Before you can start adTempus using a user account for the service, you must set a Registry option to enable this configuration:

• Run the Registry Editor and go to the key HKEY_LOCAL_MACHINE\Software\Arcana Development\adTempus\Instances\Default\Options. (Replace "Default" with the instance name if you are configuring an adTempus instance other than the default.)
• Create a new DWORD value named Server:AllowServiceAsUser and set it to 1.

Limitations When Running the Service Under a User Account

When the adTempus service is run under a user account instead of the Local System account, interactive program execution will be disabled (it will not be possible for a job to execute a program that is visible to the user). The only option available for the User Interaction setting for jobs will be "Hidden," and the Make the job visible on my desktop option will not be available in the Execute Job window when you run a job manually.