Post reply

DTSER_FAILURE when using unc path to the flat file across the network

  • March 30, 2011 at 10:22 am

    #142453

    This has to be security issue but I do not know how to set the security the SYSTEM user so that this job that executes the SSIS package will run from a stored procedure this statement - EXEC msdb.dbo.sp_start_job @job_name = 'ExpData_CTSImportRawFiles'

    The user has rights to the folder containing the flat file but the job executes by the SYSTEM user. I am new to SQL server 2008 and all this security.

    error Message:

    Executed as user: CT3\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 10:45:31 AM Error: 2011-02-17 10:45:31.88 Code: 0xC001401E Source: expData_ImportCounselingNote Connection manager "SourceConnectionFlatFile" Description: The file name "\\Ct3\ImportFiles\expData_CounselingNote.csv" specified in the connection was not valid. End Error Error: 2011-02-17 10:45:31.88 Code: 0xC001401D Source: expData_ImportCounselingNote Description: Connection "SourceConnectionFlatFile" failed validation. End Error Error: 2011-02-17 10:45:31.89 Code: 0xC001401E Source: expData_ImportCounselingNote Connection manager "SourceConnectionFlatFile" Description: The file name "\\Ct3\ImportFiles\expData_CounselingNote.csv" specified in the connection was not valid. End Error Error: 2011-02-17 10:45:31.89 Code: 0xC0202070 Source: expData_ImportCounselingNote Connection manager "SourceConnectionFlatFile" Description: The file name property is not valid. The file name is a device or contains invalid characters. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:45:31 AM Finished: 10:45:31 AM Elapsed: 0.25 seconds. The package execution failed. The step failed.[/size]

    Thanks for you help

    Roxanne

  • March 30, 2011 at 10:40 am

    #1305555

    Please set your font to a smaller size.

    Does the user that executes the package have rights on that path?

    Did you check if the user is the one you expect?

    How is this package executed? Is it a job step? Does it work interactively?

    You could check SPNs for the SQL Server service account and see if it is trusted for delegation.

    -- Gianluca Sartori

Viewing 2 posts - 1 through 2 (of 2 total)

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