Background:
This error means that the Process Manager in Prognosis found that a Prognosis process has crashed and tried to start it up again. After restarting it the process crashed again. Process Manager tried up to 5 times to start up the process and then gave up as the process kept crashing each time. This "Process is over restart limit" therefore means that the process has become permanently down.
Solution:
The next step is to look at previous events leading up to the process crash/restarts and see if the cause can be identified from those. The cause is either an environmental issue (like low system memory or a locked file etc) or something that changed in Prognosis.
For example, if it were "memory limit exceeded" events before the restarts then increasing the memory limit for that process should allow it to stay running (using a SET MEM-SIZE in the PROGNOSIS configuration). However it could be various other errors and searching the knowledge base should help get more guidance for more common errors.
Once the cause is addressed or otherwise has gone away, then clicking Start in the PROGNOSIS configuration (No changes needed) should trigger Process Manager to start up the down process again. Alternatively if it was a database, threshold, or analyst, then they can also be started manually through the user interface.
IR Official article 00003360
