SSMS crashing after upgrade to 3.0.5.7

• 
  [Post text removed on request of the user]

  gvarol February 02, 2012 12:04

  - 0 +
• 
  Hi,
  Sorry that you've run into this. We've not had other reports of this happening yet; and usually, if SQL Source Control encounters a problem we would throw one of our errors rather than crashing SSMS as a whole.
  
  A couple of simple things to begin with:
  
  - presumably you've rebooted and tried again - if not, can you?
  - have other developers upgraded to the new build? Do they get the same thing happen?
  - if you have time, could you try our debugger? Grab Red Flag from here, unzip it and run the x86 version. Use this to launch SSMS. Once the problem has occurred, save the output from Red Flag and mail it in to support@red-gate.com
  - to get working again, the next thing would be to downgrade by uninstalling the current version, then grabbing the installer from the main Red Gate website (we've not updated the bundle installers with the new build yet)

  James B February 02, 2012 13:15

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 02, 2012 15:32

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 02, 2012 15:35

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 03, 2012 17:44

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 06, 2012 15:38

  - 0 +
• 
  Sorry, I am still awaiting feedback on the error information you sent through. No one else has reported the same issue so it may be something specific to your environment, but I'll update as soon as I hear more.

  James B February 07, 2012 07:03

  - 0 +
• 
  Can I check if downgrading to the previous version worked okay?
  
  Also, could you mail across the full logfile (you pasted a snippet in the original post) to us with F0056946 in the subjectline?

  James B February 07, 2012 10:12

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 07, 2012 10:43

  - 0 +
• 
  I got the red flag output - I've not seen the actual SQL Source Control logs though. Apologies if I missed them - zipping them up should make them smaller and you can find them in c:\users\<your username>\appdata\local\red gate\logs\sql source control 3

  James B February 07, 2012 10:46

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 07, 2012 10:52

  - 0 +
• 
  Just got your email, but there didn't seem to be anything attached - could you send again please?

  James B February 07, 2012 11:04

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 07, 2012 11:11

  - 0 +
• 
  OK - I see what happens.
  
  It appears our ticketing system is doing something massively stupid in that when I edit your message to add in your ticket number (so I can update your ticket), it appears to drop the attachment!
  
  Could you send it once more, but please put the reference "F0056946" in the subject line, then I won't need to edit it.
  
  Sorry for the inconvenience!

  James B February 07, 2012 11:16

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 07, 2012 11:18

  - 0 +
• 
  Success! Thanks

  James B February 07, 2012 11:21

  - 0 +
• 
  Also - in the Logs folder, is there a folder for the SSMS Integration Pack? If so, can you send logs from around the crash time from there as well please?

  James B February 07, 2012 11:35

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 07, 2012 11:36

  - 0 +
• 
  Fair enough - thanks for checking.

  James B February 07, 2012 11:37

  - 0 +
• 
  Unfortunately the logs and crash dump aren't really telling us anything.
  When you have some time available, could you revert to the new version, and (assuming it still crashes) check the Windows Event Logs for any messages? Please forward those on to the same email as before.
  
  Also, we could tell from the logs you have some other SSMS addins installed. To eliminate these from possibly conflicting, could you disable the other addins to see if it makes any difference? To do this:
  
  - Go into the registry, and navigate to:
  HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node if on a 64-bit machine]\Microsoft\Microsoft SQL Server\[100 for SSMS 2008, 90 for SSMS 2005]\Tools\Shell\AddIns
  
  - For each one, change the LoadBehavior key from 1 to 0 for each one asides from the Red Gate ones, and see if it changes anything.

  James B February 08, 2012 07:15

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 08, 2012 09:02

  - 0 +
• 
  I see - I didn't realise you were running it on a shared server. This would of course make it harder.
  Do you have a local SSMS instance (such as on your own PC) that you could test against without causing trouble for other users?
  
  The debug tool we sent would theoretically spot any problem but it appears not to have done so the problem may be occurring in some other process perhaps.

  James B February 08, 2012 09:07

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 08, 2012 10:34

  - 0 +
• 
  I've just mailed you a trial extension key.

  James B February 08, 2012 10:39

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 08, 2012 11:10

  - 0 +
• 
  OK, if it crashes on your desktop, that's great - back to my earlier query:
  
  - is there anything in the Windows Event Logs?
  - Do you have the same other Add-ins installed as on the other server? If so, can you disable them with the registry key change and see if the problem goes away?

  James B February 08, 2012 11:11

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 08, 2012 11:18

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 08, 2012 11:18

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 08, 2012 11:23

  - 0 +
• 
  [Post text removed on request of the user]

  gvarol February 08, 2012 11:25

  - 0 +

Add comment

Please sign in to leave a comment.