Sql-docs: SSMS2018 - Installed, but will not run

[fwd079]

Need to announce that this version does not run at all.
I just installed (as of 31-May-2019) - need to follow the fix in this link:
https://feedback.azure.com/forums/908035-sql-server/suggestions/37502512-ssms2018-installed-but-will-not-run

Copying here for others to see and use.

The issue (in .NET) has been investigated and understood.

The recommended workaround, in the interim, is:
1) Close all instances of SSMS
2) Edit ssms.exe.config
3) Remove the line that has the following text (should be line 38):
NgenBind_OptimizeNonGac enabled=“1”

That’s the same change that will be in the next release of SSMS 18.x

Thanks,

-Matteo

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 45daf2f0-bb22-338f-062b-a9fabcb71a92
• Version Independent ID: b6e909fe-15d9-c1cf-c018-d4f6f36ff31f
• Content: Download SQL Server Management Studio (SSMS) - SQL Server
• Content Source: docs/ssms/download-sql-server-management-studio-ssms.md
• Product: sql
• Technology: ssms
• GitHub Login: @dnethi
• Microsoft Alias: dinethi

[SushiGuy]

SSMS when launched showed the splash screen then instantly crashed. Making the suggested config change as described did the trick. Here is the full path to config file.
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe.config

[chrisheil]

This worked me for as well

[MightyPen]

@markingmyname Hi Mark, On a forum, Matteo has posted the steps necessary for customers to Fix this SSMS bug locally on their own computers. Those same steps have subsequently been pasted into the top of this Issue 2234.
You _might_ want to temporarily add a Cautionary alert into the SSMS Download documentation, to display the text of these same fix steps. I have no opinion on that, and the decision totally belongs to you and @rothja .
Thanks.

[boennhoff]

Why isn't Microsoft pulling back this beta release? Or replacing it immediately with a fixed version?

_"Here is the final episode of GoT.... Ahhh wait, the file is defect.... Just replace the first few bytes with NULs and your favourite Non-Microsoft video player should be able to continue at chapter 2........"_ :laughing: :rofl:

[kathleenkoson]

Gah, I'm sure this is something dumb, but please help... I can get to the line and delete it, but I can't re-save the file to the same location ("you do not have permission to open this file. See the owner of the file or the administrator to obtain permission"). What am I missing? I am getting very tired of uninstalling and reinstalling the entire studio... Thank you.

[SushiGuy]

First be sure to close SSMS app. Then, be sure to open your desired editing tool As Administrator which will allow you to Save the config file. Easiest way is to find your software shortcut or exe and Right-Click -> Run As Administrator

[kathleenkoson]

@SushiGuy – thank you!! With that advice I got it fixed! I’m back in, no more crashing.

From: Jeremy Heiner [e-mail]
Sent: Tuesday, June 4, 2019 10:28 PM
To: MicrosoftDocs/sql-docs [e-mail]
Cc: Kathleen Koson [e-mail]; Comment [e-mail]
Subject: Re: [MicrosoftDocs/sql-docs] SSMS2018 - Installed, but will not run (#2234)

[EXTERNAL]

First be sure to close SSMS app. Then, be sure to open your desired editing tool As Administrator which will allow you to Save the config file. Easiest way is to find your software shortcut or exe and Right-Click -> Run As Administrator

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/sql-docs/issues/2234?email_source=notifications&email_token=ALPULXTHRG7D26GUMR65XXLPY4QCTA5CNFSM4HR25SWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW6NK5Q#issuecomment-498914678, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALPULXRUSCO5FFBPYO7JV3DPY4QCTANCNFSM4HR25SWA.

[bineeshraghavan]

The recommended workaround worked me for as well, in the interim, is:

Close all instances of SSMS
Edit ssms.exe.config
Remove the line that has the following text (should be line 38):
NgenBind_OptimizeNonGac enabled=“1”

[csurrey]

Can confirm this worked for us - Thanks
As above you need to make sure all instances of SSMS are closed first and in our case we ported the configs from the preview after it kicked back into life

[dnethi]

hi folks, the updated SSMS 18.1 should have fixed this. Please update and let us know if the issue still exist.

[moosehunt2007]

I had the same problem as the people above with 18.1, it crashed after the splash screen. I went back to 17.0 and it works just fine. In my opinion, this is not fixed, this is 2 of us in my SQL Server class that have had this issue on our personal computers.

[markingmyname]

@MightPen,

A "known issues" section has been added to the release notes under the 18.0 section. :)

@moosehunt2007,

I see where you state - "I had the same problem as the people above" - referring to 18.1. Have you tried the workarounds the people have tried as well? It would be good to know if that works the same for 18.1 too.

[fwd079]

@MightPen,

A "known issues" section has been added to the release notes under the 18.0 section. :)

@moosehunt2007,

I see where you state - "I had the same problem as the people above" - referring to 18.1. Have you tried the workarounds the people have tried as well? It would be good to know if that works the same for 18.1 too.

Okay tested,

Well @markingmyname - if you install fresh it gives the same splash screen crash, but if you have 18.0 installed and upgrade to 18.1, the fix is _kept_ and not overwritten. So perhaps add this to 18.1 Known Issues too. But yes, from 18.0 to 18.1 _upgrade_ works, not a clean install.

Regards.

[Matteo-T]

@fwd079: are you saying that installing 18.1 on a clean machine (i.e. with no 18.0 ever installed on it), you are still observing the flashing splash screens? If so, would you enter a UserVoice item (https://aka.ms/sqlfeedback) and share the SSMS 18.1 setup log files (%TEMP%\SSMSSetup)? Also, could you share your ssms.exe.config, the one installed by SSMS 18.1 (before any changes you may have done)?

[MichaelAzzar]

we need debugging tool to be added back please

[chaim1221]

Good lord I thought I was going crazy. I have uninstalled this program _so many times_ and reinstalled it thinking it was my computer. Seriously?

Test your software! Sorry for original caps! Was facing a database issue!

[price5583]

I downloaded SSMS from the link on this page and found out they have now remarked out the NgenBind that was giving all the problems. Here is how the NgenBind line reads in the Ssms.exe.config file now:

    <!-- Don't enable this setting. While it may give a perf boost when loading
         a lot of NGEN'ed assemblies outside of the GAC, it may run into issue
         in some cases due to its limitations.
        <NgenBind_OptimizeNonGac enabled="1"/>
    -->

So, now all you have to do is download and run it, no config file editing is necessary. Yeah!

[mrwensveen]

Adding this so it's easier to find this issue (hopefully). When you run smss.exe from the command line, you might get this message: Program 'smss.exe' failed to run: The %1 application cannot be run in Win32 mode. Above workaround should work, as well as installing SSMS.

Also, strangely, the executable seems to have been renamed from smss.exe to ssms.exe in this version?

[Matteo-T]

@mrwensveen:

Adding this so it's easier to find this issue (hopefully). When you run smss.exe from the command line, you might get this message: Program 'smss.exe' failed to run: The %1 application cannot be run in Win32 mode. Above workaround should work, as well as installing SSMS.
Also, strangely, the executable seems to have been renamed from smss.exe to ssms.exe in this version?

No, no... be very careful with that.

• SSMS.EXE is "SQL Server Management Studio"
• Smss.exe is "Session Manager Subsystem" - it's Windows stuff.

You will regret deeply if you mess with smss.exe :-)

[mrwensveen]

Ah, didn't know that. Thanks.

On 02:18, Thu, Jun 20, 2019 Matteo Taveggia <[email protected] wrote:

@mrwensveen https://github.com/mrwensveen:

Adding this so it's easier to find this issue (hopefully). When you run
smss.exe from the command line, you might get this message: Program
'smss.exe' failed to run: The %1 application cannot be run in Win32 mode.
Above workaround should work, as well as installing SSMS.
Also, strangely, the executable seems to have been renamed from smss.exe
to ssms.exe in this version?

No, no... be very careful with that.

• SSMS.EXE is "SQL Server Management Studio"
• Smss.exe is "Session Manager Subsystem" - it's Windows stuff.

You will regret deeply if you mess with smss.exe :-)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/sql-docs/issues/2234?email_source=notifications&email_token=AAJ2QDURDL7OFIJ2T4UBFELP3LEHFA5CNFSM4HR25SWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDUGAI#issuecomment-503792385,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJ2QDUE42JQGHOKEXUQO7LP3LEHFANCNFSM4HR25SWA
.

[IncubusSlayer]

I downloaded 18.1 today and cant connect to my local server anymore. Not sure if its tied to this same issue but some feedback would be greatly appreciated.

[Matteo-T]

I downloaded 18.1 today and cant connect to my local server anymore. Not sure if its tied to this same issue but some feedback would be greatly appreciated.

I have no problem answering questions here, but... keep in mind this is the Git repo for the documentation, so the "doc" people may get mad at me :-)

To get help on SSMS:
https://docs.microsoft.com/en-us/sql/ssms/sql-server-management-studio-ssms?view=sql-server-2017#info_tip-get-help

And, I can confidently say that the issue @IncubusSlayer is seeing in not related to the one discussed here. Can you try to use either sqlcmd.exe or Invoke-Sqlcmd (PowerShell cmdlet in the SQLServer module) to see if you can connected? If it does not work, then it's more like a configuration issue on the server side. If it does work, then log a UserVoice item (info at the same link I provided above).

[fwd079]

@fwd079: are you saying that installing 18.1 on a clean machine (i.e. with no 18.0 ever installed on it), you are still observing the flashing splash screens? If so, would you enter a UserVoice item (https://aka.ms/sqlfeedback) and share the SSMS 18.1 setup log files (%TEMP%\SSMSSetup)? Also, could you share your ssms.exe.config, the one installed by SSMS 18.1 (before any changes you may have done)?

Tested today, fresh install is fixed and crashes no more. Cheers :)

Closing the issue now.

Regards.