March 17, 2007 at 9:43 pm
Looks like you are reading encrypted data.
Can you query the data through Query Window?
MohammedU
Microsoft SQL Server MVP
March 19, 2007 at 6:12 am
Not sure if this will help or not, but you might try going into the actual package properties and under the Security make sure the ProtectionLevel is set to Don'tSaveSensitive. Unless you want to choose (and set up) one of the security option.
Hope this helps!!!
MarkA
March 20, 2007 at 12:07 pm
If you are trying to execute the package through a job then you can try to go into SSIS and go to File > Save a Copy of >
At the bottom is a Protection Level setting. Make sure you select 'rely on server storage and roles for access control. Now save the package to SQL Server with that setting. Then try and execute your job that points to that package you saved.
March 22, 2007 at 10:26 pm
even with the package u r facing the problem u can execute the same with the option 'rely on server storage and roles for access control' selected. if possible run the package using the user that have access to msdb database.
Nitin'
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply