Comments on: SSIS & Mapped Network Drives

By: Tavukio

Tavukio — Wed, 28 Apr 2010 17:29:25 +0000

This was my problem. Thanks for the solution.

By: Adam

Adam — Thu, 18 Dec 2008 20:53:23 +0000

In the end I did exactly that, I setup some sql security credentials, then created a proxy under SSIS Package Execution which I gave the SQL Agent to run as when calling my pacakage.

Thanks for the all your responses and the acticle.

By: Henry

Henry — Thu, 18 Dec 2008 16:04:52 +0000

I actually dealt with this issue today.

Remember that if you execute the package “in context of the server” thus via SQL Agent (scheduled job) you need to give the account under which the SQL Agent is running access to the folders where you are trying to access files/data.

By: Phil Brammer

Phil Brammer — Mon, 15 Dec 2008 19:19:32 +0000

What errors are you receiving, Adam? Are you running the package through SQL Server Agent, or another scheduling tool?

Remember that just because you might have access to a network resource doesn’t mean that the account that executes the package does.

Phil

By: Adam

Adam — Mon, 15 Dec 2008 17:36:21 +0000

Hi Phil,

I’ve encountered the exact problem you’ve described but even using the UNC path has not helped. Is there somethin else I might be missing like a specific package proctection level or something?

By: ABBAS

ABBAS — Sun, 02 Nov 2008 11:19:15 +0000

ihave agree