February 15, 2009 at 7:30 pm
I've created an SSIS package that runs fine in the development IDE.
However when I deploy the package and schedule the package to run I
get the following error
Executed as user: PCA\svcsqladm. Microsoft (R) SQL Server Execute
Package Utility Version 9.00.3042.00 for 32-bit Copyright (C)
Microsoft Corp 1984-2005. All rights reserved. Started: 4:20:00
PM Error: 2007-11-29 16:20:19.28 Code: 0xC020200E Source:
Data Flow Task Destination - CRRFDExport_csv [25] Description:
Cannot open the datafile "S:\Dialer Reports\rfd\CR_RFD
\CRRFDExport.csv". End Error Error: 2007-11-29 16:20:19.30 Code:
0xC004701A Source: Data Flow Task DTS.Pipeline Description:
component "Destination - CRRFDExport_csv" (25) failed the pre-execute
phase and returned error code 0xC020200E. End Error DTExec: The
package execution returned DTSER_FAILURE (1). Started: 4:20:00 PM
Finished: 4:20:19 PM Elapsed: 18.313 seconds. The package execution
failed. The step failed.
I'm using the SQL Server agent account which is a dooain account and
has full access to the durectory in question. Can anyone tell me what
is going wrong. I don't understand what security change is required.
February 16, 2009 at 4:26 am
Have you changed the default Protection Level propery on the package so that it is not EncryptSensitiveWithUserKey? Have you tried to login as the domain account and execute the package manually?
Take a look at this article for more guidance to this issue - An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step.
----------------------------------------------------------------------------------------
Dan English - http://denglishbi.wordpress.com
February 16, 2009 at 8:50 am
Is "S" a mapped drive? Since the SQL Server Agent account is not "logged in" to the server the drive is not being mapped. Try using the UNC path.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 17, 2009 at 8:01 am
well after creating the credentials and proxy, it was still not executing in the sql agent job, but finally it was successful when in the package itself i entered the Network Path, since the drive was mapped i thought the package will get through it but now the package is running successful. I still dont understand that the package was showing the mapped drive name in the old server job and was working fine.
Thanks to all.
February 17, 2009 at 3:56 pm
mapped drives are a pain in scripts...avoid them anytime you can... 😀
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply