Installation Error with SQL Search 3.2

I tried with SQL Tool Belt and also with a standalone installation of Sql Search - same installation error:

Installation Summary
x 1 item could not be installed
* SQL Search 3.2
MSI returned failure code InstallFailure
Failed to open XML file D:\ManagementStudio\Extensions\SQLSearch\extension.vsixmanifest, system error: -2147024786


Any help?

Tagged:

Answers

  • thum_lotharthum_lothar Posts: 8 New member
    Additional information: while installation the directory D:\ManagementStudio\Extensions\SQLSearch is created.
    But I didn't give this path to the setup software.
  • Hi @thum_lothar

    Firstly, if you haven't installed the latest version of SQL Search please can you try this.  Here's the latest installer:
    ftp://support.red-gate.com/patches/SQLSearch/31May2019/SQLSearch.exe

    If the problem persists please can you run the installer and click the Redgate icon at the top left and use verbose logging? Then after reproducing the error, can you please attach a copy of the log file? 
    Kind regards

    Victoria Wiseman | Redgate Software
    Have you visited our Help Center?
  • thum_lotharthum_lothar Posts: 8 New member
    The latest release of SQL Search didn't bring any change.

    According to your advice I switched to verbose logging and I looked for a log file. As your online help says the file is in
    %ProgramData%\Red Gate\Shared Client\Log
    I found there file Client.2019-07-15.log, but the file seems not to be more verbose than the older files. And the file didn't change as I retried to install SQL Search a few times. This is the content:


    15 Jul 2019 08:58:55.315 [4] INFO  RedGate.Client.Service - Starting...
    15 Jul 2019 08:58:55.945 [4] INFO  RedGate.Client.PluginRunner.Runner - Autoupdate install directory set to: C:\Program Files (x86)\Common Files\Red Gate\Shared Client\
    15 Jul 2019 08:58:56.015 [4] INFO  RedGate.Client.PluginRunner.Runner - Found latest package at C:\Program Files (x86)\Common Files\Red Gate\Shared Client\RedGate.Client.PluginProvider.dll, file version 6.0.1.2182
    15 Jul 2019 08:58:56.015 [4] INFO  RedGate.Client.PluginRunner.Runner - Attempting to load RedGate.Client.Plugins.Common.IPluginProvider from package at C:\Program Files (x86)\Common Files\Red Gate\Shared Client\RedGate.Client.PluginProvider.dll
    15 Jul 2019 08:58:56.025 [4] INFO  RedGate.Client.PluginRunner.Runner - Successfully loaded RedGate.Client.Plugins.Common.IPluginProvider from package at C:\Program Files (x86)\Common Files\Red Gate\Shared Client\RedGate.Client.PluginProvider.dll
    15 Jul 2019 08:58:56.135 [4] INFO  RedGate.Client.PluginProvider.PluginProvider - Starting HTTP server at http://127.0.0.1:22223/
    15 Jul 2019 08:58:56.425 [4] INFO  RedGate.Client.PluginProvider.PluginProvider - Activation website hosted on port 22223
    15 Jul 2019 08:58:56.765 [4] INFO  RedGate.Client.PluginRunner.Runner - Marking package as known 'Good' at C:\Program Files (x86)\Common Files\Red Gate\Shared Client\RedGate.Client.PluginProvider.dll
    15 Jul 2019 08:58:56.765 [4] INFO  RedGate.Client.PluginRunner.Runner - Cleaning up packages earlier than version 6.0.1.2182
    15 Jul 2019 08:58:56.795 [4] INFO  RedGate.Client.PluginProvider.PluginProvider - IPC: Starting activation plugin IPC on 'RedgateClientIpc'
    15 Jul 2019 08:58:57.948 [4] INFO  RedGate.Client.PluginProvider.PluginProvider - ActivationEndpoint hosted at net.tcp://127.0.0.1:22222/activationplugin/
    15 Jul 2019 08:58:57.980 [4] INFO  RedGate.Client.PluginProvider.PluginProvider - IPC: Starting update plugin IPC on 'RedgateUpdateIpc'
    15 Jul 2019 08:58:57.980 [4] INFO  RedGate.Client.PluginProvider.PluginProvider - IPC: Starting notification plugin IPC on 'RedgateNotificationIpc'
    15 Jul 2019 08:58:57.995 [4] INFO  RedGate.Client.Service.ShellService - Starting HTTP server at http://127.0.0.1:22221/
    15 Jul 2019 08:58:58.136 [4] INFO  RedGate.Client.Service.ShellService - Redgate Client status page available at: http://127.0.0.1:22221/redgate/status
    15 Jul 2019 08:58:58.136 [4] INFO  RedGate.Client.Service - Started
    15 Jul 2019 09:08:56.246 [32] INFO  RedGate.Client.PluginRunner.Runner - Autoupdate install directory set to: C:\Program Files (x86)\Common Files\Red Gate\Shared Client\
    15 Jul 2019 09:08:56.246 [32] INFO  RedGate.Client.PluginRunner.Runner - Beginning check for updates
    15 Jul 2019 09:08:56.309 [4] INFO  RedGate.Client.PluginRunner.Runner - Checking the latest available version of Redgate Client
    15 Jul 2019 09:08:57.338 [4] WARN  RedGate.Client.PluginRunner.Runner - No updates for Redgate Client found.



  • thum_lotharthum_lothar Posts: 8 New member
    Sorry. Now I found the real log file in the menu of the setup.


  • Please can you browse to http://localhost:22221/redgate/status.html, select SQL Search under the 'recently connected products' section, and log in and activate through there?
    Kind regards

    Victoria Wiseman | Redgate Software
    Have you visited our Help Center?
  • thum_lotharthum_lothar Posts: 8 New member
    There are no connected products, see below in the screenshot.
    But I have a normal licence!?


  • Tianjiao_LiTianjiao_Li Posts: 684 Rose Gold 5
    edited July 15, 2019 2:50PM
    What's your SSMS version?

    Does the 'D:\ManagementStudio\Extensions\SQLSearch\extension.vsixmanifest' file exist? Can you please check if an antivirus has quarantined the file or is blocking access to it?
    Kind regards

    Tianjiao Li | Redgate Software
    Have you visited our Help Center?
  • thum_lotharthum_lothar Posts: 8 New member
    I have installed SSMS v17.9.1 and also v18.

    The file 'D:\ManagementStudio\Extensions\SQLSearch\extension.vsixmanifest' doesn't exist. It's in an empty directory that is been created while sql search is installing.

    We deactivated the antivirus software but the installation problem is yet there. I attached the new log file.

  • Can you please open the installer by running it as administrator
    · Click on the Redgate icon at the top left of the installer and choose "Open temporary file folder"
    · Open the SQL Prompt folder and locate the SQL Search_xxxx.msi file
    · Open a command prompt running as administrator and then run the following (making sure to change the temporary path and logfile location as needed): msiexec /i "c:\temporary\file\path\SQLSearch_SQL Search_xxxx.msi" ADDLOCAL=ALL /L*vx "c:\logfile.txt"

    Should it still fails, please attach the log again.
    Thanks.
    Kind regards

    Tianjiao Li | Redgate Software
    Have you visited our Help Center?
  • thum_lotharthum_lothar Posts: 8 New member
    I did it as explained, but it comes to the same result. The logfile is from the path c:\temp\logfile.txt.

    My installation call from dos prompt:
    -----------------------------------------------
    C:\Users\thuml.EDV\AppData\Local\Temp\{6BAA2C94-2B96-42F0-A934-10FD8247B081}\SQL
     Search>msiexec /i "C:\Users\thuml.EDV\AppData\Local\Temp\{6BAA2C94-2B96-42F0-A9
    34-10FD8247B081}\SQL Search\SQL Search_3.2.7.2379_x86.msi" ADDLOCAL=ALL /L*vx "c
    :\temp\logfile.txt"

    the result:
    ------------



  • Thanks for log again. I've run it past the development team and it looks like the SQL Search installer failed to detect the path where SSMS 2016 is installed, which it does by reading HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\130\Tools\ClientSetup.

    We think this means that SSMS is partially installed, hence can you try a repair or reinstall of SSMS?
    Kind regards

    Tianjiao Li | Redgate Software
    Have you visited our Help Center?
  • thum_lotharthum_lothar Posts: 8 New member
    I can see now that there is a problem in my sql server 2017 installation. Till now I don't know how to correct.
    I hope I can find a way.
    But thank you for your help.
Sign In or Register to comment.