November 22, 2013 at 9:13 am
SSMS
November 22, 2013 at 9:38 am
Have you typed the password out in a text editor and then copied and pasted it into the login window?
Are the SSMS the same version on both servers?
Same OS patch level?
Anything weird about character sets or localizations?
If you use the wrong password (on purpose) on the second server, do you see the failed login entry in the SQL Server error log?
November 24, 2013 at 11:14 pm
Yes
Yes
Yes and
No, character sets are same on both servers
I have also tried a incorrect password on the 2nd server and it threw out the same error in the alert log.
November 25, 2013 at 10:28 pm
Is there anyone with any more ideas/suggestions? Or anyone who has experienced this before?
Regards
November 27, 2013 at 12:58 am
Is it possible that registry entries could cause this? Or would reinstalling SSMS fix this? I don't want to try to many things as this is a live environment
November 27, 2013 at 3:02 am
Did you try to use sqlcmd or any other client tool apart from SSMS? do they work? any alias created for the sqlserver name?
November 27, 2013 at 3:21 am
Wow, I never thought of trying sqlcmd.
Strangely enough, I can connect to sa using sqlcmd
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply