"bigbrorpi@gmail.com" wrote:

> I narrowed this down to happenning only after I add a configuration
> file to the package.
>
> Any ideas?
>
> bigbrorpi@gmail.com wrote:
> > Charles -
> >
> > I actually already had it set this way and provided a password. The
> > problem does still occur.
> >
> > thanks
> >
> > Charles Kangai wrote:
> > > Try changing the ProtectionLevel property of each package in BIDS from
> > > EncryptSensitiveWithUserKey to EncryptSensitiveWithPassword, then provide a
> > > password. See whether the problem occurs after this.
> > >
> > > Charles Kangai, MCT, MCDBA
> > > Author of Learning Tree's 4-day course: "SQL Server 2005 Integration
> > > Services" http://www.learningtree.com/courses/134.htm
> > > Author of Learning Tree's 4-day course: "SQL Server Reporting Services"
> > > http://www.learningtree.com/courses/523.htm
> > > email alias: charles
> > > email domain: kangai.demon.co.uk
> > >
> > >
> > >
> > >
> > > "bigbrorpi@gmail.com" wrote:
> > >
> > > > Hi -
> > > >
> > > > I've been having a problem with all of the packages I create. I create
> > > > them in BIDS on my local machine (which is running SSIS, as I
> > > > discovered that was needed for the packages to run properly on the
> > > > server). I then create an XML config file and deploy them to the file
> > > > system on the server.
> > > > For some reason (and I can't seem to pin down when this occurs), but
> > > > when I re-open the solution with the package in BIDS, I get a whole
> > > > slew of errors:
> > > > Changing the namespace of a variable failed because it is a system
> > > > variable. System variables are read-only. (Line 1 Column 1).
> > > >
> > > > I can't figure out what these are - it appears that my package somehow
> > > > gets corrupted.
> > > >
> > > > Does anybody know how to fix this?
> > > >
> > > > Thanks
> > > >
> > > >
>