February 2, 2015 at 5:28 pm
I recently attempted to change the password of the sa login. There were no issues while updating the password neither did I get an error when I logged in as sa. Everything appeared to connect and I was able to query a database. However, an error was logged (error 18456 severity 14 state 8) as though I did not log in successfully. Even though I can connect successfully, I don't like having these misleading errors in the SQL Server Log. Has anyone ever had this problem before?
February 2, 2015 at 9:56 pm
This was removed by the editor as SPAM
February 2, 2015 at 10:38 pm
I never faced this error. I tried changing password of sa and log in. Didn't logged any error
February 3, 2015 at 7:42 am
Do you get this error every time you login as sa?
If it was only at the point of password change, is it possible that a system or user process was running under sa at the exact moment that you changed the password and thus the credentials failed for that process resulting in the error.
February 3, 2015 at 7:48 am
Yes, it occurs every time I log in as sa. I have a query window open and select change selection. When I enter sa and the password the query window appears to connect and I can query the database. However, the error is generated that the password is incorrect. The IP address that is listed for the error is my computer so I know it's not a separate process.
February 11, 2015 at 10:37 am
Although I don't have a satisfactory explanation of "why", I have found one. I'm posting this in case anyone else has this same error and runs across this thread. So, I found two things...
1. A coworker tried the login and didn't get an error. We also did an nslookup on my IP address and found that it gets an error back from the active directory server. This IP issue could be unrelated. However, my coworker's successful attempt does show that there is something specific to the connection I had to the DB that was happening... which leads to #2...
2. I found that this only happens when I log in with the original password... and then change it... and then log in with the new password.
Perhaps there is some connection from my computer that is holding onto the first login? I'm not sure. I may research this later. But, for now, I have enough info about what is happening to keep moving past this error until I have extra time to look into it further.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply