ASP.NET service faulting error Sitecore 6 workaround

We have sitecore 6 environments working on Virtual Machines (VM’s). Sitecore 6 seems to cause an ASP error at seemingly random intervals leading to a total loss of service 9only on VM’s. Event Viewer will show you the following error:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date:  8/8/2008
Time:  4:09:35 PM
User:  N/A
Computer: SCTEST
Description:
Faulting application w3wp.exe, version 6.0.3790.3959, faulting module unknown, version 0.0.0.0, fault address 0x709a2075.

Sitecore have provided a work-around for this. Set the following web.config entry to ‘false’ as show below:

<!–  ENABLE COUNTERS
Indicates if performance counters are enabled.
Default value: true
–>
<setting name=”Counters.Enabled” value=”false” />

We have made this change and it seems to get rid of the issue. Seems like Sitecores backend performance monitoring may be using some .NET 3.5 functionality that causes this error (this is just a guess).

See the SC forum for more details:

http://sdn5.sitecore.net/forum/ShowPost.aspx?PostID=11838#11838

This entry was posted on Sunday, October 5th, 2008 at 10:57 pm and is filed under Sitecore. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

5 Responses to ASP.NET service faulting error Sitecore 6 workaround

  1. Darren Guarnaccia says:
    October 6, 2008 at 2:11 pm

    Hi Richard,

    Sitecore’s been working with Microsoft on this issue,and we’ve tracked it down to an error state in Perflib.dll. It’s apparently a known issue for windows 2003, though it’s been fixed in Windows 2008. We’re still working with Microsoft on getting a hotfix released from them to correct this issue, but I’m glad the work around worked well for you.

    Reply
  2. richdias says:
    October 6, 2008 at 8:24 pm

    Hi Darren,

    Yes I realise this is Microsoft’s fault. I guess I should have stated that specifically. “Sitecores backend performance monitoring may be using some .NET 3.5 functionality that causes this error”, I intended to imply that it is the .NET functionality that is being used which is causing this error.

    Thanks,
    Richard

    Reply
  3. Jack Tseng says:
    August 21, 2009 at 4:11 pm

    Hi Richard,

    First of all, a great post you got here. Secondly, I’ve noticed that this error is known in Sitecore 6 but I’m getting this error for older version of sitecore, 5.1. I searched for the counters settings in web.config but cannot find it. Would you happen to have a solution for it?

    Thanks in advance!

    Reply

Leave a comment