Symptom
- The Administrator user performs JCo connection test. The JCo destination test fails, the status line displays message:com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Ticket contains no / an empty ABAP user ID (see note 1159962)
OR - In the Enterprise Portal the 'Connection Test for Connectors' may fail with the following error in the defaultTrace:
SAPCFConnectorManagedConnection.connectWithJCO
[EXCEPTION]
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Ticket contains no / an empty ABAP user ID (see note 1159962)
Caused by: RfcException: [null]
message: Ticket contains no / an empty ABAP user ID (see note 1159962)
Return code: RFC_SYS_EXCEPTION(3)
error group: 103
key: RFC_ERROR_LOGON_FAILURE
PortalSystemLandscapeSource.getConnection(IUser,String,DestinationFilter,Map) Failed to get connection. Original exception: A nested exception occurredCould not initialize physical connection. Linked Exception: A nested exception occurredCould not create JCO connection. Linked Exception: Ticket contains no / an empty ABAP user ID (see note 1159962)
Along with the following debug entries:
Entering method
Administrator
Trying to get subject from security session.
Too long for an R/3 user: Administrator
Read more...
Environment
SAP NetWeaver AS Java Release Independent
Product
SAP NetWeaver all versions
Keywords
RFC_ERROR_LOGON_FAILURE, SAP AS Java, JCo, Destination, Ping, Too long for an R/3 user: Administrator, connection test , KBA , BC-JAS-SEC-LGN , Logon, SSO , EP-PIN-AI , Application Integration , BC-MID-CON-JCO , Java-Connector , EP-PIN-PSL , Portal System Landscape , How To
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.