Results 1 to 3 of 3
  1. #1
    Join Date
    Apr 2004

    Exclamation Unanswered: Scheduled SSIS failing all the time - Help!

    Hi all. We recently migrated to SQL Server '05 from 2000 and I'm trying to learn SSIS by crash course.

    I just wrote an SSIS for one of our nightly processes in Studio 2005. It built with no errors, and the solution and resulting package are saved on the server housing SQL Server.

    I ran the package in debug and it completed 100% with no errors. However, when I scheduled the package in SQL Server, it starts and fails.

    Now, I'm very new to SQL '05 and I'm trying to figure out how to log the SSIS jobs, but is there any way to find out why the scheduled packages fail?

    I'm desperately needing help on this, and any help would be greatly appreciated!

  2. #2
    Join Date
    Jan 2007
    Provided Answers: 12
    who's the owner of the scheduled job that runs this package?
    Home | Blog

  3. #3
    Join Date
    Apr 2004
    I found the problem, and it's SQL Server's insane paranoia. In Studio 2005, you have to set package security to EncryptSesnitiveWithPassword, then set a password.

    In SQL Server, you can schedule the package after entering the package password. However, you'll STILL have to go to the connection manager settings and manuall ADD the database passwords - because it can't use the passwords from the package.

    Once jumping through all those wonderful hoops, I can run the packages.

    This kind of stuff makes me miss the old school DTS!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts