DEFECT: 5.3.2 installed. SSMS crashed immediately!

PDinCAPDinCA Posts: 642 Silver 1
edited May 11, 2012 12:48PM in SQL Prompt Previous Versions
First invoke of SSMS after successful install of 5.3.2 over 5.3.0.3 induced an unrecoverable crash of SSMS:
    SSMS is 2008R2 with all latest patches applied Environment is Windows 2003 Server R2 SP2 Standard Edition.
"An unhandled win32 exception occurred in Ssms.exe [22248]"

No experimental features were involved - all turned off prior to upgrade.

2nd invoke was OK.
Jesus Christ: Lunatic, liar or Lord?
Decide wisely...
· Share on Twitter

Comments

  • Eddie DEddie D Posts: 1,803 Rose Gold 5
    Hi PDinCA

    Thank you for your forum post and sorry that you encountered a problem.

    Sadly I have been unable to replicate the error you have reported on my workstation and on Virtual Machines on a test system.

    Was there any other information apart from the error message?

    "An unhandled win32 exception occurred in Ssms.exe [22248]"

    Many Thanks
    Eddie
    Eddie Davis
    Senior Product Support Engineer
    Redgate Software Ltd
    Email: support@red-gate.com
    · Share on Twitter
  • PDinCAPDinCA Posts: 642 Silver 1
    Sadly, Eddie, "that's all she wrote"

    I had hoped for more, but that was the sum total of the information unless I'd try to debug w/ VS.
    Jesus Christ: Lunatic, liar or Lord?
    Decide wisely...
    · Share on Twitter
  • Eddie DEddie D Posts: 1,803 Rose Gold 5
    Thank you for your reply.
    Sadly, Eddie, "that's all she wrote"

    I expected this would be your reply, as you are normally very thorough with your error reports, providing us with excellent information.

    Is this error been a one off or occurs everytime you start up SSMS or occurs intermittently when you start up SSMS?

    Many Thanks
    Eddie
    Eddie Davis
    Senior Product Support Engineer
    Redgate Software Ltd
    Email: support@red-gate.com
    · Share on Twitter
  • PDinCAPDinCA Posts: 642 Silver 1
    This has happened twice now, both times immediately after a SQL Prompt upgrade initiated from looking for updates from within an SSMS instance that has been running for days, if not weeks.

    I had this happen on a prior 5.x upgrade but didn't report it as it only happened the first time SSMS was fired up.

    Just to be sure, I just closed SSMS and waited a few, then successfully fired it up again, so the crash is, sadly, not repeatable.

    I'll be sure to post again should a subsequent upgrade eventuate in an initial crash.

    Cheers, Eddie, enjoy the weekend.
    Jesus Christ: Lunatic, liar or Lord?
    Decide wisely...
    · Share on Twitter
Sign In or Register to comment.