Symptoms

During adTempus installation, the Database Configuration Wizard is run to configure a database for adTempus. If you select the option to have the Configuration Wizard connect to SQL Server using Windows (integrated) security, the Configuration Wizard may fail with the following error:

Creating database
Cannot open database connection: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
Database creation failed

This occurs in either of the following situations:

• You are using a SQL Server instance on another computer
• You are using a local SQL Server instance, but the computer's SYSTEM account does not have administrator permissions in SQL Server.

Cause

This error occurs because during setup the Database Configuration Wizard is being run in the Local System security context used by the Windows Installer. Since the Local System account has authority only on the local computer, a remote SQL Server will not accept the connection unless a trust relationship has been established between the computers. For a local SQL Server instance, the operation will fail if the system account does not haver administrator permissions.

Workaround

There is no need to uninstall or reinstall the adTempus software as a result of this error.

After this error occurs, click Finish to close the Database Configuration Wizard. The adTempus software remains installed, but is not usable because the database connection has not been configured.

Run the "adtdbconfig" program found in the "database" directory under the adTempus program directory (e.g., "c:\program files\arcana development\adtempus\database") and go through the configuration process again. The Configuration Wizard is now running under your user account and therefore will be able to connect to SQL Server (assuming that you have the necessary permission for the server).

If your SQL Server instance is configured to allow SQL Server security (explicit user ID and password), you can avoid this problem when performing future installations by choosing the option to enter explicit credentials in the database configuration wizard.

Additional Causes

If this error still occurs when you run adtdbconfig under your user account, possible causes include:

• You have entered the name of the SQL Server incorrectly, or SQL Server is not running.
• Your user account does not have permission to connect to SQL Server. Check the security settings for the SQL Server instance, or select the option to use explicit credentials when going through the database wizard.