Summary
Several warning errors appear in the Windows Application log of OfficeScan servers:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 10/18/2013 4:25:17 AM
Event time (UTC): 10/18/2013 8:25:17 AM
Event ID: 6a52497af2e64cdcb6532ab321910d64
Event sequence: 11618
Event occurrence: 7975
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/5/ROOT-2-130265456602252153
Trust level: Full
Application Virtual Path: /
Application Path: D:\Apps\Trend Micro\OfficeScan\PCCSRV\LWCS\isapi\
Machine name: ASPNY4AV01
Process information:
Process ID: 1116
Process name: w3wp.exe
Account name: IIS APPPOOL\DefaultAppPool
Exception information:
Exception type: HttpException
Exception message: The length of the URL for this request exceeds the configured maxUrlLength value.
at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)
Request information:
Request URL: http://ASPNY4AV01.asp.paladyne.com:5274/T/384/
gkijNyRcjhV9RrBbc4_mPNRFzWl4hAIutM4uriStwAwyNLmIjRon15OoumDBJnsI-
DcewWtuBwQXQHshKfH3ADyQDZ6Iww9zGLg12PD5F69vqBA6xBpvS77QIdUk2y8N3MVqNnO5Q7NeBH8n3-
IzC3LCoKmvIw7bO7hSFWcMyUiZZk6l27k1_9Rvkd_kSklbdCOz5ZPjm9hOM_eduwQCpIw6ionFMufn3dP
jQU5ok2Q-G2vpBvuWz1IfetguxownnQgBa18JWC0vJ5sy9EN7KIYcAszZtyLkRE4VIzmLv5ZwQj6bNip6dUITZKxzb
HONZGFpkzoAwuccs9vX2c_E4N6v2uoHhS4YT747TRMWieuD28H6aED1ZBKhP8a3uJna
Request path: /T/384/gkijNyRcjhV9RrBbc4_mPNRFzWl4hAIutM4uriStwAwyNLmIjRon15OoumDB
JnsI-DcewWtuBwQXQHshKfH3ADyQDZ6Iww9zGLg12PD5F69vqBA6xBpvS77QIdUk2y8N3MVqNnO5Q7NeBH8n3-
IzC3LCoKmvIw7bO7hSFWcMyUiZZk6l27k1_9Rvkd_kSklbdCOz5ZPjm9hOM_eduwQCpIw6ionFMufn3dP
jQU5ok2Q-G2vpBvuWz1IfetguxownnQgBa18JWC0vJ5sy9EN7KIYcAszZtyLkRE4VIzmLv5ZwQj6bNip6dUITZKxz
This issue is caused by environment compatibility. WRS protocol will send the URL request longer than 4096, but when asp.net 4.0 is installed onto IIS, it may create another default constraint of default virtual website.
This is a configuration size limit for the requesting URL on ASP.NET, .NET Framework 4 and its supported OS platform running IIS 7.
This can also occur on an environment without OSCE installed.
Refer to this Microsoft article for more information.
Do the following:
- Back up the old web.config file.
- Download the new web.config file.
- Depending on your version, put the new web.config file on the following location:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG(web)
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG(web64)
C:\Windows\Microsoft.NET\Framework\v4.0.30319\CONFIG(web)
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\CONFIG(web64)
- Restart the IIS service.
- Restart the Trend Micro Local Web Classification Server service.
