AbleCommerceHttpModule.a Error

[ripdog]

I get an error very frequently in my event logs from the AbleCommerceHttpModule. The obfuscated method "a" seems to be trying to call the MajorVersion property to get version of the browser, but sometimes an exception is thrown. This is poor design on Microsoft's part in my opinion (why don't they just return 0 instead of throwing an exception?).

Is there a fix for this? I am on version 7.0 build 10152.

Event[0]:
Log Name: Application
Source: ASP.NET 2.0.50727.0
Date: 2010-11-19T08:53:46.000
Event ID: 1309
Task: Web Event
Level: Warning
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: WW420
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 11/19/2010 8:53:46 AM
Event time (UTC): 11/19/2010 4:53:46 PM
Event ID: b7609e1d3c8a405d88530cbfc2f73960
Event sequence: 3413
Event occurrence: 33
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/ROOT-1-129346138795302734
Trust level: Full
Application Virtual Path: /
Application Path: C:\inetpub\wwwroot\
Machine name: WW420

Process information:
Process ID: 3712
Process name: w3wp.exe
Account name: IIS APPPOOL\mydomain.com

Exception information:
Exception type: ArgumentNullException
Exception message: Value cannot be null.
Parameter name: String

Request information:
Request URL: http://www.mydomain.com/Category.aspx?CategoryId=58
Request path: /Category.aspx
User host address: 209.85.238.68
User:
Is authenticated: False
Authentication Type:
Thread account name: IIS APPPOOL\mydomain.com

Thread information:
Thread ID: 22
Thread account name: IIS APPPOOL\mydomain.com
Is impersonating: False
Stack trace: at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.Web.Configuration.HttpCapabilitiesBase.get_MajorVersion()
at CommerceBuilder.Services.AbleCommerceHttpModule.a(Object A_0, EventArgs A_1)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

[Logan Rhodehamel]

A fix for this problem was included as part of the 7.0.6 update.

Edit: And I agree it would have been nice if Microsoft could have just returned a 0 to us. That's what we ended up doing - trapping the error and then returning 0 to our calling code.