After applying the wsus updates to my server I'm getting Error code: 0x80004005 while executing a SSIS Job which tries to export data to Excel.

It was running for some years, but suddenly stopped on two machines. The same error exists on my workstation while exporting from SSMS.

Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "Unexpected error from external database driver (1).". End Error Error: 2017-10-13 08:15:33.82 Code: 0xC020801C Source: DataPump ATT Excel-Tabelle in Langform [124] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "ATT_Excel" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2017-10-13 08:15:33.82 Code: 0xC0047017 Source: DataPump ATT SSIS.Pipeline Description: Excel-Export failed validation and returned error code 0xC020801C. End Error Error: 2017-10-13 08:15:33.82 Code: 0xC004700C

This is the list of the new updates on the first server:

• 2017-10 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4041687)
• 2017-10 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4041693)
• Cumulative Security Update for Internet Explorer 11 for Windows Server 2012 R2 (KB4040685)
• Windows Malicious Software Removal Tool for Windows 8, 8.1, 10 and Windows Server 2012, 2012 R2, 2016 x64 Edition - October 2017 (KB890830)
• 2017-10 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7 on Windows 8.1 and Server 2012 R2 for x64 (KB4043767)
• Security Update for Microsoft Office 2010 (KB2553338) 64-Bit Edition

I've filed a connect item for this error code 0x80004005 after wsus update

Workaround

After removing these updates (which I have found on the second server, too):

• KB 4040685 (This is on my workstation, too)
• KB 4041687
• KB 4041693

it is working fine on my server, but not yet on my machine. Another workaround seems to be using Jet OLEDB 12 and Excel 2007 for the connection, but this is a lot more work than removing some updates today!

Update 2017-10-18

Have a look at this discussion: social.msdn.microsoft.com/Forums/sqlserver/en-US

There you can read this statement:
The JET provider has been deprecated since 2002 and has not had updates since then. For all who are using SSIS, I recommend using the built in Excel connector within SSIS. Otherwise it would seem your best alternative would be to use the ACE provider as it was an upgrade to the JET engine.

There is not a direction to revert any changes or make any modifications to the JET provider. I apologize for this as I know that this will cause inconvenience to change all of your connection methods, or to look for alternative solutions.

My Opinion

So the best way is to install the Microsoft Access Database Engine 2016 and change the connection string to:

Provider=Microsoft.ACE.OLEDB.12.0;Data Source=<myoldexcelfile>.xls;Extended Properties="EXCEL 8.0;HDR=YES";

if you still need the old excel format.

Please be aware not to use the wizard, because the wizard changes the connection in my SSIS-package back to

Provider=Microsoft.Jet.OLEDB.4.0 

if you still want "Microsoft Excel 97-2003".

Now, I cannot use more than 1 Excel file parallel in SSIS-packages, so I have to change the logic to work sequential.

Next step is to test our software much better before applying wsus updates.