'EE_POZERROR Repository Error ISE_BACKENDREFERRAL backend referring to other service'.

book

Article ID: 53852

calendar_today

Updated On:

Products

CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER 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

Description

Users cannot access the applications area on the configure tab within eIAM. They get the following error message 'EE_POZERROR Repository Error ISE_BACKENDREFERRAL backend referring to other service'

Solution

Logging into eIAM, clicking on the configure tab and select applications the following error is reported 'EE_POZERROR Repository Error ISE_BACKENDREFERRAL backend referring to other service'.

<Please see attached file for image>

Figure 1

A possible cause for the error could be either the Ingres database, dxserver or both are not running. To check this please try the following steps:

If Ingres is not running run the following command at the operating system command prompt:

su - ingres -c "ingstatus" (UNIX)

The output will look as follows when all the processes are running:

Ingres EI name server (iigcn) - running
Ingres EI recovery server (dmfrcp) - running
Ingres EI DBMS server (iidbms) - 1 running
Ingres EI Star server (iistar) - not active
Ingres EI Net server (iigcc) - 2 running
Ingres EI Data Access server (iigcd) - 1 running
Ingres EI Bridge server (iigcb) - not active
Ingres EI JDBC server (iijdbc) - not active
Ingres EI RMCMD process (rmcmd) - running
Ingres EI archiver process (dmfacp) - running

The iistar, iigcb and iijdbc processes are not usually active. If Ingres is not running then the following is reported:

Ingres EI name server (iigcn) - not active
Ingres EI recovery server (dmfrcp) - not active
Ingres EI DBMS server (iidbms) - not active
Ingres EI Star server (iistar) - not active
Ingres EI Net server (iigcc) - not active
Ingres EI Data Access server (iigcd) - not active
Ingres EI Bridge server (iigcb) - not active
Ingres EI JDBC server (iijdbc) - not active
Ingres EI RMCMD process (rmcmd) - not active
Ingres EI archiver process (dmfacp) - not active

There is no ingstatus command on windows so the same process names, iigcn, dmfrcp, etc, can be reviewed via the Windows Task Manager to see if they are all running. If you suspect that the eTrust directory dxserver is not running you can checked this by running the following command. On UNIX it should be run as the root user account:

dxserver status (WINDOWS)
su - dsa -c "dxserver status" (UNIX)
If the dxserver is up and running it should return the following:
iTechPoz-<server name>-Router started
iTechPoz-<server name> started
If the dxserver is stopped the following is reported:
iTechPoz-<server name>-Router stopped
iTechPoz-<server name> stopped

If Ingres is not running, start Ingres and then the eTrust Directory Dsa's. This must be done at the operating system command prompt on UNIX but on windows it can be started by starting the services via the Windows services or

net start "Ingres Intelligent Database [ET]" (WINDOWS)
su - ingres -c "ingstart" (UNIX)

If Dsa servers are not running, then start the Dsa server's by running the following command.

dxserver start all (WINDOWS)
su - dsa -c "dxserver start all" (UNIX)

Environment

Release:
Component: ARGIS

Attachments

1558711314585000053852_sktwi1f5rjvs16s55.gif get_app