How to Fix Prognosis Services when getting an Error 1067

[andrew_gjertsen]

This Error: Prognosis Services cannot start 1067 pops up when Prognosis services fail to start.  It pops up often after an upgrade. Below is a fix that has minimal impact to the server itself and other processes running.  In short, moving the confpro "file" (not any confrpo folders)  out of the (Progonosis\Server\Config directory) and then deleting inside that config directory will fix it

[andrew_gjertsen · Accepted solution]

Details:

This error can be common, especially after an upgrade.  This isn't the only way to solve this error , but it's one of first solutions to use and try if this Error 1067 pop up.  It's also the easist to try with minimal impact on the server as you're just removing a file>then deleting a file>then trying to start Prognosis again.  Another solution for this was an irCLEAN but I'd recommend trying this first.

Solution Summary:

1. When trying to start the service, you should see the error "Windows could not start the Prognosis Service on local computer. Error 1067. The process terminated unexpectedly"

2. Always a good idea to navigate to the wvlog.txt to see if this error is present (\Prognosis\Server\Configuration)

3. Once opened, scroll all the way down to the bottom where the most current errors with current date is.  

4 The error will look something like this:

00004000 promgrp 11592 irpromgs 11.7.0 002060 - Internal program error - Fail to open stream to restore process list
2020-09-25 14:33:12 00015003 exhandp 00471 irpromgs 11.7.0 002060 - Illegal Address Trap - ACCESS_VIOLATION

5. Next just stay in the \Prognosis\Server\Configuration and look for the confpro "file".  DON"T remove the confpro folders (confpro.dir & confdb)

6. Copy out the confpro file to a backup directory (or another folder) 

7. Next just delete the confpro file

8. Try starting up the Prognosis service via Services and it should start up