I have a package that runs from my 64 bit server. I run it via a command line: ""C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe" /DTS "\MSDB\BankImportsProd" /SERVER VSLPBBIDB01 /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V" It has been working.but then stopped. If I run it from my workstation or when it runs from it's schedule - I get a "login failed for user sa' If I login to the server and execute the job from the server it runs fine. Any ideas?qeqw

what is Protection Level that you used? http://www.rad.pasfu.com

look at this article for how to use DontSaveSensitive protectionLevel: http://blogs.msdn.com/b/runeetv/archive/2009/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspxhttp://www.rad.pasfu.com

My guess is that someone designed this package initially while logged in as the SQL Agent service account (bad idea) and saved the sa password (another bad idea) because he/she didn't understand Package Protection levels or Configurations. When you run it in BIDS (as you) your user key cannot DE-crypt the password because it was not the user key that was in effect when it was EN-crypted. But you are going to do your due-dilligence and get the scoop on these features and correct this problem, right? My blog on Configurations is here. Package Configurations are very powerful and there is a lot of stuff in this forum on them. Read up and good luck.Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.