Follow

Troubleshooting a SQL Server Connection

 

 

1) Find the SQL Server's Name. 

 

Generally, when you open SQL Server Management Studio on your server, it will prompt you to connect.

 

The Server Name here is what you are looking for. Once you've connected, this is also what is displayed in the tree on the left hand side. 

In this case, the server name is WIN7-DEV\sql2012.  Sometimes the slash is part of it, if you set up SQL server to allow for multiple instances.  Sometimes it will just show the server name, if it is only set up for a single instance.  

 

2) Test this on your client machine. 

a) On the desktop of your client machine, right-click and choose create new | text file. 

b) Rename this file to temp.udl

c) Double-click this file and it will open a Data Link Properties dialog. 

d) On the Provider Tab, choose "Microsoft OLE DB Provider for SQL Server"

e) On the Connection tab, click the pull down and wait.  In some cases your server will be available in the pull down. 

f) If the server name is not available, type it in.  IN our case we type WIN7-DEV\sql2012  (Note this is a backslash)

g) Choose Windows NT integrated security. 

h) Click the drop-down next to "Select the database on the server".  It should list the databases on the server.  If you created a database for Training Tracker already, it should be listed.  

i) If that didn't work, choose "Use a specific user name and password" and enter the combination you created for the Training Tracker database. (In this case you would have used "Set Up Database Login Option 2" in our MSSQL Installation Guide.)

j) Once you get the list of databases to appear.  Select the Training Tracker database and click "TEST Connection", If this works, use the same information in the Training Tracker database setup screen. 

3) Troubleshooting: If step 2 doesn't give you a list of databases on the server, there are a few things to troubleshoot. 

a) Within SQL Server Configuration Manager, ensure that both Named Pipes and TCP/IP are enabled in the protocol sections of both SQL Native Client 11.0 Configuration and SQL Server Network Configuration.

b) Sometimes the database server name from step 1 doesn't work.  If that's the case, try substituting the IP Address of the server.  For example, 10.10.10.10\SQL2012, if set for multiple instances, 10.10.10.10 if set for a single instance.  Substitute your IP address for 10.10.10.10.

c) Try doing the test in Step 2 on the server.  This will tell you if you have a server setup issue or a network issue. 

d) Try the test from Step 2 on another machine.  If it works there, you probably have a network setup issue. 

e) Is the firewall on the server set to allow connections to SQL Server?  If the server is already in use for other systems, then probably.  If you set it up specifically for Training Tracker on a new server, you might want to check the firewall documentation.  Or, just turn the firewall completely off temporarily and test the connect.  The default ports for SQL Server are TCP port 1433 and UDP port 1434.

f) Within SQL Server Configuration Manager, ensure that the SQL Server Browser service is enabled.

g) Another thing to try is to install Microsoft SQL Server Management Studio Express on the same PC where you are trying to get Training Tracker to work.  See if it will connect.  If it will connect, but Training Tracker doesn't, you probably have mis-typed the connection string. 

 

 

 

 

 

 

 

 

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk