How To Fix WGDS_PROCESS672 - Daemon could not be started. See error log for details

SAP Error Message - Details

• Message type: E = Error

• Message class: WGDS_PROCESS - Global data synchronisation

• Message number: 672

• Message text: Daemon could not be started. See error log for details

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message WGDS_PROCESS672 - Daemon could not be started. See error log for details ?

  The SAP error message:
  WGDS_PROCESS672 Daemon could not be started. See error log for details
  typically occurs in the context of SAP Gateway or related background processes where a daemon process is expected to start but fails.
  
  Cause
  
  Daemon startup failure: The SAP system tries to start a background daemon process (often related to the Gateway or a specific service) but is unable to do so.
  Possible reasons include:
  
  Incorrect or missing configuration parameters for the daemon.
  Insufficient authorizations or permissions for the user trying to start the daemon.
  Operating system-level issues such as missing executables, incorrect environment variables, or resource constraints.
  Network or port conflicts preventing the daemon from binding to required ports.
  Corrupted or missing SAP kernel files related to the daemon.
  The daemon process is already running or hung, causing conflicts.
  Errors in the SAP Gateway configuration or profile parameters.
  
  
  
  
  Solution
  
  
  Check the error log:
  
  The message advises to "See error log for details." Check the SAP system logs (transaction SM21) and the developer trace files (via ST11) for detailed error messages related to the daemon startup.
  Also check the OS-level logs for any related errors.
  
  
  
  Verify daemon configuration:
  
  Check the relevant profile parameters in transaction RZ10 or RZ11 related to the daemon.
  For Gateway daemons, parameters like gw/acl_mode, gw/acl_info, gw/acl_log, and gw/acl_file should be checked.
  Ensure the daemon executable path and environment variables are correctly set.
  
  
  
  Check if the daemon is already running:
  
  Use OS commands (e.g., ps, netstat) to verify if the daemon process is already running or if the port is in use.
  If hung, kill the process and try restarting.
  
  
  
  Check authorizations:
  
  Ensure the SAP user or OS user starting the daemon has sufficient permissions.
  
  
  
  Restart the SAP Gateway or the entire SAP system:
  
  Sometimes a restart of the Gateway or the SAP instance resolves transient issues.
  
  
  
  Check SAP Notes:
  
  Search the SAP Support Portal for notes related to WGDS_PROCESS672 or daemon startup issues.
  Apply any relevant patches or kernel updates.
  
  
  
  Kernel and OS checks:
  
  Verify that the SAP kernel files are intact and compatible with your OS.
  Check for OS-level resource limits (e.g., max open files, processes).
  
  
  
  
  Related Information
  
  Transaction SMGW: SAP Gateway monitoring and administration.
  Transaction SM21: System log to check for detailed error messages.
  Transaction ST11: Access to developer traces and logs.
  SAP Notes: Search for WGDS_PROCESS672 or daemon startup errors on the SAP Support Portal.
  SAP Gateway documentation: For configuration and troubleshooting of Gateway daemons.
  OS commands: ps, netstat, lsof to check running processes and port usage.
  
  
  If you provide the exact context (e.g., which daemon, SAP system version, OS), I can help with more specific instructions.