Just a question to address a problem that has come up in a piece of software that has been live for 4.5 years without this issue, and the code of which has been unchanged since 10/07/2020.
All of a sudden we have started getting numerous SEHException (System.Runtime.InteropServices.SEHException) errors from various DataAdapters when attempting to retrieve data from Microsoft Access databases. The error code is always "(0x80004005): External component has thrown an exception at System.Data.OleDb.DataSourceWrapper.InitializeAndCreateSession".
As far as I can work out, the 0x80004005 equates to Microsoft's really helpful "Unspecified Error" which does not help a whole lot. We have started getting this error on various Databases, with various DataAdapters, against various Tables, with varying actions against those Tables. The error is not EVERY time, but is random throughout the day, and will appear in batches lasting a couple of minutes when we will get a burst of about 20 errors,
We have investigated environmental changes, and we cannot spot any change to the environment that might be causing this issue. No change to Antivirus, no change to the software (as mentioned), no changes to the databases. The only thing we did spot were a couple of .NET Framework updates a week or so ago, but searching the internet has shown to increase in people complaining about errors of this type after those updates
As I said, the software has been stable for 4.5 years, and the current version of the software was released on 10/07/2020, so has been running for 2 months unchanged with no issues whatsoever.
Does anyone have any ideas of what might be causing this issue and where it might have come from?
I know its not a lot to go on, but its all I have and I have run out of things to check. I am sure it must be something "environmental" as the software and its components are unchanged. The only other things that I can think of is a change to Microsoft Access itself (we are using Office 365, so updates supposedly go in quarterly supposedly - but last time Microsoft kindly broke Access - with the broken UPDATE query issue - that went into our server off schedule), or a change to the OleDb Driver.
I am stumped!