SSMS 22 Plugin Causing Lockup

4 Posts
2 Users
0 Reactions
83 Views
(@whetdawg)
Member
Joined: 1 month ago
Posts: 2
Topic starter  

I purchase Pro license today for SSMS 22.  SSMS is locking up after a couple of minutes.  This started after I licensed PRO and after I made some customizations to SQLinForm settings -- nothing wierd (unchecked some new line options).

I found this in Event Viewer:
The program SSMS.exe version 22.2.11415.280 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Is there a log file that you need to debug?

I could not find an uninstall option but saw the "how to uninstall" post from 2 years ago.
I killed SSMS, deleted the folder:
C:\Program Files\Microsoft SQL Server Management Studio 22\Release\Common7\IDE\Extensions\izp55lfh.lre
and restarted. I've not had a lockup since.

The SQLinForm menu item still exists on the Tools menu.



   
Quote
Guido
(@admin)
Member Admin
Joined: 4 years ago
Posts: 284
 

@whetdawg, thanks for your feedback. I am sorry for any inconveniences. I publisched a fix on https://www.sqlinform.com/download-ssms-21-plugin/  

In order to deinstall the old version you have use the Visual Studio installer and changing the instllation of SSMS22. Go to components and uncheck the Plugin.

Now you can install the new vsix.

Please let me know if it worked

Regards

Guido



   
ReplyQuote
Guido
(@admin)
Member Admin
Joined: 4 years ago
Posts: 284
 

@whetdawg,

if you want to get rid of the Tools menu (SSMS still has the Menu in its cache), please run as Admin the command "C:\Program Files\Microsoft SQL Server Management Studio 22\Release\Common7\IDE\ssms.exe" /setup.

This will force ssms to rebuild the cache.

I am sorry about all these manual commands but Microsoft does not officially support 3rd party extensions and changed the behavior significantly in SSMS21 and SSMS22 without announcements. Until now it was mandatory that the extension is installed for all users and therefore can only be de-installed using the Visual studio installer. Now it also supports the installation per user. Directory Names and Cache Location changed. I wil have to adapt the installation routine and de-installation instructions. My feeling is that Microsoft is going into the right direction how they handle 3rd party  but it will still take some time

Regards

Guido


This post was modified 1 month ago by Guido

   
ReplyQuote
(@whetdawg)
Member
Joined: 1 month ago
Posts: 2
Topic starter  

@admin Thanks much!!
I uninstalled, reinstalled the new version and have not locked up once today. 😀



   
ReplyQuote
Share: