Several of our users who are using Outlook Web Access are getting this error. We are running Exchange2007 on Server2003 Enterprise SP1. Any help on this problem would be greatly appreciated. Thank-you Error - Outlook Web Access has encountered a Web browsing error. The entire error report is listed below: [[Note: I have removed the actual names of servers]] Client Information ------------------ User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 1.1.4322) CPU Class: x86 Platform: Win32 System Language: en-us User Language: en-us CookieEnabled: true Mime Types: Exception Details ----------------- Date: Wed Dec 23 15:19:06 EST 2009 Message: 'gtLV' is null or not an object Url: https://exchangeserver.domain.net/owa/8.1.8.61/scripts/premium/clistview.js Line: 39 Call Stack ---------- onFcsInLV() Dump Event ---------- recordset = null type = error fromElement = null toElement = null altLeft = false keyCode = 0 repeat = false reason = 0 data = behaviorCookie = 0 source = null contentOverflow = false behaviorPart = 0 url = dataTransfer = null ctrlKey = false shiftLeft = false dataFld = returnValue = undefined qualifier = wheelDelta = 0 bookmarks = null button = 0 srcFilter = null nextPage = cancelBubble = false x = 0 y = 0 srcElement = null screenX = 1588 screenY = 220 srcUrn = origin = boundElements = [object] clientX = 130 clientY = 26 propertyName = shiftKey = false ctrlLeft = false offsetX = 0 offsetY = 0 altKey = false errorMessage = 'gtLV' is null or not an object errorUrl = https://exchangeserver.domain.net/owa/8.1.8.9/scripts/premium/clistview.js errorLine = 39 errorCharacter = 22 errorCode = 0

Does the issue happen when attempting to login to OWA, or anything else, like refresh the view by clicking “Check Message” button? Does the issue happen to problematic users when using the machines that can be used well by other users? Does the issue happen when access the OWA URL directly, without any other redirection? Could the issue be reproduced to problematic users when attempting to access OWA on the CAS server directly? Please describe the exchange topology, version Please compare the difference between the problematic users’ machines and the fine ones’, especially about the version of the Internet Explorer and OSJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

This happens only in Outlook Web Access after users have already been logged in. Users are telling me that they are replying to email addresses outside the organization when the error message pops up. This does not seem to be targetting certain problematic users. One whole dept told me they were getting this error. We are running Exchange 2007 on server 2003.

Please verify the other questions in the post above If the client configuration is Windows 7/Internet Explorer 8, please change the value of “tabprocgrowth” to 0, and then see if the issue still persists Opening a New Tab may launch a New Process with Internet Explorer 8.0James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

All of our users are running Windows XP. Users with desktops are running IE8, but users who are using thin client and Citrix are using IE7. The problem seems to affect both browsers. I checked for that registry setting, but did not find it in XP so I am assuming that is Win7 specific. Thank-you for your feedback. Any new ideas?

Same issue here with XP & IE8. Seems to be pretty random in occurrence and only a handful of users out of a 1000. One tech guy got the error when reinstalling the s/mime control. Most get it on sending an email. Some times it happens just clicking between folders.

I have a ticket open with the IE Team at Microsoft, and apparently the problem is with the OWA code. "It looks like the IE team has given some suggestions to the OWA developers for a way to work-around this issue in the OWA code." I am waiting for their findings........