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 |
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:
|
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 error log entry above. 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.
|
Subscription times out | Possible causes:
Possible solutions:
|