December 11, 2014 at 9:31 am
I'm using ssms 2014, but got the same problem with 2012. I use ssms almost entirely on remote desktop sessions ( Windows 7, Server 2008R2, Server 2012 ). It may be related to having filtered job activity monitor windows open for hours, but about once per day ssms fails, and has to restart.
Upon resuming usually only one of several queries is restored.
Randy
December 11, 2014 at 9:38 am
I don't understand what you mean by "restart".
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
December 11, 2014 at 9:38 am
Indianrock (12/11/2014)
I'm using ssms 2014, but got the same problem with 2012. I use ssms almost entirely on remote desktop sessions ( Windows 7, Server 2008R2, Server 2012 ). It may be related to having filtered job activity monitor windows open for hours, but about once per day ssms fails, and has to restart.Upon resuming usually only one of several queries is restored.
Randy
OK. Not totally sure what question you are asking ...
Install SQL Prompt and all of your queries will be restored.
If you're on a budget, SSMSBoost can do something similar.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
December 11, 2014 at 10:16 am
ssms just hangs and offers a window to debug, restart or restart and search for solution. That's what I mean by restart. Do you gents use ssms on a remote desktop? Do you open job activity monitor and filter the job list? If you do and it doesn't blow up regularly, then I'm at a loss.
Might have to look at Toad for Sql of something like Embarcadero's product.
December 11, 2014 at 12:03 pm
Have you checked the event viewer to see what the error is?
December 11, 2014 at 12:20 pm
Faulting application name: Ssms.exe, version: 2011.110.3350.0, time stamp: 0x515343cd
Faulting module name: ntdll.dll, version: 6.3.9600.17278, time stamp: 0x53eeb4a3
Exception code: 0x4000001f
Fault offset: 0x000270bc
Faulting process id: 0x174c
Faulting application start time: 0x01d014f4660fd6cf
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe
Faulting module path: C:\Windows\SYSTEM32tdll.dll
Report Id: 78f73edb-814f-11e4-80c4-005056921599
Faulting package full name:
Faulting package-relative application ID:
December 11, 2014 at 5:13 pm
Have you tried running SSMS with activity logging enabled?
run it with the "/log" command line switch.
When it dies, before you allow it to restart look at the log for errors.
C:\Users\your user name\AppData\Roaming\Microsoft\AppEnv\10.0\ActivityLog.xml
You may need to grab a copy of ActivityLog.xsl as well - it needs to be copied to the same folder as ActivityLog.xml, then you can open ActivityLog.xml in Internet Explorer.
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);
December 11, 2014 at 6:17 pm
MM, I'll try that. Thanks
December 14, 2014 at 1:32 pm
Here is the captured log error.
Unexpected system error mode before loading package
Visual Studio Task List Package windows forms designer
This time I did have job activity monitor open with a filter. I may just decide to query msdb and not use job activity monitor. Also asking my company about Toad for Sql licensing. This is a microsoft server OS with all the latest patches -- needs to just work ( reminds me of the arguments for using Apple products -- or Linux. )
Also upon restart I'm offered the chance to reload one of several queries I had open. I think ssms does better than that if the server is rebooted while ssms is open.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply