Microsoft Access Database Engine 2010 Build List

On 20.08.2019

From Microsoft:

Microsoft Access Database Engine 2010 Build List For Sale
Microsoft Access Database Engine

Microsoft Access Database Engine 2010 Redistributable (32-bit) enables the transfer of data between existing Microsoft Office files such as Microsoft Office Access 2010 (*.mdb and *.accdb) files and Microsoft Office Excel 2010 (*.xls, *.xlsx, and *.xlsb) files to other data sources such as Microsoft SQL Server. Connectivity to existing text files is also supported. ODBC and OLEDB drivers are installed for application developers to use in developing their applications with connectivity to Office file formats.

Microsoft Access Database Engine 2010 from Microsoft is clear and my sample project is zipped and in Visual Studio Solution format without any executable/binary file included. This but is probably is not in Visual Studio but in Access Data Components 2010, because the same code works great with Access Data Components 2007.

What do you need to know about free software?

I've done some work for a client over the past 2 years, developing numerous SSIS pkgs. for the client.

The packages have all been running perfectly fine week to week until about a month ago. The client's network was hit with some type of malware / ransomware and highly compromised their network. The had about a week's worth of down time with their third-party IT services firm cleaning the network, trying to restore backed-up files, etc.

Fast forward to a week later when I was told that their SQL Server machine didn't seem to be affected and that I could resume work on the current project I was working on.. I determined that the several SQL Server Agent Jobs that run each week to call various SSIS jobs were now failing, whereas they'd all been working without issue prior to the malware/ransomware attack.

Their 3rd party IT services firm understandably did all sorts of work to restore the integrity of their network, and along the way, apparently reset / rebuilt some user accounts and had to re-establish various permissions for these accounts.

We *thought* the user account rebuilding/etc. may have restricted permissions to where the accts. used for calling the automated SQL Server Agent Jobs now didn't have sufficient permissions to run the job nor call the respective SSIS packages.

The IT firm relaxed permissions for a couple of accounts in question and I found that the jobs would at least start to run at that point, so my suspicion was partially correct.

So now with all of the SSIS packages, I'm getting errors all seemingly related to an inability by the packages to read/write to numerous Excel spreadsheets. All of the SSIS packages do different things but basically they all query a few SQL Server databases, & write the recordsets obtained from SQL Server to empty Excel spreadsheet templates.

The SQL Server machine doesn't have Microsoft Office installed, so I've had the Microsoft Access Database Engine 2010 Redistributable (32-bit) installed on the machine for 2 years and it HAD been serving us fine as far as allowing the SSIS pkgs. to read/write to the Excel spreadsheets with ease.

I'm thinking with all of the malware/ransomware issues experienced by the client, and whatever work had to be done by the 3rd party IT services firm to get their network back in a stable, working order, something else has been done that's unfortunately still causing the SSIS packages to fail.

Here's the collection of error msgs. written to a log by just one of the SSIS packages: