How To Fix WGDS_PROCESS671 - Daemon already started on job &1/&2. Not stopped properly last time?!

SAP Error Message - Details

• Message type: E = Error

• Message class: WGDS_PROCESS - Global data synchronisation

• Message number: 671

• Message text: Daemon already started on job &1/&2. Not stopped properly last time?!

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_PROCESS671 - Daemon already started on job &1/&2. Not stopped properly last time?! ?

  The SAP error message:
  WGDS_PROCESS671 Daemon already started on job &1/&2. Not stopped properly last time?!?
  Meaning / Cause:
  This message indicates that the SAP spool daemon process (background job) identified by job name (&1) and job number (&2) is already running or was not properly terminated during its last execution. The spool daemon is responsible for managing print requests and spool processing.
  Common causes include:
  
  The previous spool daemon job did not stop correctly due to system crash, manual termination, or a hang.
  The job is still running in the background, causing a conflict when SAP tries to start a new instance.
  System or OS-level issues preventing proper termination of the spool daemon.
  Stale lock or process entries in the system.
  
  Effects:
  
  New spool daemon jobs cannot start because the system believes one is already running.
  Printing or spool processing may be delayed or halted.
  Potential spool system instability.
  
  
  Solution / How to fix:
  
  
  Check the running spool daemon jobs:
  
  Use transaction SM37 (Job Monitoring) to find the spool daemon jobs (job name usually starts with SAP* or SPOOL*).
  Look for jobs with the name and number mentioned in the error (&1/&2).
  Check if the job is still active or stuck.
  
  
  
  Terminate or cancel the stuck job:
  
  If the job is still running but should not be, cancel or terminate it from SM37.
  If the job is stuck at the OS level, you may need to kill the process manually on the application server.
  
  
  
  Check OS processes:
  
  On the application server, check for any running spool daemon processes (e.g., sapspool or similar).
  Use OS commands like ps (Unix/Linux) or Task Manager (Windows) to identify and kill any orphaned spool daemon processes.
  
  
  
  Restart the spool work process:
  
  Sometimes restarting the spool work process or the entire application server instance can clear the issue.
  Use transaction SM51 to identify the server and then restart the instance if necessary.
  
  
  
  Check for locks or stale entries:
  
  Use transaction SM12 to check for any locks related to spool or daemon jobs.
  Remove stale locks if found.
  
  
  
  Review system logs:
  
  Use transaction SM21 to check system logs for any related errors or warnings that might indicate why the daemon did not stop properly.
  
  
  
  Apply SAP Notes / Patches:
  
  Check SAP Support Portal for any relevant SAP Notes related to spool daemon issues or this specific error message.
  Sometimes, bugs or patches address daemon stability.
  
  
  
  
  Additional Information:
  
  The spool daemon is critical for print and spool management in SAP.
  Proper shutdown of spool daemon jobs is necessary to avoid conflicts.
  Regular monitoring of spool jobs and system health can prevent such issues.
  If this problem occurs frequently, investigate underlying causes such as system resource issues, network problems, or SAP kernel bugs.
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  Spool daemon job already running or not stopped properly last time (stuck or orphaned).
  
  
  Effect
  New spool daemon jobs cannot start; spool processing may be blocked.
  
  
  Solution
  Check and terminate stuck jobs (SM37), kill OS processes if needed, clear locks (SM12), restart spool work process or server, check logs (SM21), apply SAP Notes.
  
  
  Related Tcodes
  SM37, SM12, SM21, SM51
  
  
  
  
  If you need help with specific commands or further troubleshooting steps, please let me know!