Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

<b> Error while try to execute using SQL Jobs </b> 2

Status
Not open for further replies.

sqlmann

Technical User
May 5, 2009
15
IN


Created one IIS Package, which will extract data from db2 to SQL server
It working fine when we excute it spearatly.

Tried to create jobs shedule ran this IIS package for every 3hours. When we try to run the excute the step it thorws error as
'
An OLE DB record is available. Source: "IBM OLE DB Provider for DB2" Hresult: 0x80040E4D Description: " SQL30082N Attempt to establish connection failed with security reason "3" ("PASSWORD MISSING"). SQLSTATE=08001'

I think there is simplere property setting to be done to fix this..

Note : Deployed this pack as File system


Please help me to fix this

 
When you design an SSIS package, you are designing it under the credentials you are logged into your workstation with. When you have sensitive data saved in your package such as your password to DB2, it can be encypted with your user credentials. However, SQL Server Agent will run under a different user account, so it will not be able to decrypt your sensitive information. So you have some choices:

1. Use a configuration file to supply the password at runtime.

2. Use a password for your package to use for the encryption, and supply that password to the SQL Agent job.

There are other options, but the two above are the methods I commonly use.

You can change these settings in the properties pane of the package, under the Security heading.

Here's some more information on MSDN:
 
Most packages I build are fairly complex and need to be highly portable so I am a huge fan of Using configurations, but not so much a file. I use an envirmoent vaiable config to point the package to a config file that holds a connection string for my config database where all the remaining configurations are stored. To me if you have any more than one or 2 items in config file they start to get messy and easy to mess up when modifying.

I can deploy a full solution to a new enviroment without having to replicate folder structures or even housing things on the same drive letter.
 
Thank you very much. I will try using configurations
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top