SAP Crystal Reports randomly crashes on .Export call with access violation

[Scott-Weaver]

We have a VB.Net application that generates PDF files using the CR .export function. It can generate 100's of PDF files. It works fine on Windows 10 but when any of our developers move to Windows 11 the code will start to have random access violations on the .export call which cannot be handled with a Try/Catch. We have updated the Crystal runtime to the latest version (CR13SP37MSI64_0-80007712) but that does not correct the issue. Has anyone else had this issue and been able to resolve it?

[DonWilliams · Accepted solution]

Windows 11 has a lot of updated security functions.

Most common is permissions to various resources, c:\windows\temp folder needs full permissions.

Also,  make sure you are closing and disposing after each export.

Using this MS tool add Private Bytes to check the memory usage to see if there is a leak somewhere:

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/using-performance-monitor-to-fin...

Note: there usually is in MS dll's, most of them are small so don't fret if you see a lot. MS Memory Manager leaks due to MS not capable of defragging memory on the fly like Linux can. Only way to fix it is to close the app and reboot once a week... or more often.