SSIS Package Fails Remotely or in Job but Runs on Server

  • Hello,

    I've built a package and have been following the mdsn guidelines

    http://support.microsoft.com/kb/918760

    Method 4: Use SSIS Package configuration files

    and DontSaveSensitive, etc.

    The method usually works fine.

    But this one package runs locally in my BIDS,

    but since deploying it can only be run by term serv-ing

    onto the server and running the package from the file system.

    It will not run from SQL Manager Studio/Integration Server remotely or in a job.

    It errors out on the login for the OLEDB connections, the login is fine and

    there are no errors when I double clickon the package file itself

    and run it in SMS directly on the server.

    Pardon me if this is a re-post, all the related mentions I found here did not seem

    to fit this exactly and refer to that MSDN fix we already implemented.

    Thanks everyone!

    Skål - jh

  • hey,

    Are you sure your SQL server agent has sufficient rights to be running the package?

    ~PD

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

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