After you view an ASP.NET webpage which displays performance counter data via the PerformanceCounter class, scripts no longer function. This includes scripts launched from a command line as well as client-side scripts in any browser window that is opened after you viewed the original page. Scripts are working again after you have stopped the Word Wide Publishing service.

A deadlock occurs because of a bug in one of the WMI providers. An event tracing is done which calls the RegisterTraceGuids API which in turn calls into one of the WMI Service hosted within the Services.exe.

A hotfix is available from Microsoft, at least in english and german.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix for KB834010. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

1. Create a new ASP.NET web application
2. Add a label control to the page
3. Add this code to the Page_Load event:

    1 using (PerformanceCounter counter = new PerformanceCounter())

    2 {

    3     counter.CategoryName = "Memory";

    4     counter.CounterName = "Available MBytes";

    5     Label1.Text = counter.NextValue().ToString();

    6 }

4. Compile the application

5. Open the webform with Internet Explorer

6. Now, open any website which has client-side scripting

After you view an ASP.NET webpage which displays performance counter data via the PerformanceCounter class, scripts no longer function. This includes scripts launched from a command line as well as client-side scripts in any browser window that is opened after you viewed the original page. Scripts are working again after you have stopped the Word Wide Publishing service.

A deadlock occurs because of a bug in one of the WMI providers. An event tracing is done which calls the RegisterTraceGuids API which in turn calls into one of the WMI Service hosted within the Services.exe.

<xsl:template match="xhtml:img" mode="xhtmlimage">

A hotfix is available from Microsoft, at least in english and german.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

1. Create a new ASP.NET web application
2. Add a label control to the page
3. Add this code to the Page_Load event:
   

   using (PerformanceCounter counter = new PerformanceCounter())

   {

   counter.CategoryName = "Memory";

   counter.CounterName = "Available MBytes";

   Label1.Text = counter.NextValue().ToString();

   }

4. Compile the application

5. Open the webform with Internet Explorer

6. Now, open any website which has client-side scripting