File system task error - Could not find a part of the path

  • I am trying to move a folder from one location to another and am using a file system task to accomplish this. I am using "Move directory" and variables for the source and destination. The to folder does not exist but \\File-02\DevSSIS\Applications\Results\Failure\ does exist.

    The parameter values are

    From folder: \\File-02\DevSSIS\Applications\Uploads\MarketBasket\NatlShare\PROCESSING_ABBIL_kbatta_20080918000000\

    To folder: \\File-02\DevSSIS\Applications\Results\Failure\ABBIL_kbatta_20080918000000\

    I keep getting the following error:

    OnError,,,FST_ArchiveFailure,9/30/2008 7:40:49 AM,9/30/2008 7:40:49 AM,-1073548540,0x,An error occurred with the following error message: "Could not find a part of the path '\\File-02\DevSSIS\Applications\Results\Failure\ABBIL_kbatta_20080918000000\'.".

    Both variables are set to EvaluateAsExpression true and the file system task has DelayValidation true.

    I have tried the folder names with and without "\" at the end.

  • check the issourcepathvariable true.IsDestinationPathVariable True and OverwriteDestination True .It might helps.

  • They are all true.

  • Hi Mate,

    It seems to be a bug in SQL Server if you supply a file name!

    As a work around I have used 2 file system tasks. The first copies the file and the second deletes the original.

    More info here - http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=180741

    Jc

  • Hi Mate,

    It seems to be a bug in SQL Server if you supply a file name!

    As a work around I have used 2 file system tasks. The first copies the file and the second deletes the original.

    More info here - http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=180741

    Jc

  • The better answer for this is to use rename. Rename will accept a new path and effectively do the same thing as your copy then delete, but in a single step.

  • Another solution for us was to use the IP address. It seems like SSIS/SQL Server had issues resolving the domain name.

  • Thanks, rename instead of move worked great!

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply