August 23, 2010 at 8:16 am
I built an SSIS package on Server A to extract data from an MS Access file on Server B. My domain account has access to the Server B and the package executes correctly if I debug in VS on Server A. I scheduled the job to run under the SQL "sa" account on Server A and it fails, I presume because SQL "sa" doesn't have access rights to Server B. So I had a domain account created that I want to use to execute the job. I assigned the account sysadmin role on Server A and it has access rights to Server B, but I still get the same error:
Unable to determine if the owner of [domain account] of job MyAccessJob has server access (reason: could not obtain info....)
August 23, 2010 at 9:39 am
nano2nd (8/23/2010)
I built an SSIS package on Server A to extract data from an MS Access file on Server B. My domain account has access to the Server B and the package executes correctly if I debug in VS on Server A. I scheduled the job to run under the SQL "sa" account on Server A and it fails, I presume because SQL "sa" doesn't have access rights to Server B. So I had a domain account created that I want to use to execute the job. I assigned the account sysadmin role on Server A and it has access rights to Server B, but I still get the same error:Unable to determine if the owner of [domain account] of job MyAccessJob has server access (reason: could not obtain info....)
FYI: Please move this post to the SSIS forum.
Please post the error message you're getting when you run the job manually. My guess is at run time your package doesn't know the credentials to connection to the Access DB. You will have to use a package configuration file to store your Access credentials and add that config file when you configure the job.
Thanks,
MCTS: BI 2008, MCITP: BI 2008
Stay Thirsty My Friends
August 23, 2010 at 10:12 am
No, this isn't an SSIS issue. SQL Agent can't verify that the job owner exists and has rights. I have seen this often and never found a reliable cause or troubleshooting path. The only way I have resolved this is to set the job owner to SA. But the error happens before the package is even hit by SQL.
August 23, 2010 at 11:21 am
I think you are correct. I have a domain account that the package can use, but I haven't passed the password to it. I'll have to figure out how to do that.
August 23, 2010 at 1:41 pm
A proxy account was the solution. I created a credential, a proxy and change the job to run under the proxy. Thanks to both of you.
August 23, 2010 at 2:33 pm
nano2nd (8/23/2010)
A proxy account was the solution. I created a credential, a proxy and change the job to run under the proxy. Thanks to both of you.
Thanks for posting your solution.
MCTS: BI 2008, MCITP: BI 2008
Stay Thirsty My Friends
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply