Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
JeffK627
Yak Posting Veteran
50 Posts |
 Posted - 2011-01-28 : 14:50:06
|
| Hi All,I have an SSIS job that runs on three different servers (Dev, QA and Production) once a week. This week it suddenly failed in the Production server and will not run. Here the message from the Job history:MessageExecuted as user: XXXXXXX. ...on 10.0.2531.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:27:48 PM Error: 2011-01-28 13:28:26.10 Code: 0xC020200E Source: IT0032 Data Flow Task IT0032 176573 SourceSystem CDS FF Source [119] Description: Cannot open the datafile "D:\SSIS\R9\Hewitt\Import\HRMS_CDS_CON176573.TXT". End Error Error: 2011-01-28 13:28:26.10 Code: 0xC004701A Source: IT0032 Data Flow Task SSIS.Pipeline Description: component "IT0032 176573 SourceSystem CDS FF Source" (119) failed the pre-execute phase and returned error code 0xC020200E. End ErrorIt gives this error for all the flat files that it's supposed to read. The Server Admin swears blind that nothing has been changed on the Production server, but this is a job that has run fine for 5 months and just started failing this week. Any ideas at all are welcomed, I'm stumped. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2011-01-28 : 15:29:54
|
| Check permissions on that path, specifically for the SQL service account. To troubleshoot it, login with the SQL service account on the database server and manually kick off the SSIS package. You should be able to see better information by doing it this way. Validate that you can open that file via this account. Do NOT use your own account, you must troubleshoot this with the same account that is executing the job.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
 |
|
|
Stamey
Starting Member
14 Posts |
Posted - 2011-02-01 : 15:41:24
|
| Sometimes admins in other areas change things and don't inform others about it, such as permissions to get to your data file. I have had corporate put domain policies in place that affected file and share rights that they never considered when they thought up their policy.Could also be the file source changed something. We had a source for our data files suddenly change the internal file name format. The zip file name format was the same as last month's files, but the file name format inside the zip no longer resembled the zip file name.Chris |
|
|
|
JeffK627
Yak Posting Veteran
50 Posts |
Posted - 2011-02-03 : 11:51:51
|
| I had the server admin open the package from the server where it was failing. Somehow the Language tag of first script task, which had been written in VB.NET, got changed to C# 2008. Needless to say it broke. We re-migrated the SSIS package from one of the servers where it was working and all is now well - for the time being! |
|
|
|
|
|
|
|
|
SSIS Job that used to run fine suddenly failing