Excel Connection Manager failed with error code 0xC0202009

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?
LenTompkinsAsked:
Who is Participating?
 
Rainer JeschorConnect With a Mentor Commented:
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
0
 
Rainer JeschorCommented:
Hi,
can you try to set the delay validation property to true?
stackoverflow.com/questions/748136/ssis-acquireconnection-method-call-to-the-connection-manager-excel-connection
0
 
Rainer JeschorCommented:
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.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
LenTompkinsAuthor Commented:
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
0
 
Anthony PerkinsCommented:
I am not sure if you know or if we have covered this in the past, but there is no 64-bit JET driver.
0
 
LenTompkinsAuthor Commented:
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.FileNotFoundException: Could not load file or assembly
'Microsoft.VisualStudio.Tools.Applications.Core, Version=10.0.0.0, culture=neutral,
PublicKeyToken=b03f5f7ff11d50a3a' or one of its dependencies.  The system cannot find the file specified.
File name: "Microsoft.VisualStudio.Tools.Applications.Core, Version=10.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7ff11d50a3a
  at Microsoft.Sqlerver.IntegrationServices.VSTA.VstaHelper.<Cleanup>b__1a()
  at Microsoft.Sqlerver.IntegrationServices.VSTA.MTaExecution.Run(Action action)
  at Microsoft.Sqlerver.IntegrationServices.VSTA.VstaHelper.Cleanup()
  at Microsoft.Sqlerver.VSTAHosting.VSTAScriptingEngine.DisposeVSTAHelper()

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.OLEDB.4.0;Data Source=C:Lincare\CreditRTB_.xls;Extended Properties="EXCEL 8.0;HDR=YES";

Is the server missing "'Microsoft.VisualStudio.Tools.Applications.Core" or is the real problem the Excel output string?
0
 
LenTompkinsAuthor Commented:
I am going to ask that BIDS be installed on this server, so I can determine what the problem is tomorrow.
0
 
LenTompkinsAuthor Commented:
I am still waiting for BIDS to get installed on this server, but appreciate the assistance.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.