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 |
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
 Posted - 2011-10-06 : 11:20:51
|
| I am running a SSIS package as a job.It is selected to run as "sql server agent service account" in the job step properties.But when running the job it gives the following error.I think it is to do with file or folder permissions but not sure what to do.Any suggestions please?ThanksDescription: The file name "\\servername\myfolder\filename.csv" specified in the connection was not validAnd it also says:Description: Connection "Filename_connection" failed validation. |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-10-06 : 12:21:44
|
| is the path accessible from server where you created the job using proxy account?------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
Posted - 2011-10-06 : 12:34:06
|
| I did a test to confirm the permission issue. 1- In BI the ssis package runs fine and access the network file which points to a Dev server... 2- Set up a job for this ssis package and works fine. 3- In BI changed the path to point to the production server and still the package runs fine and accesses the file on the production server. 3- setup a job for the package which points to the production server, BUT it gives the error as mentioned previously. The path I have setup for the ssis package to access is \\servername\myfolder\filename.csv Does this mean that in the production folder ie. \\productionServername\myfolder" I have to give read rights to the localSystem user (Which is the user that runs the sql server agent(MSSQLSERVER)? Thanks |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-10-06 : 12:41:38
|
| yep. you need to if its the login under which agent runs and executes the package.In actual scenario you will be creating a seperate proxy account with reqd folder permissions and it will be used by sql agent to execute the package. and this will be having seperate credentials b/w environments so that nobody will be able to get access through this account in production.I didnt understand why you're running package pointing to production server from your BI though. its certainly not a good thing to do as you might end up manipulating live data.------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
arkiboys
Master Smack Fu Yak Hacker
1433 Posts |
Posted - 2011-10-07 : 13:01:08
|
| thanks |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-10-07 : 13:07:44
|
| welcome------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
|
|
|
run ssis package as a job