0
hi there, 
            i am getting this error while activity monitoring on sql server 2008 R2(SP2) and at the same time all the users application (i.e arround 200 users window user application) connected to the database in this server gets Hang and again starts functioning properly after 1 or 2 mins and this is happening 4 - 5 times a day ,i searched for this problem on web but have'nt got any solution to the same 
            so,i will be thankfull if anyone can provide me the solution to this problem.


    ===================================

    The Activity Monitor is unable to execute queries against server NEXSUSDBMSSQLSERVER1.
    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.

    ===================================

    Could not find stored procedure '#am_get_querystats'. (.Net SqlClient Data Provider)

    ------------------------------
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600&EvtSrc=MSSQLServer&EvtID=2812&LinkId=20476

    ------------------------------
    Server Name: NEXSUSDBMSSQLSERVER1
    Error Number: 2812
    Severity: 16
    State: 62
    Line Number: 1


    ------------------------------
    Program Location:

       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
       at System.Data.SqlClient.SqlDataReader.get_MetaData()
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
       at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
       at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
       at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
       at Microsoft.SqlServer.Management.ResourceMonitoring.BackgroundQueryTask.Execute()
       at Microsoft.SqlServer.Management.ResourceMonitoring.BackgroundWorkRequest.Execute()
       at Microsoft.SqlServer.Management.ResourceMonitoring.BackgroundWorkRequestQueue.BackgroundWorker_DoWork(Object sender, DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Edited by mandar_palse

2
Contributors
1
Reply
21
Views
3 Years
Discussion Span
Last Post by Daemon_CC
0

it may typically relate back to an issue during the installation or an upgrade.
or
Check the schema the stored procedure belongs to on your host - it could be that it's not in the "dbo" schema.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.