Checkpoint file name error
Hi all, I have a set of SSIS packages running smoothly daily by SQL Server Agent. When I am checking last night's log, I am getting following error message. Even though there was no change yesterday. MessageExecuted as user: SNL\sqladmin. ...on 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:08:31 PM Error: 2008-09-24 23:08:33.33 Code: 0xC020207E Source: Import Dim_Postcode Description: The file name is not valid. The file name is a device or contains invalid characters. End Error Error: 2008-09-24 23:08:33.33 Code: 0xC0017004 Source: Import Dim_Postcode Description: The result of the expression "@[C7::CheckpointFileName]" on property "CheckpointFileName" cannot be written to the property. The expression was evaluated, but cannot be set on the property. End Error Error: 2008-09-24 23:08:33.35 Code: 0xC020207E Source: Import Dim_Postcode Description: The file name is not valid. The file name is a device or contains invalid characters. End Error Error: 2008-09-24 23:08:33.35 Code: 0xC0017004 Source: Import Dim_Postcode Description: The result o... The package executed successf... The step succeeded. And same is error for all the packages running as steps in thisjob. Thanks & Regards
September 25th, 2008 6:44am

are you using the cmdexec subsystem and dtexec to execute the package? if not, then do so. this will yield more informative log messages. if necessary, please re-run the job and repost the new log.
Free Windows Admin Tool Kit Click here and download it now
September 25th, 2008 7:48am

I am new to SSIS actually, so dont know about anything other than SQL Server Management Studio. But the job did not run next time either when I tried to run it. The same error. Cud u plz tell me how to run using cmdexec or dtexec please ??? Or any other Idea please ???
September 25th, 2008 8:42am

OK. Got that. Someone had removed thefolder containing the configuration file and error, log and checkpoint folders were also in that folder. After making folders again and with config file back in folder, package is running now fine. Thx Kashif Zia
Free Windows Admin Tool Kit Click here and download it now
September 25th, 2008 9:14am

This problem is due to long path errors,i had the same problem and it cannot be resolved by primary methods,you will have to use a tool for it,i am using a very small tool available at http://pathtoodeep.com for it and it is working like a charm
November 22nd, 2010 12:28am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics