SQLSearchSSMSPackage Not Loading Correctly
ShuttleBILL
Posts: 3 Bronze 1
in SQL Prompt
I've been getting this for a while now. The XLM referenced looks like this:
<entry>
<record>316</record>
<time>2020/06/11 18:57:35.553</time>
<type>Warning</type>
<source>VisualStudio</source>
<description>Unexpected system error mode before loading package [SQLSearchSsmsPackage]</description>
<guid>{26218D92-039D-466C-BF66-EAE1098379BE}</guid>
</entry>
<entry>
<record>317</record>
<time>2020/06/11 18:57:35.553</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Begin package load [SQLSearchSsmsPackage]</description>
<guid>{26218D92-039D-466C-BF66-EAE1098379BE}</guid>
</entry>
<entry>
<record>318</record>
<time>2020/06/11 18:57:35.563</time>
<type>Error</type>
<source>VisualStudio</source>
<description>SetSite failed for package [SQLSearchSsmsPackage]Source: 'RedGate.SQLSearch.SSMSPackage18' Description: Could not load file or assembly 'RedGate.SIPFramework.Services, Version=0.2.1.208, Culture=neutral, PublicKeyToken=7f465a1c156d4d57' or one of its dependencies. The system cannot find the file specified.
System.IO.FileNotFoundException: Could not load file or assembly 'RedGate.SIPFramework.Services, Version=0.2.1.208, Culture=neutral, PublicKeyToken=7f465a1c156d4d57' or one of its dependencies. The system cannot find the file specified.
File name: 'RedGate.SIPFramework.Services, Version=0.2.1.208, Culture=neutral, PublicKeyToken=7f465a1c156d4d57'
 at RedGate.SQLSearch.SSMSPackage.SQLSearchSsmsPackage.<InitializeAsync>d__1.MoveNext()
 at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
 at RedGate.SQLSearch.SSMSPackage.SQLSearchSsmsPackage.InitializeAsync(CancellationToken cancellationToken, IProgress`1 progress)
 at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass17_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
 at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e)
 at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck)
 at Microsoft.VisualStudio.Services.VsTask.GetResult()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
</description>
<guid>{26218D92-039D-466C-BF66-EAE1098379BE}</guid>
<hr>80070002</hr>
<errorinfo></errorinfo>
</entry>
<entry>
<record>319</record>
<time>2020/06/11 18:57:35.568</time>
<type>Error</type>
<source>VisualStudio</source>
<description>End package load [SQLSearchSsmsPackage]</description>
<guid>{26218D92-039D-466C-BF66-EAE1098379BE}</guid>
<hr>80070002</hr>
<errorinfo></errorinfo>
</entry>
</activity>
Answers
After at least 10 different methods of uninstalling and re-installing all 3 components in my errors, SSMS, Red Gate products & Visual Studio, I decided to go into the program directory and root around for any old hangers-on.
Sure enough, the Red Gate dlls were all in their program directory, and the Red Gate IDE Extensions for SSMS were all still in 18's directories... So I removed all these, did clean installs of SSMS & Red Gate products. And it looks like everything is running without problems.
Mucky. But done.
To resolve, I uninstalled SQL Search, deleted the "C:\Program Files (x86)\Red Gate" folder and installed SQL Search again.
Thank you! I struggled with this issue this week with SSMS 2019.1 and SQL Search 3.6.7.3908
Multiple reinstalls did not work. But finally found your comment and deleted the left over files after another uninstall and that did fix the issue.
Posted here mentioning this issue/fix too
https://forum.red-gate.com/discussion/89626/sql-search-now-available-for-ssms-19?