When we launch PI Processbook and try File > New > Processbook Display (.pdi) file, we get an APPCRASH. Any idea how to fix this? Please see the attachment.
The error you are seeing is a generic Application Crash error. Can you try the following troubleshooting steps:
1) Does ProcessBook consistently crash on the same display?
2) Does ProcessBook crash on other displays or is this isolated to 1 display?
3) If isolated to 1 display, can you ask a colleague to open it on their system? If it crashes on their system as well, the display may be corrupt.
4) If it is not crashing on their display, their might be an issue with your ProcessBook.exe. Try and repair it from Control Panel.
5) If possible upgrade to the latest version of ProcessBook and try with that.
6) Is there any VBA in this display?
Situations like these are often time better handled as a Tech Support case. Feel free to call or email us: Contact Us
Thank you very much for the reply.
The error began (at only one of 13 servers) after applying the latest
microsoft Windows Server 2008 R2 Standard operating system patches to my 13
servers at remote power-plants. Thus, I began uninstalling the patches one
by one (on the broken server) and retesting Processbook after each reboot.
Eventually, Processbook began working again. So, now I am applying the
patches again to test to see if there were some kind of Communication error
while applying the patches (we patch on an 'offline' network over a radio
system across mountain peaks)... ...so error checking is supposed to remove
Communication errors, but I'm wondering why the patches didn't break
Processbook on my other 12 servers... ...so, I am re-patching this server
to see if it will break Processbook again...
On Thu, Jan 12, 2017 at 2:05 PM, Sebastien Raposo <email@example.com>
Would it be possible for you to obtain a crash dump and submit it to Tech Support? Does the crash occur for opening existing displays? You should be able to use Windows Error Reporting to generate a crash dump file:
Collecting User-Mode Dumps (Windows)
thank you for the reply... ...please see the e-mail that I forwarded
to you that I replied to ... ...to Sebastian.
We're getting lots of crashes with PB as well. What values should I set in these registry keys? I've used decimal 10 for DumpCount and 1 for DumpType for now.
Usually we recommend capturing full dumps (DumpType = 2), as this contains the most information to help troubleshooting/debugging.
Retrieving data ...