Browser Form Page Errors in Internet Explorer Only. - InfoPath Dev
in

InfoPath Dev

Browser Form Page Errors in Internet Explorer Only.

Last post 01-07-2011 09:11 AM by shniggens. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 01-06-2011 08:58 AM

    Browser Form Page Errors in Internet Explorer Only.

    Expanding on a previous problem I was having with conditional formatting, where I was going around and around in circles trying to determine why certain controls in my form were not posting back, I eventually figured out that this problem only occured in IE Explorer (which I find kind of ironic), and not in any other browser.  Actually, this form behaves best in Firefox. 

    This is unacceptable for our organization, since most of our users use to IE, and probably will not want to change.  Nor should I expect them to. 

    I tried upgrading to IE 9, and adding our SP site to the compatibility view, but neither one of these approaches changed anything. 

    Here is the error I am getting -

    Webpage error details

    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; .NET4.0E)
    Timestamp: Thu, 6 Jan 2011 16:57:28 UTC


    Message: Invalid argument.
    Line: 2
    Char: 452421
    Code: 0
    URI: http://10.10.2.139/_layouts/inc/Core.js?rev=8PdoqL6fQahtzwwVSZ2lpw%3D%3D

    Any suggestions on how I should approach troubleshooting this problem?

     Thanks!

  • 01-06-2011 03:59 PM In reply to

    Re: Browser Form Page Errors in Internet Explorer Only.

     

    Looks like a rich text box control in my form is causing the error.  That's all I've been able to figure out so far.  I've tried re-inserting it with the default sizing.  It changed the position (char) of the error, but didn't resolve the issue. 
  • 01-07-2011 09:11 AM In reply to

    Re: Browser Form Page Errors in Internet Explorer Only.

    OK, removing the rich text boxes completely fixed the problem. 

Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.