Skip to main content

BPA: Error: 'Server is in Maintenance Mode. Please try again later'

BPA Alerts are not running when a task is queued.

Updated over a month ago

The BPA scheduled alerts are not running as scheduled.
When queueing a task in the BPA Client, the following error dialog is displayed:

Server is in Maintenance Mode. Please try again later.

image.png


This dialog returns every time the Retry button is clicked.
​Upon the Cancel button being clicked, the following error dialog is displayed:

image.png



You will need to stop and restart the BPA services.
​Follow the below to stop and restart BPA:

  1. Go to Start, Administrative Tools, Services. The service viewer will open.

  2. If are are unable to see this, go to Start, Control Panel.

  3. Click Administrative Tools, double click on Services.

  4. The Services Viewer should now open.

image.png


The services need to be stopped in the following order:

  1. Advance BPA Schedule Agent.

  2. Advance BPA Server.

Once they have both been stopped, they need to be restarted in the reverse order:

  1. Advance BPA Server.

  2. Advance BPA Schedule Agent.

To stop or start a service, right click on the service and select Stop or Start.

When the service is running, Start is greyed out, and when the service is stopped, Stop is greyed-out.

image.png


There have been instances where either of these services has been so badly hung that they cannot be stopped. The service will give an error about being unable to stop, and it will sit there with a status of Stopping.

In this case the only option is to kill the executables with Task Manager.

Start Task Manager by right-clicking on the Task Bar and clicking on Task Manager.

Once Task Manager starts up, the tasks to stop (in order) are:

  1. iwschdea.exe (the scheduling agent)

  2. iwtsksvr.exe (the BPA server itself)

image.png


3. Stop a process by right-clicking on it and clicking on End Process Tree, you may be asked for confirmation.

image.png


Once the executables have been killed, the services can be started again as per normal (see above).

Did this answer your question?