search cancel

Application Server not starting

book

Article ID: 213165

calendar_today

Updated On:

Products

CA Service Management - Service Desk Manager

Issue/Introduction

Customer installed CA SDM in a new environment, and successfully migrated the configurations from a previous Service Desk Manager installation to the New Application Server environment using the sdmp -a export/Import command methods as detailed in the Techdocs(https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/ca-service-management/17-3/administering/administering-ca-service-desk-manager/ca-sdm-environment-promotion/ca-sdm-configuration-and-customization/export.html).  However, when the command to start the app server using net start pdm_daemon_manager executed, the cmd keeps processing the command for a long time and in the end gives a message saying "the server could not be started."

 

Cause

The Application Server was unable to communicate with Standby or Background servers.

 

04/14 17:54:27.89 PTCTSAPPD01 pdm_rfbroker_nxd        5928 ERROR        ServerStatusMonitor.  2224 Invalid values in  DB_CHANGE notification for server node 0 from P. domsrvr() userid() NODE_NAME((NULL)) TYPE(<UNDEFINED>) DELETE_FLAG(<UNDEFINED>) LINKED(<UNDEFINED>)
04/14 17:54:40.52 PTCTSAPPD01 pdm_d_mgr               4976 ERROR        ServerStatusMonitor.  2224 Invalid values in  DB_CHANGE notification for server node 0 from P. domsrvr() userid() NODE_NAME((NULL)) TYPE(<UNDEFINED>) DELETE_FLAG(<UNDEFINED>) LINKED(<UNDEFINED>)
04/14 17:55:35.52 PTCTSAPPD01 rep_daemon              6368 ERROR        ServerStatusMonitor.  2224 Invalid values in  DB_CHANGE notification for server node 0 from P. domsrvr() userid() NODE_NAME((NULL)) TYPE(<UNDEFINED>) DELETE_FLAG(<UNDEFINED>) LINKED(<UNDEFINED>)
04/14 17:57:36.07 PTCTSAPPD01 boplgin                 5408 ERROR        ServerStatusMonitor.  2224 Invalid values in  DB_CHANGE notification for server node 0 from P. domsrvr() userid() NODE_NAME((NULL)) TYPE(<UNDEFINED>) DELETE_FLAG(<UNDEFINED>) LINKED(<UNDEFINED>)
04/14 17:57:41.29 PTCTSAPPD01 kt_daemon               6540 ERROR        ServerStatusMonitor.  2224 Invalid values in  DB_CHANGE notification for server node 0 from P. domsrvr() userid() NODE_NAME((NULL)) TYPE(<UNDEFINED>) DELETE_FLAG(<UNDEFINED>) LINKED(<UNDEFINED>)
04/14 17:57:44.22 PTCTSAPPD01 web:local               5884 ERROR        ServerStatusMonitor.  2224 Invalid values in  DB_CHANGE notification for server node 0 from P. domsrvr() userid() NODE_NAME((NULL)) TYPE(<UNDEFINED>) DELETE_FLAG(<UNDEFINED>) LINKED(<UNDEFINED>)
04/14 17:57:46.90 PTCTSAPPD01 spelsrvr                4464 ERROR        ServerStatusMonitor.  2224 Invalid values in  DB_CHANGE notification for server node 0 from P. domsrvr() userid() NODE_NAME((NULL)) TYPE(<UNDEFINED>) DELETE_FLAG(<UNDEFINED>) LINKED(<UNDEFINED>)
04/14 19:58:48.86 PTCTSAPPD01 domsrvr                 6348 ERROR        sql_prod.c             567 Lost connection to virtdb bopLDAP
04/14 20:35:11.95 PTCTSAPPD01 domsrvr                 6348 ERROR        sql_prod.c             567 Lost connection to virtdb bopLDAP
04/20 11:35:17.47 PTCTSAPPD01 bpvirtdb_srvr           5204 ERROR        vdbsql.c               686 Internal error: table not found: z_ref_tab
04/20 11:35:31.99 PTCTSAPPD01 bpvirtdb_srvr           5204 ERROR        vdbsql.c               686 Internal error: table not found: z_lrel_pcat_grc
04/20 12:55:05.24 PTCTSAPPD01 domsrvr                 6348 ERROR        sql_prod.c             567 Lost connection to virtdb bopLDAP

 

Environment

Release : 17.3

Component : CA SERVICE MANAGEMENT

Resolution

The root cause of the problem turned out to be that the Application server was unable to communicate with Standby or Background servers due to Firewall. Windows Firewall on Standby server was blocking communication.  Customer changed Windows Firewall configuration settings in Standby server and Application server Services successfully started.