search cancel

CA SDM Installation Failed, with Error Can't find RF Server

book

Article ID: 214769

calendar_today

Updated On:

Products

CA Service Management - Service Desk Manager

Issue/Introduction

CA SDM installation failed at Configuration step with error:  Can't find RF server XXX

 

Cause

From SDM server login to DB is failing

StdLogs have entry as:

pdm_ver               392 ERROR        ServerStatusMonitor.  1783 Can't find RF server XXX
pdm_ver               392 EXIT         ServerStatusMonitor.   587 Slump host XXX is not defined as an RF server or is not configured and active

and install.log:

[DeployThread: Configuring CA Service Desk Manager] [ConfigureSDM] Executing remote query : sqlcmd  -S XXX -U sqladm -P <PASSWORD> -i tmp_sql.sql 
[DeployThread: Configuring CA Service Desk Manager] [ConfigureSDM] Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Named Pipes Provider: Could not open a connection to SQL Server [2]. .
[DeployThread: Configuring CA Service Desk Manager] [ConfigureSDM] Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Login timeout expired.
[DeployThread: Configuring CA Service Desk Manager] [ConfigureSDM] Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

Environment

CA Service Desk Manager 17.x

Resolution

-> We have to check below points on SDM application server:

1. Launch management studio and make sure that we can successfully login with same data given in installation window.
example: if at installation we gave DB server as :xxx
then at management studio-> use the same xxx.

Or if at DB window in installation step you have specified DB server as :xxx,1900 (1900, being new port number you used in instance name)
then at management studio also -> use the same xxx,1900

2. From command prompt check: sqlcmd -S <servername> -U username -P password
update server name, username and password in above syntax with your details.

3. From SQL server configuration manager -> make sure named pipes are enabled and correct port number is updated.

4.Other causes of SQL server error[2], can be found in below link:
https://www.arysontechnologies.com/updates/fix-ms-sql-server-error-2/

Note: The above link is an external global link and if for reference only. Please take the help of you DB admin while performing the steps.