At times, the REST Dispatch and Reply function may fail to direct traffic to the necessary processes despite matching URIs, resulting in abrupt termination. The functionality of the REST Dispatch and Reply activity can be impacted by the Dynatrace App, potentially resulting in the inability to invoke the subprocess or encountering a (500) Internal Server Error. This article delves into potential solutions to address this issue.

Below are a few examples of error messages:
1) The remote server returned an error: (500) Internal Server Error.
2) HTTP/1.1 500 ..dws-correlation-id: 4a8d85f954eb4df28423c3791fa74c1c..X-Content-Type-Options: nosniff..X-XSS-Protection: 1; mode=block..X-Frame-Options: DENY..Cache-Control: no-cache, no-store,max-age=0, must-revalidate..Pragma: no-cache..Expires: 0..Content-Type: application/json..Transfer-Encoding: chunked..Connection: close....3e..."status":"INTERNAL_SERVER_ERROR","errors":[."message":null.]...


 

The Dynatrace application could potentially lead to the REST Dispatcher being unable to invoke the subprocess

Operation Systems: All

       Below are the current available solutions to address this problem:

1. Remove/Uninstall the Dynatrace App from the affected server.
2. If uninstallation is not desired, consider disabling the Full Stack/real user monitor feature.

        Please refer the below links for the process:

• https://docs.dynatrace.com/docs/platform-modules/digital-experience/web-applications/additional-configuration/rum-for-process-groups
• https://docs.dynatrace.com/docs/setup-and-configuration/dynatrace-oneagent/installation-and-operation/windows/operation/stop-restart-oneagent-on-windows