With the increasing importance of apps & networks in both business & personal interconnections, perfor. has become one of the key metrics of successful communication. This ebook is a hands-on business-case-driven guide to understanding MySQL query parameter tuning & database perf
Solved
Excel Connection Manager failed with error code 0xC0202009
Posted on 2013-05-11
What driver will I need to add to our server to get an SSIS job that creates Excel files to run? I have the job set to "Use 32 bit runtime" enabled but I keep getting Excel Connection Manager failed with error code 0xC0202009. When I read other posts they say I need to download Excel jet drivers. I have found the 2007 Office System Driver: Data Connectivity component, but when I read the details, it states that this is not intended for server side programs where the code will run under a system account. I want to run the SSIS job weekly from SQL Server Agent. Is this the correct or should I be using another dll?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
4
3
8 Comments
Hi,
can you try to set the delay validation property to true?
stackoverflow.com/question
can you try to set the delay validation property to true?
stackoverflow.com/question
The OOTB driver are fine as long as you use 32bit.
For 64 bit you can use the MS Access drivers package but it seems that its more complicated because BIDS is 32 bit so you would have to install both.
Which SQL server edition and version are you using?
You can also run the agent job using a combo of SQL proxy and SQL credentials to run as a specific domain user.
For 64 bit you can use the MS Access drivers package but it seems that its more complicated because BIDS is 32 bit so you would have to install both.
Which SQL server edition and version are you using?
You can also run the agent job using a combo of SQL proxy and SQL credentials to run as a specific domain user.
Rainer,
I changed my application on the Data Flow task for the Excel destination to delay validation property to true. I then transferred the new code up to the server and changed the data sources to the current database name and server name and the file location for the Excel output.
I reran the job and got the same error:
Executed as user: HQ\SQLServerHQVSQL01. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4263.0 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Argument "Excel" for option "connection" is not valid. The command line parameters are invalid. The step failed.
I am using SQL Server 2008 r2. I am not sure what you mean by your last statement - You can also run the agent job using a combo of SQL proxy and SQL credentials to run as a specific domain user. Explain further.
Thanks
I changed my application on the Data Flow task for the Excel destination to delay validation property to true. I then transferred the new code up to the server and changed the data sources to the current database name and server name and the file location for the Excel output.
I reran the job and got the same error:
Executed as user: HQ\SQLServerHQVSQL01. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4263.0 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Argument "Excel" for option "connection" is not valid. The command line parameters are invalid. The step failed.
I am using SQL Server 2008 r2. I am not sure what you mean by your last statement - You can also run the agent job using a combo of SQL proxy and SQL credentials to run as a specific domain user. Explain further.
Thanks
Active 4 days ago
I am not sure if you know or if we have covered this in the past, but there is no 64-bit JET driver.
Hi,
a SQL proxy account in SQL agent can be used to impersonate another user. This is useful if you have a managed environment where you can use a technical service account to run jobs (eg no password expiration, specific permissions on SQL Server ...).
SQL agent job configuration should be like this:
http://sqlblog.com/blogs/john_paul_cook/archive/2010/03/24/running-32-bit-ssis-in-a-64-bit-environment.aspx
a SQL proxy account in SQL agent can be used to impersonate another user. This is useful if you have a managed environment where you can use a technical service account to run jobs (eg no password expiration, specific permissions on SQL Server ...).
SQL agent job configuration should be like this:
http://sqlblog.com/blogs/john_paul_cook/archive/2010/03/24/running-32-bit-ssis-in-a-64-bit-environment.aspx
The job stream definitely has "Use 32 bit runtime" enabled, so this time I ran the job from Execute Package Utility and this time I received the following error:
Code:0x00000003
Source: Delete Worksheets if exists
Description: There was an exception while loading Script Task from XML:
System.IO.FileNotFoundExce
'Microsoft.VisualStudio.To
PublicKeyToken=b03f5f7ff11
File name: "Microsoft.VisualStudio.To
PublicKeyToken=b03f5f7ff11
at Microsoft.Sqlerver.Integra
at Microsoft.Sqlerver.Integra
at Microsoft.Sqlerver.Integra
at Microsoft.Sqlerver.VSTAHos
etc
until the last line which states
Option "8.0;HDR=Yes\;" is not valid.
Sometimes I get this first detailed error and yet most other times when I execute the package in Execute Package Utility I just get :
Option "8.0;HDR=Yes\;" is not valid.
The way I got this message was :
Within the Execute Package Utility, I selected the Connection Managers
if I check both connection Managers, I receive the simple error: Option "8.0;HDR=Yes\;" is not valid.
The connection string actually has : Provider=Microsoft.Jet.OLE
Is the server missing "'Microsoft.VisualStudio.T
Code:0x00000003
Source: Delete Worksheets if exists
Description: There was an exception while loading Script Task from XML:
System.IO.FileNotFoundExce
'Microsoft.VisualStudio.To
PublicKeyToken=b03f5f7ff11
File name: "Microsoft.VisualStudio.To
PublicKeyToken=b03f5f7ff11
at Microsoft.Sqlerver.Integra
at Microsoft.Sqlerver.Integra
at Microsoft.Sqlerver.Integra
at Microsoft.Sqlerver.VSTAHos
etc
until the last line which states
Option "8.0;HDR=Yes\;" is not valid.
Sometimes I get this first detailed error and yet most other times when I execute the package in Execute Package Utility I just get :
Option "8.0;HDR=Yes\;" is not valid.
The way I got this message was :
Within the Execute Package Utility, I selected the Connection Managers
if I check both connection Managers, I receive the simple error: Option "8.0;HDR=Yes\;" is not valid.
The connection string actually has : Provider=Microsoft.Jet.OLE
Is the server missing "'Microsoft.VisualStudio.T
Featured Post
Every day, more and more legacy backup customers switch to Veeam. Technologies designed for the client-server era cannot restore any IT service running in the hybrid cloud within seconds. Learn top Veeam advantages over legacy backup and get Veeam for the price of your renewal
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
One of the most important things in an application is the query performance. This article intends to give you good tips to improve the performance of your queries.
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.
Suggested Courses
Course of the Month14 days, 20 hours left to enroll
649 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.