Renaming the Computer

If you rename the computer on which adTempus is running, the adTempus service may fail to start or may behave incorrectly. Check the following items after renaming the computer.

License

The license is tied to the name of the computer, and becomes invalid when the computer is renamed. The service reports a licensing error and does not start. To correct this, reactivate the software as described in License Invalid After Renaming the Computer.

Database Connection Settings

If the database is on the same computer, check the "server" value in the database connection settings. If it contains the old computer name (e.g., "oldname\ADTEMPUS"), replace the computer name with "." (e.g., ".\ADTEMPUS"). Do not change the "database" value, even if the database name contains the old computer name.

SQL Server Express Server Name

Renaming the computer can also cause problems within SQL Server Express. adTempus may fail to start, fail to record job history, or report database errors such as:

  • Could not find server 'newname\ADTEMPUS' in sys.servers.
  • The cursor does not include the table being modified or the table is not updatable through the cursor.

To correct this, run the Database Utility and execute the following commands, pressing F5 after each one. Replace oldname with the old computer name and newname with the new name.

sp_dropserver 'oldname\ADTEMPUS'
sp_addserver 'newname\ADTEMPUS', local
EXEC sp_serveroption 'newname\ADTEMPUS', 'DATA ACCESS', TRUE

If you do not know the old name, run select name from sys.servers to find it. Then restart the adTempus service.

Remote SQL Server

If adTempus connects to a remote SQL Server using Windows integrated security, it connects using the computer account ("domain\computername$"). After a rename, make sure the login in SQL Server is for the new computer account (see SQL Server Computer Account).