How can we help you today? How can we help you today?

SQL Prompt crashes SSMS 22.5.0

After installing SSMS 22.5.0 and connecting to a databaseserver, SSMS crashes. Probably caused by SQL Prompt, because the log contains:


1820 2026-04-15 12:01:42.783 +02:00 [Information] Logging level set to 'Information'
1820 2026-04-15 12:01:43.567 +02:00 [Information] Launching package entry point Ssms22 (version 22.5.11709.299) for SQL Prompt 11.3.10.22862.
1820 2026-04-15 12:01:43.615 +02:00 [Information] Initialising DTE and AddIn connections.
DTE.FullName: C:\Program Files\Microsoft SQL Server Management Studio 22\Release\Common7\IDE\SSMS.exe
DTE.Version: 18.0
DTE.CommandLine: 
Current culture: nl-NL
Current UI culture: en-US
1820 2026-04-15 12:01:46.352 +02:00 [Information] SqlPromptApplication initialised (startup took 0:00:00.001)
1820 2026-04-15 12:01:46.967 +02:00 [Information] Current license: Enabled = True, Activated = True, Supported = True, Features = BulkCodeAnalysis, BulkFormatting, CrossProductIntegration, PlatformSnippetSharing, PlatformStyleSharing
1820 2026-04-15 12:01:47.173 +02:00 [Information] Sql History initialized successfully
1820 2026-04-15 12:02:09.316 +02:00 [Error] Check for updates: Failure whilst attempting check for updates
[Outer exception] System.Net.WebException : The operation has timed out
  at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
  at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
  at RedGate.Update.Client.SoapUpdateServer.Check.CheckForUpdates(String xmlArgument, String& xmlResponse, String& errorMessage)
  at RedGate.Update.Client.UpdateServer.UpdateServer.CheckForUpdates(String serialNumber, Boolean automatic)
1820 2026-04-15 12:02:09.348 +02:00 [Error] Check for updates: Facade failure
[Outer exception] System.Net.WebException : The operation has timed out
  Server stack trace:
  at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
  at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
  at RedGate.Update.Client.SoapUpdateServer.Check.CheckForUpdates(String xmlArgument, String& xmlResponse, String& errorMessage)
  at RedGate.Update.Client.UpdateServer.UpdateServer.CheckForUpdates(String serialNumber, Boolean automatic)
  at RedGate.Update.Client.UpdateService.CheckForUpdatesStatic(IUpdateServer updateServer, IDownloadManager downloadManager, String serialNumber, Boolean automatic, DownloadProgress progress)
  at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
  at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
  Exception rethrown at [0]:
  at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
  at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
  at RedGate.Update.Client.UpdateService.Callback.EndInvoke(IAsyncResult result)
  at RedGate.Update.Client.UpdateFacade.CheckFinished(IAsyncResult ar)

Evert
2

Comments

4 comments

Sort by
  • Dave Kekish

    I have this issue as well, ended up uninstalling SQL Prompt and SSMS 22.5,   put 22.5 back on and its stable.The issue was SQL Prompt, which I miss dearly at this point.

    Dave Kekish
    0
  • John

    I urge people, if they rely on Red-Gate tools, to not upgrade SSMS to _any_ new release until you see each tool state that it supports the latest SSMS.

    I've gone through this so many times - upgrade, then break immediately. I've come to peace with the fact that I value my Red-Gate products working more than the very latest SSMS release, AND that they very rarely do they “just work” even for a minor point release in the SSMS world.

    John
    0
  • Erwin Richard

    Same issue here. Reverting to earlier SSMS fixed it for now.

    Erwin Richard
    0
  • veroslav.olic

    Hi, I confirm the issue. After installing the MS update promomed in SSMS, then Redgate Prompt starts crashing. Similar situation was after every recent MS update of SSMS. It's been pretty frustrating to solve it after every recent SSMS update and I wonder if alternatives (Apex, dbForge,…) are more stable in that sense?
     

    veroslav.olic
    0

Add comment

Please sign in to leave a comment.