NOTES

1

Clearly verify that the Client Edition is already installed and at least one user / interface is already able to connect and that they are using Windows Authentication.

2

Start on the SQL server. Note whether this is a SQL Express installation. Note the exact SQL Server name at it appears in Object Explorer.

3

Confirm that the windows login ID of the new user has been added to the SQL database. Check that it has read / write permissions for the TRAIN TRACK database.

4

Move to the workstation that is unable to connect.

5

Clearly verify that you are signed in with the windows login ID of the new user.

6

Is there a user ODBC connection in place?

7

Is it testing successfully?

8

Launch the application, click through the error messages and attempt to connect using a DSN Less connection.

9

From the Control Panel, create a user ODBC with the SQL Server Driver using the exact server name as it appears in SSMS - does it work? Note that is this is a SQL Express instance “\SQLEXPRESS” will appear after the server name.

10

Confirm that the user may browse to the server – i.e. pull up Object Explorer on the workstation, confirm the server appears under Network and that if you double click on it, it opens.

11

Repeat step 9 but this time, when creating the ODBC, from the “Create a New Data Source to SQL Server” screen, click the Client Configuration button and change the Network Library from TCP/IP to Named Pipes.

12

Attempt step 9 using the IP address of the server.

13

If this is a SQL Express installation, attempt step 9 using the IP address of the server with \SQL Express added.

14

Create new ODBC using the application in C:\Windows\SysWow64\odbcad32.exe. Does it test successfully?

15

Attempt step 13 using the IP address of the server.

16

If this is a SQL Express installation, attempt step 13 using the IP address of the server with \SQL Express added.

17

Is there a firewall on the new workstation that is preventing the connection? Can it be disabled?

18

Is there virus protection software on the new workstation that is preventing the connection?

Once the ODBC connection is made, launch the TRAIN TRACK application and enter the registration code. Go to DBA > Edit Users and add the windows login name of the new user. Close and re-open the application to confirm everything is working correctly.

Yes, but the interface will not connect.

No

Is there an ODBC connection in place?

Is the user connecting with SQL authentication using the SQL db user and password. Is “trusted connection” Unchecked?

Has the SQL db user been added to tbl.pswd with the correct password?

Is it testing successfully?

While logged in as the TRAIN TRACK user, create a USER ODBC, does it work?

Delete and add a new ODBC using the application in C:\Windows\SysWow64\odbcad32.exe. Does it test successfully?

Is the windows login ID of the TRAIN TRACK user added to the SQL database

Can I connect using those same SQL setting on my computer? If so, can I save a copy of the interface with those settings in Linked Table Manager and send it to the client?

Are we sure it is the actual windows login ID of the currently signed in user?