Microsoft SQL Server being configured with named instances has the "TCP Dynamic Ports" option automatically set with the port number (dynamic port configuration).

Products

• CA Automation Suite for Data Centers - Configuration Automation
• CA Client Automation - Asset Management
• CA Client Automation - IT Client Manager
• CA Client Automation
• CA Client Automation - Remote Control
• CA Client Automation - Asset Intelligence
• CA Client Automation - Desktop Migration Manager
• CA Client Automation - Patch Manager

Issue/Introduction

Symptoms: 

If Microsoft SQL Server is being configured with named instances, the "TCP Dynamic Ports" option is automatically set with the port number (dynamic port configuration). Then, it may happen that the Domain or Enterprise Manager cannot access the database.

 

Environment:  

Client Automation all releases for Windows.

 

Cause: 

Because the port number on the MDB system has changed in the meantime, for example, due to a system restart.

 

Resolution:

To avoid these access failures, we recommend that you change the port setting manually to a static port ID, as follows:

 

1.   From the Windows Start menu, open SQL Server Configuration Manager, SQL Server Network Configuration, Protocols for instance_name, TCP/IP.

 

2.   Right-click and select Properties from the context menu.

 

3.   On the TCP/IP Properties dialog select the IP Addresses tab. In the IP All area, cut the port value in the TCP Dynamic Ports field and paste it into the TCP Port field.

 

Additional Information:

The following installation log can show the messages below:

 

TRC_Inst2_ITRM.log:

=============

|CiCheckDBMsSQL::msSQLName: The instance does not contain the port

| server <database_server_name\instance_name,1433> is using port no <64766>

Environment

Release: UASIT.99000-12.8-Asset Intelligence
Component: