May 9, 2013 at 1:45 pm
When I look into the SQL Server Job it is run as “SQL Server Integration Service Account” and it is NOT run as Proxy Account but when I look at the job history it says Executed as ‘UserOne’ (for example). I am trying to find out where this is tied because I need to access a fileShare where Agent account does not have access where as UserOne would- without actually using a proxy account. Thanks.
May 9, 2013 at 2:25 pm
What user is running the IS Service on that box?
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
May 9, 2013 at 3:58 pm
Evil Kraig F (5/9/2013)
What user is running the IS Service on that box?
Evil Kraig F, I have no clue. Its our production box and i doubt if i have access to find that out-how can i go about it if that is the approach?
May 9, 2013 at 4:25 pm
You have to RDC to the box, rt-click computer, manage, and check the services. Rt-click services and in properties for it you'll be able to see the login for it.
Usually jobs that run packages run under one of three contexts. The SQL Agent login, the SSIS service, or the proxy that's assigned to the job step. Your description sounds like it's the SSIS Service's login, so I was wondering if that matched what you were seeing.
If you don't have RDC rights and box admin, you won't be able to see the services and will need to inquire of those that do, probably the Senior DBAs on your staff.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
May 9, 2013 at 5:05 pm
Evil Kraig F (5/9/2013)
You have to RDC to the box, rt-click computer, manage, and check the services. Rt-click services and in properties for it you'll be able to see the login for it.Usually jobs that run packages run under one of three contexts. The SQL Agent login, the SSIS service, or the proxy that's assigned to the job step. Your description sounds like it's the SSIS Service's login, so I was wondering if that matched what you were seeing.
If you don't have RDC rights and box admin, you won't be able to see the services and will need to inquire of those that do, probably the Senior DBAs on your staff.
You were right- the SSIS is running Under SSIS SERVICE - 'UserOne' (In our context) when I RDC-ed the box. Is this where i would make the change?
May 9, 2013 at 6:09 pm
Yeah, either modify that to be one of the logins from the other systems that are working, or check that user's permissions against the target system. My guess is that the permissions aren't equivalent in the network or on the target system if it can inherit NT permissions.
SSIS Service though sounds more like a local account than an NT account, which may be half the issue.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply