Here are some various troubleshooting steps you can take to find the root cause of the error and their subsequent resolutions:
1. Go to Start
2. All Programs
3. Microsoft SQL Server
4. Configuration Tool
5. Click SQL Server Configuration Manager
6. Expand SQL Server Network Configuration
8. Enable TCP/IP Right box
9. Double Click on TCP/IP
10. Go to IP Addresses Tap and Put port 1433 under TCP port.
- If you see that SQL Server/ SQL Server Browser State is 'stopped', right click on SQL Server/SQL Server Browser and click start.
- In some cases above state can stop though TCP connection to port 1433 is assigned.
Enable TCP/IP (Listen All):
1. Open SQL Server Configuration Manager, and then expand SQL Server Network Configuration.
2. Click Protocols for InstanceName, and then make sure TCP/IP is enabled in the right panel and double-click TCP/IP.
3. On the Protocol tab, notice the value of the Listen All item.
4. Click the IP Addresses tab: If the value of Listen All is yes, the TCP/IP port number for this instance of SQL Server is the value of the TCP Dynamic Ports item under IPAll. If the value of Listen All is no, the TCP/IP port number for this instance of SQL Server is the value of the TCP Dynamic Ports item for a specific IP address.
5. Make sure the TCP Port is 1433.
6. Click OK.
Host reachable and running:
- Check the host is actually reachable and running.
- A good check I often use is to use telnet, eg on a windows command prompt run: telnet 127.0.0.1 1433
- If you get a blank screen, it indicates network connection established successfully, and it's not a network problem.
- If you get 'Could not open connection to the host' then this is network problem.
- Check to see if your SQL server hostname, username, and password is correct.
- Check there is no firewall rule blocking TCP connection to port 1433.
- Remove your port information and try to reconnect.
- You should specify either Instance Name or Port number for SQL Server, not both.
SQL Server Express:
- Are you using a dynamic or static port?
- Remove the dynamic entry and enter the static under TCP port.
- You also need to enable TCP/IP as by default it assumes a local memory connection.
Profiles.xml for Subset:
- Go to C:\%AppData%\Roaming\Grid-Tools
- Open your Profiles.xml file in a program like Notepad.
- Verify that the server name, password, and other connection details are listed correctly throughout the file. (They will appear multiple times)
- Save the file.
- Re-launch Datamaker and Subset.
- If Profiles.xml was corrupted:
- Delete profiles.xml from C:\%AppData%\roaming\Grid-Tools folder.
- Launch GTSubset and create the new profiles for source and Repository connections.
Localhost or IP Address:
- Typically when you connect to SQL Server DB from SQL Server Management Studio or from ODBC admin, using the server name 'local' works because it is internally translated.
- For connecting to a generic application, like Subset, that asks for server name, you need to enter either localhost or the IP address.
- When you change the Server Name to 'localhost' or the IP Address, you will able to connect to Subset.