Syskit Monitor
Try it for FreeContact UsProduct Site
  • Syskit Monitor
  • Product Updates
    • Syskit Monitor 9.1.0 - Release Note
    • Syskit Monitor 9 – The monster has awoken!
    • Syskit Monitor 8.4.0 - Release Note
    • Syskit 2012 R2 8.3.0 - Release Note
    • Syskit 2012 R2 8.2.0 Release Note
    • Syskit 2016 R2 8.0.1 - Release Note
    • Syskit 2016 R2 – Monitor and script all the things!
  • Requirements
    • System Requirements
    • User Permission Requirements
    • Pre Installation Requirements
  • Installation and Configuration
    • Install Wizard
      • Install Syskit Monitor
      • Install Syskit Monitor Data Collector
    • Configuration Wizard
      • Configure Syskit Monitor
      • SQL Permissions
        • Create a SQL Server Login
        • Create a SQL Server Database
        • Create a Service User Login Permission
        • Connect an Existing Database
    • Upgrade to the Latest Version
    • Uninstall Wizard
  • Editions
    • Editions
  • Activation
    • Activation Privacy Statement
    • Online and Offline Activation
    • Activation FAQ
  • Get to Know Syskit Monitor
    • Quick Start Guide
    • Administration
      • Servers and Groups
      • Monitoring Templates
      • PowerShell Scripts
    • Backstage Screen
      • Manage Data Gathering
      • Help Screen
      • Configuration
        • Configure
        • Options
      • Syskit Monitor Web App
    • Dashboards
      • Sessions Dashboard
      • Performance Dashboard
    • Reports
      • User Reports
      • Application Reports
      • Performance Reports
        • System Overview
        • Computer Performance
        • Application Performance
        • User Performance
      • Gateway Reports
      • License Reports
      • Event Log Reports
      • Inventory Reports
        • Hardware and Software
        • Powershell Reports
        • Compare Wizard
      • Custom Reports
  • Common Tasks with Syskit Monitor
    • Monitoring Windows Server and Application Performance
    • Monitoring and Restarting Stopped Windows Services
    • Real Time Alerting
    • Monitoring User Activities and Application Usage
    • Monitoring RD Gateway Connections
    • File System Auditing
    • Malicious IP Blocking
    • Computer Inventory
  • How To
    • Custom Reports
      • Create Custom Report
      • Create SQL Custom Report
      • Create an Alert
    • Users
      • Add Users Manually
      • Add Users From Active Directory
      • Manage Security Permissions
    • Dashboards
      • Create a Custom Dashboard
      • Edit Dashboards
      • Add Formatting Condition to Metrics
    • Reports
      • Export Report to Excel
      • Configure Cost Overview Report
      • Configure Report Subscriptions
      • Create Customized Report Views
    • Computers
      • Add/Remove or Delete Computer from Monitoring
      • Add Citrix Servers to Monitoring
    • Monitoring Templates
      • Predefined Monitoring Templates
      • Template Wizard
      • Import / Export Monitoring Template
      • Download Templates
    • Powershell Scripts
      • PowerShell Wizard
      • Manage Scripts
      • Import / Export PowerShell Script
      • Import and Use PowerShell Script Modules
      • Download Scripts
    • Service Accounts
      • Add Service User to Local Administrators Group via Group Policy
      • Add Service User to Local Administrators Group Manually
    • Audit Events
      • Enable Folder Auditing
      • Configure Audit Logon Events
      • Configure Syskit Monitor server to support the Block Malicious IP Addresses feature
    • Citrix Xenapp
      • Allow Remote RPC on Xenapp
      • Monitor Citrix Published Applications
      • Configure Syskit Monitor for Citrix XenApp 5 Published Application monitoring
      • Configure Syskit Monitor for Citrix XenApp 6.x Published Application monitoring
      • Configure Syskit Monitor for Citrix XenApp 7.x Published Application monitoring
    • Performance Counters Management
    • Manage Syskit Monitor Data Collector
    • Move database to new server
    • Exclude installation folder from antivirus scanning
  • FAQ
    • FAQ
  • Troubleshooting
    • SQL Server Connection
    • SQL Server Express 2012 LocalDB
    • How to resolve the Offline and Unauthorized computer states
    • Network Ports
    • Fixing WMI to work with Syskit Monitor
    • Enable-PSRemoting for untrusted domains to work with Syskit Monitor
    • Configuring CredSSP for use with PowerShell in Syskit Monitor
    • Installation Issues
    • User States
    • User Connections
    • Miscellaneous
Powered by GitBook
On this page
  • How to configure the SQL Server to listen on a specific port
  • Problem:
  • Solution:
  • Error: Configuration Wizard won’t connect to a provided server and database
  • Problem:
  • Solution:
  • Error: Check if your SQL Server is configured to use a named instance
  • Problem:
  • Solution:
  • Error: TCP/IP network traffic is not enabled on the SQL Server
  • Problem:
  • Solution:
  • Error: Inbound traffic on TCP Port 1433 needs to be allowed on the SQL Server
  • Problem:
  • Solution:

Was this helpful?

  1. Troubleshooting

SQL Server Connection

This article explains how to troubleshoot some of the most common SQL Server Connection problems to get the Syskit Monitor up and running.

How to configure the SQL Server to listen on a specific port

Problem:

How to configure the SQL Server to listen on a specific port?

Solution:

Due to security issues it is often not recommended to use the default port number 1433 for communicating with the SQL Server. This article helps set up the SQL Server to use a non-standard port number.

1.Run the SQL Server Configuration Manager. 2. Select the SQL Server Network Configuration. 3. Select from the list the instance you want to configure to listen to on a specific port. 4. To change the port assignment right-click on the TCP/IP protocol and select Properties. 5. Click on the IP Addresses tab.

Both IP5 and IP6 are disabled and the TCP Dynamic Ports setting is set to “0”, which means that the database engine is listening on dynamic ports. This instance currently uses the port number 1433.

  1. Specify the TCP Port number you want to use instead of 1433, by entering the preferred port number. In this case the new port number is going to be 8181. Also, turn off the dynamical port number setting by removing the “0” mark in the TCP Dynamic Ports field for both IP5 and IP6.

  2. In order to finish the adjustment, select SQL Server Services, right-click the SQL Server and restart it.

Error: Configuration Wizard won’t connect to a provided server and database

Problem:

The SQL Server Browser service is not running. When this service is not running you cannot connect on named instances.

Solution:

The SQL Server Browser service needs to be up and running.

  1. Open the SQL Server Configuration Manager on your SQL server.

  2. Click on the SQL Server Services. Find the SQL Server Browser service, right-click on it and press Start.

  3. Do not forget to allow inbound traffic on TCP Port 1434. Refer to the last paragraf for more detailed information.

Error: Check if your SQL Server is configured to use a named instance

Problem:

The wrong database server name has been entered while trying to connect to the database server through the Syskit Monitor Configuration Wizard.

Solution:

Check if your SQL server is configured to use a named instance, e.g. Server/InstanceName.

  1. Run the Microsoft SQL Server Management Studio and connect to the desired SQL Server instance.

  2. Right-click on the SQL Server instance and select Properties.

  3. Check the full server Name, i.e. both server and instance name.

  4. Change the server name in the Syskit Monitor Configuration Wizard according to the name written in the Microsoft SQL Server Management Studio.

  5. The SQL connection should now be available.

Error: TCP/IP network traffic is not enabled on the SQL Server

Problem:

TCP/IP is not enabled on the SQL Server.

Solution:

TCP/IP network traffic needs to be enabled on the SQL Server, so that remote connections can be allowed on the SQL Server.

  1. Run the SQL Server Configuration Manager.

  2. Click on the SQL Server Network Configuration.

  3. Select Protocols for SQLEXPRESS and check if the TCP/IP Protocol is enabled.

  4. If the TCP/IP is disabled, double-click on it and change the Enabled row status to Yes.

  5. In order to finish the adjustment, select the SQL Server Services, right-click on the SQL Server and restart it.

  6. The SQL connection should now be available.

Error: Inbound traffic on TCP Port 1433 needs to be allowed on the SQL Server

Problem:

Port 1433 is closed on the SQL Server.

Solution:

Inbound traffic on the TCP Port 1433 needs to be allowed on the SQL Server.

1.Connect to your SQL Server. 2. Open the Windows Firewall, click on Inbound Rules and select New Rule. 3. In the Rule Type step, select the Port rule type. 4. In the Protocol and Ports step, select the TCP port and specify the local ports which this rule applies to. In this case, 1433 stands for the SQL Server, and 1434 for the SQL Server Browser. Enter the ports in the following format: 1433,1434. 5. In the Action step, leave the default selection: Allow the connection. 6.In the Profile step, select the profiles which this rule applies to.

If the SQL server is in the same domain with other servers and you wish to open this port only for the domain traffic, it is enough to select Domain. For other scenarios use the Private or Public profile option.

7.In the Name step, specify the name and the description of this rule, e.g. Name: SQL, and the Description: Allows SQL to connect to the SQL Server and SQL Server Browser. 8. The inbound traffic on the SQL Server is now allowed and the SQL connection should be available.

PreviousTroubleshootingNextSQL Server Express 2012 LocalDB

Last updated 2 years ago

Was this helpful?