Given the following response we have had after experiencing intermittent crashes in our application and submitting an incident to Microsoft
"The AV is happening at COM, Oleau32.dll, module which is part of the COM plumbing.
I hate to be the bearer of bad news, but your application which is an Asp.Net 4.0 application that is using the ADOBD PIA assembly that shipped with visual studio 2005, unfortunately, is not supported in server side application such as ASP.Net and is and has not been recommended for usage anymore by Microsoft.
ADODB was merely provided as temporary workaround in the early days of .net, until our customer fully migrate to ADO.Net"
do SAP still support use of the 'pull' method in reports embedded in ASP.NET applications, or should ASP.NET applications only use 'push'? We could not tell whether the crashes were occurring in our VB code, which currently still uses ADODB, or in the embedded Crystal Reports, which use OLEDB connections (and the connection may or may not use the ADODB assembly internally - this is obviously outside our control). We are currently updating the VB code in our application to only use ADO,NET, but we have 100+ reports in our application, and we don't want to have to convert them all to 'push' if we can avoid it!
We have been advised by SAP to update the reports to use the native SQL drivers (rather than SQLOLEDB), but if the problem is more basic, i.e. in using 'pull' mode per se, changing the drivers is not going to help.
It is worth noting that we only started to experience these intermittent errors when we installed the app on Windows 2008 R2, It has run fine on Windows 2003 for many years.