Machine ID and Database Ownership

When you start the adTempus service for the first time on a new computer, adTempus generates a Machine ID to uniquely identify this instance of adTempus. This value is stored in the Registry and also in the adTempus database.

Database Ownership

If another adTempus instance (running on the same computer or a different computer) tries to connect to the adTempus database, the service will fail to start and will log the following message to the Application log in the Event Viewer:

The adTempus database belongs to another instance of adTempus. To switch ownership to this instance, start the adTempus service with the "-resetdbowner" option.

This is done to protect against accidentally running two adTempus instances against the same database. Depending on your scenario, use one of the following options to override this error condition:

The adTempus software has been transferred to a new computer and the new installation should now be the owner of the database: Use the "-resetdbowner" startup option to permanently reset the ownership information in the database.
You have made a copy of the adTempus database for use by the adTempus software on a new computer: Use the "-resetdbowner" startup option to permanently reset the ownership information in the database.
The adTempus service needs to use this database temporarily (e.g., for testing or disaster recovery failover). Use the "-ignoredbowner" startup option to temporarily ignore the database owner. Before doing this, ensure that no other adTempus instances are running using this database.

Resetting the Machine ID

If you have cloned the server where the adTempus service is installed, you should also reset the Machine ID on the cloned server if adTempus is still running on the new server. To do this, restart the adTempus service using the "-resetidentity" startup option.