April 24, 2007 at 5:33 am
When I start SSMS using "run as" another windows account, it messes up my own registered servers encrypted data
When I want to connect to a registered server, it first says it cannot decrypt the password data (System.Exception: CryptUnprotectData: Win32 error:-2146893813)
When I alter the password and save it, I cannot logon (same error) when I launch SSMS in a normay way.
Shouldn't the "run as" use another set of registered servers ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
April 24, 2007 at 12:20 pm
That is an odd one. I use "run as" almost daily and haven't run into an issue. I don't have encrypted data. Maybe that's the difference.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 25, 2007 at 2:39 am
This happens when using a sql-user. Not with Windows authentication.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply