Unexpected character encountered while parsing value: <. Path '', line 0, position 0. Starting SSMS

PhilipBA

I recently updated from SQL Prompt 10.6 to 10.7 and now the Prompt Tab is gone in SSMS 18. I see the error:

Unexpected character encountered while parsing value: <. Path '', line 0, position 0.

follow by: 
The SOLPromptSsmsPackagelS’ package did not load

correctly.

The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file \AppData\Roaming\Microsoft\AppEnv\ 15.0\ActivityLog.xml'.

Restarting Visual Studio could help resolve this issue. 

Restarting Visual Studio didn't help, and reverting back to SQL Prompt 10.6 didn't work either

Here is particle part of the Activity Log, it seems related to Visual Studio has anyone else experienced this?

 <entry>

    <record>284</record>

    <time>2021/08/12 14:05:53.931</time>

    <type>Error</type>

    <source>FrameControlManager</source>

    <description>Failed to load the frame control registered at MainWindowFrameControls\{304ee989-b7c9-46c8-aa48-f080bc47cee0}.&#x000D;&#x000A;Exception: Microsoft.VisualStudio.PlatformUI.ControlRegistrationException: Registration error for MainWindowFrameControls\{304ee989-b7c9-46c8-aa48-f080bc47cee0} ---&gt; System.Runtime.InteropServices.COMException: Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))&#x000D;&#x000A;   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControl.LoadDisplayName(SettingsStore store, String collection)&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControl.Read(SettingsStore store, String collection)&#x000D;&#x000A;   --- End of inner exception stack trace ---&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControl.Read(SettingsStore store, String collection)&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControlManager.&lt;LoadFrameControls_OnIdle&gt;d__7.MoveNext()</description>

  </entry>

  <entry>

    <record>285</record>

    <time>2021/08/12 14:05:53.931</time>

    <type>Warning</type>

    <source>VisualStudio</source>

    <description>Performance warning: String load failed. Pkg:{5E80A5A1-B722-4727-9015-148AAB6310B0} LANG:0409 ID:1000&#x000D;&#x000A;</description>

  </entry>

  <entry>

    <record>286</record>

    <time>2021/08/12 14:05:53.931</time>

    <type>Error</type>

    <source>FrameControlManager</source>

    <description>Failed to load the frame control registered at MainWindowFrameControls\{73988e61-7e30-4e87-b891-23b5e460db21}.&#x000D;&#x000A;Exception: Microsoft.VisualStudio.PlatformUI.ControlRegistrationException: Registration error for MainWindowFrameControls\{73988e61-7e30-4e87-b891-23b5e460db21} ---&gt; System.Runtime.InteropServices.COMException: Error HRESULT E_FAIL has been returned from a call to a COM component.&#x000D;&#x000A;   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControl.LoadDisplayName(SettingsStore store, String collection)&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControl.Read(SettingsStore store, String collection)&#x000D;&#x000A;   --- End of inner exception stack trace ---&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControl.Read(SettingsStore store, String collection)&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControlManager.&lt;LoadFrameControls_OnIdle&gt;d__7.MoveNext()</description>

  </entry>

  <entry>

    <record>287</record>

    <time>2021/08/12 14:05:54.011</time>

    <type>Warning</type>

    <source>VisualStudio</source>

    <description>Performance warning: String load failed. Pkg:{B22490B8-AA51-43B1-97EE-509A33B681F3} LANG:0409 ID:1001&#x000D;&#x000A;</description>

  </entry>

  <entry>

    <record>288</record>

    <time>2021/08/12 14:05:54.011</time>

    <type>Error</type>

    <source>FrameControlManager</source>

    <description>Failed to load the frame control registered at MainWindowFrameControls\{F66FBC48-9AE4-41DC-B1AF-0D64F0F54A07}.&#x000D;&#x000A;Exception: Microsoft.VisualStudio.PlatformUI.ControlRegistrationException: Registration error for MainWindowFrameControls\{F66FBC48-9AE4-41DC-B1AF-0D64F0F54A07} ---&gt; System.Runtime.InteropServices.COMException: Error HRESULT E_FAIL has been returned from a call to a COM component.&#x000D;&#x000A;   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControl.LoadDisplayName(SettingsStore store, String collection)&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControl.Read(SettingsStore store, String collection)&#x000D;&#x000A;   --- End of inner exception stack trace ---&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControl.Read(SettingsStore store, String collection)&#x000D;&#x000A;   at Microsoft.VisualStudio.PlatformUI.FrameControlManager.&lt;LoadFrameControls_OnIdle&gt;d__7.MoveNext()</description>

  </entry>

  <entry>

    <record>289</record>

    <time>2021/08/12 14:05:54.026</time>

    <type>Warning</type>

    <source>AutoLoadManager</source>

    <description>Package {e33b8a3b-d1cf-4eb0-92aa-0590f0b55b1a} for UI context {e80ef1cb-6d64-4609-8faa-feacfd3bc89f} loads synchronously and may not be supported in a future release.</description>

  </entry>

  <entry>

    <record>290</record>

    <time>2021/08/12 14:05:54.026</time>

    <type>Information</type>

    <source>VisualStudio</source>

    <description>Entering function CVsPackageInfo::HrInstantiatePackage</description>

    <guid>{E33B8A3B-D1CF-4EB0-92AA-0590F0B55B1A}</guid>

  </entry>

  <entry>

    <record>291</record>

    <time>2021/08/12 14:05:54.026</time>

    <type>Information</type>

    <source>VisualStudio</source>

    <description>Begin package load [SQLPromptSsmsPackage18]</description>

    <guid>{E33B8A3B-D1CF-4EB0-92AA-0590F0B55B1A}</guid>

  </entry>

  <entry>

    <record>292</record>

    <time>2021/08/12 14:05:59.336</time>

    <type>Error</type>

    <source>VisualStudio</source>

    <description>LegacySitePackage failed for package [SQLPromptSsmsPackage18]Source: &apos;Newtonsoft.Json&apos; Description: Unexpected character encountered while parsing value: &lt;. Path &apos;&apos;, line 0, position 0.&#x000D;&#x000A;</description>

    <guid>{E33B8A3B-D1CF-4EB0-92AA-0590F0B55B1A}</guid>

    <hr>80131500</hr>

    <errorinfo></errorinfo>

  </entry>

  <entry>

    <record>293</record>

    <time>2021/08/12 14:05:59.336</time>

    <type>Error</type>

    <source>VisualStudio</source>

    <description>SetSite failed for package [SQLPromptSsmsPackage18](null)</description>

    <guid>{E33B8A3B-D1CF-4EB0-92AA-0590F0B55B1A}</guid>

    <hr>80131500</hr>

    <errorinfo></errorinfo>

  </entry>

  <entry>

    <record>294</record>

    <time>2021/08/12 14:05:59.336</time>

    <type>Error</type>

    <source>VisualStudio</source>

    <description>End package load [SQLPromptSsmsPackage18]</description>

    <guid>{E33B8A3B-D1CF-4EB0-92AA-0590F0B55B1A}</guid>

    <hr>80131500</hr>

    <errorinfo></errorinfo>

  </entry>

</activity>

Dan_J

Hi @PhilipBA

I'm sorry to hear to are encountering this issue with SQL Prompt! Thanks for reaching out to us regarding this.

Please can you confirm the exact version number of SSMS you currently have installed?

Also, as a very first action on this, would you mind completely removing SQL Prompt before then reinstalling it?  We generally advise using Revo Uninstaller Free (https://www.revouninstaller.com/revo-uninstaller-free-download/) to ensure all residual files are removed.  Following removal off the product, the latest version of SQL Prompt can be downloaded directly from: https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_10.7.1.22264.exe

PhilipBA

It is happening on two computers that have Microsoft SQL Server Management Studio - 18.9.1

Dan_J

Hi @PhilipBA

I see, it is interesting that you are seeing the same issue on two separate computers!

Would it be possible to attempt a full removal and reinstall of SQL Prompt on one of those computers to see if this resolves the issue?

PhilipBA

Four Computers now. The only process that has worked was installing Revo Uninstaller, reboot and reverting back to SQL Prompt 10.6. I tired the running Revo Uninstaller rebooting and installing SQL Prompt 10.7.1 with the same error. And two of the four still errored on 10.6 so I ran Revo Uninstaller, rebooted and had to select SSMS only option on the installer for SQL Prompt 10.6
  

I have added the full activity log for the errors, I have seen on this computers

Thanks

PhilipBA

I have newly installed Microsoft SQL Server Management Studio - 18.9.2 and updated to SQL Prompt 10.7 and it errors as well 

"Failed to load the frame control registered at MainWindowFrameControls\{304ee989-b7c9-46c8-aa48-f080bc47cee0}.

Exception: Microsoft.VisualStudio.PlatformUI.ControlRegistrationException: Registration error for MainWindowFrameControls\{304ee989-b7c9-46c8-aa48-f080bc47cee0} ---> System.Runtime.InteropServices.COMException: Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))

   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

   at Microsoft.VisualStudio.PlatformUI.FrameControl.LoadDisplayName(SettingsStore store, String collection)

   at Microsoft.VisualStudio.PlatformUI.FrameControl.Read(SettingsStore store, String collection)

   --- End of inner exception stack trace ---

   at Microsoft.VisualStudio.PlatformUI.FrameControl.Read(SettingsStore store, String collection)

   at Microsoft.VisualStudio.PlatformUI.FrameControlManager.<LoadFrameControls_OnIdle>d__7.MoveNext()"

Package {e33b8a3b-d1cf-4eb0-92aa-0590f0b55b1a} for UI context {e80ef1cb-6d64-4609-8faa-feacfd3bc89f} loads synchronously and may not be supported in a future release.

Entering function CVsPackageInfo::HrInstantiatePackage

Begin package load [SQLPromptSsmsPackage18]

LegacySitePackage failed for package [SQLPromptSsmsPackage18]Source: 'Newtonsoft.Json' Description: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.

SetSite failed for package [SQLPromptSsmsPackage18](null)

End package load [SQLPromptSsmsPackage18]

Ran Revo Uninstaller/Rebooted and  https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_10.7.1.22264.exe and Same Error

Finally running this revo software/reboot and reverting the, back to 10.6 works and SQL Prompt loads. One laptop I installed SQL Prompt 10.6 without Visual Studio component and other laptop both components are working fine. Both those laptops have SSMS 18.9.1 installed and they have also have Microsoft Visual Studio Tools for Applications 2017 on one and the other has Microsoft Visual Studio Tools for Applications 2015

PhilipBA

I have newly installed Microsoft SQL Server Management Studio - 18.9.2 and updated to SQL Prompt 10.7 and it errors as well 

"Failed to load the frame control registered at MainWindowFrameControls\{304ee989-b7c9-46c8-aa48-f080bc47cee0}.

Exception: Microsoft.VisualStudio.PlatformUI.ControlRegistrationException: Registration error for MainWindowFrameControls\{304ee989-b7c9-46c8-aa48-f080bc47cee0} ---> System.Runtime.InteropServices.COMException: Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))

   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

   at Microsoft.VisualStudio.PlatformUI.FrameControl.LoadDisplayName(SettingsStore store, String collection)

   at Microsoft.VisualStudio.PlatformUI.FrameControl.Read(SettingsStore store, String collection)

   --- End of inner exception stack trace ---

   at Microsoft.VisualStudio.PlatformUI.FrameControl.Read(SettingsStore store, String collection)

   at Microsoft.VisualStudio.PlatformUI.FrameControlManager.<LoadFrameControls_OnIdle>d__7.MoveNext()"

Package {e33b8a3b-d1cf-4eb0-92aa-0590f0b55b1a} for UI context {e80ef1cb-6d64-4609-8faa-feacfd3bc89f} loads synchronously and may not be supported in a future release.

Entering function CVsPackageInfo::HrInstantiatePackage

Begin package load [SQLPromptSsmsPackage18]

LegacySitePackage failed for package [SQLPromptSsmsPackage18]Source: 'Newtonsoft.Json' Description: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.

SetSite failed for package [SQLPromptSsmsPackage18](null)

End package load [SQLPromptSsmsPackage18]

Ran Revo Uninstaller/Rebooted and  https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_10.7.1.22264.exe and Same Error

Finally running this revo software/reboot and reverting the, back to 10.6 works and SQL Prompt loads. One laptop I installed SQL Prompt 10.6 without Visual Studio component and other laptop both components are working fine. Both those laptops have SSMS 18.9.1 installed and they have  Microsoft Visual Studio Tools for Applications 2017 on one and 

Microsoft Visual Studio Tools for Applications 2015

Jessica R

Hi @PhilipBA,

Is it possible for you to zip up and share the contents of c:\Users\<username>\AppData\Local\Red Gate\SQL Prompt 10 with us? You can email to support@red-gate.com with subject "For ticket #255982".

PhilipBA

I will next week

Dan_J

Hi @PhilipBA

I just wondered if you'd been able to take a look at this yet? Are you still requiring our support on this?

Data_Writer

@Dan_J I've encountered this error across several versions of Prompt as well and when it happens on startup, I haven't been able to resolve it without a clean reinstall of prompt.

However, I have found a way to generate the error in version 10.8.2.23489 that will not corrupt the installation.

With "Manage Code Analysis Rules" enabled, click on the light-bulb in the margin of an item and select "show issue details".  If I then select "Disable Rule" from the "issue Details" popup, Prompt then displays the error dialog with the "Unexpected Character encountered when parsing value..." error. Unike the startup error, however,  I'm able to close the dialog and continue working. 

PhilipBA

Sorry I was waiting for a staff member get back to me with the error. Here the file you requested

Data_Writer

Any update on this? Has anyone found a workaround/solution to this issue?  I still encounter it from time to time when I launch SSMS and I'd love to have an alternative to uninstalling/reinstalling the application.