JCC2999: No matching user credentials were found.
search cancel

JCC2999: No matching user credentials were found.


Article ID: 53879


Updated On:


CA Directory CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent



Environment: UWCC 1.0 SP4+ (Windows 2003)
AutoSys 4.5.1 on TRU64 (OSF1)
Oracle Database

Our UWCC 1.0 connects to 3 different AutoSys instances (DRV, DRU and DRT). DRV and DRU are on HP/UX IA64 and work fine from UWCC.

Though we are not able to verify the AutoSys instance DRT on the TRU64 system from UWCC and gets messages:

JCC3998: The server status is unknown. The server and/or network connection may be down.
JCC2999: No matching user credentials were found.

Verified the following information:

  1. The userid/password combination works locally and the RCS demon are active on the TRU64 system.
  2. The Oracle database user works from the UWCC-system against the Oracle database (using SQLPLUS).


The following error message reflects the following:

Message: JCC3998: The server status is unknown. The server and/or network connection may be down.

Explanation: The connection to the server failed due to unknown reasons.
The server or network connection might not be available.

Recommended Action:

  1. Check whether the server is up.
  2. If the server is not up, start it.
  3. Ping the server using the following command:

ping <server_name or IP_address>  

If you are unable to ping the server using the server_name but are able to ping using the IP_address, then check the Domain Name Server (DNS) settings.

For AutoSys 4.0 or 4.5 & 4.51 Server: Verify the following:

  1. Event Processor host name.
  2. Event Server host name, Event Server Database Name and Instance Database type.
  3. Check the Configuration log file located in the:

<UWCC_Install_directory>\ Logs\application\config\uejm_configuration_servlet.log

IF there is a "Command Agent Failed" or "Failed connecting to Primary event server" error at the bottom of The Configuration log file, then check your Event Server Configuration (ports, names, etc.).

IF the Event Server database type is Oracle, make sure the same SID was used for Event Server Database Name and TNS Names fields.

IF the Event Server is SQLServer 2000 (a version prior to SQLServer Service Pack 4), the netstat command output on the SQL server machine may show the database port (usually,1433) as listening, but an SQLServer 2000 feature does not allow connections to SQL Server from remote clients. The Windows Event Viewer on the SQL Server machine will display the error:

                                 "Remote clients not allowed to connect due to security concerns"

The resolution of this problem is to apply SQL Server SP4. The SQLServer Client/Server Network Utility may help to identify the port number which the clients use to connect to SQLServer.

  1. Event Processor listener port (RCS/Java Listener): By default the value of this port is 4444.
  2. Verify that the RCS/JavaListener is configured properly using the steps below:

                  * Use the command netstat -an to see whether the machine is listening on the UWCC Event
                      Listener configured port number.
                  * Ping from the UWCC server machine to the AutoSys machines' RCS/Java Listener port to verify connectivity.
                  * Verify valid IPs for the Listener (RCS/Java Listener). You will find an error in the asrcslsn.log/jil.log if
                      The IPs are an issue.


Component: ETRDIR