Troubleshooting

Determine the causes of problems and apply the recommended solutions.

Problem Resolution

SAP user sees Password logon no longer possible – too may failed attempts and is locked out after too many failed login attempts
  1. Log in to SAP with a different user account.
  2. In the Transaction Code field, enter su01.
  3. In the User field, enter the ID of the user who is locked out.
  4. Click the Lock icon.
  5. If the Lock User dialog indicates that the user is Locked due to incorrect logins. click the Unlock icon.

If the dialog in step 5 indicates the user is not locked, the system has automatically unlocked the user account after a set period of time has passed.

Unable to parse error in DOE-C logs

Possible causes:

  1. Duplicate SyncKey – verify that the failed XML uses unique SYNCKEY_MMW values across all nodes.
  2. Metadata mismatch – verify that:
    • The DOE configuration for ESDMA is as expected.
    • If the ESDMA has been regenerated, the older ESDMA is undeployed from Sybase Unwired Platform and the new one is deployed.
    • Ensure the code is regenerated, recompiled, and deployed to devices.

Packet dropped state with message, Request Entity Too Large

Three consecutive entries in the log contain the text shown below – in the first entry, <actual_byteSize> is larger than <max_byteSize>.

... Detected a packet-dropped candidate message - size <actual_byteSize>, maximum <max_byteSize>

... DOE-C MESSAGE ID: 554 CODE: 413 MESSAGE: Request Entity Too Large

...is now in a packet-dropped state. The DOE-C will no longer push messages to this subscription.

Use the setEndpointProperties command in the Sybase SAP DOE Connector Command Line Utility (CLU) to make the doePacketDropSize larger than the <actual_byteSize> in the first of the three consecutive error log entries.

setEndpointProperties
{-i|--in inputXmlFile} |
{-d|--domain domainName 
{-a|--all | -ps|--packageNames nameAndVersionList}
{-u|--technicalUser SAPUserAccount 
-pw|--password SAPUserPassword} | 
{-ca|-certAlias certificateAlias} 
[-ds|--doePacketDropSize byteSize] 
[-ew|--doeExtractWindow maxNumMsgs] 
[-t|--soapTimeout seconds] 
[-h|--help] [-sl|--silent]
Note: When you increase doePacketDropSize you should also increase the JVM heap size.

For more details on setEndpointProperties, see setEndpointProperties Command in System Administration Guide.
User cannot get application through the SAP portal
The SAP portal must be configured to allow users to get DOE-based applications without administrator assistance.
  1. Ask your SAP basis team to apply note 1250795 to the portal server, which enables the challenge pop-up. See https://websmp230.sap-ag.de/sap/support/notes/1250795.
  2. Have users enter a URL in SUP that is something like this: http://<portalUrl:port>/redirect/redirect?url=/irj/portal.
Subscription times out

Possible causes:

  1. During import, there are exceptions in processing the message. For example, Parsing Error, ADS Exception.
  2. importResult is not being generated (Check JMSBridge).
  3. The DOE server is sending all messages with SER_MSG_ID = 0 (visible in SOAP dumps). This causes DOE-C to drop messages as duplicates.

Possible solutions:

  • For Parsing errors, identify the data causing the parsing failure (for example, causing a Duplicate Sync Key error) and re-subscribe.