"Not Associated With a Trusted SQL Server Connection" Login Error

Problem:

After logging in, a "Page cannot be displayed" error comes up with the following Technical Information at the bottom of the screen:

Error Type:

Microsoft OLE DB Provider for SQL Server (0x80004005)

Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server Connection.

/qqest/include/Permissions.asp, line 5

Cause:

The SQL Server Authentication is set to "Windows Only."

Solution 1 (for Microsoft SQL Server 2000 Users):

  1. From the Windows Start Menu go to the following location, Programs | Microsoft SQL Server | Enterprise Manager.  The "SQL Server Enterprise Manager" window opens.

  2. From the tree-directory on the left-hand side of the screen, click on the plus sign next to "Microsoft SQL Servers."

  3. Directly under Microsoft SQL Servers, click on the plus sign next to "SQL Server Group."

  4. The TimeForce server for your machine should appear under SQL Server Group.  It will be labeled "COMPNAME\TIMEFORCE (OS)."
    Note:     "COMPNAME" stands for the network name of your computer.  "OS" stands for the Operating System on your machine.

  5. Right-click on your server and select "Properties" from the menu that appears.  The "SQL Server Properties" window opens.

  6. From the row of tabs at the top of the screen, click on "Security."

  7. The very first section in this screen is labeled Security.  For the Authentication setting, ensure that "SQL Server and Windows" is selected.

  8. Click on the [OK] icon and exit the Enterprise Manager.

You should now be able to log into the TimeForce program normally.

Solution 2 (for Microsoft SQL Server Desktop Engine users with a Typical Install):

Note: The following information is taken from a Microsoft Knowledgebase article.

Turn on Mixed Mode Authentication after you install MSDE.

Warning: If you modify the registry incorrectly, serious problems may occur that require you to reinstall your operating system.  Microsoft cannot guarantee that the problems can be solved.  Modify the registry at your own risk.

Microsoft recommends that you back up the registry before you modify it.  If you are running Microsoft Windows NT or Microsoft Windows 2000, also update your Emergency Repair Disk (ERD).

By default, the value of the LoginMode Windows registry subkey is set to "1" for Windows Authentication.  To turn on Mixed Mode authentication after you install MSDE, you must change this value to "2."  The location of the LoginMode subkey depends on whether you installed MSDE as the default MSDE instance, or as a named instance.

  • If you installed MSDE as the default instance, the LoginMode subkey is located in the following registry subkey: "HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode".

  • If you installed the MSDE as a named instance, the LoginMode subkey is located in the following registry subkey: "HKLM\Software\Microsoft\Microsoft SQL Server\Instance Name\MSSQLServer\LoginMode".

To change the value of LoginMode to 2, follow these steps:

  1. In Control Panel, open the Services tool, and then stop MSSQLSERVER and all other related services (such as SQLSERVERAgent).

  2. On the Start Menu, click on Run, type "regedt32", and then click on OK to start the Registry Editor.

  3. Locate either of the subkeys mentioned above (depending on whether you installed MSDE as the default MSDE instance, or as a named instance).

  4. In the right pane, double-click on the LoginMode subkey.

  5. In the DWORD Editor dialog box, set the value of this subkey to 2.  Verify that the Hex option is selected, and then click on OK.

  6. Restart the MSSQLSERVER service and the SQLSERVERAgent service for this change to take effect.

You should now be able to log into the TimeForce software normally.