SSMS crashing after upgrade to 3.0.5.7
gvarol@corelogic.com
Posts: 90 Bronze 3
[Post text removed on request of the user]
gvarol@corelogic.com
Posts: 90 Bronze 3
Comments
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)
Redgate Software
Redgate Software
Also, could you mail across the full logfile (you pasted a snippet in the original post) to us with F0056946 in the subjectline?
Redgate Software
Redgate Software
Redgate Software
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!
Redgate Software
Redgate Software
Redgate Software
Redgate Software
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.
Redgate Software
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.
Redgate Software
Redgate Software
- 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?
Redgate Software