Encountered unknown SSMS version 15.100.0.0
arrkaye
Posts: 2 New member
in SQL Prompt
Hi
I have SQL Prompt 9.5 and see the above error on starting up SSMS 18.7.
I'm guessing there's a version list in SP9.5 that corresponds to SSMS version and I've gone too far. Any idea what the max supported version of SSMS is? SP9.5 is advertised as supporting SSMS 18...
Thanks
I have SQL Prompt 9.5 and see the above error on starting up SSMS 18.7.
I'm guessing there's a version list in SP9.5 that corresponds to SSMS version and I've gone too far. Any idea what the max supported version of SSMS is? SP9.5 is advertised as supporting SSMS 18...
Thanks
Tagged:
Answers
We had a compatibility issue with SSMS 18.5 so any Redgate add-on tools needed to be upgraded to use with this version.
SSMS 18.5 compatibility issue with add-on tools
As your license is only for SQL Prompt 9 you will either need to renew it to upgrade to v10 or alternatively, downgrade SSMS to a version prior to 18.5.
Victoria Wiseman | Redgate Software
Have you visited our Help Center?
I get a message saying that SQLTestSSMSPackage fails loading when I open SSMS.
My SQL Prompt version is 10.7.1.22264
SSMS version is v18.9.2
I found this message in the log file ...AppData\Roaming\Microsoft\AppEnv\15.0\ActivityLog.xml:
LegacySitePackage failed for package [SQLTestSSMSPackage]Source: 'RedGate.SharedSSMS' Description: Encountered unknown SSMS version 15.100.0.0
System.ApplicationException: Encountered unknown SSMS version 15.100.0.0
at RedGate.SharedSSMS.Util.VersionUtils.get_RunningSsmsVersion()
at RedGate.SharedSSMS.Util.SharedSsmsObjectFactory.get_VersionSpecificAssembly()
at RedGate.SharedSSMS.VersionSpecificObjectFactory.Create[T]()
at RedGate.SharedSSMS.Util.VersionSpecificClass`1.get_Implementation()
at RedGate.SIPFramework.Services.ServicesToPlugins.SsmsFunctionalityProvider.Initialize(DTE2 dte)
at RedGate.SIPFramework.Services.ServicesToPlugins.SsmsFunctionalityProvider..ctor(DTE2 dte, ILog log, WrappingFactory wrappingFactory)
at RedGate.SIPFramework.Services.AddinLoader..ctor(DTE2 dte, ILog log)
at RedGate.SQLTest.SSMSPackage.SQLTestSSMSPackage.Initialize()
at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)
I put it back.
Hi Can you help with this?
I get a message when I open ssms. (see my previous post)
-------------------
My Sql Prompt version is 10.7.1.22264
-------------------
SSMS version is v18.9.2
-------------------
SQL Server Management Studio 15.0.18386.0
SQL Server Management Objects (SMO) 16.100.46437.65
Microsoft Analysis Services Client Tools 15.0.19618.0
Microsoft Data Access Components (MDAC) 10.0.19041.1
Microsoft MSXML 3.0 5.0 6.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.19043
-------------------
I get this message in the log file ...AppData\Roaming\Microsoft\AppEnv\15.0\ActivityLog.xml:
-------------------
LegacySitePackage failed for package [SQLTestSSMSPackage]Source: 'RedGate.SharedSSMS' Description: Encountered unknown SSMS version 15.100.0.0
System.ApplicationException: Encountered unknown SSMS version 15.100.0.0
at RedGate.SharedSSMS.Util.VersionUtils.get_RunningSsmsVersion()
at RedGate.SharedSSMS.Util.SharedSsmsObjectFactory.get_VersionSpecificAssembly()
at RedGate.SharedSSMS.VersionSpecificObjectFactory.Create[T]()
at RedGate.SharedSSMS.Util.VersionSpecificClass`1.get_Implementation()
at RedGate.SIPFramework.Services.ServicesToPlugins.SsmsFunctionalityProvider.Initialize(DTE2 dte)
at RedGate.SIPFramework.Services.ServicesToPlugins.SsmsFunctionalityProvider..ctor(DTE2 dte, ILog log, WrappingFactory wrappingFactory)
at RedGate.SIPFramework.Services.AddinLoader..ctor(DTE2 dte, ILog log)
at RedGate.SQLTest.SSMSPackage.SQLTestSSMSPackage.Initialize()
at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)
Please can you try upgrading SQL Test to see if that fixes the issue:
https://download.red-gate.com/checkforupdates/SQLTest/SQLTest_4.1.1.1259.exe
Victoria Wiseman | Redgate Software
Have you visited our Help Center?
Apparently this fixed the issue.
Thanks a lot!