Article ID: 6673, created on Sep 14, 2009, last review on May 11, 2014

  • Applies to:
  • Plesk 9.x for Windows

Symptoms

The following error appears in Application log while browsing Sitebuilder panel from time to time:

Log Name: Application
Source: ASP.NET 2.0.50727.0
Date: 30.06.2009 23:24:08
Event ID: 1309
Task Category: Web Event
Level: Warning
Keywords: Classic
User: N/A
Computer: computername.local 
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 30.06.2009 23:24:08
Event time (UTC): 30.06.2009 21:24:08
Event ID: d4efadb071344b96ba1286f790b10116
Event sequence: 230
Event occurrence: 29
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/3/ROOT-1-128908665684975322  
Trust level: Full
Application Virtual Path: /
Application Path: C:\Program Files (x86)\Parallels\Plesk\SiteBuilder\Web\
Machine name: PPB12  

Process information:
Process ID: 3700
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: HttpException
Exception message: An error occurred while communicating with the remote
host. The error code is 0x80070057.

Request information:
Request URL: http://localhost:2006/Logo.ashx?i=sblogo.png
Request path: /Logo.ashx
User host address: ::1
User: 125eeb52-3b26-4cc7-acdf-3370844868b7
Is authenticated: True
Authentication Type: Forms
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 6
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at
System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status, Byte[] header, Int32 keepConnected,
Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths,
Int32 doneWithSession, Int32 finalStatus, Boolean& async) 
at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal) 
at System.Web.Hosting.ISAPIWorkerRequest.FlushResponse(Boolean finalFlush)
at System.Web.HttpResponse.Flush(Boolean finalFlush)
at System.Web.HttpResponse.Flush()
at System.Web.HttpWriter.WriteFromStream(Byte[] data, Int32 offset, Int32 size) 
at System.Web.HttpResponseStream.Write(Byte[] buffer, Int32 offset, Int32 count) 
at SWsoft.SiteBuilder.Web.Handlers.Images.SendImage(HttpResponse response,
Image image, HttpCacheability cacheability)
at SWsoft.SiteBuilder.Web.Handlers.LogoHandler.ProcessRequest(HttpContext context) 
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&completedSynchronously)

Cause

The initial problem related to the logohandler.ashx.  Similar problem was discussed at forum http://forums.iis.net/p/1149787/1908163.aspx#1908163 and relates to the bug in IIS7.0 on Win2k8 x64. 
This bug is not appeared on default configuration. It appears only after manual change settings on SiteBuilderSitesWebAppPool -> Properties -> Performance -> Web garden .

Resolution

The following workaround could be applied here:

Please increase number of worker processes, which serve the pool. When you increase the number of process serving the pool, you decrease the request queue length and time request spent in the queue, and therefore reduce the probability request will be closed by client (due to socket timeout).

We strongly recommend do not use web garden configuration for Sitebuilder server, it might be used for sites created by Sitebuilder however. You may think about other ways to reduce request queue length: scale server up for example.

aac4a8fcd879de03758354e15495d69a a914db3fdc7a53ddcfd1b2db8f5a1b9c 85a92ca67f2200d36506862eaa6ed6b8 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF