Re: Prognosis service fails to start and gets Error 1067
Prognosis service fails to start and gets Error 1067
Description: Prognosis service fails to start and gets the following poppup error:
Windows could not start the Prognosis service on the Local Computer. Error 1067: The process terminated unexpectedly
Possible cause: If the license file is locked by another process like your antivirus software, it will have this symptom. To see if this is the cause try the following:
1. Rename license to licensex 2. Open this in notepad and then select 'File | Save As' and save it back as the original license filename (Ensure the .txt extension does not get added. Rename it quickly in file explorer if it does) 3. Try starting the service
Note: You may have to show known extensions to be able to rename it. Time is crucial as starting the service before the new file gets locked again. The above is not a solution. The file will get locked again and when you stop start the service again, it will have the same problem.
If it starts, then something is locking our license file and possibly others. Solution: Ensure the Prognosis files / folders have adequet exclusions in your antivirus software.