May 6, 2009 at 7:44 am
Hi...
Under VS2005 I have several SSIS Packages with OLE DB Connections into our MS SQL databases, pretty basic stuff, and the Encryption Level of the packages are set at the default EncryptSensitiveWithUserKey.
Due to an issue with Windows I had to have my workstation reloaded (Win XP) and afterwards when I open the SSIS Packages all the OLE DB login info is removed, which is as expected since I'm now using a different profile. The catcher is even after I update the OLE DB information (username, password, server name, etc) and run the package from Designer it fails saying it can not log into the database. I can go into the Data Flow tab and Preview all the data in the steps it failed on, but if I save, close, then reopen the package it's like all the OLE DB info I entered in is gone. I know the passwords will not show, but even changing the Database Server name does not get saved.
So my first question, is there some key or file I can copy from my old profile into the new one to prove to VS2005 that I am the same user who created this package? Or is there anyway to get the package to recognize my new profile so I can make changes to the OLE DB Connections? Or do I have to delete the connections and start over?
Just checking. This is quite frustrating.
Thanks in advance for any suggestions...
Sam Alex
May 6, 2009 at 9:20 am
Hi,
Quick update... I just noticed this is also happening on ADO.NET:SQL Connections as well as OLEDB connections. I can edit the connection, save it, but whether I run it before closing or save and reopen it, it errors out saying the user has no access to the database. I have reentered the password and even changed the Database name to use our Test database instead of Production, but it keeps going back to Production when I save and reopen. I know the Encryption removes the Password, but is it supposed to also prevent editing the connectionstring or database name?
I then tried to delete and recreate the database connections, but of course each task goes by the ID and not the Name, and recreating them generates a new ID.
I'm at a loss... I guess I can create a new package and copy everything over, but it will only let me copy items one at a time, and with 40+ items this'll take a while and I don't even know if that'll work :-/
Any suggestions? Thanks---
Sam Alex
May 6, 2009 at 9:38 am
Resolved....
I found out what was happening... We keep all our Configuration files on the server, and this package was set to use a Configuration file which was overwriting what I manually entered in for the connections.
To fix I went into the Package properties under Configuration and unchecked 'Enable Package Configurations'. This then allowed my package to save and reopen with the appropriate settings.
I'm 99% sure this is fixed, but if I run into other problems I'll post incase someone else has the same issue.
Take care,
Sam Alex
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply