Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
misc
exam.security
microsoft_update_catalog
msdn.annotations
msdn.drgui.discussion
msdn.duwamish
msdn.general
msdn.magazine
msdn.soaptoolkit
msdn.webservices
msdntraining
opsmgr.connectors
opsmgr.sp1
technet
technet.howtofeedback
technet.howtoneeds
technet.magazine
technet.technettalks
  
 
date: Fri, 18 Jul 2008 09:11:03 -0700,    group: microsoft.public.opsmgr.sp1        back       


Console is constantly throwing exceptions.    
Right after moving to SP1-RTM all of our consoles are throwing exceptions. 
I'll include the code blurb but it still makes no sense. 

I've added the /ClearCache switch to all of them. It only helps a little.

Researching the 26319 error only brings up a patch for the 5000 series build. 

Are there patches I'm missing?

***

Event Type:	Error
Event Source:	OpsMgr SDK Service
Event Category:	None
Event ID:	26319
Date:		7/18/2008
Time:		11:59:32 AM
User:		N/A
Computer:	NAUSBF-MOMP02
Description:
An exception was thrown while processing GetObjectsFromReader for session id 
uuid:da8a6e40-4079-41ea-a8f8-e9afd8ce7966;id=140.
 Exception Message: ExecuteScalar requires an open and available Connection. 
The connection's current state is closed.
 Full Exception: 
Microsoft.EnterpriseManagement.Common.InvalidConnectionException: 
ExecuteScalar requires an open and available Connection. The connection's 
current state is closed. ---> System.InvalidOperationException: ExecuteScalar 
requires an open and available Connection. The connection's current state is 
closed.
   at System.Data.SqlClient.SqlConnection.GetOpenConnection(String method)
   at 
System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String 
method, SqlCommand command)
   at System.Data.SqlClient.SqlCommand.ValidateCommand(String method, 
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.ExecuteScalar()
   at 
Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments 
executeArguments, RetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   --- End of inner exception stack trace ---
   at 
Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments 
executeArguments, RetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at 
Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader 
sqlDataReader, SqlConnection sqlConnection, IList`1 prologEpilogList, 
RetryPolicy retryPolicy)
   at Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
   at 
Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid id, Int32 count)
   at 
Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid readerId, Int32 count)
   at 
Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid readerId, Int32 count)
   at 
Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid readerId, Int32 count)

For more information, see Help and Support Center at 
http://go.microsoft.com/fwlink/events.asp.
date: Fri, 18 Jul 2008 09:11:03 -0700   author:   Jeff Prusinski

Re: Console is constantly throwing exceptions.    
Jeff,
What view(s) are you opening where you get this exception?  I'm guessing the 
Alerts view right?
If so, can you check your Alert Table to see if you have Alerts with a high 
repeat count?

SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
FROM Alert
WHERE ResolutionState = 0
 AND RepeatCount > 0
ORDER BY COUNT(*) DESC

-- 
Michael Pearson
-------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at 
http://www.microsoft.com/info/cpyright.htm
-------------------------

"Jeff Prusinski"  wrote in message 
news:BBA6FF1B-0ED9-44AD-B75B-46C369B20E47@microsoft.com...
> Right after moving to SP1-RTM all of our consoles are throwing exceptions.
> I'll include the code blurb but it still makes no sense.
>
> I've added the /ClearCache switch to all of them. It only helps a little.
>
> Researching the 26319 error only brings up a patch for the 5000 series 
> build.
>
> Are there patches I'm missing?
>
> ***
>
> Event Type: Error
> Event Source: OpsMgr SDK Service
> Event Category: None
> Event ID: 26319
> Date: 7/18/2008
> Time: 11:59:32 AM
> User: N/A
> Computer: NAUSBF-MOMP02
> Description:
> An exception was thrown while processing GetObjectsFromReader for session 
> id
> uuid:da8a6e40-4079-41ea-a8f8-e9afd8ce7966;id=140.
> Exception Message: ExecuteScalar requires an open and available 
> Connection.
> The connection's current state is closed.
> Full Exception:
> Microsoft.EnterpriseManagement.Common.InvalidConnectionException:
> ExecuteScalar requires an open and available Connection. The connection's
> current state is closed. ---> System.InvalidOperationException: 
> ExecuteScalar
> requires an open and available Connection. The connection's current state 
> is
> closed.
>   at System.Data.SqlClient.SqlConnection.GetOpenConnection(String method)
>   at
> System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
> method, SqlCommand command)
>   at System.Data.SqlClient.SqlCommand.ValidateCommand(String method,
> 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.ExecuteScalar()
>   at
> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
> genericExecute)
>   --- End of inner exception stack trace ---
>   at
> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
> genericExecute)
>   at
> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader
> sqlDataReader, SqlConnection sqlConnection, IList`1 prologEpilogList,
> RetryPolicy retryPolicy)
>   at 
> Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
>   at
> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid 
> id, Int32 count)
>   at
> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid 
> readerId, Int32 count)
>   at
> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid 
> readerId, Int32 count)
>   at
> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid 
> readerId, Int32 count)
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
>
date: Fri, 18 Jul 2008 15:44:27 -0700   author:   Michael Pearson [MSFT]

Re: Console is constantly throwing exceptions.    
I left out a key part of that script.  Here's a working version  :)
So, if we see a lot of alerts with high repeat counts, we have two ways or 
proceed:
1.  Give you a script that will change how we handle repeated alerts so that 
we do not update the Context field.  That makes the exception you are seeing 
go away

2.  Track down the rules / monitors that are generating these repeated 
alerts and tune them / disable them.

SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
FROM Alert
WHERE ResolutionState = 0
 AND RepeatCount > 0
GROUP BY RepeatCount
ORDER BY COUNT(*) DESC

-- 
Michael Pearson
-------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at 
http://www.microsoft.com/info/cpyright.htm
-------------------------

"Michael Pearson [MSFT]"  wrote in message 
news:%23GICWfS6IHA.3512@TK2MSFTNGP02.phx.gbl...
> Jeff,
> What view(s) are you opening where you get this exception?  I'm guessing 
> the Alerts view right?
> If so, can you check your Alert Table to see if you have Alerts with a 
> high repeat count?
>
> SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
> FROM Alert
> WHERE ResolutionState = 0
> AND RepeatCount > 0
> ORDER BY COUNT(*) DESC
>
> -- 
> Michael Pearson
> -------------------------
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
> Use of included script samples are subject to the terms specified at 
> http://www.microsoft.com/info/cpyright.htm
> -------------------------
>
> "Jeff Prusinski"  wrote in 
> message news:BBA6FF1B-0ED9-44AD-B75B-46C369B20E47@microsoft.com...
>> Right after moving to SP1-RTM all of our consoles are throwing 
>> exceptions.
>> I'll include the code blurb but it still makes no sense.
>>
>> I've added the /ClearCache switch to all of them. It only helps a little.
>>
>> Researching the 26319 error only brings up a patch for the 5000 series 
>> build.
>>
>> Are there patches I'm missing?
>>
>> ***
>>
>> Event Type: Error
>> Event Source: OpsMgr SDK Service
>> Event Category: None
>> Event ID: 26319
>> Date: 7/18/2008
>> Time: 11:59:32 AM
>> User: N/A
>> Computer: NAUSBF-MOMP02
>> Description:
>> An exception was thrown while processing GetObjectsFromReader for session 
>> id
>> uuid:da8a6e40-4079-41ea-a8f8-e9afd8ce7966;id=140.
>> Exception Message: ExecuteScalar requires an open and available 
>> Connection.
>> The connection's current state is closed.
>> Full Exception:
>> Microsoft.EnterpriseManagement.Common.InvalidConnectionException:
>> ExecuteScalar requires an open and available Connection. The connection's
>> current state is closed. ---> System.InvalidOperationException: 
>> ExecuteScalar
>> requires an open and available Connection. The connection's current state 
>> is
>> closed.
>>   at System.Data.SqlClient.SqlConnection.GetOpenConnection(String method)
>>   at
>> System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
>> method, SqlCommand command)
>>   at System.Data.SqlClient.SqlCommand.ValidateCommand(String method,
>> 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.ExecuteScalar()
>>   at
>> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
>> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
>> genericExecute)
>>   --- End of inner exception stack trace ---
>>   at
>> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
>> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
>> genericExecute)
>>   at
>> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader
>> sqlDataReader, SqlConnection sqlConnection, IList`1 prologEpilogList,
>> RetryPolicy retryPolicy)
>>   at 
>> Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
>>   at
>> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid 
>> id, Int32 count)
>>   at
>> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid 
>> readerId, Int32 count)
>>   at
>> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid 
>> readerId, Int32 count)
>>   at
>> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid 
>> readerId, Int32 count)
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>>
>>
>
date: Fri, 18 Jul 2008 19:18:18 -0700   author:   Michael Pearson [MSFT]

Re: Console is constantly throwing exceptions.    
Rob from MSFT mentioned this also and found this way to look at them similar 
information. 

Thanks both Mike and Rob. Will post back here with results.

***********

I looked up the error and found the following.  Does this match your scenario?

 

See below - 

 

Ok, here’s what’shappening with this error.  In the SQL Server error logs at 
about the sametime as the console exception happened, you should see an error 
with a descriptionof “A read operation on a large object failed while sending 
data to the client. A common cause for this is if the application is running 
in READ UNCOMMITTED isolation level. This connection will be terminated.”  
What we’ve seen is that a user has the Console open on an Alerts View.  While 
the Alerts View is opening or refreshing, there are Alerts coming in that are 
repeated Alerts which updates the Repeat Count and Context fields for that 
Alert.  Since the Context field is a “large object” type field, and the Alert 
View queries have NOLOCK hints in them, The Alert View has already “read” 
this changing Alert.  That gives us a dirty read and SQL Server disconnects 
that SQL Connection since we’ve tried to do a dirty read on a “large object” 
field which is not allowed.  So, since that connection is disconnected the 
next line of SDK code that tries to use this connection that it thinks is 
still open will cause this “Execute Scalar requires an open and available 
Connection. The connection's current state is closed.”Error since the SQL 
Connection is closed.

 

Now, how do you fix this?

One way is to eliminate any diskperf issues so that reads and write happen 
very quickly and the user should probably never see this issue again.  The 
root cause for another of our customers was an unhealthy monitored 
environment.  They had 400+ Active Alerts, with many of those Alerts having 
Repeat Counts of over 10,000.  What was happening was they had several SMS 
2003 machines that were throwing an Alert every 30-60 seconds.  This caused 
Alerts to be updated every 30-60seconds, which greatly increased the likely 
hood of hitting this “dirty read” condition.  The solution was to address the 
Alerts and make the problem go away or disable / override the Rules that were 
generating all these repeated Alerts.

 

Here’s a set of troubleshooting scripts from *** Wang on this from the 
Microsoft.Public.OpsMgr.UInewsgroup:

 

Hi Idan

Here is a procedure you can use to find the alert with high repeat counts.

1 Run the following 2 SQL queries and save the result to 2 csv files.
2 Wait a 30 minutes or so
3 Run the following 2 SQL queries and save the result to 2 csv files.
4 Use windiff to compare the old csv files and new csv files, from the 
difference, you will find which rule / monitor's repeat counter is changing 
and how much it has changed, this will tell you which rules / monitor has 
send alert to DB and how much times it has sent.

Hope this will help.

***



-- Get statistics for rule generated alerts

select

rulename as RuleName,

MT1.typename as TargetTypeBase,

MT2.typename as TargetType,

mpname as MPName,

count(*) as RuleAlertNumber,

sum(repeatcount + 1) as RuleAlertTotalNumber

from alert with(nolock)

inner join basemanagedentity with(nolock)

on alert.basemanagedentityid = basemanagedentity.basemanagedentityid

inner join managedtype as MT1 with(nolock)

on basemanagedentity.basemanagedtypeid = MT1.ManagedTypeId

inner join rules with(nolock)

on alert.ruleid = rules.ruleid

inner join managedtype as MT2 with(nolock)

on rules.targetmanagedentitytype = MT2.managedtypeid

inner join managementpack with(nolock)

on rules.managementpackid = managementpack.managementpackid

group by rules.ruleid, rulename, MT1.typename, MT2.typename, mpname

order by rulename desc



-- Get statistics for monitor generated alerts

select

monitorname as MonitorName,

MT1.typename as TargetTypeBase,

MT2.typename as TargetType,

mpname as MPName,

count(*) as MonitorAlertNumber,

sum(repeatcount + 1) as MonitorAlertTotalNumber

from alert with(nolock)

inner join basemanagedentity with(nolock)

on alert.basemanagedentityid = basemanagedentity.basemanagedentityid

inner join managedtype as MT1 with(nolock)

on basemanagedentity.basemanagedtypeid = MT1.ManagedTypeId

inner join monitor with(nolock)

on alert.ruleid = monitor.monitorid

inner join managedtype as MT2 with(nolock)

on monitor.targetmanagedentitytype = MT2.managedtypeid

inner join managementpack with(nolock)

on monitor.managementpackid = managementpack.managementpackid

group by monitor.monitorid, monitorname, MT1.typename, MT2.typename, mpname

order by monitorname desc


"Michael Pearson [MSFT]" wrote:

> I left out a key part of that script.  Here's a working version  :)
> So, if we see a lot of alerts with high repeat counts, we have two ways or 
> proceed:
> 1.  Give you a script that will change how we handle repeated alerts so that 
> we do not update the Context field.  That makes the exception you are seeing 
> go away
> 
> 2.  Track down the rules / monitors that are generating these repeated 
> alerts and tune them / disable them.
> 
> SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
> FROM Alert
> WHERE ResolutionState = 0
>  AND RepeatCount > 0
> GROUP BY RepeatCount
> ORDER BY COUNT(*) DESC
> 
> -- 
> Michael Pearson
> -------------------------
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at 
> http://www.microsoft.com/info/cpyright.htm
> -------------------------
> 
> "Michael Pearson [MSFT]"  wrote in message 
> news:%23GICWfS6IHA.3512@TK2MSFTNGP02.phx.gbl...
> > Jeff,
> > What view(s) are you opening where you get this exception?  I'm guessing 
> > the Alerts view right?
> > If so, can you check your Alert Table to see if you have Alerts with a 
> > high repeat count?
> >
> > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
> > FROM Alert
> > WHERE ResolutionState = 0
> > AND RepeatCount > 0
> > ORDER BY COUNT(*) DESC
> >
> > -- 
> > Michael Pearson
> > -------------------------
> > This posting is provided "AS IS" with no warranties, and confers no 
> > rights.
> > Use of included script samples are subject to the terms specified at 
> > http://www.microsoft.com/info/cpyright.htm
> > -------------------------
> >
> > "Jeff Prusinski"  wrote in 
> > message news:BBA6FF1B-0ED9-44AD-B75B-46C369B20E47@microsoft.com...
> >> Right after moving to SP1-RTM all of our consoles are throwing 
> >> exceptions.
> >> I'll include the code blurb but it still makes no sense.
> >>
> >> I've added the /ClearCache switch to all of them. It only helps a little.
> >>
> >> Researching the 26319 error only brings up a patch for the 5000 series 
> >> build.
> >>
> >> Are there patches I'm missing?
> >>
> >> ***
> >>
> >> Event Type: Error
> >> Event Source: OpsMgr SDK Service
> >> Event Category: None
> >> Event ID: 26319
> >> Date: 7/18/2008
> >> Time: 11:59:32 AM
> >> User: N/A
> >> Computer: NAUSBF-MOMP02
> >> Description:
> >> An exception was thrown while processing GetObjectsFromReader for session 
> >> id
> >> uuid:da8a6e40-4079-41ea-a8f8-e9afd8ce7966;id=140.
> >> Exception Message: ExecuteScalar requires an open and available 
> >> Connection.
> >> The connection's current state is closed.
> >> Full Exception:
> >> Microsoft.EnterpriseManagement.Common.InvalidConnectionException:
> >> ExecuteScalar requires an open and available Connection. The connection's
> >> current state is closed. ---> System.InvalidOperationException: 
> >> ExecuteScalar
> >> requires an open and available Connection. The connection's current state 
> >> is
> >> closed.
> >>   at System.Data.SqlClient.SqlConnection.GetOpenConnection(String method)
> >>   at
> >> System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
> >> method, SqlCommand command)
> >>   at System.Data.SqlClient.SqlCommand.ValidateCommand(String method,
> >> 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.ExecuteScalar()
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
> >> genericExecute)
> >>   --- End of inner exception stack trace ---
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
> >> genericExecute)
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader
> >> sqlDataReader, SqlConnection sqlConnection, IList`1 prologEpilogList,
> >> RetryPolicy retryPolicy)
> >>   at 
> >> Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid 
> >> id, Int32 count)
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid 
> >> readerId, Int32 count)
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid 
> >> readerId, Int32 count)
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid 
> >> readerId, Int32 count)
> >>
> >> For more information, see Help and Support Center at
> >> http://go.microsoft.com/fwlink/events.asp.
> >>
> >>
> >>
> > 
> 
>
date: Mon, 21 Jul 2008 07:03:37 -0700   author:   Jeff Prusinski

Re: Console is constantly throwing exceptions.    
Thanks Michael. 

The scripts you provided generated a table with repeat count and number of 
alerts with repeat count but as far as I could see didn't generate the name 
of the alert. Using the scripts Rob found I was able to find something. 

Nothing showed up for the 'monitors' query, there was no difference between 
the two outputs.

The first alert was - "Performance Data Source Modeule Could not find a 
performance counter" - The count was literally 1000's upon 1000's of alerts. 
As it was impossible to even use the console I disabled this alert and will 
have to go back and figure out why it's alerting on all our Managed Agents. 
Maybe the upgrade missed some code on the Agents?

The next highest count alert is - 
"One_or_more_domain_controllers_may_not_be_replicating" repeated 586 times in 
~32 minutes. How do I track this one down?

Jeff.

"Michael Pearson [MSFT]" wrote:

> I left out a key part of that script.  Here's a working version  :)
> So, if we see a lot of alerts with high repeat counts, we have two ways or 
> proceed:
> 1.  Give you a script that will change how we handle repeated alerts so that 
> we do not update the Context field.  That makes the exception you are seeing 
> go away
> 
> 2.  Track down the rules / monitors that are generating these repeated 
> alerts and tune them / disable them.
> 
> SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
> FROM Alert
> WHERE ResolutionState = 0
>  AND RepeatCount > 0
> GROUP BY RepeatCount
> ORDER BY COUNT(*) DESC
> 
> -- 
> Michael Pearson
> -------------------------
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at 
> http://www.microsoft.com/info/cpyright.htm
> -------------------------
> 
> "Michael Pearson [MSFT]"  wrote in message 
> news:%23GICWfS6IHA.3512@TK2MSFTNGP02.phx.gbl...
> > Jeff,
> > What view(s) are you opening where you get this exception?  I'm guessing 
> > the Alerts view right?
> > If so, can you check your Alert Table to see if you have Alerts with a 
> > high repeat count?
> >
> > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
> > FROM Alert
> > WHERE ResolutionState = 0
> > AND RepeatCount > 0
> > ORDER BY COUNT(*) DESC
> >
> > -- 
> > Michael Pearson
> > -------------------------
> > This posting is provided "AS IS" with no warranties, and confers no 
> > rights.
> > Use of included script samples are subject to the terms specified at 
> > http://www.microsoft.com/info/cpyright.htm
> > -------------------------
> >
> > "Jeff Prusinski"  wrote in 
> > message news:BBA6FF1B-0ED9-44AD-B75B-46C369B20E47@microsoft.com...
> >> Right after moving to SP1-RTM all of our consoles are throwing 
> >> exceptions.
> >> I'll include the code blurb but it still makes no sense.
> >>
> >> I've added the /ClearCache switch to all of them. It only helps a little.
> >>
> >> Researching the 26319 error only brings up a patch for the 5000 series 
> >> build.
> >>
> >> Are there patches I'm missing?
> >>
> >> ***
> >>
> >> Event Type: Error
> >> Event Source: OpsMgr SDK Service
> >> Event Category: None
> >> Event ID: 26319
> >> Date: 7/18/2008
> >> Time: 11:59:32 AM
> >> User: N/A
> >> Computer: NAUSBF-MOMP02
> >> Description:
> >> An exception was thrown while processing GetObjectsFromReader for session 
> >> id
> >> uuid:da8a6e40-4079-41ea-a8f8-e9afd8ce7966;id=140.
> >> Exception Message: ExecuteScalar requires an open and available 
> >> Connection.
> >> The connection's current state is closed.
> >> Full Exception:
> >> Microsoft.EnterpriseManagement.Common.InvalidConnectionException:
> >> ExecuteScalar requires an open and available Connection. The connection's
> >> current state is closed. ---> System.InvalidOperationException: 
> >> ExecuteScalar
> >> requires an open and available Connection. The connection's current state 
> >> is
> >> closed.
> >>   at System.Data.SqlClient.SqlConnection.GetOpenConnection(String method)
> >>   at
> >> System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
> >> method, SqlCommand command)
> >>   at System.Data.SqlClient.SqlCommand.ValidateCommand(String method,
> >> 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.ExecuteScalar()
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
> >> genericExecute)
> >>   --- End of inner exception stack trace ---
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
> >> genericExecute)
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader
> >> sqlDataReader, SqlConnection sqlConnection, IList`1 prologEpilogList,
> >> RetryPolicy retryPolicy)
> >>   at 
> >> Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid 
> >> id, Int32 count)
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid 
> >> readerId, Int32 count)
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid 
> >> readerId, Int32 count)
> >>   at
> >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid 
> >> readerId, Int32 count)
> >>
> >> For more information, see Help and Support Center at
> >> http://go.microsoft.com/fwlink/events.asp.
> >>
> >>
> >>
> > 
> 
>
date: Mon, 21 Jul 2008 08:08:03 -0700   author:   Jeff Prusinski

Re: Console is constantly throwing exceptions.    
Found it under the AD Monitoring MP. Now am going to figure out what to do 
with it.

Now I have to figure out what the "Performance Data Source Module Could not 
find a performance counter" issue is.


"Jeff Prusinski" wrote:

> Thanks Michael. 
> 
> The scripts you provided generated a table with repeat count and number of 
> alerts with repeat count but as far as I could see didn't generate the name 
> of the alert. Using the scripts Rob found I was able to find something. 
> 
> Nothing showed up for the 'monitors' query, there was no difference between 
> the two outputs.
> 
> The first alert was - "Performance Data Source Modeule Could not find a 
> performance counter" - The count was literally 1000's upon 1000's of alerts. 
> As it was impossible to even use the console I disabled this alert and will 
> have to go back and figure out why it's alerting on all our Managed Agents. 
> Maybe the upgrade missed some code on the Agents?
> 
> The next highest count alert is - 
> "One_or_more_domain_controllers_may_not_be_replicating" repeated 586 times in 
> ~32 minutes. How do I track this one down?
> 
> Jeff.
> 
> "Michael Pearson [MSFT]" wrote:
> 
> > I left out a key part of that script.  Here's a working version  :)
> > So, if we see a lot of alerts with high repeat counts, we have two ways or 
> > proceed:
> > 1.  Give you a script that will change how we handle repeated alerts so that 
> > we do not update the Context field.  That makes the exception you are seeing 
> > go away
> > 
> > 2.  Track down the rules / monitors that are generating these repeated 
> > alerts and tune them / disable them.
> > 
> > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
> > FROM Alert
> > WHERE ResolutionState = 0
> >  AND RepeatCount > 0
> > GROUP BY RepeatCount
> > ORDER BY COUNT(*) DESC
> > 
> > -- 
> > Michael Pearson
> > -------------------------
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > Use of included script samples are subject to the terms specified at 
> > http://www.microsoft.com/info/cpyright.htm
> > -------------------------
> > 
> > "Michael Pearson [MSFT]"  wrote in message 
> > news:%23GICWfS6IHA.3512@TK2MSFTNGP02.phx.gbl...
> > > Jeff,
> > > What view(s) are you opening where you get this exception?  I'm guessing 
> > > the Alerts view right?
> > > If so, can you check your Alert Table to see if you have Alerts with a 
> > > high repeat count?
> > >
> > > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
> > > FROM Alert
> > > WHERE ResolutionState = 0
> > > AND RepeatCount > 0
> > > ORDER BY COUNT(*) DESC
> > >
> > > -- 
> > > Michael Pearson
> > > -------------------------
> > > This posting is provided "AS IS" with no warranties, and confers no 
> > > rights.
> > > Use of included script samples are subject to the terms specified at 
> > > http://www.microsoft.com/info/cpyright.htm
> > > -------------------------
> > >
> > > "Jeff Prusinski"  wrote in 
> > > message news:BBA6FF1B-0ED9-44AD-B75B-46C369B20E47@microsoft.com...
> > >> Right after moving to SP1-RTM all of our consoles are throwing 
> > >> exceptions.
> > >> I'll include the code blurb but it still makes no sense.
> > >>
> > >> I've added the /ClearCache switch to all of them. It only helps a little.
> > >>
> > >> Researching the 26319 error only brings up a patch for the 5000 series 
> > >> build.
> > >>
> > >> Are there patches I'm missing?
> > >>
> > >> ***
> > >>
> > >> Event Type: Error
> > >> Event Source: OpsMgr SDK Service
> > >> Event Category: None
> > >> Event ID: 26319
> > >> Date: 7/18/2008
> > >> Time: 11:59:32 AM
> > >> User: N/A
> > >> Computer: NAUSBF-MOMP02
> > >> Description:
> > >> An exception was thrown while processing GetObjectsFromReader for session 
> > >> id
> > >> uuid:da8a6e40-4079-41ea-a8f8-e9afd8ce7966;id=140.
> > >> Exception Message: ExecuteScalar requires an open and available 
> > >> Connection.
> > >> The connection's current state is closed.
> > >> Full Exception:
> > >> Microsoft.EnterpriseManagement.Common.InvalidConnectionException:
> > >> ExecuteScalar requires an open and available Connection. The connection's
> > >> current state is closed. ---> System.InvalidOperationException: 
> > >> ExecuteScalar
> > >> requires an open and available Connection. The connection's current state 
> > >> is
> > >> closed.
> > >>   at System.Data.SqlClient.SqlConnection.GetOpenConnection(String method)
> > >>   at
> > >> System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
> > >> method, SqlCommand command)
> > >>   at System.Data.SqlClient.SqlCommand.ValidateCommand(String method,
> > >> 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.ExecuteScalar()
> > >>   at
> > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
> > >> genericExecute)
> > >>   --- End of inner exception stack trace ---
> > >>   at
> > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
> > >> genericExecute)
> > >>   at
> > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader
> > >> sqlDataReader, SqlConnection sqlConnection, IList`1 prologEpilogList,
> > >> RetryPolicy retryPolicy)
> > >>   at 
> > >> Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
> > >>   at
> > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid 
> > >> id, Int32 count)
> > >>   at
> > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid 
> > >> readerId, Int32 count)
> > >>   at
> > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid 
> > >> readerId, Int32 count)
> > >>   at
> > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid 
> > >> readerId, Int32 count)
> > >>
> > >> For more information, see Help and Support Center at
> > >> http://go.microsoft.com/fwlink/events.asp.
> > >>
> > >>
> > >>
> > > 
> > 
> >
date: Mon, 21 Jul 2008 11:05:01 -0700   author:   Jeff Prusinski

Re: Console is constantly throwing exceptions.    
And then I found this...

http://blogs.technet.com/momteam/archive/2008/03/01/performance-module-could-not-find-a-performance-counter.aspx

Looks like it's a problem for the developers to figure out.

Thanks all.

"Jeff Prusinski" wrote:

> Found it under the AD Monitoring MP. Now am going to figure out what to do 
> with it.
> 
> Now I have to figure out what the "Performance Data Source Module Could not 
> find a performance counter" issue is.
> 
> 
> "Jeff Prusinski" wrote:
> 
> > Thanks Michael. 
> > 
> > The scripts you provided generated a table with repeat count and number of 
> > alerts with repeat count but as far as I could see didn't generate the name 
> > of the alert. Using the scripts Rob found I was able to find something. 
> > 
> > Nothing showed up for the 'monitors' query, there was no difference between 
> > the two outputs.
> > 
> > The first alert was - "Performance Data Source Modeule Could not find a 
> > performance counter" - The count was literally 1000's upon 1000's of alerts. 
> > As it was impossible to even use the console I disabled this alert and will 
> > have to go back and figure out why it's alerting on all our Managed Agents. 
> > Maybe the upgrade missed some code on the Agents?
> > 
> > The next highest count alert is - 
> > "One_or_more_domain_controllers_may_not_be_replicating" repeated 586 times in 
> > ~32 minutes. How do I track this one down?
> > 
> > Jeff.
> > 
> > "Michael Pearson [MSFT]" wrote:
> > 
> > > I left out a key part of that script.  Here's a working version  :)
> > > So, if we see a lot of alerts with high repeat counts, we have two ways or 
> > > proceed:
> > > 1.  Give you a script that will change how we handle repeated alerts so that 
> > > we do not update the Context field.  That makes the exception you are seeing 
> > > go away
> > > 
> > > 2.  Track down the rules / monitors that are generating these repeated 
> > > alerts and tune them / disable them.
> > > 
> > > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
> > > FROM Alert
> > > WHERE ResolutionState = 0
> > >  AND RepeatCount > 0
> > > GROUP BY RepeatCount
> > > ORDER BY COUNT(*) DESC
> > > 
> > > -- 
> > > Michael Pearson
> > > -------------------------
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > Use of included script samples are subject to the terms specified at 
> > > http://www.microsoft.com/info/cpyright.htm
> > > -------------------------
> > > 
> > > "Michael Pearson [MSFT]"  wrote in message 
> > > news:%23GICWfS6IHA.3512@TK2MSFTNGP02.phx.gbl...
> > > > Jeff,
> > > > What view(s) are you opening where you get this exception?  I'm guessing 
> > > > the Alerts view right?
> > > > If so, can you check your Alert Table to see if you have Alerts with a 
> > > > high repeat count?
> > > >
> > > > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
> > > > FROM Alert
> > > > WHERE ResolutionState = 0
> > > > AND RepeatCount > 0
> > > > ORDER BY COUNT(*) DESC
> > > >
> > > > -- 
> > > > Michael Pearson
> > > > -------------------------
> > > > This posting is provided "AS IS" with no warranties, and confers no 
> > > > rights.
> > > > Use of included script samples are subject to the terms specified at 
> > > > http://www.microsoft.com/info/cpyright.htm
> > > > -------------------------
> > > >
> > > > "Jeff Prusinski"  wrote in 
> > > > message news:BBA6FF1B-0ED9-44AD-B75B-46C369B20E47@microsoft.com...
> > > >> Right after moving to SP1-RTM all of our consoles are throwing 
> > > >> exceptions.
> > > >> I'll include the code blurb but it still makes no sense.
> > > >>
> > > >> I've added the /ClearCache switch to all of them. It only helps a little.
> > > >>
> > > >> Researching the 26319 error only brings up a patch for the 5000 series 
> > > >> build.
> > > >>
> > > >> Are there patches I'm missing?
> > > >>
> > > >> ***
> > > >>
> > > >> Event Type: Error
> > > >> Event Source: OpsMgr SDK Service
> > > >> Event Category: None
> > > >> Event ID: 26319
> > > >> Date: 7/18/2008
> > > >> Time: 11:59:32 AM
> > > >> User: N/A
> > > >> Computer: NAUSBF-MOMP02
> > > >> Description:
> > > >> An exception was thrown while processing GetObjectsFromReader for session 
> > > >> id
> > > >> uuid:da8a6e40-4079-41ea-a8f8-e9afd8ce7966;id=140.
> > > >> Exception Message: ExecuteScalar requires an open and available 
> > > >> Connection.
> > > >> The connection's current state is closed.
> > > >> Full Exception:
> > > >> Microsoft.EnterpriseManagement.Common.InvalidConnectionException:
> > > >> ExecuteScalar requires an open and available Connection. The connection's
> > > >> current state is closed. ---> System.InvalidOperationException: 
> > > >> ExecuteScalar
> > > >> requires an open and available Connection. The connection's current state 
> > > >> is
> > > >> closed.
> > > >>   at System.Data.SqlClient.SqlConnection.GetOpenConnection(String method)
> > > >>   at
> > > >> System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
> > > >> method, SqlCommand command)
> > > >>   at System.Data.SqlClient.SqlCommand.ValidateCommand(String method,
> > > >> 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.ExecuteScalar()
> > > >>   at
> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> > > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
> > > >> genericExecute)
> > > >>   --- End of inner exception stack trace ---
> > > >>   at
> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> > > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1 
> > > >> genericExecute)
> > > >>   at
> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader
> > > >> sqlDataReader, SqlConnection sqlConnection, IList`1 prologEpilogList,
> > > >> RetryPolicy retryPolicy)
> > > >>   at 
> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
> > > >>   at
> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid 
> > > >> id, Int32 count)
> > > >>   at
> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid 
> > > >> readerId, Int32 count)
> > > >>   at
> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid 
> > > >> readerId, Int32 count)
> > > >>   at
> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid 
> > > >> readerId, Int32 count)
> > > >>
> > > >> For more information, see Help and Support Center at
> > > >> http://go.microsoft.com/fwlink/events.asp.
> > > >>
> > > >>
> > > >>
> > > > 
> > > 
> > >
date: Mon, 21 Jul 2008 12:28:01 -0700   author:   Jeff Prusinski

Re: Console is constantly throwing exceptions.    
Jeff,
It looks like we have a hotfix which may address the "Performance Module 
could not find a performance counter" issue.  Take a look at this KB article 
and see if that applies to you.

http://support.microsoft.com/kb/951979/en-us

-- 
Michael Pearson
-------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at 
http://www.microsoft.com/info/cpyright.htm
-------------------------

"Jeff Prusinski"  wrote in message 
news:2EBBD39E-AF74-4346-A31A-FFC0EAAC294B@microsoft.com...
> And then I found this...
>
> http://blogs.technet.com/momteam/archive/2008/03/01/performance-module-could-not-find-a-performance-counter.aspx
>
> Looks like it's a problem for the developers to figure out.
>
> Thanks all.
>
> "Jeff Prusinski" wrote:
>
>> Found it under the AD Monitoring MP. Now am going to figure out what to 
>> do
>> with it.
>>
>> Now I have to figure out what the "Performance Data Source Module Could 
>> not
>> find a performance counter" issue is.
>>
>>
>> "Jeff Prusinski" wrote:
>>
>> > Thanks Michael.
>> >
>> > The scripts you provided generated a table with repeat count and number 
>> > of
>> > alerts with repeat count but as far as I could see didn't generate the 
>> > name
>> > of the alert. Using the scripts Rob found I was able to find something.
>> >
>> > Nothing showed up for the 'monitors' query, there was no difference 
>> > between
>> > the two outputs.
>> >
>> > The first alert was - "Performance Data Source Modeule Could not find a
>> > performance counter" - The count was literally 1000's upon 1000's of 
>> > alerts.
>> > As it was impossible to even use the console I disabled this alert and 
>> > will
>> > have to go back and figure out why it's alerting on all our Managed 
>> > Agents.
>> > Maybe the upgrade missed some code on the Agents?
>> >
>> > The next highest count alert is -
>> > "One_or_more_domain_controllers_may_not_be_replicating" repeated 586 
>> > times in
>> > ~32 minutes. How do I track this one down?
>> >
>> > Jeff.
>> >
>> > "Michael Pearson [MSFT]" wrote:
>> >
>> > > I left out a key part of that script.  Here's a working version  :)
>> > > So, if we see a lot of alerts with high repeat counts, we have two 
>> > > ways or
>> > > proceed:
>> > > 1.  Give you a script that will change how we handle repeated alerts 
>> > > so that
>> > > we do not update the Context field.  That makes the exception you are 
>> > > seeing
>> > > go away
>> > >
>> > > 2.  Track down the rules / monitors that are generating these 
>> > > repeated
>> > > alerts and tune them / disable them.
>> > >
>> > > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
>> > > FROM Alert
>> > > WHERE ResolutionState = 0
>> > >  AND RepeatCount > 0
>> > > GROUP BY RepeatCount
>> > > ORDER BY COUNT(*) DESC
>> > >
>> > > -- 
>> > > Michael Pearson
>> > > -------------------------
>> > > This posting is provided "AS IS" with no warranties, and confers no 
>> > > rights.
>> > > Use of included script samples are subject to the terms specified at
>> > > http://www.microsoft.com/info/cpyright.htm
>> > > -------------------------
>> > >
>> > > "Michael Pearson [MSFT]"  wrote in 
>> > > message
>> > > news:%23GICWfS6IHA.3512@TK2MSFTNGP02.phx.gbl...
>> > > > Jeff,
>> > > > What view(s) are you opening where you get this exception?  I'm 
>> > > > guessing
>> > > > the Alerts view right?
>> > > > If so, can you check your Alert Table to see if you have Alerts 
>> > > > with a
>> > > > high repeat count?
>> > > >
>> > > > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
>> > > > FROM Alert
>> > > > WHERE ResolutionState = 0
>> > > > AND RepeatCount > 0
>> > > > ORDER BY COUNT(*) DESC
>> > > >
>> > > > -- 
>> > > > Michael Pearson
>> > > > -------------------------
>> > > > This posting is provided "AS IS" with no warranties, and confers no
>> > > > rights.
>> > > > Use of included script samples are subject to the terms specified 
>> > > > at
>> > > > http://www.microsoft.com/info/cpyright.htm
>> > > > -------------------------
>> > > >
>> > > > "Jeff Prusinski"  wrote in
>> > > > message news:BBA6FF1B-0ED9-44AD-B75B-46C369B20E47@microsoft.com...
>> > > >> Right after moving to SP1-RTM all of our consoles are throwing
>> > > >> exceptions.
>> > > >> I'll include the code blurb but it still makes no sense.
>> > > >>
>> > > >> I've added the /ClearCache switch to all of them. It only helps a 
>> > > >> little.
>> > > >>
>> > > >> Researching the 26319 error only brings up a patch for the 5000 
>> > > >> series
>> > > >> build.
>> > > >>
>> > > >> Are there patches I'm missing?
>> > > >>
>> > > >> ***
>> > > >>
>> > > >> Event Type: Error
>> > > >> Event Source: OpsMgr SDK Service
>> > > >> Event Category: None
>> > > >> Event ID: 26319
>> > > >> Date: 7/18/2008
>> > > >> Time: 11:59:32 AM
>> > > >> User: N/A
>> > > >> Computer: NAUSBF-MOMP02
>> > > >> Description:
>> > > >> An exception was thrown while processing GetObjectsFromReader for 
>> > > >> session
>> > > >> id
>> > > >> uuid:da8a6e40-4079-41ea-a8f8-e9afd8ce7966;id=140.
>> > > >> Exception Message: ExecuteScalar requires an open and available
>> > > >> Connection.
>> > > >> The connection's current state is closed.
>> > > >> Full Exception:
>> > > >> Microsoft.EnterpriseManagement.Common.InvalidConnectionException:
>> > > >> ExecuteScalar requires an open and available Connection. The 
>> > > >> connection's
>> > > >> current state is closed. ---> System.InvalidOperationException:
>> > > >> ExecuteScalar
>> > > >> requires an open and available Connection. The connection's 
>> > > >> current state
>> > > >> is
>> > > >> closed.
>> > > >>   at System.Data.SqlClient.SqlConnection.GetOpenConnection(String 
>> > > >> method)
>> > > >>   at
>> > > >> System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
>> > > >> method, SqlCommand command)
>> > > >>   at System.Data.SqlClient.SqlCommand.ValidateCommand(String 
>> > > >> method,
>> > > >> 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.ExecuteScalar()
>> > > >>   at
>> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
>> > > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1
>> > > >> genericExecute)
>> > > >>   --- End of inner exception stack trace ---
>> > > >>   at
>> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
>> > > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1
>> > > >> genericExecute)
>> > > >>   at
>> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader
>> > > >> sqlDataReader, SqlConnection sqlConnection, IList`1 
>> > > >> prologEpilogList,
>> > > >> RetryPolicy retryPolicy)
>> > > >>   at
>> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
>> > > >>   at
>> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid
>> > > >> id, Int32 count)
>> > > >>   at
>> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid
>> > > >> readerId, Int32 count)
>> > > >>   at
>> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid
>> > > >> readerId, Int32 count)
>> > > >>   at
>> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid
>> > > >> readerId, Int32 count)
>> > > >>
>> > > >> For more information, see Help and Support Center at
>> > > >> http://go.microsoft.com/fwlink/events.asp.
>> > > >>
>> > > >>
>> > > >>
>> > > >
>> > >
>> > >
date: Thu, 24 Jul 2008 16:27:55 -0700   author:   Michael Pearson [MSFT]

Re: Console is constantly throwing exceptions.    
Thanks Michael,

We installed this patch directly after we did our RTM SP1 upgrade last week. 
The problems still remains. 

One thing we've noticed, as well, is that the sql log for the OpsMgr db is 
filling up with the following error, always with a different SPID- 

07/30/2008 08:37:35,spid68,Unknown,A read operation on a large object failed 
while sending data to the client. A common cause for this is if the 
application is running in READ UNCOMMITTED isolation level. This connection 
will be terminated.
07/30/2008 08:37:35,spid68,Unknown,Error: 7886<c/> Severity: 20<c/> State: 2.

Any ideas? I'll post to the sql group as well.

"Michael Pearson [MSFT]" wrote:

> Jeff,
> It looks like we have a hotfix which may address the "Performance Module 
> could not find a performance counter" issue.  Take a look at this KB article 
> and see if that applies to you.
> 
> http://support.microsoft.com/kb/951979/en-us
> 
> -- 
> Michael Pearson
> -------------------------
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at 
> http://www.microsoft.com/info/cpyright.htm
> -------------------------
> 
> "Jeff Prusinski"  wrote in message 
> news:2EBBD39E-AF74-4346-A31A-FFC0EAAC294B@microsoft.com...
> > And then I found this...
> >
> > http://blogs.technet.com/momteam/archive/2008/03/01/performance-module-could-not-find-a-performance-counter.aspx
> >
> > Looks like it's a problem for the developers to figure out.
> >
> > Thanks all.
> >
> > "Jeff Prusinski" wrote:
> >
> >> Found it under the AD Monitoring MP. Now am going to figure out what to 
> >> do
> >> with it.
> >>
> >> Now I have to figure out what the "Performance Data Source Module Could 
> >> not
> >> find a performance counter" issue is.
> >>
> >>
> >> "Jeff Prusinski" wrote:
> >>
> >> > Thanks Michael.
> >> >
> >> > The scripts you provided generated a table with repeat count and number 
> >> > of
> >> > alerts with repeat count but as far as I could see didn't generate the 
> >> > name
> >> > of the alert. Using the scripts Rob found I was able to find something.
> >> >
> >> > Nothing showed up for the 'monitors' query, there was no difference 
> >> > between
> >> > the two outputs.
> >> >
> >> > The first alert was - "Performance Data Source Modeule Could not find a
> >> > performance counter" - The count was literally 1000's upon 1000's of 
> >> > alerts.
> >> > As it was impossible to even use the console I disabled this alert and 
> >> > will
> >> > have to go back and figure out why it's alerting on all our Managed 
> >> > Agents.
> >> > Maybe the upgrade missed some code on the Agents?
> >> >
> >> > The next highest count alert is -
> >> > "One_or_more_domain_controllers_may_not_be_replicating" repeated 586 
> >> > times in
> >> > ~32 minutes. How do I track this one down?
> >> >
> >> > Jeff.
> >> >
> >> > "Michael Pearson [MSFT]" wrote:
> >> >
> >> > > I left out a key part of that script.  Here's a working version  :)
> >> > > So, if we see a lot of alerts with high repeat counts, we have two 
> >> > > ways or
> >> > > proceed:
> >> > > 1.  Give you a script that will change how we handle repeated alerts 
> >> > > so that
> >> > > we do not update the Context field.  That makes the exception you are 
> >> > > seeing
> >> > > go away
> >> > >
> >> > > 2.  Track down the rules / monitors that are generating these 
> >> > > repeated
> >> > > alerts and tune them / disable them.
> >> > >
> >> > > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
> >> > > FROM Alert
> >> > > WHERE ResolutionState = 0
> >> > >  AND RepeatCount > 0
> >> > > GROUP BY RepeatCount
> >> > > ORDER BY COUNT(*) DESC
> >> > >
> >> > > -- 
> >> > > Michael Pearson
> >> > > -------------------------
> >> > > This posting is provided "AS IS" with no warranties, and confers no 
> >> > > rights.
> >> > > Use of included script samples are subject to the terms specified at
> >> > > http://www.microsoft.com/info/cpyright.htm
> >> > > -------------------------
> >> > >
> >> > > "Michael Pearson [MSFT]"  wrote in 
> >> > > message
> >> > > news:%23GICWfS6IHA.3512@TK2MSFTNGP02.phx.gbl...
> >> > > > Jeff,
> >> > > > What view(s) are you opening where you get this exception?  I'm 
> >> > > > guessing
> >> > > > the Alerts view right?
> >> > > > If so, can you check your Alert Table to see if you have Alerts 
> >> > > > with a
> >> > > > high repeat count?
> >> > > >
> >> > > > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
> >> > > > FROM Alert
> >> > > > WHERE ResolutionState = 0
> >> > > > AND RepeatCount > 0
> >> > > > ORDER BY COUNT(*) DESC
> >> > > >
> >> > > > -- 
> >> > > > Michael Pearson
> >> > > > -------------------------
> >> > > > This posting is provided "AS IS" with no warranties, and confers no
> >> > > > rights.
> >> > > > Use of included script samples are subject to the terms specified 
> >> > > > at
> >> > > > http://www.microsoft.com/info/cpyright.htm
> >> > > > -------------------------
> >> > > >
> >> > > > "Jeff Prusinski"  wrote in
> >> > > > message news:BBA6FF1B-0ED9-44AD-B75B-46C369B20E47@microsoft.com...
> >> > > >> Right after moving to SP1-RTM all of our consoles are throwing
> >> > > >> exceptions.
> >> > > >> I'll include the code blurb but it still makes no sense.
> >> > > >>
> >> > > >> I've added the /ClearCache switch to all of them. It only helps a 
> >> > > >> little.
> >> > > >>
> >> > > >> Researching the 26319 error only brings up a patch for the 5000 
> >> > > >> series
> >> > > >> build.
> >> > > >>
> >> > > >> Are there patches I'm missing?
> >> > > >>
> >> > > >> ***
> >> > > >>
> >> > > >> Event Type: Error
> >> > > >> Event Source: OpsMgr SDK Service
> >> > > >> Event Category: None
> >> > > >> Event ID: 26319
> >> > > >> Date: 7/18/2008
> >> > > >> Time: 11:59:32 AM
> >> > > >> User: N/A
> >> > > >> Computer: NAUSBF-MOMP02
> >> > > >> Description:
> >> > > >> An exception was thrown while processing GetObjectsFromReader for 
> >> > > >> session
> >> > > >> id
> >> > > >> uuid:da8a6e40-4079-41ea-a8f8-e9afd8ce7966;id=140.
> >> > > >> Exception Message: ExecuteScalar requires an open and available
> >> > > >> Connection.
> >> > > >> The connection's current state is closed.
> >> > > >> Full Exception:
> >> > > >> Microsoft.EnterpriseManagement.Common.InvalidConnectionException:
> >> > > >> ExecuteScalar requires an open and available Connection. The 
> >> > > >> connection's
> >> > > >> current state is closed. ---> System.InvalidOperationException:
> >> > > >> ExecuteScalar
> >> > > >> requires an open and available Connection. The connection's 
> >> > > >> current state
> >> > > >> is
> >> > > >> closed.
> >> > > >>   at System.Data.SqlClient.SqlConnection.GetOpenConnection(String 
> >> > > >> method)
> >> > > >>   at
> >> > > >> System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
> >> > > >> method, SqlCommand command)
> >> > > >>   at System.Data.SqlClient.SqlCommand.ValidateCommand(String 
> >> > > >> method,
> >> > > >> 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.ExecuteScalar()
> >> > > >>   at
> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> >> > > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1
> >> > > >> genericExecute)
> >> > > >>   --- End of inner exception stack trace ---
> >> > > >>   at
> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
> >> > > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1
> >> > > >> genericExecute)
> >> > > >>   at
> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader
> >> > > >> sqlDataReader, SqlConnection sqlConnection, IList`1 
> >> > > >> prologEpilogList,
> >> > > >> RetryPolicy retryPolicy)
> >> > > >>   at
> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
> >> > > >>   at
> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid
> >> > > >> id, Int32 count)
> >> > > >>   at
> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid
> >> > > >> readerId, Int32 count)
> >> > > >>   at
> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid
> >> > > >> readerId, Int32 count)
> >> > > >>   at
> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid
> >> > > >> readerId, Int32 count)
> >> > > >>
> >> > > >> For more information, see Help and Support Center at
> >> > > >> http://go.microsoft.com/fwlink/events.asp.
> >> > > >>
> >> > > >>
> >> > > >>
> >> > > >
> >> > >
> >> > > 
> 
>
date: Wed, 30 Jul 2008 06:46:04 -0700   author:   Jeff Prusinski

Re: Console is constantly throwing exceptions.    
Ah yes, that issue.  I'm very familiar with that one.
Can you check your RMS's OpsMgr Event Log for the same time period to see if 
you have errors from the SDK Service?
Let's see if you have an error that looks like this:

An exception was thrown while processing GetObjectsFromReader for session id 
uuid:39f82379-aced-490e-ba72-ca4400bb49e5;id=100.
Exception Message: ExecuteScalar requires an open and available Connection. 
The connection's current state is closed.
Full Exception: 
Microsoft.EnterpriseManagement.Common.InvalidConnectionException: 
ExecuteScalar requires an open and available Connection. The connection's 
current state is closed. ---> System.InvalidOperationException: 
ExecuteScalar requires an open and available Connection. The connection's 
current state is closed.


-- 
Michael Pearson
-------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at 
http://www.microsoft.com/info/cpyright.htm
-------------------------

"Jeff Prusinski"  wrote in message 
news:862F236D-C0FF-4B70-980D-846B27A4C138@microsoft.com...
> Thanks Michael,
>
> We installed this patch directly after we did our RTM SP1 upgrade last 
> week.
> The problems still remains.
>
> One thing we've noticed, as well, is that the sql log for the OpsMgr db is
> filling up with the following error, always with a different SPID-
>
> 07/30/2008 08:37:35,spid68,Unknown,A read operation on a large object 
> failed
> while sending data to the client. A common cause for this is if the
> application is running in READ UNCOMMITTED isolation level. This 
> connection
> will be terminated.
> 07/30/2008 08:37:35,spid68,Unknown,Error: 7886<c/> Severity: 20<c/> State: 
> 2.
>
> Any ideas? I'll post to the sql group as well.
>
> "Michael Pearson [MSFT]" wrote:
>
>> Jeff,
>> It looks like we have a hotfix which may address the "Performance Module
>> could not find a performance counter" issue.  Take a look at this KB 
>> article
>> and see if that applies to you.
>>
>> http://support.microsoft.com/kb/951979/en-us
>>
>> -- 
>> Michael Pearson
>> -------------------------
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>> -------------------------
>>
>> "Jeff Prusinski"  wrote in 
>> message
>> news:2EBBD39E-AF74-4346-A31A-FFC0EAAC294B@microsoft.com...
>> > And then I found this...
>> >
>> > http://blogs.technet.com/momteam/archive/2008/03/01/performance-module-could-not-find-a-performance-counter.aspx
>> >
>> > Looks like it's a problem for the developers to figure out.
>> >
>> > Thanks all.
>> >
>> > "Jeff Prusinski" wrote:
>> >
>> >> Found it under the AD Monitoring MP. Now am going to figure out what 
>> >> to
>> >> do
>> >> with it.
>> >>
>> >> Now I have to figure out what the "Performance Data Source Module 
>> >> Could
>> >> not
>> >> find a performance counter" issue is.
>> >>
>> >>
>> >> "Jeff Prusinski" wrote:
>> >>
>> >> > Thanks Michael.
>> >> >
>> >> > The scripts you provided generated a table with repeat count and 
>> >> > number
>> >> > of
>> >> > alerts with repeat count but as far as I could see didn't generate 
>> >> > the
>> >> > name
>> >> > of the alert. Using the scripts Rob found I was able to find 
>> >> > something.
>> >> >
>> >> > Nothing showed up for the 'monitors' query, there was no difference
>> >> > between
>> >> > the two outputs.
>> >> >
>> >> > The first alert was - "Performance Data Source Modeule Could not 
>> >> > find a
>> >> > performance counter" - The count was literally 1000's upon 1000's of
>> >> > alerts.
>> >> > As it was impossible to even use the console I disabled this alert 
>> >> > and
>> >> > will
>> >> > have to go back and figure out why it's alerting on all our Managed
>> >> > Agents.
>> >> > Maybe the upgrade missed some code on the Agents?
>> >> >
>> >> > The next highest count alert is -
>> >> > "One_or_more_domain_controllers_may_not_be_replicating" repeated 586
>> >> > times in
>> >> > ~32 minutes. How do I track this one down?
>> >> >
>> >> > Jeff.
>> >> >
>> >> > "Michael Pearson [MSFT]" wrote:
>> >> >
>> >> > > I left out a key part of that script.  Here's a working version 
>> >> > > :)
>> >> > > So, if we see a lot of alerts with high repeat counts, we have two
>> >> > > ways or
>> >> > > proceed:
>> >> > > 1.  Give you a script that will change how we handle repeated 
>> >> > > alerts
>> >> > > so that
>> >> > > we do not update the Context field.  That makes the exception you 
>> >> > > are
>> >> > > seeing
>> >> > > go away
>> >> > >
>> >> > > 2.  Track down the rules / monitors that are generating these
>> >> > > repeated
>> >> > > alerts and tune them / disable them.
>> >> > >
>> >> > > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
>> >> > > FROM Alert
>> >> > > WHERE ResolutionState = 0
>> >> > >  AND RepeatCount > 0
>> >> > > GROUP BY RepeatCount
>> >> > > ORDER BY COUNT(*) DESC
>> >> > >
>> >> > > -- 
>> >> > > Michael Pearson
>> >> > > -------------------------
>> >> > > This posting is provided "AS IS" with no warranties, and confers 
>> >> > > no
>> >> > > rights.
>> >> > > Use of included script samples are subject to the terms specified 
>> >> > > at
>> >> > > http://www.microsoft.com/info/cpyright.htm
>> >> > > -------------------------
>> >> > >
>> >> > > "Michael Pearson [MSFT]"  wrote in
>> >> > > message
>> >> > > news:%23GICWfS6IHA.3512@TK2MSFTNGP02.phx.gbl...
>> >> > > > Jeff,
>> >> > > > What view(s) are you opening where you get this exception?  I'm
>> >> > > > guessing
>> >> > > > the Alerts view right?
>> >> > > > If so, can you check your Alert Table to see if you have Alerts
>> >> > > > with a
>> >> > > > high repeat count?
>> >> > > >
>> >> > > > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
>> >> > > > FROM Alert
>> >> > > > WHERE ResolutionState = 0
>> >> > > > AND RepeatCount > 0
>> >> > > > ORDER BY COUNT(*) DESC
>> >> > > >
>> >> > > > -- 
>> >> > > > Michael Pearson
>> >> > > > -------------------------
>> >> > > > This posting is provided "AS IS" with no warranties, and confers 
>> >> > > > no
>> >> > > > rights.
>> >> > > > Use of included script samples are subject to the terms 
>> >> > > > specified
>> >> > > > at
>> >> > > > http://www.microsoft.com/info/cpyright.htm
>> >> > > > -------------------------
>> >> > > >
>> >> > > > "Jeff Prusinski"  wrote 
>> >> > > > in
>> >> > > > message 
>> >> > > > news:BBA6FF1B-0ED9-44AD-B75B-46C369B20E47@microsoft.com...
>> >> > > >> Right after moving to SP1-RTM all of our consoles are throwing
>> >> > > >> exceptions.
>> >> > > >> I'll include the code blurb but it still makes no sense.
>> >> > > >>
>> >> > > >> I've added the /ClearCache switch to all of them. It only helps 
>> >> > > >> a
>> >> > > >> little.
>> >> > > >>
>> >> > > >> Researching the 26319 error only brings up a patch for the 5000
>> >> > > >> series
>> >> > > >> build.
>> >> > > >>
>> >> > > >> Are there patches I'm missing?
>> >> > > >>
>> >> > > >> ***
>> >> > > >>
>> >> > > >> Event Type: Error
>> >> > > >> Event Source: OpsMgr SDK Service
>> >> > > >> Event Category: None
>> >> > > >> Event ID: 26319
>> >> > > >> Date: 7/18/2008
>> >> > > >> Time: 11:59:32 AM
>> >> > > >> User: N/A
>> >> > > >> Computer: NAUSBF-MOMP02
>> >> > > >> Description:
>> >> > > >> An exception was thrown while processing GetObjectsFromReader 
>> >> > > >> for
>> >> > > >> session
>> >> > > >> id
>> >> > > >> uuid:da8a6e40-4079-41ea-a8f8-e9afd8ce7966;id=140.
>> >> > > >> Exception Message: ExecuteScalar requires an open and available
>> >> > > >> Connection.
>> >> > > >> The connection's current state is closed.
>> >> > > >> Full Exception:
>> >> > > >> Microsoft.EnterpriseManagement.Common.InvalidConnectionException:
>> >> > > >> ExecuteScalar requires an open and available Connection. The
>> >> > > >> connection's
>> >> > > >> current state is closed. ---> System.InvalidOperationException:
>> >> > > >> ExecuteScalar
>> >> > > >> requires an open and available Connection. The connection's
>> >> > > >> current state
>> >> > > >> is
>> >> > > >> closed.
>> >> > > >>   at 
>> >> > > >> System.Data.SqlClient.SqlConnection.GetOpenConnection(String
>> >> > > >> method)
>> >> > > >>   at
>> >> > > >> System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
>> >> > > >> method, SqlCommand command)
>> >> > > >>   at System.Data.SqlClient.SqlCommand.ValidateCommand(String
>> >> > > >> method,
>> >> > > >> 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.ExecuteScalar()
>> >> > > >>   at
>> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
>> >> > > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1
>> >> > > >> genericExecute)
>> >> > > >>   --- End of inner exception stack trace ---
>> >> > > >>   at
>> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
>> >> > > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1
>> >> > > >> genericExecute)
>> >> > > >>   at
>> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader
>> >> > > >> sqlDataReader, SqlConnection sqlConnection, IList`1
>> >> > > >> prologEpilogList,
>> >> > > >> RetryPolicy retryPolicy)
>> >> > > >>   at
>> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
>> >> > > >>   at
>> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid
>> >> > > >> id, Int32 count)
>> >> > > >>   at
>> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid
>> >> > > >> readerId, Int32 count)
>> >> > > >>   at
>> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid
>> >> > > >> readerId, Int32 count)
>> >> > > >>   at
>> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid
>> >> > > >> readerId, Int32 count)
>> >> > > >>
>> >> > > >> For more information, see Help and Support Center at
>> >> > > >> http://go.microsoft.com/fwlink/events.asp.
>> >> > > >>
>> >> > > >>
>> >> > > >>
>> >> > > >
>> >> > >
>> >> > >
>>
>>
date: Wed, 30 Jul 2008 17:22:20 -0700   author:   Michael Pearson [MSFT]

Re: Console is constantly throwing exceptions.    
Jeff - I'm sorry looks like we already talked about this issue further up 
the thread.  The two error messages are actually connected.  The SQL Error 
occurs first, and that disconnects the SQL connection the SDK had open for 
that request.  The SDK tries to retry, but fails since the connection was 
closed.  That generates the error you are seeing with the "ExecuteScalar 
requires an open and available Connection. The connection's current state is 
closed." message.

So, if you can stop the frequently repeating Alerts, that's one mitigation. 
If not, you can call into Microsoft Support and ask for a fix that we have 
for this issue.  I've sent mails to the lead on our side to see what exactly 
you need to tell CSS so that you get the right fix as qucik as possible. 
You could just try calling support and reference the two error messages. 
That should point them at the correct documentation and fix, but I want to 
be sure that they find the right fix as quickly as possible.


-- 
Michael Pearson
-------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at 
http://www.microsoft.com/info/cpyright.htm
-------------------------

"Michael Pearson [MSFT]"  wrote in message 
news:328991F1-AB03-41A6-9328-CFFFF1D81AEA@microsoft.com...
> Ah yes, that issue.  I'm very familiar with that one.
> Can you check your RMS's OpsMgr Event Log for the same time period to see 
> if you have errors from the SDK Service?
> Let's see if you have an error that looks like this:
>
> An exception was thrown while processing GetObjectsFromReader for session 
> id uuid:39f82379-aced-490e-ba72-ca4400bb49e5;id=100.
> Exception Message: ExecuteScalar requires an open and available 
> Connection. The connection's current state is closed.
> Full Exception: 
> Microsoft.EnterpriseManagement.Common.InvalidConnectionException: 
> ExecuteScalar requires an open and available Connection. The connection's 
> current state is closed. ---> System.InvalidOperationException: 
> ExecuteScalar requires an open and available Connection. The connection's 
> current state is closed.
>
>
> -- 
> Michael Pearson
> -------------------------
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
> Use of included script samples are subject to the terms specified at 
> http://www.microsoft.com/info/cpyright.htm
> -------------------------
>
> "Jeff Prusinski"  wrote in 
> message news:862F236D-C0FF-4B70-980D-846B27A4C138@microsoft.com...
>> Thanks Michael,
>>
>> We installed this patch directly after we did our RTM SP1 upgrade last 
>> week.
>> The problems still remains.
>>
>> One thing we've noticed, as well, is that the sql log for the OpsMgr db 
>> is
>> filling up with the following error, always with a different SPID-
>>
>> 07/30/2008 08:37:35,spid68,Unknown,A read operation on a large object 
>> failed
>> while sending data to the client. A common cause for this is if the
>> application is running in READ UNCOMMITTED isolation level. This 
>> connection
>> will be terminated.
>> 07/30/2008 08:37:35,spid68,Unknown,Error: 7886<c/> Severity: 20<c/> 
>> State: 2.
>>
>> Any ideas? I'll post to the sql group as well.
>>
>> "Michael Pearson [MSFT]" wrote:
>>
>>> Jeff,
>>> It looks like we have a hotfix which may address the "Performance Module
>>> could not find a performance counter" issue.  Take a look at this KB 
>>> article
>>> and see if that applies to you.
>>>
>>> http://support.microsoft.com/kb/951979/en-us
>>>
>>> -- 
>>> Michael Pearson
>>> -------------------------
>>> This posting is provided "AS IS" with no warranties, and confers no 
>>> rights.
>>> Use of included script samples are subject to the terms specified at
>>> http://www.microsoft.com/info/cpyright.htm
>>> -------------------------
>>>
>>> "Jeff Prusinski"  wrote in 
>>> message
>>> news:2EBBD39E-AF74-4346-A31A-FFC0EAAC294B@microsoft.com...
>>> > And then I found this...
>>> >
>>> > http://blogs.technet.com/momteam/archive/2008/03/01/performance-module-could-not-find-a-performance-counter.aspx
>>> >
>>> > Looks like it's a problem for the developers to figure out.
>>> >
>>> > Thanks all.
>>> >
>>> > "Jeff Prusinski" wrote:
>>> >
>>> >> Found it under the AD Monitoring MP. Now am going to figure out what 
>>> >> to
>>> >> do
>>> >> with it.
>>> >>
>>> >> Now I have to figure out what the "Performance Data Source Module 
>>> >> Could
>>> >> not
>>> >> find a performance counter" issue is.
>>> >>
>>> >>
>>> >> "Jeff Prusinski" wrote:
>>> >>
>>> >> > Thanks Michael.
>>> >> >
>>> >> > The scripts you provided generated a table with repeat count and 
>>> >> > number
>>> >> > of
>>> >> > alerts with repeat count but as far as I could see didn't generate 
>>> >> > the
>>> >> > name
>>> >> > of the alert. Using the scripts Rob found I was able to find 
>>> >> > something.
>>> >> >
>>> >> > Nothing showed up for the 'monitors' query, there was no difference
>>> >> > between
>>> >> > the two outputs.
>>> >> >
>>> >> > The first alert was - "Performance Data Source Modeule Could not 
>>> >> > find a
>>> >> > performance counter" - The count was literally 1000's upon 1000's 
>>> >> > of
>>> >> > alerts.
>>> >> > As it was impossible to even use the console I disabled this alert 
>>> >> > and
>>> >> > will
>>> >> > have to go back and figure out why it's alerting on all our Managed
>>> >> > Agents.
>>> >> > Maybe the upgrade missed some code on the Agents?
>>> >> >
>>> >> > The next highest count alert is -
>>> >> > "One_or_more_domain_controllers_may_not_be_replicating" repeated 
>>> >> > 586
>>> >> > times in
>>> >> > ~32 minutes. How do I track this one down?
>>> >> >
>>> >> > Jeff.
>>> >> >
>>> >> > "Michael Pearson [MSFT]" wrote:
>>> >> >
>>> >> > > I left out a key part of that script.  Here's a working version 
>>> >> > > :)
>>> >> > > So, if we see a lot of alerts with high repeat counts, we have 
>>> >> > > two
>>> >> > > ways or
>>> >> > > proceed:
>>> >> > > 1.  Give you a script that will change how we handle repeated 
>>> >> > > alerts
>>> >> > > so that
>>> >> > > we do not update the Context field.  That makes the exception you 
>>> >> > > are
>>> >> > > seeing
>>> >> > > go away
>>> >> > >
>>> >> > > 2.  Track down the rules / monitors that are generating these
>>> >> > > repeated
>>> >> > > alerts and tune them / disable them.
>>> >> > >
>>> >> > > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
>>> >> > > FROM Alert
>>> >> > > WHERE ResolutionState = 0
>>> >> > >  AND RepeatCount > 0
>>> >> > > GROUP BY RepeatCount
>>> >> > > ORDER BY COUNT(*) DESC
>>> >> > >
>>> >> > > -- 
>>> >> > > Michael Pearson
>>> >> > > -------------------------
>>> >> > > This posting is provided "AS IS" with no warranties, and confers 
>>> >> > > no
>>> >> > > rights.
>>> >> > > Use of included script samples are subject to the terms specified 
>>> >> > > at
>>> >> > > http://www.microsoft.com/info/cpyright.htm
>>> >> > > -------------------------
>>> >> > >
>>> >> > > "Michael Pearson [MSFT]"  wrote in
>>> >> > > message
>>> >> > > news:%23GICWfS6IHA.3512@TK2MSFTNGP02.phx.gbl...
>>> >> > > > Jeff,
>>> >> > > > What view(s) are you opening where you get this exception?  I'm
>>> >> > > > guessing
>>> >> > > > the Alerts view right?
>>> >> > > > If so, can you check your Alert Table to see if you have Alerts
>>> >> > > > with a
>>> >> > > > high repeat count?
>>> >> > > >
>>> >> > > > SELECT RepeatCount, COUNT(*) AS NumAlertsWithRepeatCount
>>> >> > > > FROM Alert
>>> >> > > > WHERE ResolutionState = 0
>>> >> > > > AND RepeatCount > 0
>>> >> > > > ORDER BY COUNT(*) DESC
>>> >> > > >
>>> >> > > > -- 
>>> >> > > > Michael Pearson
>>> >> > > > -------------------------
>>> >> > > > This posting is provided "AS IS" with no warranties, and 
>>> >> > > > confers no
>>> >> > > > rights.
>>> >> > > > Use of included script samples are subject to the terms 
>>> >> > > > specified
>>> >> > > > at
>>> >> > > > http://www.microsoft.com/info/cpyright.htm
>>> >> > > > -------------------------
>>> >> > > >
>>> >> > > > "Jeff Prusinski"  
>>> >> > > > wrote in
>>> >> > > > message 
>>> >> > > > news:BBA6FF1B-0ED9-44AD-B75B-46C369B20E47@microsoft.com...
>>> >> > > >> Right after moving to SP1-RTM all of our consoles are throwing
>>> >> > > >> exceptions.
>>> >> > > >> I'll include the code blurb but it still makes no sense.
>>> >> > > >>
>>> >> > > >> I've added the /ClearCache switch to all of them. It only 
>>> >> > > >> helps a
>>> >> > > >> little.
>>> >> > > >>
>>> >> > > >> Researching the 26319 error only brings up a patch for the 
>>> >> > > >> 5000
>>> >> > > >> series
>>> >> > > >> build.
>>> >> > > >>
>>> >> > > >> Are there patches I'm missing?
>>> >> > > >>
>>> >> > > >> ***
>>> >> > > >>
>>> >> > > >> Event Type: Error
>>> >> > > >> Event Source: OpsMgr SDK Service
>>> >> > > >> Event Category: None
>>> >> > > >> Event ID: 26319
>>> >> > > >> Date: 7/18/2008
>>> >> > > >> Time: 11:59:32 AM
>>> >> > > >> User: N/A
>>> >> > > >> Computer: NAUSBF-MOMP02
>>> >> > > >> Description:
>>> >> > > >> An exception was thrown while processing GetObjectsFromReader 
>>> >> > > >> for
>>> >> > > >> session
>>> >> > > >> id
>>> >> > > >> uuid:da8a6e40-4079-41ea-a8f8-e9afd8ce7966;id=140.
>>> >> > > >> Exception Message: ExecuteScalar requires an open and 
>>> >> > > >> available
>>> >> > > >> Connection.
>>> >> > > >> The connection's current state is closed.
>>> >> > > >> Full Exception:
>>> >> > > >> Microsoft.EnterpriseManagement.Common.InvalidConnectionException:
>>> >> > > >> ExecuteScalar requires an open and available Connection. The
>>> >> > > >> connection's
>>> >> > > >> current state is closed. ---> 
>>> >> > > >> System.InvalidOperationException:
>>> >> > > >> ExecuteScalar
>>> >> > > >> requires an open and available Connection. The connection's
>>> >> > > >> current state
>>> >> > > >> is
>>> >> > > >> closed.
>>> >> > > >>   at 
>>> >> > > >> System.Data.SqlClient.SqlConnection.GetOpenConnection(String
>>> >> > > >> method)
>>> >> > > >>   at
>>> >> > > >> System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String
>>> >> > > >> method, SqlCommand command)
>>> >> > > >>   at System.Data.SqlClient.SqlCommand.ValidateCommand(String
>>> >> > > >> method,
>>> >> > > >> 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.ExecuteScalar()
>>> >> > > >>   at
>>> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
>>> >> > > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1
>>> >> > > >> genericExecute)
>>> >> > > >>   --- End of inner exception stack trace ---
>>> >> > > >>   at
>>> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.Execute[T](ExecuteArguments
>>> >> > > >> executeArguments, RetryPolicy retryPolicy, GenericExecute`1
>>> >> > > >> genericExecute)
>>> >> > > >>   at
>>> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.SqlRetryHandler.ExecuteReaderSingleRow(SqlDataReader
>>> >> > > >> sqlDataReader, SqlConnection sqlConnection, IList`1
>>> >> > > >> prologEpilogList,
>>> >> > > >> RetryPolicy retryPolicy)
>>> >> > > >>   at
>>> >> > > >> Microsoft.EnterpriseManagement.Mom.DataAccess.QueryResultsReader.Read()
>>> >> > > >>   at
>>> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.ClientReaderManager.GetObjects(Guid
>>> >> > > >> id, Int32 count)
>>> >> > > >>   at
>>> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.GetObjectsFromReader(Guid
>>> >> > > >> readerId, Int32 count)
>>> >> > > >>   at
>>> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessTieringWrapper.GetObjectsFromReader(Guid
>>> >> > > >> readerId, Int32 count)
>>> >> > > >>   at
>>> >> > > >> Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccessExceptionTracingWrapper.GetObjectsFromReader(Guid
>>> >> > > >> readerId, Int32 count)
>>> >> > > >>
>>> >> > > >> For more information, see Help and Support Center at
>>> >> > > >> http://go.microsoft.com/fwlink/events.asp.
>>> >> > > >>
>>> >> > > >>
>>> >> > > >>
>>> >> > > >
>>> >> > >
>>> >> > >
>>>
>>>
>
date: Wed, 30 Jul 2008 18:03:11 -0700   author:   Michael Pearson [MSFT]

Re: Console is constantly throwing exceptions.    
You are correct the Exception Thrown error correlates to and event log entry 
with the same information. 

We've reduced as many of the informational/non-critical errors being 
reported to the console via override or disable, but these exceptions 
continue.

Also note. We have one of our DBA's looking at the database and we are 
considering the idea of a 'read uncommitted' tweak to the OpsMgr db so that 
we aren't getting the 7886 errors in the db log. Any thoughts on that before 
we call MSFT support?

Thanks much,
Jeff.



"Michael Pearson [MSFT]" wrote:

> Jeff - I'm sorry looks like we already talked about this issue further up 
> the thread.  The two error messages are actually connected.  The SQL Error 
> occurs first, and that disconnects the SQL connection the SDK had open for 
> that request.  The SDK tries to retry, but fails since the connection was 
> closed.  That generates the error you are seeing with the "ExecuteScalar 
> requires an open and available Connection. The connection's current state is 
> closed." message.
> 
> So, if you can stop the frequently repeating Alerts, that's one mitigation. 
> If not, you can call into Microsoft Support and ask for a fix that we have 
> for this issue.  I've sent mails to the lead on our side to see what exactly 
> you need to tell CSS so that you get the right fix as qucik as possible. 
> You could just try calling support and reference the two error messages. 
> That should point them at the correct documentation and fix, but I want to 
> be sure that they find the right fix as quickly as possible.
> 
> 
> -- 
> Michael Pearson
> -------------------------
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at 
> http://www.microsoft.com/info/cpyright.htm
> -------------------------
> 
> "Michael Pearson [MSFT]"  wrote in message 
> news:328991F1-AB03-41A6-9328-CFFFF1D81AEA@microsoft.com...
> > Ah yes, that issue.  I'm very familiar with that one.
> > Can you check your RMS's OpsMgr Event Log for the same time period to see 
> > if you have errors from the SDK Service?
> > Let's see if you have an error that looks like this:
> >
> > An exception was thrown while processing GetObjectsFromReader for session 
> > id uuid:39f82379-aced-490e-ba72-ca4400bb49e5;id=100.
> > Exception Message: ExecuteScalar requires an open and available 
> > Connection. The connection's current state is closed.
> > Full Exception: 
> > Microsoft.EnterpriseManagement.Common.InvalidConnectionException: 
> > ExecuteScalar requires an open and available Connection. The connection's 
> > current state is closed. ---> System.InvalidOperationException: 
> > ExecuteScalar requires an open and available Connection. The connection's 
> > current state is closed.
> >
> >
> > -- 
> > Michael Pearson
> > -------------------------
> > This posting is provided "AS IS" with no warranties, and confers no 
> > rights.
> > Use of included script samples are subject to the terms specified at 
> > http://www.microsoft.com/info/cpyright.htm
> > -------------------------
> >
> > "Jeff Prusinski"  wrote in 
> > message news:862F236D-C0FF-4B70-980D-846B27A4C138@microsoft.com...
> >> Thanks Michael,
> >>
> >> We installed this patch directly after we did our RTM SP1 upgrade last 
> >> week.
> >> The problems still remains.
> >>
> >> One thing we've noticed, as well, is that the sql log for the OpsMgr db 
> >> is
> >> filling up with the following error, always with a different SPID-
> >>
> >> 07/30/2008 08:37:35,spid68,Unknown,A read operation on a large object 
> >> failed
> >> while sending data to the client. A common cause for this is if the
> >> application is running in READ UNCOMMITTED isolation level. This 
> >> connection
> >> will be terminated.
> >> 07/30/2008 08:37:35,spid68,Unknown,Error: 7886<c/> Severity: 20<c/> 
> >> State: 2.
> >>
> >> Any ideas? I'll post to the sql group as well.
> >>
> >> "Michael Pearson [MSFT]" wrote:
> >>
> >>> Jeff,
> >>> It looks like we have a hotfix which may address the "Performance Module
> >>> could not find a performance counter" issue.  Take a look at this KB 
> >>> article
> >>> and see if that applies to you.
> >>>
> >>> http://support.microsoft.com/kb/951979/en-us
> >>>
> >>> -- 
> >>> Michael Pearson
> >>> -------------------------
> >>> This posting is provided "AS IS" with no warranties, and confers no 
> >>> rights.
> >>> Use of included script samples are subject to the terms specified at
> >>> http://www.microsoft.com/info/cpyright.htm
> >>> -------------------------
> >>>
> >>> "Jeff Prusinski"  wrote in 
> >>> message
> >>> news:2EBBD39E-AF74-4346-A31A-FFC0EAAC294B@microsoft.com...
> >>> > And then I found this...
> >>> >
> >>> > http://blogs.technet.com/momteam/archive/2008/03/01/performance-module-could-not-find-a-performance-counter.aspx
> >>> >
> >>> > Looks like it's a problem for the developers to figure out.
> >>> >
> >>> > Thanks all.
> >>> >
> >>> > "Jeff Prusinski" wrote:
> >>> >
> >>> >> Found it under the AD Monitoring MP. Now am going to figure out what 
> >>> >> to
> >>> >> do
> >>> >> with it.
> >>> >>
> >>> >> Now I have to figure out what the "Performance Data Source Module 
> >>> >> Could
> >>> >> not
> >>> >> find a performance counter" issue is.
> >>> >>
> >>> >>
> >>> >> "Jeff Prusinski" wrote:
> >>> >>
> >>> >> > Thanks Michael.
> >>> >> >
> >>> >> > The scripts you provided generated a table with repeat count and 
> >>> >> > number
> >>> >> > of
> >>> >> > alerts with repeat count but as far as I could see didn't generate 
> >>> >> > the
> >>> >> > name
> >>> >> > of the alert. Using the scripts Rob found I was able to find 
> >>> >> > something.
> >>> >> >
> >>> >> > Nothing showed up for the 'monitors' query, there was no difference
> >>> >> > between
> >>> >> > the two outputs.
> >>> >> >
> >>> >> > The first alert was - "Performance Data Source Modeule Could not 
> >>> >> > find a
> >>> >> > performance counter" - The count was literally 1000's upon 1000's 
> >>> >> > of
> >>> >> > alerts.
> >>> >> > As it was impossible to even use the console I disabled this alert 
> >>> >> > and
> >>