We help IT Professionals succeed at work.

Logging in as SQL's "sa" Fails on the First Attempt but Not on the Second

102 Views
Last Modified: 2016-09-05
Hello:

This experience that I had, yesterday, simply peaked my curiosity.  So, I thought that I would ask you all.

Yesterday, our DBA changed a SQL instance's "sa" password.  

In addition, we have an app that utilizes an ODBC connection to connect to this SQL instance.  The ODBC connection, though, was not configured with "sa" as the user ID.  

In any case, we have this app installed on three Terminal Server boxes.

After this password change, I attempted to login to the app as "sa" on all three boxes.  

The very first attempt on each box failed but not the second.

True, it's possible that I may have simply typed the new password incorrectly, during the first attempt on each box.  

But, I'm not so sure that that's the case.  It just really seems odd to me that, after an "sa" password change, the first attempt on three Terminal Server boxes fails but not on the second attempt.

This seems more than just a simple case of a mistyped password or coincidence.  Again, though, what do you all think?

John
Comment
Watch Question

"Batchelor", Developer and EE Topic Advisor
CERTIFIED EXPERT
Top Expert 2015
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Hi There, Qlemo:

Thank you, so much, for the quick response.

I'm sorry.  But, can you please tell me what you meant by, "Probably the old password has been provided instead of the one you entered. "?

Thanks, again!

John
Qlemo"Batchelor", Developer and EE Topic Advisor
CERTIFIED EXPERT
Top Expert 2015

Commented:
As said, the app might be the culprit - using the old password first, then replacing it with the new one. An application bug.
Mark WillsTopic Advisor, Page Editor
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
Qlemo is probably correct, a caching issue. It can also be caused by your authentication mode and a confused SQL Server as to who you really are. SQL will store user and (hashed) password in Master database and try to match that with SQL login (windows authentication). Basically the user always needs to be associated with a trusted connection. It would normally throw an error message, and would need to see that.

If it was a once off problem, I wouldn't worry too much. But if it is happening often enough, then you will need to resolve properly.

Here is a MS Support link (so, you aren't the only one) describing a possible fix... https://support.microsoft.com/en-au/kb/2121736 also check (this newer one, and describes better with links and error message explanations) https://support.microsoft.com/en-us/kb/555332

To fully diagnose the problem we would need a lot more information from you...
Mark WillsTopic Advisor, Page Editor
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
John,

How are you going with this ? Havent heard from you in a while... Would be interested to hear of any developments.

Author

Commented:
Hi Mark:

I was just waiting to see, if I received other opinions.  It sound like, based on what you all are saying though, the password was simply cached--either in SQL or the app that I was using.

John
Mark WillsTopic Advisor, Page Editor
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
Fair enough...

Just curious, what authentication mode are you using ?

Author

Commented:
Our SQL uses Mixed Mode Authentication.

John
Vitor Montalv√£oIT Engineer
CERTIFIED EXPERT
Distinguished Expert 2017

Commented:
Old question but seems not any comment marked as solution.

John, do you remember the error thrown by the first attempt?
Mark WillsTopic Advisor, Page Editor
CERTIFIED EXPERT
Distinguished Expert 2018

Commented:
Sounds like Qlemo had the right answer...
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.