Post reply

Problem running a SSIS package under the SQL Agent using Timberline DSN.

  • March 19, 2012 at 1:34 pm

    #1461321

    I may have figured out what the problem is. I spoke with one of our network engineers and he mentioned that the DSN for the Pervasive database relies on a mapped drive location. The agent does not load a profile when it runs, so the drive mapping is not executed first and the DSN connection fails. When I ran it from BIDS, SSIS and command line DTEXEC, it was all running under my profile so the drive mapping was established.

    I'm going to work with him later this week on a possible solution. I'll report back then.

  • March 21, 2012 at 2:53 pm

    #1462435

    Drive mapping was the issue. To fix it, we scheduled a job which runs the xp_cmdshell stored procedure to execute a bat file. The bat file has the drive mapping script followed by a call to the dtexec utility with switches for the SSIS package.

Viewing 2 posts - 1 through 3 (of 3 total)

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