"Cillian" wrote:

> Thanks B@ns for the response , I will try and amend the protection level as
> you have suggested and let you know how I get on
>
> Regards
> Cillian
>
>
> "B@ns" wrote:
>
> > Hi Cillian,
> >
> > Since I have never used Protection Level - Rely on Server Storage, I am not
> > sure how it works.
> > However, I have developed and deployed SSIS packages that fetch data from
> > IBM DB2.
> >
> > I have been using the Protection Level - EncryptSensitiveWithPassword. I
> > give a password to the package, which needs to be decrypted while executing
> > the package on the target machine (in your case, the live server).
> >
> > Hope this helps.
> >
> > Regards,
> > B@ns
> >
> > "Cillian" wrote:
> >
> > > Hi there
> > >
> > > I'm hoping someone can give a pointer as to issues I am having regarding
> > > SSIS configuration. I have developed an SSIS package which extracts data
> > > from an iSeries IBM machine. The configurations I am storing in a SQL table.
> > > I have loaded the package into the MSDB on Development with Package
> > > Protection Level - Rely on Server Storage and run it and it runs cleanly. I
> > > have then deployed it onto the soon to be Live server along with the
> > > appropriate SQL configuration entries. This if run from msdb through SQL
> > > Server Management Studio from the Development machine runs OK.
> > >
> > > However if I run it from SQL Server Management Studio on the Live machine I
> > > get a null password error. I have tried several different SQL configuration
> > > combination mainly revolving aroung using ConnectionString or User Password
> > > entries, but get the same issue. I can get it to work by amending the
> > > Connection Manager entry within the Execute Package Utility
> > >
> > > I have verified the ISeries ODBC entries match on both machines. The only
> > > other complication is that the Live Server is running on a cluster, we are
> > > running sp2 on SQL 2005.
> > >
> > > Any ideas welcome
> > >
> > > Thanks
> > > --