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