Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
shank
Starting Member
6 Posts |
 Posted - 2007-09-08 : 18:12:13
|
| I'm having an issue with an SSIS package. It supposed to run on a schedule and pull data from one server (SQL1) to another (SQL2). Unfortunately, I'm using a shared server and I'm not that admin. So I'm limited to what I can try. According to the admin, my package is not retaining the password when I build it. It runs fine in debug mode on my machine, but will not run on his. I found this link...http://vyaskn.tripod.com/sql_server_2005_making_ssis_packages_portable.htm... and tried it. It describes how to create an XML for validation. Still no good. He sent a screenshot indicating error code: DTS_E_CANNOTACQUIRECONNECTION and OLE DB Source failed validation. In effect, login failed for SQL1 and it could not pull data.How do I get the package to retain login data?thanks! |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-09-08 : 19:17:12
|
| Possible to use windows authentication? |
 |
|
|
shank
Starting Member
6 Posts |
Posted - 2007-09-08 : 19:36:04
|
| No. It's not my server. It's a shared server controlled by the host. |
|
|
|
igorblackbelt
Constraint Violating Yak Guru
407 Posts |
Posted - 2007-09-11 : 16:10:17
|
| What type of protection level are you using, when saving your packages to the server? |
|
|
|
shank
Starting Member
6 Posts |
Posted - 2007-09-11 : 16:23:43
|
I was using: EncryptSensistiveWithUserKeyNow I'm trying: EncryptAllWithPasswordI found the below in another forum. Without being admin, it's taking me 24 hours to figure out what works and what doesn't. Working wirth shared servers is cheap, but not too handy.thanks quote:
The standard security on an SSIS package is "EncryptSensistiveWithUserKey" which only allows the user that created it to be able to run in as long as there is sensitive information (passwords) stored within the package.A workaround that I am using is that I changed the package security to "EncryptAllWithPassword" which protects the entire package with a password. When you set the package as a job step, go into the properties of that job step, click on the "Command Line" tab and you should be prompted for the password. After you enter the password, the /DECRYPT switch should show up in the command line and the job should then be able to run under a different user.
|
|
|
|
|
|
|
save password in SSIS