Previous Topic: CAE0232E-Repository error code 22

Next Topic: Filter Error Messages


Review Server Configuration

When the CA SDM server is on a UNIX or Windows computer and CA NSM is on a different Windows computer, the CA SDM server must be up and running. Start the NSM Event Converter service on the CA NSM computer. To ensure the converter is up and running, check the processes using Task Manager. If tngcnv does not appear as a running process after the event converter service was started, check the most recent tngcnv.n or stdlog.n files (located in installation-directory\log). These files provide you with information about why the event converter is not running.

When the CA SDM server and CA NSM server are on the same Windows computer, the CA SDM Service must be up and running. Start the CA NSM Event Converter Service on the computer. To ensure the converter is up and running, check the processes using Task Manager. If tngcnv does not appear as a running process after the CA SDM service was started, check the following:

  1. Using WordPad, edit the pdm_startup file located in installationdirectory\pdmconf. In this file, you will see text similar to the following:
    [ procset MAIN_PROCSET]
    pdm_info
    sw_ver_ctl
    bpnotify_nxd
    PDMBASE
    PDMBOP
    FILTERING
    

    If a semicolon (;) is used to comment out FILTERING, remove the semicolon.

  2. Moving backwards toward the top of the file, you should see the following text:
    [ procset FILTERING ]
    tngfilter
    tngwriter
    ehc
    ; UNICNV_REPLACE
    ; tngcnv:NT_ONLY
    

    If a semicolon (;) is used to comment out any of the above options, remove the semicolon.

  3. If you made any changes to this file, save them, then recycle CA SDM server.

If the event converter still does not show up as a running process, check the most recent tngcnv.n file (located in installation-directory\log). This file provides you with information about why the event converter is not running.