Why is my Prizm Service failing to start in a timely fashion?


Today we noticed that when trying to start the Prizm service, it hangs for a few minutes and then displays an error: “Service Failed to start in a timely fashion”, and the service remains stopped.

The watchdog.console.log shows “DieError: Configuration error, failed to parse the configuration file”.

How can we fix this?


This issue typically happens when the server was not shut down properly, and some of the PrizmDoc files have become corrupted.

To resolve the issue, take the following steps:

  1. Make a backup of your PrizmDoc configuration files.
  2. Uninstall and then re-install PrizmDoc.
  3. Verify the service is running.
  4. Stop the service, restore backed-up configuration files.
  5. Restart Prizm service.