Activity overview
Latest activity by dmans1
Hi @Jessica R
Yes, both options are disabled as per previous suggestion. Let me point out that locking also occurs when i disable Sql prompt code suggestions from SqlPrompt-Options-Behaviour-Show code suggestions and
SqlPrompt-Options-Connections-Only load suggestions for certain databases (with an empty liist), and the 2 checkboxes above unchecked. / comments
Hi @Jessica R
Yes, both options are disabled as per previous suggestion. Let me point out that locking also occurs when i disable Sql prompt code suggestions from SqlPrompt-Options-Behaviour-Show c...
Hi @Jessica R ,
Following up the other post , I have no other, non RedGate, ssms related plugins. To test the plugins indivirually, i uninstalled all the software, downloaded the latest developers pack (sql prompt pro 9, ssms integration pack 1.6) and started installing them individually, monitoring my bad password count with an ldap tool.
I have not come to a definite conclusion, but what is certain, is that with SSMS integration pack or sql prompt installed, when the ssms starts, the bad password count starts going up. [image]
Sometimes that count stays at 2, sometimes it goes up to 3 or above(AD account gets locked on 3 wrong attempts, so I cannot know how more above 3 that number goes) / comments
Hi @Jessica R ,
Following up the other post , I have no other, non RedGate, ssms related plugins. To test the plugins indivirually, i uninstalled all the software, downloaded the latest developers ...
Sadly, that's not the case. I unchecked everything and i still get lockouts.
Might be a hint that the lock occurs immediately after ssms is opened, even if no connection to any database is opened. [image] / comments
Sadly, that's not the case. I unchecked everything and i still get lockouts.
Might be a hint that the lock occurs immediately after ssms is opened, even if no connection to any database is opened.
Hi @Jessica R ,
My connection settings are: [image]
I tried consecutively,
Unchecking "Enable tab history"
Checking "Enable Tab History" ,unchecking "Restore open tabs when SSMS starts",unchecking "automatically reconnect restored tabs"
Deleting appdata/local/redgate/sql prompt 8/savedTabs.db (also deleted sql prompt 6,7 directories on that folder level since history seemed to be rebuild on start from the old databases)
, with no sucess [image] / comments
Hi @Jessica R ,
My connection settings are:
I tried consecutively,
Unchecking "Enable tab history"
Checking "Enable Tab History" ,unchecking "Restore open tabs when SSMS starts",unchecking "automa...
Hi @Jessica R
I confirm, I am getting account Lockouts without the errors mentioned in the OP.
I mentioned the redgate client part in my previous post, as when SSMS is misconfigured and sql prompt cannot communicate with the redgate client (see the nolock logs and the screenshot), I do not get any account lockouts at all. [image]
When everything is configured "as it should" (lock logs) I get immediate account lockouts after starting SSMS. I have also noticed recently that i also get account lockouts if SSMS is running and I log on to my station via remote Desktop / comments
Hi @Jessica R
I confirm, I am getting account Lockouts without the errors mentioned in the OP.
I mentioned the redgate client part in my previous post, as when SSMS is misconfigured and sql prompt ...
Hi @Jessica R
Sadly, my "success" was due to making the following error in the config
<settings>
<defaultProxy useDefaultCredentials="true"/>
<ipv6 enabled="true"/>
</settings>
(default proxy element wrongly
placed inside the settings) which resulted in the below error [image]
Once correcting my error, the problem reappeared.
That mistake made absolutely clear to me what caused the issue. It is the redgate client service that proxies the licensing requests (made from Sql Prompt, and any other product that uses the new licensing proplem)to you that is causing this.
So, I added the following section in the configuration section of the C:\Program Files (x86)\Common Files\Red Gate\Shared Client\RedGate.Client.Service.exe.config file
<system.net>
<defaultProxy useDefaultCredentials="true"/>
</system.net>
,restarted the service... and problem solved!!!
*Edit: The issue still seems to exist, I got locked some minutes after opening Management studio, still think that this is a redgate client issue
*Edit2: Still back to square one. I opened sql compare, data compare, but no account locking exists, account gets locked only with management studio/Sql prompt 8. The really weird thing is that the locking occurs when management studio 17.3,2016, VS2013 open but not on VS2010. / comments
Hi @Jessica R
Sadly, my "success" was due to making the following error in the config
<settings>
<defaultProxy useDefaultCredentials="true"/>
<ipv6 enabled="true"/>
</settings>
(default proxy elem...
Hi @Jessica R
I did modify the ssms config file, and there is an OMG moment for me. The AD locking account no longer occurs after starting SSMS. So I suppose SQL prompt uses the exe's config to do it's network stuff.
A nice thing to do in a future release (since I can only suppose this will happen in all users that use a proxy) would be to override this part an progammaticaly make use of the useDefaultCredentials value.
Anyway, thanks for the support and keep up the good Work!! / comments
Hi @Jessica R
I did modify the ssms config file, and there is an OMG moment for me. The AD locking account no longer occurs after starting SSMS. So I suppose SQL prompt uses the exe's config to do...
Hi @Jessica R
The UniversalAuthenticationAccessTokenCache [(null)] is gone with the latest version (8.2.5.2924) but the account locking still exists. [image]
I have attached verbose logs from management studio startup. resulting in AD account lockout (SSMS 17.3 and windows 10x64 Enteprise V.1709) / comments
Hi @Jessica R
The UniversalAuthenticationAccessTokenCache [(null)] is gone with the latest version (8.2.5.2924) but the account locking still exists.
I have attached verbose logs from management s...
Might the message be relevant with this issue? / comments
Might the message be relevant with this issue?
Sql Prompt locks AD accounts
Recently we upgraded to Sql prompt 8 (8.1.0.2354) and we noticed that AD user accounts were being frequently locked for no apparent reason (users do not enter AD credentials anywhere).
The account...