Corrupted OWA Signature
Running Exchange 2007, I tried to duplicate my HTML signature that I use in Outlook as well as I could, in Outlook Web Access. The signature was created in Microsoft Word, copy-pasted into Outlook because it includes a table, and the signature edit box in Outlook does not support the creation of a table. When I copied the signature to the OWA, and fixed it to display correctly (removed the graphic, etc.), and saved, everything said it saved. Clicking to another Option setting got this error: Outlook Web Access has encountered a Web browsing error. Client Information------------------User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; InfoPath.2; .NET CLR 3.0.04506.30; .NET CLR 2.0.50727)CPU Class: x86Platform: Win32System Language: en-usUser Language: en-usCookieEnabled: trueMime Types: Exception Details-----------------Date: Wed Jan 30 08:40:12 CST 2008Message: 'all' is null or not an objectUrl: https://aurora/owa/?ae=Options&amp;t=MessagingLine: 15 Call Stack----------dispFb(oFb,fDspPuClr)oFb = 'undefined'fDspPuClr = 'undefined'unload() Dump Event----------recordset = nulltype = errorfromElement = nulltoElement = nullaltLeft = falsekeyCode = 0repeat = falsereason = 0behaviorCookie = 0contentOverflow = falsebehaviorPart = 0dataTransfer = nullctrlKey = falseshiftLeft = falsedataFld = returnValue = undefinedqualifier = wheelDelta = 0bookmarks = nullbutton = 0srcFilter = nullnextPage = cancelBubble = falsex = 0y = 0srcElement = nullscreenX = 505screenY = 810srcUrn = boundElements = [object]clientX = 83clientY = 336propertyName = shiftKey = falsectrlLeft = falseoffsetX = 0offsetY = 0altKey = falseerrorMessage = 'all' is null or not an objecterrorUrl = https://aurora/owa/?ae=Options&t=MessagingerrorLine = 15errorCharacter = 32errorCode = 0 The signature ends with a HTML snippit of "<SPAN" and stops. You cannot clear the error and have to dump the tab. All attempts to use OWA to re-edit and resave the signature fail with the same error. Short of backing up the mailbox, dumping the account and recreating, is there another way to correct the problem? I'm sure there is a "right" way to do it, instead of that workaround. Bryan Britt Beltane Web Services
January 30th, 2008 5:46pm

Hi there...was there any resolution to this issue? I am having the same problem with one of my end users. I suspect they have copied in some dodgy HTML with their OWA Sig. Any help would be appriciated! Anthony Client Information------------------User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.2; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)CPU Class: x86Platform: Win32System Language: en-usUser Language: en-auCookieEnabled: trueMime Types: Exception Details-----------------Date: Thu Jan 31 10:52:00 UTC+0900 2008Message: 'body' is null or not an objectUrl: https://mail.yourexchange.com.au/owa/?ae=Options&amp;t=MessagingLine: 8 Call Stack----------initSgCtrl()onWL()tryWLd()chkScrpts()window.onload() Dump Event----------recordset = nulltype = errorfromElement = nulltoElement = nullaltLeft = falsekeyCode = 0repeat = falsereason = 0behaviorCookie = 0contentOverflow = falsebehaviorPart = 0dataTransfer = nullctrlKey = falseshiftLeft = falsedataFld = returnValue = undefinedqualifier = wheelDelta = 0bookmarks = nullbutton = 0srcFilter = nullnextPage = cancelBubble = falsex = 0y = 0srcElement = nullscreenX = 983screenY = 147srcUrn = boundElements = [object]clientX = 983clientY = 29propertyName = shiftKey = falsectrlLeft = falseoffsetX = 0offsetY = 0altKey = falseerrorMessage = 'body' is null or not an objecterrorUrl = https://mail.yourexchange.com.au/owa/?ae=Options&t=MessagingerrorLine = 8errorCharacter = 139errorCode = 0
Free Windows Admin Tool Kit Click here and download it now
January 31st, 2008 4:59am

And I'm another guy facing the same problem. What is odd is the fact that once you paste the dodgy signature, the error shows up in every tab orlink you select in the Option menu, even the ones where the signature is not being displayed at the moment. If you try to delete the signature, and save it, it doesn't work. It tells you the new settings were saved but next time you go to Options, the signature (and the error) still there. And one more important fact: the problem happens in any machine you access that account, so is not something with the machine and/or brwoser settings. Curious point: the error doesn't show up if using Firefox, but you can't fix the problem too... Any suggestions?
January 31st, 2008 6:05pm

Sill havent been able to find anything out on this one. Anyone at MS shed some light?
Free Windows Admin Tool Kit Click here and download it now
February 1st, 2008 10:06am

It is obvious that the error is caused by the Rich-Text/HTML Editor Control used on the Signature field. When you navigate to the Options, you see the signature in the field, but you do not see the Controls. Then you get the error when you attempt to do anything on the page and continuing after you navigate away from the page. Since you cannot successfully edit the signature using Internet Explorer or Firefox, I signed onto OWA from a Windows Mobile 6 device. When you navigate to the Options page with the errant signature field on it, you can then edit the signature. Since Windows Mobile cannot use the same Rich-Text Controls that are used on the desktop, Microsoft presents you with an alternative: You see the signature as HTML, and below it is a Checkbox for "Replace the signature above with this" and a normal text box that you can type a new signature into. And save. Replacing the signature with the plain text in the field on Mobile 6 clears the corrupted signature. When you return to a desktop, the signature is now the plain text, and can be re-edited correctly. Apparently the Rich-Text Controls cannot successfully handle either a table in the signature or possibly Microsoft Word's verbose HTML that created it. Using Word to createasignature is the Microsoft work-around for the limited Outlook Signature Editor for more complex signatures. Apparently this does not carry forward to OWA. Bryan Britt Beltane Web Services
February 2nd, 2008 5:23pm

As a further update to this, I logged in using FireFox, forcing OWA light. From there I was able to make the change as mentioned above. I would still like to know where in AD/Exchange the signitures are stored for future reference. Anthony YourASP Pty Ltd
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2008 5:38am

It is obvious that the error is caused by the Rich-Text/HTML Editor Control used on the Signature field. When you navigate to the Options, you see the signature in the field, but you do not see the Controls. Then you get the error when you attempt to do anything on the page and continuing after you navigate away from the page. Since you cannot successfully edit the signature using Internet Explorer or Firefox, I signed onto OWA from a Windows Mobile 6 device. When you navigate to the Options page with the errant signature field on it, you can then edit the signature. Since Windows Mobile cannot use the same Rich-Text Controls that are used on the desktop, Microsoft presents you with an alternative: You see the signature as HTML, and below it is a Checkbox for "Replace the signature above with this" and a normal text box that you can type a new signature into. And save. Replacing the signature with the plain text in the field on Mobile 6 clears the corrupted signature. When you return to a desktop, the signature is now the plain text, and can be re-edited correctly. Apparently the Rich-Text Controls cannot successfully handle either a table in the signature or possibly Microsoft Word's verbose HTML that created it. Using Word to create a signature is the Microsoft work-around for the limited Outlook Signature Editor for more complex signatures. Apparently this does not carry forward to OWA. Bryan Britt Beltane Web Services Thanks, this helped, had the same issue and the only way i was able to remove or change the signature was using IE on a windows mobile device 6.5 and it corrected the error and signature. im sure this will work with previous version of windows mobile.
July 27th, 2010 7:01pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics