How to restart the MPS Provisioning Engine properly

Article ID: 1851, created on May 16, 2007, last review on Oct 19, 2015

Applies to:

Operations Automation

Symptoms

Windows service provisioning tasks through the Microsoft Provisioning System (MPS) are running indefinitely, or they keep failing with an error message such as:

No provisioning engine available
Unable to find any suitable MPF client nodes
The RPC server non available
No provisioning engines are available to process the request
The remote procedure call failed and did not execute

Cause

The MPS engine uses too much memory and blocks or delays task execution. The only way to work around the problem is restarting the engine.

The engine should not be restarted by killing the dllhost.exe process running under the MPFServiceAccts account. This is not safe and, if a transaction is running, data may become inconsistent because an instant kill with no rollback is performed.

Was this article helpful?

CloudBlue, an Ingram Micro business uses cookies to improve the usability of our site. By continuing to use this site and/or log-in you are accepting the use of these cookies. For more information, visit our Privacy Policy.