  | 
			
				SoftTree Technologies 
				Technical Support Forums
			 | 
		 
		  | 
	 
	 
	
	
	
		
	
	
	
		| Author | 
		Message | 
	 
	
		
			seth.rothman 
			 
			
  
			
			
				Joined: 29 Jan 2008 Posts: 54 Country: United States | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				I don't see any errors upon launching SSMS.  Here are the entries in the log file:
 
 
8/6/2019 3:11:28 PM	Ssms.exe	Prefs: Attach
 
8/6/2019 3:11:28 PM	Ssms.exe	TargetList: SetSuspend=0
 
8/6/2019 3:11:28 PM	Ssms.exe	TargetList: Create: Rok=1
 
8/6/2019 3:11:28 PM	Ssms.exe	TargetList: EnumWnd (class=VsTextEditPane)
 
8/6/2019 3:11:28 PM	Ssms.exe	Client: Attach
 
8/6/2019 3:11:28 PM	Ssms.exe	Client: Create
 
8/6/2019 3:11:28 PM	Ssms.exe	Client: CreateTargetList
 
8/6/2019 3:11:28 PM	Ssms.exe	TargetList: SetSuspend=0
 
8/6/2019 3:11:28 PM	Ssms.exe	Client: SetCbtHook
  | 
			 
		  | 
	 
	
		| Tue Aug 06, 2019 3:12 pm | 
		          | 
	 
	
		  | 
	 
	
		
			SysOp 
			Site Admin 
			
  
			
			
				Joined: 26 Nov 2006 Posts: 7992
  | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				There is a good chance that you might be missing one or more Visual Studio assemblies that the add-on depends on, or they are installed, but not registered in the global assembly cache and so cannot be found preeventing add-on loading
 
 
Please download the assembly checker utility https://ci.appveyor.com/api/buildjobs/ly7ibc9mb9yo1mp2/artifacts/asmspy.1.3.103.zip  
 
Unzip it to C:\temp or other temporary location and then execute from the command line
 
"C:\temp\AsmSpy.exe" "C:\Program Files (x86)\SQL Assistant 11\bin\SqlAssist.vs.14.dll"
 
 
Please let us know if it outputs any assembly names in red which would refer to files not found. Please copy here the red part of the output.
  | 
			 
		  | 
	 
	
		| Wed Aug 07, 2019 12:01 am | 
		          | 
	 
	
		  | 
	 
	
		
			SergeyF 
			 
			
  
			
			
				Joined: 02 Aug 2019 Posts: 4 Country: Ukraine | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				I have the same problem. In the SSMS 18.2. There are no errors in the log file
 
 
2019-08-07 09:39:41	SqlAssist.exe	fmPrefs: Cancel
 
2019-08-07 09:39:41	SqlAssist.exe	fmPrefs: Release
 
2019-08-07 09:39:41	SqlAssist.exe	fmPrefs: Destroy
 
2019-08-07 09:39:47	SqlAssist.exe	Server: ShowPopup
 
2019-08-07 09:39:51	notepad++.exe	TargetList: SetSuspend=1
 
2019-08-07 09:39:51	Ssms.exe	TargetList: SetSuspend=1
 
2019-08-07 09:39:54	SqlAssist.exe	Server: ShowPopup
 
2019-08-07 09:40:00	notepad++.exe	TargetList: SetSuspend=0
 
2019-08-07 09:40:00	Ssms.exe	TargetList: SetSuspend=0
  | 
			 
		  | 
	 
	
		| Wed Aug 07, 2019 2:48 am | 
		          | 
	 
	
		  | 
	 
	
		
			SergeyF 
			 
			
  
			
			
				Joined: 02 Aug 2019 Posts: 4 Country: Ukraine | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				Check assemblies referenced in: C:\Program Files (x86)\SQL Assistant 11\bin\SqlAssist.vs.14.dll
 
 
Detailing only conflicting assembly references.
 
Reference: Microsoft.VisualStudio.CoreUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.CoreUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: NotFound
 
    14.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: Microsoft.VisualStudio.Editor, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.Editor, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: NotFound
 
    14.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: Microsoft.VisualStudio.Text.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.Text.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: NotFound
 
    14.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: Microsoft.VisualStudio.Text.UI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.Text.UI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: NotFound
 
    14.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: Microsoft.VisualStudio.Text.UI.Wpf, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.Text.UI.Wpf, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: NotFound
 
    14.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: Microsoft.VisualStudio.TextManager.Interop, Version=7.1.40304.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.TextManager.Interop, Version=7.1.40304.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: NotFound
 
    7.1.40304.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
  | 
			 
		  | 
	 
	
		| Wed Aug 07, 2019 2:53 am | 
		          | 
	 
	
		  | 
	 
	
		
			mgottvald 
			 
			
  
			
			
				Joined: 30 Jul 2019 Posts: 14 Country: Czech Republic | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				
	  | 
	
 
	  | 
	Thank you. Can I ask for a favor. and try the following troubleshooting steps
 
 
1.  Everybody who is having this issue, please run a search on your C drive to locate all instances of ComponentModelCache
 
Please let us know where you find them. Are there multiple copies? Where are they?
 
 
2. make sure you have all instances on SSMS and VS closed. Delete the found folders, After deleting open new Windows Explorer window and verify the folder(s) is/are actually gone. Windows UAC didn't restore them silently.
 
 
3. After SSMS restart, make sure you open new query tab. Do you see SQL Assistant in the right-click menu of that tab?   If yes, you are good. 
 
 
4. If no, locate the same folder again. In the folder find Microsoft.VisualStudio.Default.cache file and open it in Notepad
 
Search for "SqlAssist.vs.14.dll" string without quotes.  You should find something like below
 
 
	  | 
	
 
	  | 
	ation.dlliš–L¦3H *Ô/+Õ¬   CÚ;Microsoft.VisualStudio.Language.GenerateType.GenerateTypeUI   CÛCÜ<Microsoft.VisualStudio.Language.GenerateType.IGenerateTypeUICÕ CÕ   CÜCÕ@M     CÝCÞCßCàFSqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=nullCáGfile:///C:/Program Files (x86)/SQL Assistant 11/bin/SqlAssist.vs.14.dllfÆêzF¡C¶ì9šP‹Câ!SqlAssist.SqlAssistVSAddinFactory   CãCä?Microsoft.VisualStudio.Text.Editor.IWpfTextViewCreationListenerCÝ CÝ   Cä@c@TCåSQLCæT-SQL90CçPL/SQLCèSQL Server ToolsCéSQLCEA#@TCêDOCUMENTCëCì;Microsoft.VisualStudio.Text.Editor.AdornmentLayerDefinitionCÝCíCÝCîeditorAdornmentLayerCïA( Cì      CìA@TCðTextCñSqlAssistVSAddinA@TCòSelectionAndProvisionHighlightA#@TCêCóCìCÝCôCÝCõeditorAdornmentLayer2Cï   CìA@T CöSqlAssistVSAddin2A@TCðA#@TCêCÝ   C÷CÝCø
 
editorFactoryAYA_  
 
 | 
	 
 
 
 
If you didn't find it, there is a problem with the add-on registration  or the cache is corrupted for some reason (which is a fairly common case with Visual Studio, but not fatal)
 
If you find it, check the path referenced there. Does it point to C:/Program Files (x86)/SQL Assistant 11/bin/SqlAssist.vs.14.dll  or to some older version in a different folder?
 
 
Also check if there is a substring SqlAssistVSAddin referenced couple of lines below the path.
 
 
 
Lastly, just in case, you may want to see this one, that is for VS, but the same applies to SSMS which is based on VS Shell  http://hermit.no/how-to-fix-visual-studio-loading-errors-using-ifix/ | 
	 
 
 
 
1) Few copies in the old Visual studio and SQL management studio folders (these are already uninstalled - on my computer just now is VS2017, VS2019 and SSMS 18.2).
 
2) Done
 
3) Still not working.
 
4) I could find something similar in that file
 
	  | 
	
 
	  | 
	CŰCÜ<Microsoft.VisualStudio.Language.GenerateType.IGenerateTypeUICŐ CŐ   CÜCŐ@M     CÝCŢCßCŕFSqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=nullCáGfile:///C:/Program Files (x86)/SQL Assistant 11/bin/SqlAssist.vs.14.dllfĆęzFˇC¶ě9šP‹Câ!SqlAssist.SqlAssistVSAddinFactory   CăCä?Microsoft.VisualStudio.Text.Editor.IWpfTextViewCreationListenerCÝ CÝ   Cä@c@TCĺSQLCćT-SQL90CçPL/SQLCčSQL Server ToolsCéSQLCEA#@TCęDOCUMENTCëCě;Microsoft.VisualStudio.Text.Editor.AdornmentLayerDefinitionCÝCíCÝCîeditorAdornmentLayerCďA( Cě      CěA@TCđTextCńSqlAssistVSAddinA@TCňSelectionAndProvisionHighlightA#@TCęCóCěCÝCôCÝCőeditorAdornmentLayer2Cď   CěA@T CöSqlAssistVSAddin2A@TCđA#@TCęCÝ   C÷CÝCř | 
	 
 
 
The path is correct and the file exists.
 
SqlAssistVSAddin is referenced.
  | 
			 
		  | 
	 
	
		| Wed Aug 07, 2019 6:57 am | 
		          | 
	 
	
		  | 
	 
	
		
			mgottvald 
			 
			
  
			
			
				Joined: 30 Jul 2019 Posts: 14 Country: Czech Republic | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				
	  | 
	
 
	  | 
	There is a good chance that you might be missing one or more Visual Studio assemblies that the add-on depends on, or they are installed, but not registered in the global assembly cache and so cannot be found preeventing add-on loading
 
 
Please download the assembly checker utility https://ci.appveyor.com/api/buildjobs/ly7ibc9mb9yo1mp2/artifacts/asmspy.1.3.103.zip  
 
Unzip it to C:\temp or other temporary location and then execute from the command line
 
"C:\temp\AsmSpy.exe" "C:\Program Files (x86)\SQL Assistant 11\bin\SqlAssist.vs.14.dll"
 
 
Please let us know if it outputs any assembly names in red which would refer to files not found. Please copy here the red part of the output. | 
	 
 
 
 
Only yellow lines. Here is whole output:
 
 
	  | 
	
 
	  | 
	
 
 
d:\AAAA>AsmSpy.exe "C:\Program Files (x86)\SQL Assistant 11\bin\SqlAssist.vs.14.dll"
 
Check assemblies referenced in: C:\Program Files (x86)\SQL Assistant 11\bin\SqlAssist.vs.14.dll
 
Checking file SqlAssist.vs.14.dll
 
Checking reference mscorlib
 
Checking reference Microsoft.VisualStudio.Text.UI.Wpf
 
Checking reference Microsoft.VisualStudio.Editor
 
Checking reference PresentationFramework
 
Checking reference Microsoft.VisualStudio.Text.UI
 
Checking reference Microsoft.VisualStudio.Text.Data
 
Checking reference PresentationCore
 
Checking reference WindowsBase
 
Checking reference System.ComponentModel.Composition
 
Checking reference Microsoft.VisualStudio.CoreUtility
 
Checking reference WindowsFormsIntegration
 
Checking reference System.Windows.Forms
 
Checking reference System.Core
 
Checking reference Microsoft.VisualStudio.TextManager.Interop
 
Checking reference System.Drawing
 
Detailing only conflicting assembly references.
 
Reference: Microsoft.VisualStudio.CoreUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.CoreUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.CoreUtility\v4.0_14.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.CoreUtility.dll
 
    14.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: Microsoft.VisualStudio.Editor, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.Editor, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Editor\v4.0_14.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Editor.dll
 
    14.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: Microsoft.VisualStudio.Text.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.Text.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Text.Data\v4.0_14.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Text.Data.dll
 
    14.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: Microsoft.VisualStudio.Text.UI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.Text.UI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Text.UI\v4.0_14.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Text.UI.dll
 
    14.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: Microsoft.VisualStudio.Text.UI.Wpf, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.Text.UI.Wpf, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Text.UI.Wpf\v4.0_14.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Text.UI.Wpf.dll
 
    14.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: Microsoft.VisualStudio.TextManager.Interop, Version=7.1.40304.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  Microsoft.VisualStudio.TextManager.Interop, Version=7.1.40304.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\assembly\GAC\Microsoft.VisualStudio.TextManager.Interop\7.1.40304.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.TextManager.Interop.dll
 
    7.1.40304.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 
  mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 
Source: GlobalAssemblyCache, Location: C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib.dll
 
    4.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 
  PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_32\PresentationCore\v4.0_4.0.0.0__31bf3856ad364e35\PresentationCore.dll
 
    4.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 
  PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\PresentationFramework\v4.0_4.0.0.0__31bf3856ad364e35\PresentationFramework.dll
 
    4.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: System.ComponentModel.Composition, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 
  System.ComponentModel.Composition, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ComponentModel.Composition\v4.0_4.0.0.0__b77a5c561934e089\System.ComponentModel.Composition.dll
 
    4.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 
  System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
 
    4.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
  System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll
 
    4.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 
  System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll
 
    4.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: WindowsBase, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 
  WindowsBase, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\WindowsBase\v4.0_4.0.0.0__31bf3856ad364e35\WindowsBase.dll
 
    4.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 
Reference: WindowsFormsIntegration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 
  WindowsFormsIntegration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 
Source: GlobalAssemblyCache, Location: C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\WindowsFormsIntegration\v4.0_4.0.0.0__31bf3856ad364e35\WindowsFormsIntegration.dll
 
    4.0.0.0 by SqlAssist.vs.14, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
 
 | 
	 
 
  | 
			 
		  | 
	 
	
		| Wed Aug 07, 2019 7:00 am | 
		          | 
	 
	
		  | 
	 
	
		
			SysOp 
			Site Admin 
			
  
			
			
				Joined: 26 Nov 2006 Posts: 7992
  | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				Some users reported that the following super-easy fix worked for them.  Please start SSMS 18. Make sure SQL Assistant system tray application is running too.
 
In SSMS open new editor tab. Press Ctrl+Shift+F5. You should get SQL Assistant's target registration dialog on the screen. if required, change the settings, and click Ok to accept. Hopefully that does the magic and works for you too.
 
 
Please let us know if the above procedure helped you.
  | 
			 
		  | 
	 
	
		| Wed Aug 07, 2019 9:18 am | 
		          | 
	 
	
		  | 
	 
	
		
			SergeyF 
			 
			
  
			
			
				Joined: 02 Aug 2019 Posts: 4 Country: Ukraine | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				
	  | 
	
 
	  | 
	Some users reported that the following super-easy fix worked for them.  Please start SSMS 18. Make sure SQL Assistant system tray application is running too.
 
In SSMS open new editor tab. Press Ctrl+Shift+F5. You should get SQL Assistant's target registration dialog on the screen. if required, change the settings, and click Ok to accept. Hopefully that does the magic and works for you too.
 
 
Please let us know if the above procedure helped you. | 
	 
 
 
 
Not helped
  | 
			 
		  | 
	 
	
		| Wed Aug 07, 2019 10:10 am | 
		          | 
	 
	
		  | 
	 
	
		
			SysOp 
			Site Admin 
			
  
			
			
				Joined: 26 Nov 2006 Posts: 7992
  | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				One more step please.
 
 
In the options please rename "SQL Server Management Studio" target to  "MS Management Studio"
 
 
Hope this does the trick.
  | 
			 
		  | 
	 
	
		| Wed Aug 07, 2019 12:55 pm | 
		          | 
	 
	
		  | 
	 
	
		
			MarcinH 
			 
			
  
			
			
				Joined: 18 May 2019 Posts: 7 Country: Poland | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				Software:
 
Windows 7 SP1
 
SQL Assisant Pro 11.0.31
 
SQL Management Studio 2014, 2016, 17.9.1, 18.2
 
Don't have any Visual Studio edition
 
 
Tried:
 
Deleted temp, ComponentModelCache
 
Pressing Ctrl+Shift+F5 in SSMS 18.2 gives SQL Assisant warnig: Unsupported windows class (HwndWrappper[DefaultDomain;;eac SOME_LONG_GUID]). The OK button is grayed.
 
In SSMS 2014, 2016, 17.9.2 there was no error, SQL Assisant was registered but didn't work.
 
Finally renaming "SQL Server Management Studio" target to "MS Management Studio" in options helped for SSMS 2014, 2016, 17.9.2 but not for 18.2.
 
In SSMS 18.2 SQL Assisant still does not work in editor, however works in object explorer
 
 
In \AppData\Local\Microsoft\VisualStudio\ I have folders: 9.0, 11.0, 12.0, 13.0, 14.0, 15.0 but don't have any 16_
  | 
			 
		  | 
	 
	
		| Wed Aug 07, 2019 8:42 pm | 
		          | 
	 
	
		  | 
	 
	
		
			SysOp 
			Site Admin 
			
  
			
			
				Joined: 26 Nov 2006 Posts: 7992
  | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				Thank you very much for the detailed information.  After renaming the target to old name "MS Management Studio", can you please repeat the Ctrl+Shift+F9 step?   Do you still get  "Unsupported windows class" message in 18.2
  | 
			 
		  | 
	 
	
		| Thu Aug 08, 2019 12:04 am | 
		          | 
	 
	
		  | 
	 
	
		
			MarcinH 
			 
			
  
			
			
				Joined: 18 May 2019 Posts: 7 Country: Poland | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				You mean Ctrl+Shift+F5?
 
Yes, in 18.2 still the same warning message "Unsupported windows class"
 
 
Maybe Target Window Class "VsTextEditPane" is different in 18.x?
  | 
			 
		  | 
	 
	
		| Thu Aug 08, 2019 5:05 am | 
		          | 
	 
	
		  | 
	 
	
		
			mgottvald 
			 
			
  
			
			
				Joined: 30 Jul 2019 Posts: 14 Country: Czech Republic | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				Maybe I have some hints. When I use CTRL-SHIFT-F5 it shows SQL assist window but in all boxes is "None". When I have changed SQL Assistance to SQL server, it fills other choices automatically and SQL assist start to work in that actual pane in SSMS. When I open new window it stops work again and when I open SQL assist window it's None on everything again.
 
 
I am not sure where to change "SQL Server Management Studio" target to "MS Management Studio". Do you mean target title in Advanced Options? I have %Microsoft SQL Server% there. And my SSMS has "SQLQuery2.sql - MGOTTVALD.My DB (mgottvald) - Microsoft SQL Server Management Studio" title, which should be targeted. But when I click CTRL-SHIFT-F5 and switch to Advanced tab, Target title option is empty.
  | 
			 
		  | 
	 
	
		| Thu Aug 08, 2019 8:21 am | 
		          | 
	 
	
		  | 
	 
	
		
			SysOp 
			Site Admin 
			
  
			
			
				Joined: 26 Nov 2006 Posts: 7992
  | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				Please download the latest build 11.0.35 released yesterday. The setup in that build has been updated to correct the issues during the installation process. It should rename everything automatically. Hope that works for you.
  | 
			 
		  | 
	 
	
		| Thu Aug 08, 2019 11:19 am | 
		          | 
	 
	
		  | 
	 
	
		
			seth.rothman 
			 
			
  
			
			
				Joined: 29 Jan 2008 Posts: 54 Country: United States | 
			 
			  
		 | 
		
			
				   | 
				     | 
			 
			
				All good now with Build 35.  Appreciate the effort in troubleshooting.
  | 
			 
		  | 
	 
	
		| Thu Aug 08, 2019 5:29 pm | 
		          | 
	 
	
		  | 
	 
	
		 | 
	 
 
  
	 
	    
	   | 
	
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
  | 
   
 
		 | 
	 
	  |