Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Problem with SSIS Package Configurations and SQL Server Authentication Expand / Collapse
Author
Message
Posted Monday, December 9, 2013 7:19 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 10:06 AM
Points: 267, Visits: 597
SSIS on SQL Server 2008 R2

I am trying to get SSIS Package Configuration working with a conection using SQL Server Authentication instead of Windows Authentication. As far as I can see, this does not work.

Steps to recreate problem (using instance of SQL Server on my own machine):

1. in SSMS Create a new login "SQLAuth" with non-expiring password "SQLAuth"
2. in SSIS, create a new connection manager, LocalHost.SQLAuth pointing to the local server, using SQL Server authentication and the login "SQLAuth" I just created.
3. Entered the password "SQLAuth" and hit test connection. It worked. I check "Save Password" and click OK.
4. Drag and drop a new Execute SQL Task from the tool box to the design surfce.
5. Select the connection manager I just created in step 2 and enter the SQL Command "Select 1"
6. Save the new task and execute it. It executes fine.
7. Open my new connection manager again. The password is NOT saved! This in spite of the fact I checked "EncryptSensitiveWithUserKey" in the package properties. To confirm, hit Test Connection again. It fails!

Now, to test the package configurations:

8. Enter the password again and click Test Connection again. It works. Click OK.
9. Execute the task created above once more. It works
10. Open Package Configurations and set up a configuration for my new connection. Check the Server, Userid and Password boxes for the new connection for the properties to save.
11. Execute the task created above again. It fails with the message:
[Execute SQL Task] Error: Failed to acquire connection "LocalHost.SQLAuth". Connection may not be configured correctly or you may not have the right permissions on this connection.

12. Go back to the Package Configurations
13. Change my new config (from step 10) to save the the connection string.
14. Try the new task again. It fails the same way
15. Remove the new packagage config and retry. It works!

At this point, I've played with this for hours without success. Using a Package Configuration with SQL Server Authentication does not work, at least not for me
Post #1521080
Posted Monday, December 9, 2013 7:41 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Sunday, July 20, 2014 11:20 PM
Points: 13,252, Visits: 10,133
Step 7 is normal. Once you open the connection editor, the password is removed.

Which configuration did you use in step 10? Remember that the password is not saved to the configuration (if it would, it would be really use to hack that connection). You have to go to the configuration and replace ***** with the actual password.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1521088
Posted Monday, December 9, 2013 7:50 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 10:06 AM
Points: 267, Visits: 597
Koen Verbeeck (12/9/2013)
Step 7 is normal. Once you open the connection editor, the password is removed.

Which configuration did you use in step 10? Remember that the password is not saved to the configuration (if it would, it would be really use to hack that connection). You have to go to the configuration and replace ***** with the actual password.


Which config? The one I set up for my test. However, your comment

"Remember that the password is not saved to the configuration...You have to go to the configuration and replace ***** with the actual password"

Was an eye-opener. In all the reading and googling I had done to this point, I never saw that simple requirement.
Post #1521097
Posted Monday, December 9, 2013 1:27 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Sunday, July 20, 2014 11:20 PM
Points: 13,252, Visits: 10,133
Gerald.Britton 28181 (12/9/2013)
Koen Verbeeck (12/9/2013)
Step 7 is normal. Once you open the connection editor, the password is removed.

Which configuration did you use in step 10? Remember that the password is not saved to the configuration (if it would, it would be really use to hack that connection). You have to go to the configuration and replace ***** with the actual password.


Which config? The one I set up for my test.


Allo me to rephrase: which type of config? XML, SQL Server config table?




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1521289
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse