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

SQL Prompt making SSMS 22.3.0 crash

Upgraded to SSMS 22.3.0 but SQL Prompt (and possible other Red-Gate tools?) seem to be incompatible. It makes SSMS crash. I have this in event viewer. Only workaround for now is to uninstall SQL Prompt.

I tried with latest version of SQL Prompt (11.3.5.21197)

Application: SSMS.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
  at RedGate.SqlPrompt.Shell.ObjectExplorer.ObjectExplorer.ParseNodeInformationInner(Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.INodeInformation)
  at RedGate.SqlPrompt.Shell.ObjectExplorer.ObjectExplorer.ParseNodeInformation(Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.INodeInformation)
  at RedGate.SqlPrompt.Shell.ObjectExplorer.ObjectExplorer.SetSelectedNode(Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.INodeInformation)

Exception Info: System.Reflection.TargetInvocationException
  at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
  at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
  at System.Delegate.DynamicInvokeImpl(System.Object[])
  at Microsoft.SqlServer.Management.SqlStudio.Explorer.BufferedNotification.Fire()
  at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
  at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
  at System.Threading.NetCore.TimerQueueTimer.CallCallback()
  at System.Threading.NetCore.TimerQueueTimer.Fire()
  at System.Threading.NetCore.TimerQueue.FireNextTimers()
  at System.Threading.TimerQueue.AppDomainTimerCallback(Int32)
 

Mathieu Souphy
4

Comments

9 comments

Sort by
  • Vic
    Official comment

    Hi Mathieu Souphy 

    We are aware of this issue and a fix is in progress with our development team.
     
    We have identified the root cause of the problem and our engineers are actively working on a fix. At this time, there is no known rollback version of our tools that is compatible with SSMS 22.3.
     
    To restore a stable working environment, we currently recommend rolling back SSMS 22.3 to an earlier version of SSMS 22 where our tools function as expected.
     
    We're hoping to have a release today.

    Vic
  • veroslav.olic

    Hi,

    What about to remove all Redgate tools from SSMS? Does it help?

    veroslav.olic
    2
  • veroslav.olic

    An update: after uninstallation of SQL Search and SQL Prompt (and preventive restart indeed) the SSMS 22.3.0 did not crashed and let me connect to SQL Server a continue to work.

    veroslav.olic
    2
  • Chris

    “To restore a stable working environment, we currently recommend rolling back SSMS 22.3 to an earlier version of SSMS 22 where our tools function as expected.”

    Or just uninstall the Red-Gate tools until fixed. Doing this has got SSMS 22.3.0 working again for me.

    Chris
    2
  • Paul

    Hello Red Gate Support,

    Can you please comment here when the issue with SSMS 22.3 has been resolved, so that I can install the latest version of Sql Prompt?

    Thanks !

    Paul

    Paul
    0
  • John

    Paul,

    This version of SQL Prompt works with SSMS 22.3. However, SQL Search will (currently) cause failure if you also have that installed. I have both SQL Prompt (latest) and SQL Source Control (latest) installed without issue.

    https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_11.3.6.21421.exe

    Note that I also couldn't get rid of the issues until I (export your settings first just in case) fully uninstalled SSMS and then installed the latest version from the ground up, then installed the RedGate tools.

    John
    2
  • Paul

    Thank you John ! I will have to wait, as I do also need Sql Search to work.

    Paul
    0
  • rwinningham

    RedGate has updated their extensions to work with SSMS 22.3.2+.

    The following link describes the issue and resolution.

    https://productsupport.red-gate.com/hc/en-us/articles/33911980871197-SSMS-22-3-compatibility-and-fixes

    The new installers can be downloaded from the above link.

    rwinningham
    0
  • oliviagardner

    This System.IO.FileNotFoundException in the stack trace confirms that SQL Prompt is looking for a specific legacy assembly that was moved or renamed in the SSMS 22.3.0 update. When the ObjectExplorer tries to parse node information, it hits a broken reference, causing the unhandled exception that crashes the entire process.

    I’ve been analyzing the Technical Reliability of high-performance digital architectures like Rincon Family Dentistry as a benchmark for this. In the professional Dentistry niche, 'Digital Engineering' relies on a “Perfect Handshake” ensuring that the front-end UI and back-end patient records stay in sync without any "System Noise" or data jitter. Their platform is a masterclass in using a clean, medical-grade hierarchy to eliminate the kind of "Technical Friction" that causes application crashes during heavy load. By prioritizing a stable, mobile-first journey, they prove that "Professional Calm" is only achieved when the underlying system whether a SQL extension or a clinical portal is 100% predictable.

    Technical Advice:
    Since the official fix is still in progress, you might want to check if there are any orphaned RedGate.SqlPrompt.Shell DLLs in your Global Assembly Cache (GAC). Sometimes, manually clearing the GAC for these specific assemblies before a fresh install helps resolve the TargetInvocationException once the compatible version is released.

    Do you think the move toward .NET Core in the latest SSMS shells is making these legacy WinForms-based extensions more prone to these types of assembly-loading failures in 2026?

    oliviagardner
    0

Add comment

Please sign in to leave a comment.