How To Fix SRT_ADMIN004 - Task watcher is not active

SAP Error Message - Details

• Message type: E = Error

• Message class: SRT_ADMIN - Administration Messages for SOAP Runtime

• Message number: 004

• Message text: Task watcher is not active

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

What causes this issue?

The watcher for the SOAP Runtime background processes was not started by
AUTOABAP, was terminated by an error, or could not be started due to an
error in the system environment. This watcher is required for the
handling of errors in processes. In particular, the processing of the
"Compensate" message in the business scenario with the TUCC pattern
(Tentative Update and Compensate or Confirm) is the responsibility of
the task handler.

System Response

How to fix this error?

See also the list of ABAP runtime errors (transaction ST22). To find
information about errors when starting the watcher, search the initial
messages created after the system start. Possible errors are assigned to
the user name SAPSYS. Possible causes of the problem can be:
The RFC destination required for the correct operation of the watcher is
missing. Use the program SRT_ADMIN_CHECK to check whether the
destination has been configured. If the destination does not exist, the
watcher cannot start. Configure the destination and wait for the next
AUTOABAP cycle. This cycle takes approximately five minutes and starts
all important system processes.
The type of the RFC destination is not 3 (ABAP connection).
Information about the RFC destination is missing or incorrect. The user
configured for the RFC destination must have the type "Service" and must
have the authorization profile SAP_BC_WEBSERVICE_SERVICE_USER. A missing
authorization for the RFC destination user raises a runtime error of the
type CALL_FUNCTION_REMOTE_ERROR.
You can also start the task watcher manually. To do this, use the report
TASK_VITAL_RUN. This checks whether the watcher is active and starts it
if necessary. However, this procedure only provides a temporary solution
to the problem. You must ensure that the watcher is started cyclically
by AUTOABAP.

Procedure for System Administrators

Check whether the report SAPMSSY6 includes the line "perform
submit_report using 'TASK_SYSTEM_START' 30 240". If not, the version of
the system software is not up-to-date.
Use the program SRT_ADMIN_CHECK to check the existence of the name of
the RFC destination in the central configuration.
Check whether the destination with the name from the central
configuration exists. To do this, use the search function in transaction
SM59.
Run a connection test to the given RFC destination.
Check whether the given RFC destination has the type 3 (ABAP
connections).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SRT_ADMIN004 - Task watcher is not active ?

  The SAP error message SRT_ADMIN004: Task watcher is not active typically occurs in the context of SAP Process Integration (PI) or SAP Process Orchestration (PO) when the task watcher service is not running. The task watcher is responsible for monitoring and managing the execution of asynchronous tasks in the system.
  Cause:
  
  Task Watcher Not Started: The task watcher service may not have been started or may have stopped due to an error.
  Configuration Issues: There may be configuration issues in the SAP system that prevent the task watcher from starting.
  System Errors: There could be underlying system errors or issues with the Java stack that affect the task watcher.
  Resource Constraints: Insufficient resources (like memory or CPU) can lead to the task watcher not being able to start.
  
  Solution:
  
  
  Start the Task Watcher:
  
  Go to the SAP NetWeaver Administrator (NWA) or the relevant management console.
  Navigate to the "Java" section and look for the "Task Watcher" service.
  Start the service if it is not running.
  
  
  
  Check Logs:
  
  Review the logs in the NWA or the SAP system logs to identify any errors that occurred when trying to start the task watcher.
  Look for any exceptions or stack traces that might indicate the root cause of the issue.
  
  
  
  Configuration Check:
  
  Ensure that the configuration settings for the task watcher are correct.
  Check the relevant configuration files or settings in the NWA.
  
  
  
  Restart the System:
  
  If the task watcher does not start after manual intervention, consider restarting the entire SAP system or the Java stack to reset the services.
  
  
  
  Resource Monitoring:
  
  Monitor system resources to ensure that there are enough resources available for the task watcher to run.
  If necessary, allocate more resources or optimize the current usage.
  
  
  
  Update and Patch:
  
  Ensure that your SAP system is up to date with the latest patches and updates, as there may be bug fixes related to the task watcher.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to the task watcher and the specific error message for any known issues and solutions.
  Documentation: Refer to the official SAP documentation for Process Integration/Orchestration for detailed information on configuring and managing the task watcher.
  Community Forums: Engage with SAP community forums or support channels for additional insights and assistance from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to contact SAP support for further assistance.