We have several executables that are hosting on one ACE Scheduler.
Every executable is running as a separate process called PIACEClassLibraryHost.exe.
One executable periodically crashes one time in several days with the following record in Windows EventLog:
Faulting application name: PIACEClassLibraryHost.exe, version: 22.214.171.124, time stamp: 0x4e02943a Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0xff006a04 Faulting process id: 0x1bb8 Faulting application start time: 0x01cec36f4f4f04f8 Faulting application path: C:\Program Files (x86)\PIPC\ACE\Scheduler\x86\PIACEClassLibraryHost.exe Faulting module path: unknown Report Id: 5c7dc01a-2fb1-11e3-bff8-005056b2032d
All calculations hosted on this ececutable stop while other ececutables resume there calculations.
It should be mentioned that "failed" executable calculates very well between crashes.
We have to manually restart PI ACE Scheduler to restore normal work but other executables interrupt there work between restarts.
Thus, we have several questions about this:
- What are the reasons of such type crashing and how to prevent it?
- What should we do to restore the work of "failed" executable without restarting PI ACE Scheduler?
- Are there any ways to exclude human participation in elimination of crash consequences?
Thank You for replies!