Comments for MCPGuides.com http://mcpguides.com Guides from Microsoft Certified Experts Mon, 15 Mar 2010 20:43:32 +0000 http://wordpress.org/?v=2.9.2 hourly 1 Comment on Guide to Monitoring for Required Reboots with System Center Operations Manager 2007 by Fedor http://mcpguides.com/?p=12&cpage=1#comment-67 Fedor Mon, 15 Mar 2010 20:43:32 +0000 http://mcpguides.com/?p=12#comment-67 Hello. How do create, which will monitoring event autorization reboot servers nt (reboot which made admin server)? Hello. How do create, which will monitoring event autorization reboot servers nt (reboot which made admin server)?

]]> Comment on Resolving ASP Performance Counter Application Event Log Warnings by WMI ADAP was unable to create the object Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727 | Peter Van Eeckhoutte's Blog http://mcpguides.com/?p=38&cpage=1#comment-45 WMI ADAP was unable to create the object Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727 | Peter Van Eeckhoutte's Blog Tue, 16 Sep 2008 23:16:30 +0000 http://mcpguides.com/?p=38#comment-45 [...] have a look at http://mcpguides.com/?p=38, which explains how to set up a workaround for this (basically, it explains how to disable the [...] [...] have a look at http://mcpguides.com/?p=38, which explains how to set up a workaround for this (basically, it explains how to disable the [...]

]]> Comment on Resolving ASP Performance Counter Application Event Log Warnings by anonymous http://mcpguides.com/?p=38&cpage=1#comment-16 anonymous Mon, 18 Aug 2008 10:21:02 +0000 http://mcpguides.com/?p=38#comment-16 For those who don't/can't install .NET 3.5 SP1 or for Windows 2000-based computers, go to this link (http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=951683&kbln=en-us) and obtain the hotfix. For those who don't/can't install .NET 3.5 SP1 or for Windows 2000-based computers, go to this link (http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=951683&kbln=en-us) and obtain the hotfix.

]]> Comment on Resolving ASP Performance Counter Application Event Log Warnings by michel http://mcpguides.com/?p=38&cpage=1#comment-15 michel Fri, 18 Jul 2008 08:56:36 +0000 http://mcpguides.com/?p=38#comment-15 Hi, Good news. I've spoken to our internal microsoft engineer and there is a non-public hotfix for this. See KB951683. The public release is inplemented in Dot net 3.5 Sp1. I've already inplemented this non-public hotfix and it WORKS!! So all the dot net 2.0 counters are working now. Hope this helps a lot off people. See link for some more info: http://blogs.msdn.com/carloc/archive/2008/06/04/wmi-warnings-35-and-40-with-asp-net.aspx Michel Kamp Hi,

Good news. I've spoken to our internal microsoft engineer and there is a non-public hotfix for this. See KB951683. The public release is inplemented in Dot net 3.5 Sp1.

I've already inplemented this non-public hotfix and it WORKS!! So all the dot net 2.0 counters are working now.

Hope this helps a lot off people.

See link for some more info: http://blogs.msdn.com/carloc/archive/2008/06/04/wmi-warnings-35-and-40-with-asp-net.aspx

Michel Kamp

]]> Comment on Resolving ASP Performance Counter Application Event Log Warnings by MCPGuides.com http://mcpguides.com/?p=38&cpage=1#comment-14 MCPGuides.com Thu, 17 Jul 2008 18:43:30 +0000 http://mcpguides.com/?p=38#comment-14 Michel, According to the Microsoft engineers we have spoken with no hotfix is in development at this time for this bug. If your business is being seriously impacted by this issue you can open up a QFE request with them. The general discussion about a hotfix seems to be more related to the desire for MS to create a hotfix for this, rather than the actual existence of a hotfix. Michel,

According to the Microsoft engineers we have spoken with no hotfix is in development at this time for this bug. If your business is being seriously impacted by this issue you can open up a QFE request with them.

The general discussion about a hotfix seems to be more related to the desire for MS to create a hotfix for this, rather than the actual existence of a hotfix.

]]> Comment on Resolving ASP Performance Counter Application Event Log Warnings by michel http://mcpguides.com/?p=38&cpage=1#comment-13 michel Thu, 17 Jul 2008 18:27:40 +0000 http://mcpguides.com/?p=38#comment-13 Hi, You have only to disbale the "ASP64 application" counters. The other ASP 64 is working good. (you can check this with perfmon) So some MP workflows will maybe work. I agree with you that if you are sure that no dot net 2.0 applications are running and needs to be monitord that it is no problem to disbale this perf lib. But don't forget that you have done this. Is there any more info on this hoffix where everybody talks about ? Hi,

You have only to disbale the "ASP64 application" counters. The other ASP 64 is working good. (you can check this with perfmon) So some MP workflows will maybe work. I agree with you that if you are sure that no dot net 2.0 applications are running and needs to be monitord that it is no problem to disbale this perf lib. But don't forget that you have done this.

Is there any more info on this hoffix where everybody talks about ?

]]> Comment on Resolving ASP Performance Counter Application Event Log Warnings by MCPGuides.com http://mcpguides.com/?p=38&cpage=1#comment-12 MCPGuides.com Thu, 17 Jul 2008 18:17:24 +0000 http://mcpguides.com/?p=38#comment-12 Michel, You are correct. We are clearly disabling the ASP.Net performance counters, this is why we've given the warning that "Assuming that on the agent managed host you have no additional needs outside of System Center to monitor the ASP.Net performance counters there are two ways to rid yourself of these errors:" Doing so has no impact on the functionality of SCOM, or other applications, outside of simply being unable to monitor and collect ASP.Net performance metrics, which is clearly not possible on hosts impacted by this bug as it is. Since we are already unable to collect ASP.Net performance on machines impacted by this bug, what we are doing is cleaning up the noise in the event log until such time that a proper hotfix from Microsoft becomes available. Michel,

You are correct. We are clearly disabling the ASP.Net performance counters, this is why we've given the warning that "Assuming that on the agent managed host you have no additional needs outside of System Center to monitor the ASP.Net performance counters there are two ways to rid yourself of these errors:"

Doing so has no impact on the functionality of SCOM, or other applications, outside of simply being unable to monitor and collect ASP.Net performance metrics, which is clearly not possible on hosts impacted by this bug as it is.

Since we are already unable to collect ASP.Net performance on machines impacted by this bug, what we are doing is cleaning up the noise in the event log until such time that a proper hotfix from Microsoft becomes available.

]]> Comment on Resolving ASP Performance Counter Application Event Log Warnings by ulrich bernskov http://mcpguides.com/?p=38&cpage=1#comment-11 ulrich bernskov Thu, 17 Jul 2008 13:28:14 +0000 http://mcpguides.com/?p=38#comment-11 Hi michel. Do you have a better idea? Hi michel.
Do you have a better idea?

]]> Comment on Resolving ASP Performance Counter Application Event Log Warnings by michel http://mcpguides.com/?p=38&cpage=1#comment-10 michel Thu, 17 Jul 2008 06:45:15 +0000 http://mcpguides.com/?p=38#comment-10 Be aware. What you now doning is DISABLELING all dot net performance counters !!!! So applications (as SCOM) may not be able to work correctly. This is not a solution but a high impact workarround. Be aware. What you now doning is DISABLELING all dot net performance counters !!!! So applications (as SCOM) may not be able to work correctly. This is not a solution but a high impact workarround.

]]> Comment on Resolving ASP Performance Counter Application Event Log Warnings by ulrich bernskov http://mcpguides.com/?p=38&cpage=1#comment-9 ulrich bernskov Thu, 03 Jul 2008 18:10:42 +0000 http://mcpguides.com/?p=38#comment-9 Thanks for the descriptive solution. Please post a follow-up should a solution be provided Thanks for the descriptive solution.
Please post a follow-up should a solution be provided

]]>