Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

SSIS package not running with job

$
0
0


Hi,

I'm using SQL Server 2008 R2 SP1 on Windows 7 OS.
I'm running an SSIS package on my local machine and the package is located in C drive.

I created a SSIS package with 32 bit version of Excel as source and destinations in different DFTs.
For this to run properly, I changed the Run64BitRuntime to False.
The package is running fine. But when I create a job to run this package it failed.
I created a Credential, Proxy and windows user login with access to the folders where excel files are present.
I changed the job owner to the new login which I created and job step RunAs to the proxy account.

This time I got a different error as below:

Executed as user: USHYDDJANDHYAL7\SQLAgent. Microsoft (R) SQL Server Execute Package Utility  Version 10.50.2500.0 for 32-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  1:51:23 AM  Info: 2012-07-22 01:51:24.32     Code: 0x4004300A     Source: DFT_Excel To SQL -- Dates SSIS.Pipeline     Description: Validation phase is beginning.  End Info  Progress: 2012-07-22 01:51:24.32     Source: DFT_Excel To SQL -- Dates      Validating: 0% complete  End Progress  Error: 2012-07-22 01:51:24.40     Code: 0xC0202009     Source: SSIS_Pkg_RU Connection manager "Excel Connection Manager 1"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.  An OLE DB record is available.  Source: "Microsoft Access Database Engine"  Hresult: 0x80004005  Description: "Unspecified error".  End Error  Error: 2012-07-22 01:51:24.40     Code: 0xC020801C     Source: DFT_Excel To SQL -- Dates Excel Source [1]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection Manager 1" 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: 2012-07-22 01:51:24.40     Code: 0xC0047017     Source: DFT_Excel To SQL -- Dates SSIS.Pipeline     Description: component "Excel Source" (1) failed validation and returned error code 0xC020801C.  End Error  Progress: 2012-07-22 01:51:24.40     Source: DFT_Excel To SQL -- Dates      Validating: 50% complete  End Progress  Error: 2012-07-22 01:51:24.40     Code: 0xC004700C     Source: DFT_Excel To SQL -- Dates SSIS.Pipeline     Description: One or more component failed validation.  End Error  Error: 2012-07-22 01:51:24.40     Code: 0xC0024107     Source: DFT_Excel To SQL -- Dates      Description: There were errors during task validation.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  1:51:23 AM  Finished: 1:51:24 AM  Elapsed:  1.31 seconds.  Process Exit Code 1.  The step failed.


When I run the package from the SSMS --> Stored Packages --> MSDB, this is executing perfectly and when I run it from CMD, it is running successfully. But when I run the job, it is failing.

I gave the required permissions to the login like Sysadmin server role, and in user mapping, for msdb database, checked the SQL Agent related db roles and db_owner as well.
In the job step, I selected CMD and gave the fully qualified path of the 32 bit of DTExec.exe  and the remaining parameters like /SQL, Server name, package name etc.
I even changed the Protection level to DoNotSaveSensitive but still no luck.

I'm not understanding why the package is failing through job but not through BIDS, CMD, SSMS.

Could anyone please help me out with this issue?

Regards,
djandy


Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>