Tech Tip: CA-Unicenter NSM restarts on its own regularly

Document created by sirha02 Employee on May 6, 2015Last modified by Melissa Potvin on May 18, 2015
Version 2Show Document
  • View in full screen mode

On the EM Console the following message appears regularly:

"%CASP_I_176, CA-Unicenter shudding down services on node ..."

"CACM_S_027, Calendar daemon shutting down"

"%CATD_S_016, CA SNMP Trap Manager shutting down"

"%CAOP_I_DAEMONTERM, Console daemon terminated by signal 9999"

.

.

.

 

Solution:

Close the EM Console, stop and start the unicntrl services by typing in the command prompt:

unicntrl stop all

unicntrl start all

 

Open the EM Console to see if the issue is resolved. If this does not resolve the issue, open the Event Viewer on the machine (right click the My Computer icon > Manage > Event Viewer > Application); check for red cross mark Error for more details by double clicking on Red Cross Error symbol.

 

If the Description of the error says:

 

"The description for Event ID (211) in Source (WVDMN) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer..."

 

Check if the MDB is installed on the same machine or on remote machine

 

IF THE MDB IS ON THE SAME MACHINE AS EM CONSOLE:

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

If the MDB is on the same machine:

a) Close the EM Console

b) Open Command Prompt and type:

switchwvregsrvr

c) Stop and Start the unicntrl services:

unicntrl stop all

unicntrl start all

 

Open the EM Console to see if the issue is resolved. If this does not resolve the issue, perform DIA Cleanup on the machine (For instructions on how to perform DIA Cleanup please go to the bottom of the page)

 

After DIA Cleanup is performed:

 

Close the EM Console on the MDB machine, stop and start the services as shown below:

unicntrl stop all

unicntrl start all

 

Open the EM Console and verify if the issue is resolved

 

 

IF THE MDB IS ON A REMOTE MACHINE:

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

Check if the machine is pingable and hostname resolvable through the commands:

ping MDB_Machine_Hostname

nslookup MDB_Machine_Hostname

ping MDB_Machine_IPAddress

nslookup MDB_Machine_IPAddress

 

Perform the vice-versa from the MDB machine for the above commands.

 

If the above holds good then log on to the MDB machine:

a) Close the EM Console

b) Open Command Prompt and type:

switchwvregsrvr

c) Stop and Start the unicntrl services on the MDB and the EM Machine:

unicntrl stop all

unicntrl start all

d) Open the EM Console and verify if the issue is resolved

If this does not resolve the issue, perform DIA Cleanup on the MDB Machine and the EM Machine (For instructions on how to perform DIA Cleanup please go to the bottom of the page)


After DIA Cleanup is performed on the MDB and EM Machine:

 

Close the EM Console on the MDB machine, stop and start the services as shown below:

unicntrl stop all

unicntrl start all

 

Open the EM Console to verify if the issue is resolved

 

PROCEDURE FOR DIA CLEANUP:

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

a) Open services.msc

b) Stop CA DIA 1.2 DNA then CA DIA 1.2 Knowledge Base  (The reason for stopping the DNA first is so that it does not float to another KB)

c) Open Windows Explorer and go to the following location:

    \CA\SharedComponents\CCS\DIA\dia\dna\config

d) Select the following files and delete:

  1. act.dat
  2. recognizerRscTable.dat
  3. ukb.dat
  4. MDBPushTechEntries.pt

e) If you want to setup a MasterKB manually because there is no _srv record in your DNS environment, then you would modify the dna.cfg file in this directory. You would change the following settings in this file

overrideSRV=yes

MasterKB=Master_KB_Machine_Name

If this box has the UKB installed then switch to this directory:

\CA\SharedComponents\CCS\DIA\dia\ukb\config

f) Next delete all the files in here except:

  1. remins.cfg
  2. ukb.cfg
  3. ukbrule.xml

g) Next, open a command line and cd to this directory:

\CA\SharedComponents\CCS\DIA\dia\dna\bin

h) First, start CA DIA 1.2 Knowledge Base, then, after it has fully come up,start CA DIA 1.2 DNA

i) If this is an agent only box enter the following on the command line:

  1. autoactivatedna.bat <UKB_host_name >

If this box has its own local UKB then just enter autoactivatedna

j) Next, to verify that the DNA is owned by the correct KB, open the ukb.dat file in the dna\config directory using WordPad. You should see the name of the KB that now owns this DNA.

 

All the Best with your issue!!!

Attachments

    Outcomes