Troubleshooting PI Analysis Service Crashes in PI System Explorer 2016

Troubleshooting PI Analysis Service Crashes in PI System Explorer 2016

If you're working with PI System Explorer 2016 and encountering repeated crashes of the PI Analysis Service, you're not alone. Many users have faced similar issues, particularly with the error message "Processor instance has crashed unexpectedly." In this blog post, we will explore some common troubleshooting steps and recommendations to help you resolve these issues effectively.

Preliminary Checks

1. Examine the Logs:

   • Begin by checking the PI AF analysis logs located in %ProgramData%\OSIsoft\PIAnalysisNotifications\Logs. These logs provide valuable insights into any errors or warnings that may have preceded the crash.
   • Additionally, check the Windows Event Viewer for application crash entries related to the PI Analysis Service.

2. Error Messages:

   • A common error message encountered is "Processor instance has crashed unexpectedly 2 times." This indicates that the PI Analysis Service attempted to restart but failed.

3. Configuration Settings:

   • In some cases, enabling exception details via the IncludeExceptionDetailInFaults configuration setting can provide more detailed error information. Consult the Microsoft .NET Framework SDK documentation for guidance on enabling tracing and inspecting server trace logs.

Version and Installation Checks

1. Confirm the Version:

   • Ensure that you are using the correct version of PI System Explorer and PI AF Server. In this case, the concern is with PI AF Server Version 2.8.5.7759.

2. 32-bit vs 64-bit:

   • Some users have reported stability issues with the 64-bit version and found that switching to the 32-bit version resolved the issue. Verify the bitness of your PI Analysis Service installation and consider testing the 32-bit version if you are currently experiencing issues with the 64-bit version.

Seeking Further Assistance

If these troubleshooting steps do not resolve the issue, it is recommended to escalate the problem to OSIsoft tech support. When reaching out, ensure that you provide:

• Detailed log files that capture the error messages.
• The specific version numbers and bitness of your installed software.
• A description of the steps taken prior to the crash occurrence.

Tech support will have access to more comprehensive resources and may provide additional patches or configurations specific to your installation.

Conclusion

Dealing with unexpected crashes in PI Analysis Service can be challenging, but by following systematic troubleshooting steps and seeking expert support when needed, you can work towards a solution. Remember, documenting each step and error message is crucial for fast resolution by support teams.