SAP Knowledge Base Article - Preview

2624568 - Managed system configuration - Test logon in step Enter System Parameters fails: ...check whether the access control file is up-to-date

Symptom

During the Managed System Configuration of a Java technical system, the Java logon test via button "Test Logon..." in the Java Parameters pane fails with the following error:

A technical error occured; Java credentials could not be checked
Error Action failed : An error occured while communicating with Message Server <host.domain>:<internal message server port> through the instance <host>/<SID>/<instance number> (<host>) : Error to retrieve the process from Message Server (detail: java.io.IOException: Cannot connect to message server. Make sure that you connect to the message server using the internal port and/or check whether the access control file is up-to-date.); nested exception is:
java.io.IOException: Cannot connect to message server. Make sure that you connect to the message server using the internal port and/or check whether the access control file is up-to-date.(cause=java.io.IOException Cannot connect to message server. Make sure that you connect to the message server using the internal port and/or check whether the access control file is up-to-date.). Therefore the preliminary look-up of the Managed Java Message Server information (<host.domain>:<internal message server port>) via the Agent is not possible.

More details can be found in the SMDAgentApplication*.log file:

Error to retrieve the process from Message Server (detail: java.io.IOException: Cannot connect to message server. Make sure that you connect to the message server using the internal port and/or check whether the access control file is up-to-date.)
[EXCEPTION]
java.io.IOException: Cannot connect to message server. Make sure that you connect to the message server using the internal port and/or check whether the access control file is up-to-date.
at com.sap.bc.proj.jstartup.impl.JStartupRawConnection.<init>(JStartupRawConnection.java:106)
at com.sap.bc.proj.jstartup.impl.JStartupClusterControllerImpl.<init>(JStartupClusterControllerImpl.java:48)
at com.sap.bc.proj.jstartup.impl.JStartupClusterControllerFactoryImpl.createClusterControllerImpl(JStartupClusterControllerFactoryImpl.java:145)
at com.sap.bc.proj.jstartup.impl.JStartupClusterControllerFactoryImpl.createClusterController(JStartupClusterControllerFactoryImpl.java:80)
at com.sap.smd.plugin.command.tda.ThreadDumpCommand.getJ2EEProcessFromMsgServer(ThreadDumpCommand.java:462)
at com.sap.smd.plugin.remoteos.RemoteOSService.getProcessListFromMessageServer(RemoteOSService.java:411)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:241)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:483)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:282)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:759)
at java.lang.Thread.run(Thread.java:763)

Additionally, in the dev_ms of the Java stack, errors like the following are logged:

[Thr 139729201567552] Fri Mar 23 21:50:22:671 2018
[Thr 139729201567552] *** ERROR => MsSLoginClient: client JM_T1521841822670_5_<host name> (<IP address>) is not in acl list, access denied [msxxserv.c   5583]


Read more...

Environment

  • SAP Solution Manager 7.2
  • Java Managed System

Product

SAP Solution Manager 7.2

Keywords

 
A technical error occured; Java credentials could not be checked
Error Action failed : An error occured while communicating with Message Server host:internal_port through the instance host/<SID>/<instance number> : Error to retrieve the process from Message Server (detail: java.io.IOException: Cannot connect to message server. Make sure that you connect to the message server using the internal port and/or check whether the access control file is up-to-date.); nested exception is:
java.io.IOException: Cannot connect to message server. Make sure that you connect to the message server using the internal port and/or check whether the access control file is up-to-date.(cause=java.io.IOException Cannot connect to message server. Make sure that you connect to the message server using the internal port and/or check whether the access control file is up-to-date.). Therefore the preliminary look-up of the Managed Java Message Server information via the Agent is not possible , KBA , SV-SMG-DIA-SRV-AGT , Agent Framework , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.