Bassem Yehia Salama

My feedback

  1. 627 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    338 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Good news (I hope)!

    I was finally able to make progress on this. On the machine with the fix, I was able to open a diagram created by SSMS 17.9.1 (on a different machine). The same diagram opened with 18.3.1 resulted in a crash.

    I’ll do more testing in the next few days and go over all the comments on this page to make sure I capture all the scenarios and make sure they are really fixed.

    It’s looking good, I really hope… :)

    -Matteo

    Bassem Yehia Salama supported this idea  · 
  2. 1,117 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  86 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Bassem Yehia Salama supported this idea  · 
  3. 738 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  127 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Bassem Yehia Salama supported this idea  · 
  4. 45 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    34 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    I’m looking into this issue.

    In the meanwhile, could you take a look at the SSMS setup logs (%TEMP%\SSMSSetup\SSMS-Setup-ENU_20190430231104.log). I’m interested in the lines in the range 133-216. Could you share those (tip: have a look at the lines and sanitize them, if you think they may contain sensible information?

    Also, if you could share the output of:
    reg query “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32 /s

    And, finally, to unblock yourself:
    1) Make sure you don’t have any previous version (RC, Preview) of SSMS 18.0 installed (check Add/Remove programs; if you do, uninstall it)
    2) Make sure “C:\Program Files (x86)\Microsoft SQL Server Management Studio 18” does not exist (if it does, the delete it)
    3) Delete the mentioned registry key (e.g. by running from an elevated cmd prompt:
    reg DELETE “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32)
    4) Retry setup
    Please, let…

    An error occurred while saving the comment
    Bassem Yehia Salama commented  · 

    After Point 3 the setup work OK and install

    An error occurred while saving the comment
    Bassem Yehia Salama commented  · 

    SSMSInstallRoot REG_SZ C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\

    Bassem Yehia Salama supported this idea  · 

Feedback and Knowledge Base