When I run checks against my SQL Named Instance, it returns data from my Default Instance. (NETIQKB50796)

  • 7750796
  • 02-Feb-2007
  • 19-Sep-2007

Resolution

fact
NetIQ Vulnerability Manager 5.5

fact
NetIQ Vulnerability Manager Agent for Windows 5.5

symptom
When I run checks against my SQL Named Instance, it returns data from my Default Instance.

symptom
The port number specified in the endpoint for my SQL Named Instance is 1433.

cause
The port number or Named Pipe used on the Named Instance endpoint is the same as is used on the default instance.

fix

By default, the Default SQL Instance uses port 1433.  The SQL Named Instance uses a different port number or named pipe.  Change the properties of the SQL Named Instance endpoint to reflect that port number or named pipe. 

To verify the port used by other Microsoft SQL Server Named Instances perform the following steps:

  1. Log on to a Named Instance SQL Server computer as a member of the SQL Administrators group.

  2. Start the Enterprise Manager in the Microsoft SQL Server program group.

  3. In the left pane, expand the Microsoft SQL Servers > server group> Named Instance SQL Server> Management > SQL Server Logs.

  4. Where server group is the server group containing the SQL Server used for the named Instance and Named Instance SQL Server is the SQL Server used for the Named Instance.

  5. In the left pane, click Current.

  6. In the right pane, look for an entry that begins with SQL Server listening on.  This will list the IP Address of the server, followed by the port number the SQL Server uses.

  7. Verify the port number used by the SQL Server.

  8. Close Enterprise Manager and log off the computer.

  9. Log on to the Vulnerability Manager computer.

  10. Change the properties of the SQL Named Instance endpoint to the port number or named pipe you obtained in Step 6.

Alternately, you can contact your DBA to obtain the port number or Named Pipe the SQL Named Instance uses.



Additional Information

Formerly known as NETIQKB50796

Feedback service temporarily unavailable. For content questions or problems, please contact Support.