Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Log & Event Manager (LEM) > Configure the MSSQL Auditor to connect on a custom SQL port

Configure the MSSQL Auditor to connect on a custom SQL port

Table of contents

Updated: September 22, 2016

Overview

The MSSQL Auditor connects to SQL on the default TCP port 1433. If the customer has a custom port and is unable to return it to the default, you can edit the MSSQLAuditor.config configuration file to include the custom port.

Environment

  • All versions of LEM
  • MSSQL Auditor installed

Steps

You can verify the TCP port being used by connecting to the SQL Server and checking the SQL Server Configuration Manager:

  1. Expand SQL Server Network Configuration.
  2. Select Protocols for <SQL Instance Name>.
  3. Verify that TCP/IP is enabled.
    Note: If it is not, you will need to enable this for the MSSQL Auditor to connect.
  4. Double-click on TCP/IP to enter the properties.
  5. Select the IP Addresses tab.
  6. Scroll through the settings to confirm the TCP port.
    Note: The default port is 1433.  If the port is listed otherwise note it for the next section.

 

To use the custom port as discovered in the above steps:

  1. Stop the MSSQL Auditor.
  2. Edit the MSSQLAuditor.config file.
    Note: You will need to be running your text editor as admin. Default location is C:\Program Files (x86)\SolarWinds Log and Event Manager MSSQL Auditor
  3. For the Server string information, you will need to add a Port tag with the custom port.

    Before: <server name="<Hostname or IP>" instance="<SQL instance>" tdf=""/>

    After:  <server name="<Hostname or IP>" instance="<SQL instance>" port="<custom port> tdf="" />

  4. Save the file.
  5. Start the MSSQL Auditor again.

 

 

 

Last modified

Tags

Classifications

Public