Post reply

Job fails accessing mapped drive

  • August 21, 2006 at 10:53 am

    #169896

    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?

    Thanks

  • August 21, 2006 at 11:03 am

    #655942

    I'm new to SSIS, but if it is like DTS in SQL Server 2000, when you run it manually from your desktop system, it sees the mapped drive.  When run as a job, it is running on the server, and the server does not have the mapped drive, so it fails.  Try using a URL to define where the file is to be written, so it sees the same location regardless if it is running on your desktop or from the server.

    hth

    Lynn

  • August 21, 2006 at 11:10 am

    #655946

    The drive is mapped on the server and runs to success through SSIS and Management Studio. I'll try fully qualifying the machice\share and see what happens (i.e. \\machine\share\file.txt)

  • August 21, 2006 at 11:23 am

    #655950

    Fully qualifying the share folder fixed the problem.

  • August 21, 2006 at 12:04 pm

    #655957

    Glad it worked!

     

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply