SQL Prompt Installed issues

SmartFeiSmartFei Posts: 2 New member
edited June 17, 2018 3:30PM in SQL Prompt
I 'm trying too install SQL Prompt, but the progress bar hangs once it gets to "Service: Redgate Client". Eventually it returns this error:

Product: SQL Prompt 9 -- Error 1920. Service 'Redgate Client' (RedGateClient) failed to start. Verify that you have sufficient privileges to start system services.

My account is administrators,isuper power.
OS  win10 1803

The error has to do with starting the Redgate Client service. 
Can we provide an effective solution?

Tagged:

Answers

  • RichardLRichardL Posts: 417 Gold 4
    Hi @SmartFei

    Thanks for your post. 

    Below is the latest version if you haven't already installed this one. 
    ftp://support.red-gate.com/patches/SQLPrompt/13Jun2018/SQLPrompt_9.1.16.5356.exe

    Also, are you meeting the minimum system requirements for SQL Prompt? These are listed in the link below for you. 
    https://documentation.red-gate.com/sp9/requirements

    I hope this gets you up and running. 

    Kind regards

    Richard Lynch. 
    Customer Support
    Redgate Software
  • SmartFeiSmartFei Posts: 2 New member
    edited June 19, 2018 2:23PM

    yes, i have minimum system requirements for SQL Prompt.
    The os is .net Framework 4.7,

    I installed it with the latest version,still appear this issue.

    Product: SQL Prompt 9 -- Error 1920. Service 'Redgate Client' (RedGateClient) failed to start. Verify that you have sufficient privileges to start system services.




  • AAltemusAAltemus Posts: 2 New member
    I'm seeing the same.  Windows 10, .NET 4.7, SQL Server 2017, SQL Server Management Studio 2017. I've tried an uninstall and reinstall and still see the same thing. 
  • AAltemusAAltemus Posts: 2 New member
    I also verified that the 8.2 installer will install fine. 
  • RichardLRichardL Posts: 417 Gold 4
    Hi @AAltemus

    Thanks for your post. 

    It looks like the install is failing on the Redgate client service so could you try installing this by itself and then installing Prompt.

    The first thing you'll need to do is extract the .msi from the .exe

    There's instructions on how to do this through the link below:
    https://documentation.red-gate.com/xx/installing/installing-from-the-msi-file

    Once extracted could you then run through the following steps:

    Clear out the following directories:
    a. Clear all temp directories
    b. Clear C:\ProgramData\Downloaded Installations
    c. Clear C:\ProgramData\Red Gate
    d. Clear C:\Program Files (x86)\Common Files\Red Gate\Shared Client\

    Copy the extracted C:\Redgate installers\**Redgate Product**\Red Gate\Shared Client folder to C:\Program Files (x86)\Common Files\Red Gate\Shared Client\

    Add the service by running "C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe" "C:\Program Files (x86)\Common Files\Red Gate\Shared Client\RedGate.Client.Service.exe"

    Start the service manually and check http://127.0.0.1:22221/redgate/status to see if it shows you the Redgate Client page

    Start the installer as an administrator and rerun it.

    I hope this helps. 

    Kind regards

    Richard Lynch. 
    Customer Support
    Redgate Software
  • TheoLTheoL Posts: 17 Bronze 1
    I am now having the same symptom with update 9.4.7.7595.  "The bug is back!"
    Win 10 x64 - latest updates.
  • l_millerml_millerm Posts: 3 New member
    edited February 11, 2019 2:52PM
    I encountered this issue on my previous machine running Windows 7 and I've been fighting with this one for several hours after upgrading to Windows 10 1709 and ultimately I forgot what I did to get it to work... Frustrating!

    TL;DR:
    First run this from an elevated command/powershell terminal to see what's available:
    netsh http show iplisten
    If you don't have 127.0.0.1 and/or ::1 in there, then run these commands to add them:
    netsh http add iplisten 127.0.0.1
    Then try running the service and/or installing. 

    So, after taking a deeper look into the logs and trying to run several verions of RedGate.Client.Service.exe directly, looking at some OWIN & Windows networking docs I ended up trying a few netsh commands in an elevated cmd/powershell terminal and it worked!

    From the docs: Network shell (netsh) is a command-line utility that allows you to configure and display the status of various network communications server roles and components after they are installed on computers running Windows Server 2016. More specifically Netsh commands for HTTP context to query and configure HTTP.sys settings and parameters.

    So to do that, let's first run this to see what's available:
    netsh http show iplisten
    If you don't have 127.0.0.1 and/or ::1 in there, then run these commands to add them:
    netsh http add iplisten 127.0.0.1
    Then try running the service and/or installing.  This worked for me.

    @RedGate Support I would recommend updating the installer to check for this situation and add configure the network settings via netsh as needed.





  • l_millerml_millerm Posts: 3 New member
    I encountered this issue on my previous machine running Windows 7 and I've been fighting with this one for several hours after upgrading to Windows 10 1709 and ultimately I forgot what I did to get it to work... Frustrating!

    TL;DR:
    First run this to see what's available:
    netsh http show iplisten
    If you don't have 127.0.0.1 and/or ::1 in there, then run these commands to add them:
    netsh http add iplisten 127.0.0.1
    Then try running the service and/or installing. 

    So, after taking a deeper look into the logs and trying to run several verions of RedGate.Client.Service.exe directly, looking at some OWIN & Windows networking docs I ended up trying a few netsh commands in an elevated cmd/powershell terminal and it worked!

    From the docs: Network shell (netsh) is a command-line utility that allows you to configure and display the status of various network communications server roles and components after they are installed on computers running Windows Server 2016. More specifically Netsh commands for HTTP context to query and configure HTTP.sys settings and parameters.

    So to do that, let's first run this to see what's available:
    netsh http show iplisten
    If you don't have 127.0.0.1 and/or ::1 in there, then run these commands to add them:
    netsh http add iplisten 127.0.0.1
    Then try running the service and/or installing.  This worked for me.

    @RedGate Support, I would recommend that you check this configuration as part of the install process and adjust it accordingly.  I resolved this months ago and have lost a considerable amount of time and frustration trying to recall what I did to ultimately resolve the issue.





  • l_millerml_millerm Posts: 3 New member
    I encountered this issue on my previous machine running Windows 7 and I've been fighting with this one for several hours after upgrading to Windows 10 1709 and ultimately I forgot what I did to get it to work... Frustrating!

    TL;DR:
    First run this to see what's available:
    netsh http show iplisten
    If you don't have 127.0.0.1 and/or ::1 in there, then run these commands to add them:
    netsh http add iplisten 127.0.0.1
    Then try running the service and/or installing. 

    So, after taking a deeper look into the logs and trying to run several verions of RedGate.Client.Service.exe directly, looking at some OWIN & Windows networking docs I ended up trying a few netsh commands in an elevated cmd/powershell terminal and it worked!

    From the docs: Network shell (netsh) is a command-line utility that allows you to configure and display the status of various network communications server roles and components after they are installed on computers running Windows Server 2016. More specifically Netsh commands for HTTP context to query and configure HTTP.sys settings and parameters.

    So to do that, let's first run this to see what's available:
    netsh http show iplisten
    If you don't have 127.0.0.1 and/or ::1 in there, then run these commands to add them:
    netsh http add iplisten 127.0.0.1
    Then try running the service and/or installing.  This worked for me.

    @RedGate Support, I would recommend that you check this configuration as part of the install process and adjust it accordingly.  I resolved this months ago and have lost a considerable amount of time and frustration trying to recall what I did to ultimately resolve the issue.





Sign In or Register to comment.