Pakcage Error...How To Read Files On A Different Domain?

So did some troubleshooting on the my previous post -http://forums.microsoft.com/forums/ShowPost.aspx?PostID=272319&SiteID=1


Thanks to everyone who tried to help... So I got some insight into what is happening.

My package was having trouble reading files on a remote domain although I mapped the drives locally. This does not cause either running the package to failed either through directly running under VSS, or Execution Utility. But it failed when I try to schedule it through SQL server agent.

I wonder if it is the security context problem and asking for help of how to get around that issue.

So I have a for each file loop container that retrieve filenames on a remote domain which has a different security account then my local account. So how I got around that was to map that drive locally to a drive letter...example W:

then I use W: as my path within my package. I was trying to figure out where I can declare the connection within my package specifically, but don't know if I could do that.

If I run this through VSS or exectuion utility, it works okay. I was able to see W: and all the files on that mapped drive and read in the data.

However, when I schedule it under SQL agent, it doesn't see any files then exited the package as success right the way, because it has nothing to do....


So is there a different between the security context on mapped drive between VSS and my SQL agent? If so...How do I get around that challenge?

BTW, the two domain do not have share accounts between each others. I had to specified and map the drives explicitly.

THANKS!
JON