SQL Compare locking SQL Accounts?

[AnthonyBaratta]

Howdy...

I upgraded to v10 a week or two ago and it works great with my local copy of MS SQL 2008. But when I connect to my client's MS SQL 2008 server the SQL Account (that worked flawlessly with v9) is being locked when I attempt to connect using SQL Compare v10.

I can login successfully with the SQL account via SQL Studio Manager "before" I connect with SQL Compare - but not after.

I've never seen this type of behaviour before. Version 9 and the same SQL Server and SQL Account have been working fine for months.

Any ideas? Anything you need from me to help debug this?

P.S. I don't have access to the SQL logs so I can't see if it's giving a reason for the lock. When I first had this issue the lock cleared by morning - but I have a software patch that is being held up because I can't do an SQL compare and sync the DBs.

[AnthonyBaratta]

Is it possible that SQL Compare is sending the password as it's being typed? I'm seeing the following in the SQL Logs when I type the SQL Account name:


01/12/2012 22:17:04,Logon,Unknown,Login failed for user 'sql_Account'. Reason: Could not find a login matching the name provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:04,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
01/12/2012 22:17:04,Logon,Unknown,Login failed for user 'sql_Accoun'. Reason: Could not find a login matching the name provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:04,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
01/12/2012 22:17:04,Logon,Unknown,Login failed for user 'sql_Accou'. Reason: Could not find a login matching the name provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:04,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
01/12/2012 22:17:03,Logon,Unknown,Login failed for user 'sql_Acco'. Reason: Could not find a login matching the name provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:03,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
01/12/2012 22:17:03,Logon,Unknown,Login failed for user 'sql_Acc'. Reason: Could not find a login matching the name provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:03,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
01/12/2012 22:17:03,Logon,Unknown,Login failed for user 'sql_Ac'. Reason: Could not find a login matching the name provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:03,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
01/12/2012 22:17:03,Logon,Unknown,Login failed for user 'sql_A'. Reason: Could not find a login matching the name provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:03,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
01/12/2012 22:17:03,Logon,Unknown,Login failed for user 'sql_'. Reason: Could not find a login matching the name provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:03,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
01/12/2012 22:17:02,Logon,Unknown,Login failed for user 'sql'. Reason: Could not find a login matching the name provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:02,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
01/12/2012 22:17:02,Logon,Unknown,Login failed for user 'sq'. Reason: Could not find a login matching the name provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:02,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
01/12/2012 22:17:02,Logon,Unknown,Login failed for user 's'. Reason: Could not find a login matching the name provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:02,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
01/12/2012 22:17:01,Logon,Unknown,Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 10.31.37.205]
01/12/2012 22:17:01,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 58.


Then when I type the password:


01/12/2012 22:17:10,Logon,Unknown,Login failed for user 'sql_Account'. Reason: Password did not match that for the login provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:10,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
01/12/2012 22:17:09,Logon,Unknown,Login failed for user 'sql_Account'. Reason: Password did not match that for the login provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:09,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
01/12/2012 22:17:09,Logon,Unknown,Login failed for user 'sql_Account'. Reason: Password did not match that for the login provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:09,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
01/12/2012 22:17:09,Logon,Unknown,Login failed for user 'sql_Account'. Reason: Password did not match that for the login provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:09,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
01/12/2012 22:17:09,Logon,Unknown,Login failed for user 'sql_Account'. Reason: Password did not match that for the login provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:09,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
01/12/2012 22:17:09,Logon,Unknown,Login failed for user 'sql_Account'. Reason: Password did not match that for the login provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:09,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
01/12/2012 22:17:08,Logon,Unknown,Login failed for user 'sql_Account'. Reason: Password did not match that for the login provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:08,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
01/12/2012 22:17:08,Logon,Unknown,Login failed for user 'sql_Account'. Reason: Password did not match that for the login provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:08,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
01/12/2012 22:17:07,Logon,Unknown,Login failed for user 'sql_Account'. Reason: Password did not match that for the login provided. [CLIENT: 10.31.37.205]
01/12/2012 22:17:07,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.


Then the SQL Account is locked because of too many failed attempts.

[alice.easey]

Hi Anthony,

Sorry you've run into this issue. We're looking into it now and will hopefully have a fix for this.

Will post here with any updates.

[ChrisDuncanMnx]

Hey, guys.

Thought I'd throw my two cents in as well. We're new to Redgate tools and I just installed last week at the office. Everything worked fine on the lan.

This weekend I tried to work from home being connected to the company over a vpn (my Internet connection is DSL, about 2.5 meg down, 650k up). Had the same lockout issues as others reported. Thinking it might be a timeout issue with multiple retries, I set long timeout but got the same results.

If I can be of any use as your guys debug just let me know. Happy to help as I may.
_________________
Christopher Duncan
Midnite Express

[AnthonyBaratta]

I did further testing with my local installation of SQL 2008 R2, and SQL Compare v10. I get the same behaviour as reported earlier with my client's MS SQL installation.

It's definitely SQL Compare v10, because I tested v9 and that did not exhibit the auto-checking behaviour.

[james.billings]

We have a patch available which should fix the problem reported here. You can obtain it via this FTP link

Please post back if you encounter further trouble, and thanks for your patience while we investigated.