Known Issues for SAP® Data Orchestration Engine Connector

Learn about known issues and apply workarounds for SAP® Data Orchestration Engine Connector (DOE-C).

Issue #	Description
SMPONP-2901	ESDMA package deployment fails if the `DOECNoAuth` security configuration does not exist. When deploying an ESDMA package using the DOE-C CLU or the DOE-C Admin API, the deployment fails if there is no `DOECNoAuth` security configuration. After a first failed deployment, an attempt to do a second deployment is successful because the DOECNoAuth security configuration has been created. Workaround: Ensure the `DOECNoAuth` security configuration exists.
RTC-262	`Error occurred during command execution: 'deploy'.` message appears when deploying DOE-C package. Workaround: Examine the SAP Mobile Server log file. See Server Log in System Administration. If you see `NoSuchElementFoundException` in the log file at about the time the error message appeared, ignore the error and redeploy.
RTC-207	For a DOE-C package, if a device with an expired X.509 certificate initiates unsubscribe, it indicates that the DOE subscription is not cleaned up. Workaround: The DOE administrator must manually clear all such disconnected DOE subscriptions.
RTC-39	`Package Not found` error occurs randomly when DOE-C package is deployed on a cluster. Workaround: Redeploy the package.
RTC-28	Long response time to show DOE-C subscription with packet-dropped state. When a DOE-C subscription encounters a packet-dropped state, it takes more than 10 minutes to show the updated subscription information on the Subscription tab in SAP Control Center. Workaround: None.
CR-709691	SAP Mobile Server fails with `OutOfMemory` error during subscription SUSPEND/RESUME operations. Workaround: In SAP Control Center, select Configuration > General > performance configuration and set the default value for Maximum number of in memory messages to 100.
CR-708754	When the load balancer is shut down due to an HTTP 404 error, DOE-C package subscriptions may be automatically removed. Workaround: Implement SAP note number 1722501 to prevent DOE from automatically removing subscribed users. Create a scheduled job to execute the report, SDOE_RESTART_OUTBOUND_QUEUES to restart the queues in regular intervals in the DOE system.
CR-706532	Suspend/Resume operations on DOE-C subscriptions may result in `HTTP 502 - Bad gateway` error in DOE when load balancer is between SAP Mobile Server and DOE. Workaround: Resume only a few subscriptions simultaneously. For example, you can suspend 100 users in a single operation, then repeat that procedure 10 times.
CR-706111	DOE-C error: `HTTP 400, Unable To Parse Request` while resuming more than 100 users at a time. Workaround: Resume only a few subscriptions simultaneously. For example, you can suspend 100 users in a single operation, then repeat that procedure 10 times.
CR-705888	Domain deletion may cause HTTP 500 error in DOE-C device queue. When DOE sends data to a subscription for a device for which the domain has already been deleted from SAP Mobile Platform, then SAP Mobile Platform should send a recoverable HTTP 404 error, indicating that either the subscription or the domain is not found. Instead the DOE device queue shows an unrecoverable internal server error (HTTP 500) and the SAP Mobile Server log file has a `java.lang.IllegalStateException: domain already cleared` error. Workaround: Remove the subscription in DOE.
CR-703909	When DOE-C sets domain log context properties, it leaves the "domain name" field blank in the server log entry. Workaround: The domain name is set correctly in the DomainLog table.
CR-700957	If the DOE server is down, the device receives a long HTML exception. Workaround: None.