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 |
|
igorblackbelt
Constraint Violating Yak Guru
407 Posts |
 Posted - 2007-08-09 : 18:24:39
|
| Having a little bit of trouble understanding this...If I log on the server with my windows account, I'm able to execute the package without a problem, now, if I execute the job, which is owned by the agent (TakkaraSQL), the job fails. I thought it could be related to file/share permissions, but it's not and the package is failing at the validation stage.Any ideas?Executed as user: WECLICK\TakkaraSQL. ...9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 5:35:15 PM Error: 2007-08-09 17:35:16.83 Code: 0xC001401E Source: Package1 Connection manager "1080.TXT" Description: The file name "\\panaka\input\Mortgage\Fares\RawFiles\archive\NHO\incoming_files\1080.TXT" specified in the connection was not valid. End Error Error: 2007-08-09 17:35:16.83 Code: 0xC001401D Source: Package1 Description: Connection "1080.TXT" failed validation. End Error Error: 2007-08-09 17:35:16.88 Code: 0xC001401E Source: Package1 Connection manager "archive\NHO\incoming_files" Description: The file name "\\panaka\Input\Mortgage\Fares\RawFiles\archive\NHO\incoming_files\" specified in the connection was not valid. End Error Error: 2007-08-09 17:35:16.88 Code: 0xC001401D Source: Package1 Description: Connection "archive\NHO\incoming_files" failed ... The package execution fa... The step failed. |
|
|
karuna
Aged Yak Warrior
582 Posts |
Posted - 2007-08-09 : 20:28:08
|
| Either the file in the path \\panaka\input\Mortgage\Fares\RawFiles\archive\NHO\incoming_files\1080.TXT does not exists or the user executing the package does not have permission to access the file or folder.The validation fails because its not able to establish connection to the file / folder. |
 |
|
|
igorblackbelt
Constraint Violating Yak Guru
407 Posts |
Posted - 2007-08-10 : 10:02:23
|
| Thanks Karuna, you are right, the agent doesn't have access to the share, see below my workaround this issue and see my question below.I logged on the server as the user that was trying to execute the job and actually, the users doesn't have access to the shared, so I started playing around with proxy accounts, I created a credential with my domain user (which has access to shares and all), then created a proxy with that new credential and configured the job to run the step that was executing the ssis package to execute as that new proxies. Boom, it works.Now, of course, I won't keep that running under my account, I'm sending out a request to day to create a domain user dedicated for any process for this specific database and give access to that account and make it a proxy.Now comes the question, it that the best/most recommended way of doing this? I was reading about package protection levels, should I look into this type of solution instead of using proxy accounts? |
|
|
|
karuna
Aged Yak Warrior
582 Posts |
Posted - 2007-08-10 : 11:40:31
|
| This gives more detailed information on this topic. You have to decide how you want to go. If you are using configuration files, then you can go with the protection level of Dont Save Sensitive.http://support.microsoft.com/kb/918760/ThanksKarunakaran |
|
|
|
|
|
|
|
|
SSIS Execution issue - Error msg included