Win2k3 and DTS Folder access

When running a scheduled job from sql srv 2000 on win2k3, I get a "path not found" error msg in my Activex script task (I'm using Scripting.FileSystemObject).

Its a UNC path name and everyone has folder access and folder exists.

I even mapped the drive and referenced it that way and still no path found.

Tried starting server and agent using different accounts (domain & local) and still saying path not found.

Any ideas?

Based on the job owner you can determine the NT account being used.

Is the job owner a sysadmin?
Yes - SQL Server Agent Service Account
No - SQL Agent Proxy Account

Did you check SQL permissions?
Did you check the folder and file permissions at both destination and source

http://support.microsoft.com/defaul...kb;en-us;269074

When folder or file is local then its no problem.

The only way that I can get a job to be sheduled is if the owner is "win2k3Name\Administrator".

But if the package is referencing folder and files on a remote machine then I get error msg.

I even added the remote machine as a trusted site on win2k3 and I still get error msg.

by files on a remote machine are we talking about access to another SQL server or files on another machine?

If SQL, Did you set up the remote machines as linked servers?

If files,
and then this is an offset chance, but I've had a problem before where the server the package was on was using NT login and had problems with when writing to a non NT required server that it reverted to run as defaults and the default for a active x object is set in i think DCOM not the w2k administrator you have it set up to be. I think it's default is IUSR_machinename which would explain why your machine can do it locally but not remotely (in fact it'd get "path not found" remotely since it doesn't have read permissions). Meaning the active x object (FSO) is getting access denied even though your DTS package has permissions. Which is another point, what do the error logs say when you get path not found? What account is trying to do what in it? But like i said, that's a stretch and rare situation and just thought i'd put it out incase you are infact having this problem and hopefully give you some ideas.....