Resolving Connection Problems

Parent Previous Next




RESOLVING CONNECTION PROBLEMS




From time to time an SMS user may experience issues connecting to the SQL database hosting

the SQL data for SMS. This will usually occur right after clicking on the icon to launch SMSTurbo.

An error like the one above may appear. Notice the verbiage of the error indicating a connection problem

occurred.



Cause #1


The error indicates it could not connect to the server called Engineer1 with the database called QXB_dat.


SMSTurbo will attempt to connect to the server and database indicated in the smssettings.ini file located under

c:\users\<logged in user>\appdata\roaming\creativeinfosystems folder.


Screen shot of the contents of the Creativeinfosystems folder showing the smssettings.ini file.




Screen shot of the smssettings.ini file. Note the information at the top of the file. Make sure the correct SQL instance is listed.


Server=servername\instance name

DatabaseName=QXB_dat


Each logged in Windows user needs to have the creativeinfosystems folder, with the smssettings.ini file under their profile or the system will not be able to find the SQL server and you could get the above error.


Cause #2


The server indicated in the smssettings.ini file is no longer accessible on the user's network. This could be because the server is:


A. Not running or powered down. See if you can ping the server's name or IP address from a Windows command prompt.

If the server name cannot be reached try pinging the listed IP for the server. If that works but not the name it may be a DNS issue

where the name and its associated IP address are not linked. See your IT or ISP on this.


B. The server is not running the SQL server services on the host server, in this case, engineer1.

    On the server navigate to control panel,administrative tools,services. You will see the below services under SQL.



Notice that the services called "SQL Server (SMSSQL) " and "SQL Server Browser" are both "Running".

the startup state is set to "automatic" which means that if the computer restarts the service should restart

automatically. If the services are set to "disabled" then an administrator account will have to right click on

the service, select "properties" and set the service to "automatic". The other SQL services that are disabled are ok.


If either is NOT running, Right click on the service and select "start". Wait until it says "running".

Attempt to launch SMSTurbo again from the effected machine to see if it's fixed.


C. Microsoft SQL Configuration Manager is improperly configured.  Navigate to Programs, Microsoft SQL server,

Microsoft SQL Configuration Manager Tool.  Run this tool.  When it launches make sure that the protocols for

TCPIP and Named Pipes are enabled.  Restart the "SQL Server (SMSSQL)" service if you have to enable them.


In Microsoft SQL Management Studio log in as an administrator using the account cis and it's password. Make sure

this mixed mode authentication works and lets you login. If it s does not then the administrator access for the account cis is broken

and will need to be fixed.


In the left hand object explorer tree right click on the top of the tree where it lists the server and instance name. Select "properties", Select "Connections", on the left. and make sure that the selection for "Remote Server Connections" is enabled.



D.  Anti-virus or Firewall software was recently activated on one of the machines.  This could be because it was

activated deliberately or by accident. When security software is restarted, as in a re-boot, or for the first time,

it will often start with many network protocols or ports blocked by this software. Disable the anti-virus and the firewalls

to test if they are blocking communication.  Keep in mind Windows has its own default firewall that gets enabled if the anti-virus

does not have its own. Locate that one in Control Panel to make sure its turned off to test. Normally you should NOT have to re-boot the

machine after making these changes for them to take effect. If you WANT the firewall running make sure the correct

protocols are enabled through it per below.


Blocked SQL protocols


      Run "SQL Server Configuration Manager" on the SQL server machine.  On the left under "SQL
      Server Network Configuration", expand to show "Protocols for SMSSQL" or "Protocols for <instance name>". right click on

      "TCP/IP" on the right, select "properties", bring forward the "IP Addresses" tab and scroll down to the bottom of the page to view

      "TCP Dynamic Ports"  the port will be listed there. i.e 50504.  If a firewall is running between the client and SQL server make sure that a

       rule is created to allow this protocol through.