Users getting this error randomly, but still seems to function. Client Information ------------------ User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 1.1.4322; .NET4.0C; .NET4.0E) CPU Class: x86 Platform: Win32 System Language: en-us User Language: en-us CookieEnabled: true Mime Types: Exception Details ----------------- Date: Wed Aug 8 11:13:12 EDT 2012 Message: 'g_oSnd' is null or not an object Url: https://webmail.***MYDOMAIN***.org/owa/8.3.264.0/scripts/premium/unav.js Line: 63 Call Stack ---------- cbPoll(oR) oR = [object Object] sBody = stDrty("LgAAAABRziCv5C2xRrGfTrezBb+SAQD2pLCVHKT0SZ5JvMLrQv4NABKiIaw7AAAB");updCnt("LgAAAABRziCv5C2xRrGfTrezBb+SAQD2pLCVHKT0SZ5JvMLrQv4NABKiIaw7AAAB",197,18);updCnt("LgAAAABRziCv5C2xRrGfTrezBb+SAQD2pLCVHKT0SZ5JvMLrQv4NACUYUVyuAAAB",985,985);updCnt("LgAAAABRziCv5C2xRrGfTrezBb+SAQD2pLCVHKT0SZ5JvMLrQv4NABKiIaw8AAAB",1,-1);shwNM(1);g_sMId="RgAAAABRziCv5C2xRrGfTrezBb+SBwD2pLCVHKT0SZ5JvMLrQv4NABKiIaw7AAD2pLCVHKT0SZ5JvMLrQv4NAgNt8DRfAAAJ";shwNwItmDlg("Hewlett-Packard","Stop hackers cold: HP tips for safer passwords. Technology at Work, August 2012","spnNwMl","8.3.264.0/themes/base/msg-unrd.gif");plySnd();setPllInt(120000); oReq = [object Object] oCtx = null oXmlHttp = iStatus = 200 fST = false iCT = 1 cbOeReq(oReqFac) oReqFac = [object Object] oXmlHttp = iXmlVer = 2 sUrl = ev.owa?oeh=1&ns=Notify&ev=Poll oCtx = [object Object] iIdx = 27 fExp = false fLock = true cb = function cbOeReq(oReqFac){var oRsp=new oeResp(oReqFac);var oXH=oRsp.oXmlHttp;if(oXH.status==200){var er=oXH.getResponseHeader("X-OWA-EventResult");if(er=="0"){}else if(er=="1"){var oDiv=document.createElement("div");oDiv.innerHTML=oRsp.sBody;var oErr=oDiv.all["err"];oRsp.sErr=oErr._msg;oRsp.iErr=0;if(oErr._cd)oRsp.iErr=getInt(oErr._cd);var divDbg=oDiv.all["debugInfo"];if(divDbg)oRsp.sErrDbg=divDbg.outerHTML;var divCustom=oDiv.all["divCstInfo"];if(divCustom)oRsp.divCustom=divCustom;}else {oRsp.sErr=L_IntErr;}}else {oRsp.sErr=getHttpErr(oXH.status);}--g_iRC;if(oReqFac.oCtx.cb){if(!oReqFac.oCtx.cb(oRsp))updCmp(window,oRsp);}return oRsp;} cbReqFac(iIdx) iIdx = 27 anonymous() ----------------------- function anonymous() { cbReqFac(27) } ----------------------- 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 = 738 screenY = 321 srcUrn = origin = boundElements = [object] clientX = 738 clientY = 217 propertyName = shiftKey = false ctrlLeft = false offsetX = 0 offsetY = 0 altKey = false errorMessage = 'g_oSnd' is null or not an object errorUrl = https://webmail.***MYDOMAIN***.org/owa/8.3.264.0/scripts/premium/unav.js errorLine = 63 errorCharacter = 175 errorCode = 0

What are they specifically doing in OWA when this happens? Are you on the latest service pack and roll up for exchange?James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Exchange 2007 SP3 update rollup 7. Rollup 7 installed in late June. Windows updates installed on July 18. Seems to just pop up out of the blue, not necessarily when composing a message or doing anything else.

Actually it occurs every time a new email comes in...

Try creating your owa virtual directories. how to recreate owa vir dir http://support.microsoft.com/kb/941201 _oSnd' is null or not an object when trying to use OWA http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/d6837e99-668b-4c63-a897-3f2ae710fc12James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

It's not all users. So I dont think that is it.

After further research, it's definetly not everyone, but more than a handful. Many more than a handful. So that leaves me to believe it's a desktop or IE issue, what exactly would I look for there. Unfortunately one of my pc's is affected, which is good in that I can troubleshoot the issue.

if you think it's one of your pcs, have the problem user use another working machine to test. Typically these are server side errors in most of the cases.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

if you think it's one of your pcs, have the problem user use another working machine to test. Typically these are server side errors in most of the cases. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com If you can explain your thought process, that would help. Why say 30 pc's out of thousands would behave this way and it still be a server side issue makes zero sense. The issue happens every single time a new mail is received in OWA. It's not user specific. User can log on to a different PC and it does not happen. I am having our desktop support people look at it now. If it was the OWA virtual directories, it should be happening to all users...

Hi, Please verify if the issue would occur with owa inside the network and OWA outside the network. Please verify if the issue only occur to certain CAS user. You can use connection status from outlook to verify the server that it connect to. Please try to check related error event from your CAS servers and then post here. Please verify if you have anti-virus application installed on Exchange and client, such as symantec. Besides, how many CAS servers in the network? Please verify all the exchange server version is to rollup7 with SP3. Are they in the same site? Do you have ISA infront of the network? Xiu Zhang TechNet Community Support

The problematic machines are all XP SP3 with IE8. Happens inside and outside the network. We use Apache mod proxy to reverse proxy OWA and Activesync on the outside. It has been up and running since 2008 without change (the reverse proxy). We have many cas, all users hit OWA through a NLB VIP to one of 2 CAS servers at our main site. I have hit the individual CAS servers individually through https://servername.domainname.domain/owa on the inside and get same result. I am going to have one of the problematic pc's re-imaged and see if it fixes it. I think at this point it's a desktop issue, not an exchange issue.