From x:\cw\vxx\logs\server\component-logs\PrizmDoc Folder:
[#9834013] PrizmDoc server health check failed: State is STARTING
1. Log into the PrizmDocServer Admin page on each eDiscovery Platform(eDP) server:
http://localhost:18681/admin
2. Verify if all the services are in a Running state. If they are not running, please start them.
3. If the ms-office-conversion-service is stuck in a Starting state, please try the following:
a. Login to the eDP server using ESAPrizmDocServer account.
b. Go to Devices and Printers under the Control Panel.
c. Set default printer as Microsoft XPS printer.
NOTE: If the Microsoft XPS printer is already the default, set the default to another printer then set it back to the Microsoft XPS printer.
d. Restart the PrizmDocServer service.
4. Verify if all the services are now in a Running state.
If the above solution does not work, verify that the Devices registry key is populated with the Microsoft XPS Document Writer.
1. Log into the server as the EsaPrizmDocServer service account.
2. Open Regedit.exe
2a. Alternatively, log into the server with an administrator account and run C:\Windows\Regex.exe as a different user (Shift-Right Click)
3. Navigate to HKEY_CURRENT_USER > Software > Microsoft > Windows NT > CurrentVersion
4. If there is no Devices Key, right-click on CurrentVersion and select New > Key. Name it Devices.
5. If Devices is present, check if the following string exists under it:
Name: Microsoft XPS Document Writer
Value Data: winspool,Ne00:

6. If it is not there create it by right-clicking on Devices > New > String:
Name: Microsoft XPS Document Writer
Value Data: winspool,Ne00:
7. If the key was added manually, restart the server.
8. After restart, verify if ms-office-conversion-service is now running.