Paul,
the reason is security, probably you created the package with a different account than the sql server agent is running.
Solution:
you can create the package with the agent account,
or in the package -> properties -> security -> protectionlevel -> choose encryptsensitivewithpassword en fill in a password.
greetz
http://www.ns-consulting.be
|||the package was originally created in management studio using the administrator account. do I need to set up the SQL Agent as a user? Is there a book on SQL Server 2005 which walks you through creating a sample solution from start to finish? I have the Administrator's Consultant and 'Changing the Paradigm' books. SQL Server 2005 is entirely new to me; I was a dba for Sql Server 2000 before this.
Thanks for your help!
Paul
|||
the package was recreated - I changed the encription option to 'Rely on server . . .' and changed the source path from X:\Directory\FileName to \\HostServerName\Directory\FileName.
problem is solved.
No comments:
Post a Comment