Hi Guys, I have deployed a package from local computer to local SQL Server 2008. Job was working fine but some reason suddenly prompting this error message. I am not sure why. I am using proxy admin access. Local server. Admin rights. Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted 04/19/2011 16:23:52,StoreFilter,Error,1,FW-MDM02,StoreFilter,StoreFilter,,Executed as user: AUR\fdev. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 4:23:52 PM Error: 2011-04-19 16:23:52.99 Code: 0xC0202009 Source: Data Flow Task MDM LOOKUP [63] Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E14 Description: "Deferred prepare could not be completed.". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E14 Description: "Access to the remote server is denied because no login-mapping exists.". End Error. If I run this package from MSDB library, package executes fine. It was working fine before. I don't know suddenly it started playing up. Thanks, D

the proxy account who sql server job runs under it has no access to remote path provided in the package probably ( maybe this access suppress nowadays by any other staff)http://www.rad.pasfu.com

Hi Reza, I changed all the folder to local D Drive still the same error. I think its something else. Package runs fine standalone, even on Integration Service MSDB. But when I create job and try to run it, then it will fail. Any help much appreciated.

when you run the package in BIDS and from SSMS with DTEXECUI on the same machine successfully, but fail at sql server job. the only thing appears in mind is permission issue. what about ProtectionLevel of package? did you tried with EncryptSensitiveWithPassword ?http://www.rad.pasfu.com

Hi Reza, Regarding ProtectionLevel of package, I tried with EncryptSensitiveWithPassword. But some reason my package is not saving password inside the package password. Thanks,

could you follow this picture tutorial and do exact same steps to set protectionLevel: http://www.protalk.in/sql-server/steps-to-create-and-deploy-ssis-package-as-a-sqlagent-job/ let me know if your problem exists stillhttp://www.rad.pasfu.com

I went through that link, but pic's are not loading in IE browser. I read that steps and done few changes according to that. I am sorry to being pain but do you have any other website with same steps. Thanks for the patience and help.

I think the trick you missed it this: when you set protectionLevel as EncryptSensitiveWithPassword, you probably enter your password in the text box in front of PackagePassword property. do this : click on the "ellipsis" button in front of packagePassword property, and in the property editor, set password twice. then you can deploy package. http://www.rad.pasfu.com

Hi Reza, Sorry, but still the same issue. I went through all the steps and deployed to SQL Server agent but it fails to run as job. However, I can run the package in SQL Integration services no issues. I think its something with the permission issue now. I can't figure out where, I am running job as proxy admin access. One of the step is to move files from Development to Production server. I think thats the step is failing. But if run the package in integration services it moves perfectly fine. Can you suggest me where to look. Thanks,