This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 17%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
I have a DTSX package created in VS2019 which when run from laptop runs fine. When deployed to a SQL2016 server it fails on the excel import step which should be pushing data into a SQL Table. The error from the SQL server hosting the DTK package is "Excel connection Manager" failed with error code 0xC0209303 I have installed the 64bit access jet engine on the target server with no success. If i set the properties to 32 bit and redeploy all the SQL connectors fail so that didn't help either
@Martin Stephenson
This issue seems to be related to SQL Server Integration Services, but tag "office-excel-itpro" focus more on general issue of Excel, I would remove this tag.
Thanks for your understanding.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 26%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYK%3C/text%3E%3C/svg%3E)
Hi @Martin Stephenson ,
I have installed the 64bit access jet engine on the target server
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 37%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
Hi @Martin Stephenson ,
1.When deployed to a SQL2016 server it fails on the excel import step which should be pushing data into a SQL Table.
May I know if you set TargetServerVersion as SQL Server 2016?
2.This download will install a set of components that facilitate the transfer of data between existing Microsoft Office files such as Microsoft Office Access (.mdb and .accdb) files and Microsoft Office Excel (.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.
We can download both 32bit and 64bit Microsoft.ACE.OLEDB Provider.
Please refer to Installing the Microsoft.ACE.OLEDB.12.0 Provider for Both 64-bit and 32-bit Processing
Best regards,
Mona
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
I've managed to install ACE OLEDB driver on the server and edit the connection properties to reflect this
taken from here microsoftaceoledb120-is-not-registered
now its saying that it cant open the file as it doesn't have access either its open or has no permission to open it.
I can see that there is no lock on the file and permissions aren't a problem as I have made it readable to all users.
So no progress yet :-(
Hi @Martin Stephenson ,
Please check if you run packages in ssisdb catalog or job and open or use the excel files in other progress at the same time.
Best regards,
Mona
Hi @Monalv-MSFT
The excel files I'm targeting are closed and at the moment I run the job manually when here is nothing else running.
now its no longer failing with excel errors but a sql connection error
I'm using a proxy which has read/write access to the database but the error message is apparently all about the connection
External component has thrown an exception at Ms.sqlserver.dts.runtime.dtscontainer.execute(connections connections
........... ISServerExecutionEvents.StartPackage()
which is odd because we use the same data connections in another package with no problem.
Create a new one with a different name?
So I have used the import data wizard to create an import package and saved it to the target server, this works it reads the excel file and writes the data to the database, all good. I run it manually and it works if I put it into a job executed by the agent and tell it to run as the SSIS job runner proxy it fails as it cant access the integration services ( presumably the agent service?). So I exported the package and imported into the Visual Studio project redeployed to my target server and it fails but this time with excel connection errors. Reconfiguring it to use the SQL Server package in 32bit mode seems to have solved the issue for the moment, but I now have a step in the ETL process that I cant edit from Visual Studio and any issues in the future are going to be a real pain to fix.
Also as a post script SSMS v18 wont connect to Integration services on the target server (SQL2016) so I have to keep finding an older version to run which is a minor issue but still a pain