asked on July 22, 2022

The subscriber was asleep this morning and we saw the following error message after system reboot at 7/20 when the trace logs show that it fell asleep. It only waited 2 seconds for the message queuing service to start before going to sleep. We had to manually restart the subscriber service to wake it up and set the WF services to delayed start.

First time I have come across the subscriber starting before message queuing. Should the subscriber and wf service always be running in delayed mode?

0 0