Hi,
I'm experiencing a problem that first surfaced around the time hotfix KB973593 was released in Nov 2009.
This patch was released and our WSUS server automatically updated all our client workstations running Office 2007 SP1 with it. Note that SP2 hadn't yet been deployed to these workstations.
I run a series of SQL Agent jobs executing SSIS packages that export data from SQL Server 2005 to a .xlsb Excel file. These files are then picked up by operators using the above mentioned workstations, modifed in some way, and then saved. The saved files are then re-imported by another SSIS package back into the same database, updating data where relevant.
This was what was occurring without error until KB973593 was deployed (automatically) by WSUS.
Now, the package that reimports the .xlsb file is failing, with the error message:
"SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Office Access Database Engine" Hresult: 0x80004005 Description: "This file was created in a previous beta version of Excel 2007. Open the file with Excel 2007 to save it to the most recent version of the Excel 2007 file format before opening the file in Access 2007."."
I was able to replicate the problem on my local development workstation. Whenever I tried to test the SSIS connection to the (saved) .xlsb file, I would get a similar message. The solution I found was to apply Office 2007 SP2 to my machine. Now the connection manager can open the .xlsb file.
However, when I run the package on the development server (and the same behaviour occurs on our Production server), the same error occurs. Obviously, I need to apply Office SP2 to our servers.
Except they do not have MS Office installed on them!
So, what do we know?
The version of Excel has been increased from 12.0.6214.1 (which works) to 12.0.6514.5 (by KB973593). This would appear to contain some changes to how the file is saved.
Business Intelligence Development Studio (BIDS) is fixed by deploying Office 2007 SP2 on to local workstations.
BIDS (and by extension, SSIS) is not fixed on servers that do not have Office 2007 installed on them.
What patch / hotfix do I need to apply to our servers in order for SSIS to be able to interpret the new file format for Excel 2007 SP2?
Version of MS Office Access Database Engine 2007 12.0.4518.1031
SQL Server 2005 SP3 is installed. (v9.0.4035)
Any (speedy) help greatly appreciated.
I'm experiencing a problem that first surfaced around the time hotfix KB973593 was released in Nov 2009.
This patch was released and our WSUS server automatically updated all our client workstations running Office 2007 SP1 with it. Note that SP2 hadn't yet been deployed to these workstations.
I run a series of SQL Agent jobs executing SSIS packages that export data from SQL Server 2005 to a .xlsb Excel file. These files are then picked up by operators using the above mentioned workstations, modifed in some way, and then saved. The saved files are then re-imported by another SSIS package back into the same database, updating data where relevant.
This was what was occurring without error until KB973593 was deployed (automatically) by WSUS.
Now, the package that reimports the .xlsb file is failing, with the error message:
"SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Office Access Database Engine" Hresult: 0x80004005 Description: "This file was created in a previous beta version of Excel 2007. Open the file with Excel 2007 to save it to the most recent version of the Excel 2007 file format before opening the file in Access 2007."."
I was able to replicate the problem on my local development workstation. Whenever I tried to test the SSIS connection to the (saved) .xlsb file, I would get a similar message. The solution I found was to apply Office 2007 SP2 to my machine. Now the connection manager can open the .xlsb file.
However, when I run the package on the development server (and the same behaviour occurs on our Production server), the same error occurs. Obviously, I need to apply Office SP2 to our servers.
Except they do not have MS Office installed on them!
So, what do we know?
The version of Excel has been increased from 12.0.6214.1 (which works) to 12.0.6514.5 (by KB973593). This would appear to contain some changes to how the file is saved.
Business Intelligence Development Studio (BIDS) is fixed by deploying Office 2007 SP2 on to local workstations.
BIDS (and by extension, SSIS) is not fixed on servers that do not have Office 2007 installed on them.
What patch / hotfix do I need to apply to our servers in order for SSIS to be able to interpret the new file format for Excel 2007 SP2?
Version of MS Office Access Database Engine 2007 12.0.4518.1031
SQL Server 2005 SP3 is installed. (v9.0.4035)
Any (speedy) help greatly appreciated.