Home Dashboard Directory Help

The Activity Monitor is unable to execute queries against server XYZ. by ArthurZ



Sign in
to vote
Type: Bug
ID: 776611
Opened: 1/15/2013 8:40:01 AM
Access Restriction: Public
User(s) can reproduce this bug


Getting repeated errors having the Activity Monitor running against SQL Server 2005 SP2 64Bit Pro using
Microsoft SQL Server Management Studio                        10.50.2550.0
Microsoft Analysis Services Client Tools                        10.50.2500.0
Microsoft Data Access Components (MDAC)                        6.1.7601.17514
Microsoft MSXML                        3.0 5.0 6.0
Microsoft Internet Explorer                        9.0.8112.16421
Microsoft .NET Framework                        2.0.50727.5466
Operating System                        6.1.7601

The full error is

TITLE: Microsoft SQL Server Management Studio

The Activity Monitor is unable to execute queries against server XYZ.
Activity Monitor for this instance will be placed into a paused state.
Use the context menu in the overview pane to resume the Activity Monitor.


Invalid length parameter passed to the SUBSTRING function. (Microsoft SQL Server, Error: 536)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.5069&EvtSrc=MSSQLServer&EvtID=536&LinkId=20476
Sign in to post a comment.
Posted by Lynn Axelson on 10/7/2013 at 11:48 AM
The Activity Monitor has this error on servers with SQL 2008 & SQL 2012, but both on Windows 2008 R2 servers. The Additional Information is : Unable to find SQL Server process ID nnnn on server XXXX. The servers also have many Report Server errors on the windows application event log stating that counters cannot be created.

However, running SQL 2012 SSMS on Win 7 is able to connect to both the above SQL servers & run the Activity Monitor with no problem. (SQL 2008 on Win XP is also able to run the Activity Monitor on the SQL 2008 on Windows 2008 R2 server.)

So the problem appears to be related to Windows 2008 R2.
Posted by Microsoft on 1/29/2013 at 5:08 PM

We took a look at this bug along with several others recently.
Unfortunately, triaging it against other critical bugs, I do not think we would get to investigating this in the near future.
However, we have taken note of this internally, and when we revisit this functionality in the future, we will try and get this resolved.

Thanks for writing in to Microsoft.
Alex Grach[MSFT]
Posted by Microsoft on 1/15/2013 at 11:15 AM
Thank you for reporting this issue - we are investigating and will update you when we have more information.


Sign in to post a workaround.