PoorMansTSqlFormatter
PoorMansTSqlFormatter copied to clipboard
This setup requires SSMS 2014, 2016 or 17 installed
I get this error when installing the PoorMansTSqlFormatterSSMSPackage.Setup.1.6.11.msi package from http://architectshack.com/PoorMansTSqlFormatter.ashx#Download_5
I haver SSMS 17.4 installed.
Microsoft SQL Server Management Studio 14.0.17213.0 Microsoft Analysis Services Client Tools 14.0.1016.232 Microsoft Data Access Components (MDAC) 10.0.14393.0 Microsoft MSXML 3.0 5.0 6.0 Microsoft Internet Explorer 9.11.14393.0 Microsoft .NET Framework 4.0.30319.42000 Operating System 6.3.14393
I also additionally have SSMS 2008R2 and the 1.6.10 version of SQL Formatter installs no problem. Is the 2 versions of SSMS the issue?
SSMS 2016 installed here, same issue.
@TaoK any info we can give to get some help with this?
@daviespaul it is because you have 17.4 installed, which is greater than 17 (latest version supported by the Poor Man so far). The bigger issue is #197 and once that is resolved, your issue with be resolved as well.
@Huji I am on SSMS 16.5.3, why would i be getting the same error?
No idea. In f5bbf5b support for version 17 was added and support for the 2016 version already existed.
Hi guys, I think I'm missing some information here. As far as I know, the previous installer supported SSMS versions all the way to 17.9.
I just released an update to support 18.X also (https://twitter.com/PoorSQL/status/1155471888145141761), but I don't suppose this will help you because I don't know what is actually wrong in your environment(s).
Can you confirm whether this is still an issue, and we can see how to go about investigating/debugging?
Is the 2 versions of SSMS the issue?
No. this should not be a problem.
I recently got a new laptop and attempted the install. I am getting the same error. SQL Server Management Studio v17.9.1 Microsoft SQL Server Management Studio 14.0.17289.0
I was getting this error with my installation of SSMS v17.8.1. But the installer did not throw this error on a different user account on the same computer. So I ran Process Monitor while running the installer on the "good" user account to see what the installer was looking for. It is searching for these registry entries:
HKCU\Software\Microsoft\SQL Server Management Studio\12.0_Config\Initialization
HKCU\Software\Microsoft\SQL Server Management Studio\13.0_Config\Initialization
HKCU\Software\Microsoft\SQL Server Management Studio\14.0_Config\Initialization
HKCU\Software\Microsoft\SQL Server Management Studio\18.0_IsoShell_Config\Initialization
Once it finds one of them, it queries the extension path:
HKCU\Software\Microsoft\SQL Server Management Studio\14.0_Config\Initialization\ApplicationExtensionsFolder
The HKCU\Software\Microsoft\SQL Server Management Studio\14.0_Config registry path did not exist in my account's HKCU
I then realised my mistake. I run SSMS as a different user so I have access to the databases I connect to, my normal account doesn't have these permissions. These registry entries are only created when SSMS is run for the first time under a new account.
Once I ran the installer with the same account I usually run SSMS with, it detected fine and installed.