I have three SharePoint sites hosted on the same Web server. Two of the sites are running fine, but every 10 days or so, the third site just hangs. If anyone tries to access the site, it just never loads. Eventually, it times out. Every time this happens, I see this event in the Event Log: Faulting application name: w3wp.exe, version: 7.5.7600.16385, time stamp: 0x4a5bd0eb Faulting module name: onetutil.dll, version: 12.0.6421.1000, time stamp: 0x499414d5 Exception code: 0xc0000005 Fault offset: 0x00000000000abdcc Faulting process id: 0x6d4 Faulting application start time: 0x01cbc376f557ef30 Faulting application path: c:\windows\system32\inetsrv\w3wp.exe Faulting module path: C:\PROGRA~1\COMMON~1\MICROS~1\WEBSER~1\12\BIN\onetutil.dll Report Id: 4d311a84-2f9a-11e0-abcb-00155d06f003 Oddly enough, if I restart the Application Pool for the site, nothing happens. The only way I've found to get the site running again is to do an IISReset. Unfortunately, that obviously affects the other two sites that are running on this box, so it's beginning to become problematic. I've done a little research on this and tried a few things (mainly dealing with permissions on the Application Pool) but nothing has worked. Looking at a mini-dump of this also yields no clues. Does anyone know what might be causing this, or can anyone tell me what else to check so that I can find out what's going on? Thanks in advance! Eric

Hi Eric, Did you install any recent updates and do you have any patches pending? Here is a link for similar problem http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/MS-SharePoint/Q_24892540.html Thanks, Skancharla

Hey, Skancharla. Nope. To the best of my knowledge, nothing new has been installed on that server for a while, and there are no new patches pending. Plus, I would be a little shocked to see that an update would affect one SharePoint site and not the other two (though I guess stranger things have happened). Thanks for the link, but sadly, nothing mentioned in that thread seems to help.

Hey, Skancharla. Nope. To the best of my knowledge, nothing new has been installed on that server for a while, and there are no new patches pending. Plus, I would be a little shocked to see that an update would affect one SharePoint site and not the other two (though I guess stranger things have happened). Thanks for the link, but sadly, nothing mentioned in that thread seems to help.

Is this site created with out of the box template or with customized templates/definitions? Are these site collections on the same web application? Need some more details about your site structure and farm version. Thanks, DipDip http://dzeee.net/sharepoint

Is this site created with out of the box template or with customized templates/definitions? Are these site collections on the same web application? Need some more details about your site structure and farm version. Thanks, DipDip http://dzeee.net/sharepoint

Hey, Dip. Yeah, this site is relatively simple. It's created from the out-of-the-box "empty" site template. It has a single custom list and an Application Page that can make posts into that list, but the Application Page is only invoked if a user clicks a link to go there. That is to say, when the problem happens, it's when a user is first going to the site (no custom resources have been accessed at that point). This is MOSS 2007 (Version 12.0.0.6421) and the site collections are running as separate Web applications. Let me know if you need more info.

Hey, Dip. Yeah, this site is relatively simple. It's created from the out-of-the-box "empty" site template. It has a single custom list and an Application Page that can make posts into that list, but the Application Page is only invoked if a user clicks a link to go there. That is to say, when the problem happens, it's when a user is first going to the site (no custom resources have been accessed at that point). This is MOSS 2007 (Version 12.0.0.6421) and the site collections are running as separate Web applications. Let me know if you need more info.

Really? Again? My post is being marked as "answered" when it hasn't been? Nice.

> Really? Again? My post is being marked as "answered" when it hasn't been? Nice. In that case all you need to do is unmark it. As the starter of this thread, you have that right. Do that rather than posting unnecessary flames. (Another) Moderator - I've unmarked it for you.SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx Both also have links to extensive book lists and to (free) on-line chapters

Hi Eric, Have You solved the issue? I have the same problem here with Moss 2007 Enterprise version 12.0.0.6554. We installed the 2011 february cumulative update. Nothing in the sharepoint logs, the only clue is this event You described. Best, Tamas

As you say that the other web apps are affected by IISReset and two of them are working fin, I assume that this issue is in specific to the web application/collection. I don't think this could directly be a version/patch issue. If this is the case was there any custom feature that is activated? Every 10 days or so: Is that happening every 10 days in specific. if so, is there any job activity that runs every 10 days? To Troubleshoot this issue/To determine the root cause: - Run Debug diag and the analysis from there should provide a good set of info of what exactly is happening. Troubleshooting @ the worker process level is required to determine the root cause. Also the reason for the hand could be a lot of writes onto the database. SQL profiler should give you the right hint. But from the info provided I suspect the worker process Workaround is: Create a new web application, include all managed paths and map the content database to the new one. (if all the other web apps did not had any issues this should be a quick fix for you) Kind Regards, Vignesh

Hey, Tamas. No, we have not solved the issue. Unfortunately, management decided to migrate away from SharePoint for this project. Of course, having this issue around didn't help the situation. Vignesh, yes, I would agree that I don't think it's version/patch related, and it definitely seems tied to the worker process. For a while, I thought it was specific to a single Web application on our SharePoint site, but then it begin happening on a second SharePoint site with a very different configuration---though not nearly as often. When I said it happens every 10 days or so, that was just an average, but I've seen it happen as often two days in a row and even twice in one day. In short, it's sporadic and unpredictable, but usually occurs in the mornings, when a user first accesses the site. Looking for a scheduled task or activity that corresponded proved unfruitful. All the debugging and tracing I've done on this seem to point to permissions issues, but ones that I can't get resolved. That is to say, it happens with completely innocuous things, like a standard SharePoint service accessing standard SharePoint files (like standard themes, etc.). Running through a litany of permissions settings, like giving everything and everyone administrative access to the site/server didn't resolve anything. If this were only occurring with a single Web Application, I might be inclined to consider it corruption and create a new one, as you say. But since this is happening on multiple sites/applications now, I don't think that's worth the effort. I'd rather figure out exactly what the problem is and get it resolved once and for all. Thanks. Eric