This requires being connected to your server.
The Connection refused exception is given when it is unable to connect to the repository server, which commonly happens while attempting to connect to Microsoft SQL Server. This means that java cannot open a socket to the specified TCP/IP port. There are a few areas in Microsoft SQL Server to check.
Resolution
TCP/IP
Please ensure your SQL Server is configured to use TCP/IP. TCP/IP can be enabled in the SQL Server Network Utility application in SQL Server 2000 or the SQL Server Configuration Manager application in SQL Server 2005 or later.
In SQL Server 2000, TCP/IP is enabled as follows:
- Start the SQL Server Network Utility with the application C:/Program Files/Microsoft SQL Server/80/Tools/Binn/SVRNETCN.exe.
- Select the TCP/IP protocol and transfer the selection to the Enabled’ protocols frame.
- Select the Apply button.
- Select the OK button.
- Restart the <SQL SERVICE> service in Administrative Tools>Services
In SQL Server 2005 or later TCP/IP is enabled as follows:
- Select Start -> Microsoft SQL Server 2005/2008 -> Configuration Tools -> SQL Server Configuration Manager
- In SQL Server Configuration Manager, expand the node SQL Server 2005/2008 Network Configuration-> Protocol for <SQL SERVICE> -> select TCP/IP -> right-click on TCP/IP -> select Enable
- Click on SQL Server 2005/2008 Services then right-click on the SQL Server <SQL SERVICE> and select Restart
- Restart the iDashboards Application
Port
In SQL Server 2005/2008, Check the port SQL Server is listening on as follows:
- Select Start -> Microsoft SQL Server 2005/2008 -> Configuration Tools -> SQL Server Configuration Manager
- In SQL Server Configuration Manager, expand the node SQL Server 2005/2008 Network Configuration -> Protocol for <SQL SERVICE>
- Right-click on the TCP/IP protocol, select Properties, and then select IP Addresses
- Validate the port that SQL server is listening on 1433
- The default SQL Server port is 1433
- You may see a long list of IP addresses. Determine the IP address and port that the iDashboards server will connect to.
Find out how to validate the connection using Telnet.
Check the Security Setting within SQL Server
A common issue is that users create a custom User in SQL but do not allow for the connection. In Management Studio right click on the server connection and then Properties. Select Security and verify your Server Authentication method.
For More Information: Microsoft Troubleshoot Connecting to SQL Server
Disclaimer: iDashboards Technical Support Engineers are not Database Administrators who know in depth knowledge of them and their quirks. We often learn these skills on the job and have limited knowledge. We do our best to help you with your software in determining if: you are not leveraging the software in the best way for your data or you found a bug in the software, because we want to assist you in your success.
If the above is unable to resolve the issue, then please contact iDashboards Support for further assistance.
Comments
0 comments
Please sign in to leave a comment.