Discussion:
Intermittent Service Unavailable
(too old to reply)
EightBallCrazy
2010-01-07 03:37:01 UTC
Permalink
A new install of MOSS 2007 is working fine, except we experience
random"service unavailable" errors. Hit refresh a couple of times, and you're
back to business.

This only occurs 2 or 3 times a day, and only when there are around 20+
users on the SharePoint site. When fewer users are on the site, it does not
occur.

Environment is MOSS 2007 SP2 installed on Server 2008 SP1, using SQL 2008
RTM on separate database server running Server 2003 R2 SP2.

This only happens on the main intranet site and is essentially just the
application pool crashing, then restarting. SharePoint Central Admin and
other application pools on this server do not experience this problem.

Reviewing the event logs shows no corresponding errors, however looking in
the HTTP error log located here, %windir%\System32\LogFiles\HTTPERR, I can
see errors logged with the reason "Connection_Abandoned_By_ReqQueue". These
logged errors match up to the exact times we're seeing "Service Unavailable".

Does anyone know what might be causing this problem, and making the intranet
application crash? As mentioned earlier it only happens when roughly 20+
users are on the site, and not very often even then.

The problem seems to be specific to IIS7 and there is very little
information out there for the error "Connection_Abandoned_By_ReqQueue".
Microsoft describe the error as "A worker process from the application pool
has quit unexpectedly or orphaned a pending request by closing its handle.
Specific to Windows Vista and Windows Server 2008.", found here,
http://support.microsoft.com/default.aspx/kb/820729.

This is not related to the IPv6 problem with SharePoint described here,
http://blogs.msdn.com/jmacleod/archive/2008/06/25/iis7-sharepoint-2007-fails-with-503-service-unavailable-errors.aspx.

Would I possibly need to adjust the advanced settings of the application
pool that intermittently crashes? i.e. Rapid-Fail Protection > Maximum
Failures/Failure Interval.

Any help would be greatly appreciated.
Harish [MSFT]
2010-01-14 18:16:59 UTC
Permalink
I would start reviewing the event viewer messages first. Check for,

1.ASP.NET messages
2.Application pool crashes
3.Any ASP.NET or memory dead locks

IIS7 gives you the Failed request tracking, which gives you detailed
information on what hapenned in that request. That is also a good one to
start with.

Harish K

Continue reading on narkive:
Loading...