User profile for DBAJohnny

Thanks for getting back to me! / comments

Thanks for getting back to me!

0 votes

Robyn - Thanks! I now see the "trust server certificate" checkbox, just as you wrote. All's good now. Johnny / comments

Robyn -Thanks! I now see the "trust server certificate" checkbox, just as you wrote. All's good now.Johnny

0 votes

I am using Redgate SQL Compare 15.0.7.23280. I have tried uninstalling and re-installing, but that didn't help. / comments

I am using Redgate SQL Compare 15.0.7.23280. I have tried uninstalling and re-installing, but that didn't help.

0 votes

Yes, that resolved the problem. Thanks for the quick response! / comments

Yes, that resolved the problem.Thanks for the quick response!

0 votes

I've started a specific question for the SQL Compare plugin on SSMS 19. See https://forum.red-gate.com/discussion/89890/i-am-unable-to-get-the-sql-compare-plugin-working-with-ssms-19/p1?new=1 / comments

I've started a specific question for the SQL Compare plugin on SSMS 19. See https://forum.red-gate.com/discussion/89890/i-am-unable-to-get-the-sql-compare-plugin-working-with-ssms-19/p1?new=1

0 votes

I installed SSMS 19 this morning and downloaded and installed the latest version of SQL Toolbelt Essentials. I'm getting the same error message ("The 'SQLSourceControlPackage' did not load correctly") when going into SSMS. I uninstalled SSMS 18, SSMS 19 and SQL Toolbelt, rebooted, reinstalled. No difference. I need to get SQL Source control working. Please advise, and thanks! The affected section of the ActivityLog.xml file is: <entry> <record>164</record> <time>2023/06/10 12:41:29.999</time> <type>Warning</type> <source>VisualStudio</source> <description>Unexpected system error mode before loading package [SqlSourceControlPackage]</description> <guid>{29D00CBC-D1F6-4F0A-9418-FC8454E3B4FE}</guid> </entry> <entry> <record>165</record> <time>2023/06/10 12:41:29.999</time> <type>Information</type> <source>VisualStudio</source> <description>Begin package load [SqlSourceControlPackage]</description> <guid>{29D00CBC-D1F6-4F0A-9418-FC8454E3B4FE}</guid> </entry> <entry> <record>166</record> <time>2023/06/10 12:41:30.130</time> <type>Error</type> <source>VisualStudio</source> <description>CreateInstance failed for package [SqlSourceControlPackage]Source: 'mscorlib' Description: Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
 at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
 at RedGate.SQLSourceControl.Extension.SqlSourceControlPackage..ctor()
 --- End of inner exception stack trace ---
 at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
 at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
 at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
 at System.Activator.CreateInstance(Type type, Boolean nonPublic)
 at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
 at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
 at System.Activator.CreateInstanceFromInternal(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)
 at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName)System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
 at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
 at RedGate.SQLSourceControl.Extension.SqlSourceControlPackage..ctor()</description> <guid>{29D00CBC-D1F6-4F0A-9418-FC8454E3B4FE}</guid> <hr>80004005 - E_FAIL</hr> <errorinfo></errorinfo> </entry> / comments

I installed SSMS 19 this morning and downloaded and installed the latest version of SQL Toolbelt Essentials. I'm getting the same error message ("The 'SQLSourceControlPackage' did not load correct...

0 votes

I am having this exact issue in SQL Prompt version 10.1.5.14730. / comments

I am having this exact issue in SQL Prompt version 10.1.5.14730.

0 votes

eq2home: Since making those changes, the only time I've seen the "Opening window" dialog is the first time I open a new query pane after making a connection to a server. SSMS still has periods of sluggishness, but returns before I am ready to end it in task manager. I wouldn't say the dark theme helps, other than cutting out glare. There are some places that are clearly not thought through properly, such as the grey-on-grey submenus. Too bad. / comments

eq2home: Since making those changes, the only time I've seen the "Opening window" dialog is the first time I open a new query pane after making a connection to a server. SSMS still has periods of ...

0 votes

Interesting. Since I recently made several changes, I have been noticing the same behavior (SSMS v17.8.1): Installed SQL Prompt 9.4.6.7396 Installed SQL Source Control 7.0.4.8725 Switched SSMS to use the (officially unsupported) dark theme.. Per Tianjiao_Li's March 2018 post (above), I've now turned off SSMS' native intellisense. I've also turned on verbose logging. If I have to crash out SSMS again, I'll upload the log file.. / comments

Interesting. Since I recently made several changes, I have been noticing the same behavior (SSMS v17.8.1): Installed SQL Prompt 9.4.6.7396 Installed SQL Source Control 7.0.4.8725 Switched SSMS to ...

0 votes

@Tianjiao_Li - The issue is now reoccuring with me. I've attached the query I was working with and the log file. The log file captioned itself "SQL Test," although I generated it from the help submenu under SQL Prompt. It also seems that the verbose setting got turned off at some point. I'm not on the latest version of SQL prompt, but will be installing that shortly. / comments

@Tianjiao_Li - The issue is now reoccuring with me. I've attached the query I was working with and the log file. The log file captioned itself "SQL Test," although I generated it from the help su...

0 votes

How can we help you today?

DBAJohnny

Comments