Showing posts with label mode. Show all posts
Showing posts with label mode. Show all posts

Friday, March 23, 2012

Failed to decrypt protected XML node

Failed to decrypt protected XML node ... blah blah.

Looks familiar, right?

Package Protection mode is : EncryptSensitiveWithPassword

Package runs fine from within BIDS. Close package. Open package - asks for password. So far so good.

When running from command prompt with:

dtexec /File "C:\Program Files\Microsoft SQL Server\90\DTS\Packages\MyPackage.dtsx" /De mypassword

Get that cryptography error.

Doesn't happen for other packages... what can I be doing different/wrong?

Thanks,
NiteshDoes your password contains any of the following:
a) space characters - use the format /De "your_password"
b) punctuation characters - use the format /De "your_password"
c) " - double any "
d) ; - use the format /De "\"your_password\""

Hope this helps

Regards,
Ovidiu Burlacu|||

Ovidiu Burlacu wrote:

Does your password contains any of the following:
a) space characters - use the format /De "your_password"
b) punctuation characters - use the format /De "your_password"
c) " - double any "
d) ; - use the format /De "\"your_password\""

Hope this helps

Regards,
Ovidiu Burlacu

Nopes.
Password is same as that for other packages, all lowercase alphabets, 8 characters.

thanks,
Nitesh|||

Since your protection is only EncryptSensitiveWithPassword then only sensitive information will be encrypted, and my guess is that this package has been encrypted with a different password (mistyping).

Can you try to open package in BIDS and then go to View -> Error List and see if the same error has been posted?

I'm guessing that the same error happens in the designer, but we should not fail open the package just because we cannot retrieve the Password in a ConnectionString, so instead we post an error.

HTH,
Ovidiu Burlacu

Monday, March 12, 2012

Failed Connected to Sql 2005 Enterprise Edition

Hi,

We have a Sql 2005 server. It was setup by out network administrators who do not know much about sql server. It's running on Mixed Mode (Sql Server & Windows Authentication Mode). I have been able to connect to it use Integrated Security. However, I have not been able to connect to it using an username and a password. I have tried with sql accounts and windows accounts. Out of frustration, I used sql administrator account and windows domain administrator accounts. I also tried using the account the sql server is running on. But each and every time, I failed and received the following error message:

Login failed for user '<<User Name>>'. The user is not associated with a trusted SQL Server connection.

I have also changed my connection string many times, but it doesn't matter. And I have been able to connect to our Sql 2000 servers successfully.

Please help!!

Pak

The error message indicates that you are only using WIndows authentication. After switching to Mixed Auth., did you restart the service ? do have eventually have multiple instances on the machine and you are connecting to the wrong database ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

its looks like still in Windows Authentication. Check that first. ALso if it is a named instance of sql server 2005 you need to start SQL browser Server or Mention the Port in connection string

Check this.

http://madhuottapalam.blogspot.com/2007/01/sql-browser-service-in-sql-2005.html

|||

Jens and Madhu:


Thanks for your help. You are 100% correct. It turned out that one of our developers change the authentication mode to mix mode without restarting SQL server.

Pak