Job Fails accessing mapped drive

I built a package in SSIS that exports some data in a database and writes it to a flat file. The flat file is written to a mapped drive on another server (shared folder). The package runs without failure in SSIS and when I deploy it on the SQL Server. The problem comes when I try to run the package as a job; it fails. If I change the file location to the local c: drive, the job runs to sucess. The id that starts the SQL Server Agent is a domain id that is included in both the domain admin group and the local admin group. All the job log indicates is that the job failed; no details.

What am I missing?

ThanksFully qualifying the share fixed the problem. Sure would like to understand why.

job failed to start - access denied

Hi,
the SQL Server Agent job that runs a backup to a network
drive wont start.The syntax is as follows :
BACKUP DATABASE Mydb
TO
DISK='\\ServerName\BACKUP\MyDB.BAK'
WITH INIT
In the error log and in the event viewer I can see the
following error message :operating system error 5 ( access
is denied). I can not figure it out why I can not run this
job since the SQL Server Agent startup account use the
domain user account that has sufficient permissions across
the domain and the job itself is owned by the same account.
Is there something else that I should pay attention to ?
Any view is apreciatedThe backup command runs under the security context of the SQL Server service
account. Ensure that account has the needed permissions.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mirko" <anonymous@.discussions.microsoft.com> wrote in message
news:023c01c3b978$a2a45a80$a001280a@.phx.gbl...
> Hi,
> the SQL Server Agent job that runs a backup to a network
> drive wont start.The syntax is as follows :
> BACKUP DATABASE Mydb
> TO
> DISK='\\ServerName\BACKUP\MyDB.BAK'
> WITH INIT
> In the error log and in the event viewer I can see the
> following error message :operating system error 5 ( access
> is denied). I can not figure it out why I can not run this
> job since the SQL Server Agent startup account use the
> domain user account that has sufficient permissions across
> the domain and the job itself is owned by the same account.
> Is there something else that I should pay attention to ?
> Any view is apreciated
>