SSMS 2012 SP1 Activity Monitor not working against 2008 R2 - by Christoph Muthmann

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


12
0
Sign in
to vote
ID 771843 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 11/21/2012 6:50:35 AM
Access Restriction Public

Description

After the installation of SP1 for SQL Server 2012 you can not use the activity monitor against instances with SQL Server 2008 R2. 
But instances with 2008 and 2012 are working fine.
Sign in to post a comment.
Posted by Alex [MSFT] on 2/4/2013 at 5:36 PM
I will consider this issue resolved and go ahead and close it. Alex Grach[MSFT]
Posted by Alex [MSFT] on 2/4/2013 at 5:35 PM
I will consider this issue resolved and go ahead and close it. Alex Grach[MSFT]
Posted by Christoph Muthmann on 2/1/2013 at 3:13 AM
Vladimir,
thanks a lot! It works like a charm.

I've installed the hotfix on one server with x64 and after the reboot I can use my activity monitor.
Greetings,
Christoph
Posted by Microsoft on 1/31/2013 at 3:48 PM
http://support.microsoft.com/kb/932370
Posted by Microsoft on 1/31/2013 at 3:48 PM
Christoph, please read this KB and install hotfix on your Windows 2003 SP2 machines. It should fix WMI and provide additional properties Activity Monitor is expecting.

Vladimir Svidersky [MSFT SQL SERVER]
Posted by Christoph Muthmann on 11/28/2012 at 6:45 AM
Hi Alex,
if I close the Overview then the other parts are working well.

Greetings,
Christoph
Posted by Christoph Muthmann on 11/27/2012 at 2:33 AM
Hi Alex!
1. yes
2. no
3. The nine working servers have Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor), Standard Edition (64-bit) on Windows NT 6.0 <X64> (Build 6001: Service Pack 1),
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM) and are running Microsoft SQL Server 2008 (SP3) - 10.0.5512.0 (X64) , Microsoft SQL Server 2008 R2 (SP1) - 10.50.2796.0 (X64), Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) .
The six not working servers have Standard Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2) or
Standard Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2) and are running Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64), Microsoft SQL Server 2008 (SP3) - 10.0.5512.0 (X64), Microsoft SQL Server 2008 R2 (SP1) - 10.50.2769.0 (Intel X86), Microsoft SQL Server 2008 R2 (SP1) - 10.50.2861.0 (X64), Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64).
4. .Net Framework on the running machines is 3.5.1 or 4 and on the others it is 3.5 SP1 or 4.0.30319.
Greetings,
Christoph





Posted by Alex [MSFT] on 11/26/2012 at 1:53 PM
Thank you for reporting this issue to investigate this father please provide the following information:

1. Is problem present only on OS Microsoft Windows NT 5.2 (3790)?
2. Do you have any SQL Servers 2008/R2 that not experiencing this issue but still running on OS Microsoft Windows NT 5.2 (3790)?
3. Is any difference in patching upgrades between working and not working SQL Server 2008/R2 servers? Are they all upgraded to the same CU or SP?
3. Can you please provide .NET version installed on both working SQL 2008/R2 machine and not working?

Thanks,
Alex Grach [MSFT]

Alex Grach [MSFT SQL SERVER]
Posted by Christoph Muthmann on 11/23/2012 at 4:13 AM
I have to modify my first statement. It occurs with SQL Server 2008 and SQL Server 2008 R2, too. But I can use activity monitor with some servers without any problem. The working servers are SQL Server 2008 and SQL Server 2008 R2, too.
It is a mixture of Enterprise and Standard Editions.
All of the servers not working have OS Microsoft Windows NT 5.2 (3790).