{{tag>category:"OpenInsight 32-bit" author:"Andrew McAuley"}} [[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]] ==== PSA - OI Crashing (OpenInsight 32-bit) ==== === At 10 JUL 2020 01:39:28PM Andrew McAuley wrote: === Sprezz have spent around 50+ hours (with the assistance of the client and the ever helpful bods at Revelation) poring through profile logs, LH logs, procmon logs and event logs to track down an elusive issue. Symptom :- OI would just crash. Subsequent attempts to launch OI on the workstation would fail. Others would be unaffected. ~This always seemed to happen when the user attempted a report. Errors in the event log included 0xC0000005 and 0xC0000006. This was a new issue on workstations that previously worked fine. Profile logs showed us that the crash was in SET_PRINTER - combined with LH logs we were able to work out that it was when the VSPRINTER window was being created. Suspicion therefore fell on OIPI.NET. We switched from VSPRINTER2 to VSPRINTER1 and the problem went away. Google became our primary debugging tool and we found that "Microsoft acknowledged that the June 2020 Patch also breaks software-based printers on some configurations, which might prevent users from using “print to PDF” feature in apps" - which is exactly what was happening. [url=https://www.windowslatest.com/2020/06/19/windows-10-kb4567523-for-version-2004/]More details here[/url] [url=https://www.sprezzatura.com]The Sprezzatura Group[/url] [url=https://www.sprezzatura.com/blog]The Sprezzatura Blog[/url] [i]World leaders in all things RevSoft[/i] [img]https://www.sprezzatura.com/zz.gif[/img] [[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=CEBC0E482712CC46A66ABAB251583476|View this thread on the Works forum...]]