Home / SQLDBManager Plus Troubleshooting / SQL Server Monitoring / SQL Server Fails - Service Not Running

SQL Server Fails - Service Not Running


3. Adding a SQL Server fails with error message "Service is not Running. Root Cause: Service port 1433 not accessible"

Reason1 : The SQL Server port is not accessible from SQLDBManager Plus
Solution  : Check if you can access the SQL Server port from SQLDBManager Plus server by using the following command in command prompt : "telnet <sqlhost> <port>" ( ex: telnet sqlserver 1433 ). When you execute this command, you should get a blank screen, instead if you get any error messages you need to check if TCP/IP protocol is enabled in SQL server or if there is a firewall blocking connections between SQL Server and SQLDBManager Plus

Reason2 : TCP/IP protocol is turned off in the SQL Server
Solution  : You need to enable TCP/IP protocol for connecting to the SQL Server. To enable it, in SQL Server Configuration Manager go to Network Configuration > Protocols and enable  TCP/IP protocol there. Also in TCP/IP Properties, you need to mention the SQL port ( 1433 by default ) under IPAll > TCP Port. After you have changed the configurations, restart the SQL Server for the settings to take effect.




 RSS of this page