SQL Search text box grayed out in SSMS 18.1

sql123sql123 Posts: 1 New member
in SQL Search
On latest SSMS 18.1 and SQL Search 3.2.7.2379. Can't search as search box is grayed out. A restart didn't help. Any ideas?
Tagged:
· Share on Twitter

Answers

  • Russell DRussell D Posts: 1,324 Diamond 5
    edited June 20, 2019 8:05AM
    We've had a few reports of this but never really gotten to the bottom of it. First thing to check though is that you're definitely connected to a database in the object explorer?
    If so you could try closing SSMS, and clearing out the %LocalAppData%\Red Gate\SQLSearch 3\Indexes folder, then reloading and trying again.
    Have you visited our Help Centre?
    · Share on Twitter
  • bauerjubauerju Posts: 33 Bronze 3
    Hi Russel D

    I have the same problem here, SSMS 18.1 , SQl Serach 3.2.7.2379.

    I opened SSMS via WIN-R with commandline server parameter  -> ssms -s servername
    Object explorer is open and connected to the server, A connected query window is also open. 
    When I now start sql search the input boxes are grayed out. I also tried to delete the appdata before. 

    When I now connect to a server (from connect on top of object explorer) then the textboxes get white and I can enter search strings.


    Jürgen

     
    · Share on Twitter
  • wuksawuksa Posts: 1 New member
    I also have a same problem. Refresh server in object explorer helps.
    · Share on Twitter
  • Russell DRussell D Posts: 1,324 Diamond 5
    If thats the case it suggests something is stalling in the connection on startup. But I still can't reproduce it in debugging so just can't find out where.
    Have you visited our Help Centre?
    · Share on Twitter
  • bauerjubauerju Posts: 33 Bronze 3
    Maybe Antivirus?
    I have Sophos Endpoint Security and Control installed. This slows down starting programms in an remarkable way.

    Jürgen
    · Share on Twitter
  • Russell DRussell D Posts: 1,324 Diamond 5
    It's entirely possible - we've certainly never tested it with any anti-virus program.
    Have you visited our Help Centre?
    · Share on Twitter
  • simoncsimonc Posts: 5 New member
    Me too:
    SQL Server Management Studio                     15.0.18131.0
    Microsoft Analysis Services Client Tools        15.0.1347.0
    Microsoft Data Access Components (MDAC)  10.0.18362.1
    Microsoft MSXML                                          3.0 6.0
    Microsoft Internet Explorer                           9.11.18362.0
    Microsoft .NET Framework                            4.0.30319.42000
    Operating System                                         10.0.18362
    SQL Search                                  3.3.0.2332

    AV: Eset Endpoint 7.1

    Restarting didn't always help.
    Clearing Indexes helped this time.

    Simon.
    · Share on Twitter
  • DarrenHarrisonDarrenHarrison Posts: 1 New member
    edited October 9, 2019 9:50PM
    For me, it happened after upgrading to SMSS 18.3.1. Restarting SSMS didn't help.
    Clearing out the index folder hasn't helped.

    SQL Server Management Studio 15.0.18183.0
    Microsoft Analysis Services Client Tools 15.0.1487.0
    Microsoft Data Access Components (MDAC) 10.0.14393.0
    Microsoft MSXML 3.0 6.0 
    Microsoft Internet Explorer 9.11.14393.0
    Microsoft .NET Framework 4.0.30319.42000
    Operating System 10.0.14393
    SQL Search 3.3.1.2410

    I can't see anything obvious in the logs.

    Uninstalling and reinstalling didn't help, SQL Search 2 & 3 folders were removed from %LocalAppData% after uninstall.

    · Share on Twitter
  • pmosebach_18pmosebach_18 Posts: 1 New member
    Think this is an issue with sql search 3.2... Issue resolved for me after updating to 3.4
    · Share on Twitter
  • simoncsimonc Posts: 5 New member
    Hello, still occasionally happens with SSMS 18.4 and Search 3.4.2.2567
    · Share on Twitter
  • MatthewWilkersonMatthewWilkerson Posts: 1 New member
    edited April 13, 2020 11:53AM
    This is now happening to me after upgrading to SSMS 18.5 and SQL Search 3.5.0.2590.  Disconnecting and reconnecting in Object Explorer fixes it for that session, but once SSMS is closed, it continues to happen when opening SSMS again.  If it helps, I only have SQL Prompt and SQL Search installed.
    · Share on Twitter
  • dUrosdUros Posts: 21 Bronze 1
    This is happening to me too. SSMS 18.5 and SQL Search 3.5.0.2590.
    Reconnected server in Object explorer help until SSMS is reopened.
    · Share on Twitter
  • grothaggrothag Posts: 3 Bronze 1
    Can I just report bug here. Ssms Search gets enabled by opening connection, but it seems it does not register that connections are already open on start ( by other plugins ). Can you please fix this, it is really annoying. Do not enable plugin on connection open, connections are already open, just check for connections or enable on default.
    · Share on Twitter
  • bauerjubauerju Posts: 33 Bronze 3
    Same problem here:
    Starting "SSMS"  with "-s dbserver" option results also in grayed search box. I need to close and reopen the connection before I'm able to use it.
    This is really anoying as I'm used to start always ssms with -s .

    SSMS 18.5 ( 15.0.1833.0)
    SqlSearch   3.5.0.2590
    · Share on Twitter
Sign In or Register to comment.