Error is seen when running the Service Management 14.1 installer when using a named instance of SQL Server:
search cancel

Error is seen when running the Service Management 14.1 installer when using a named instance of SQL Server:

book

Article ID: 35343

calendar_today

Updated On:

Products

SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service CA Service Desk Manager CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

Issue:

 Running the Service management 14.1 installer and SQL installed the mdb is on a named instance of SQL Server using a non-default port.

 When entering the Database configuration information. The following error is returned:

 ! The TCP/IP Connection to the Host has failed. Check the server name and credentials.

 

<Please see attached file for image>

mdb1.jpg

 

The install.log shows: 

015/11/19 11.46.59.248 ERROR [AWT-EventQueue-0] [ConfigureSQLServer] The TCP/IP connection to the host

com.microsoft.sqlserver.jdbc.SQLServerException: The connection to the host AU-mdb-07, named instance test failed. Error: "java.net.SocketTimeoutException: Receive timed out". Verify the server and instance names and check that no firewall is blocking UDP traffic to port 1434. For SQL Server 2005 or later, verify that the SQL Server Browser Service is running on the host.

 

Environment: 

 The problem can be seen on in an environment where a named instance of SQL Server using a non-default port is used during a Service management 14.1 installation. 

 Cause:

This error is seen if a TCP/IP connection cannot be made from the Service Management to the SQL Server\Instance. This can be for a number of reasons:

1.       The SQL Server\instance cannot be reached

2.       The SQL Server Browser service on the MDB database server is not running

3.       The SQL Server Browser port (1434) is not open between the Service management Server and the database server.

 

Resolution/Workaround:

 See the resolution to the above causes below:

 1.       For point 1 above, ensure that the SQL Server box is pingable from Service Management box and that the database port is open for TCP/IP connections between the boxes.

2.       Start SQL Server Browser service on the MDB database server.

3.       Open port 1434 for UDP traffic through the firewall for the SQL Server Browser service, between the Service Management Server and the MDB  database server.

 

 

 

Environment

Release: SDMU0M99000-14.1-Service Desk Manager-Full License
Component:

Attachments

1558697332115000035343_sktwi1f5rjvs16ns4.jpeg get_app