Panoramio's Blog

18 Responses to “Explorer system error: -1072896658”  

1. 1 Johan Sundström on Nov 2nd, 2005 said:

   Shouldn’t that rather be Content-Type: text/plain; charset=UTF-8 (or perhaps text/javascript, depending on the content payload)?

2. 2 Joaquín Cuenca Abela on Nov 2nd, 2005 said:

   Hi Johan,

   yes, it should be Content-Type: text/plain; charset=UTF-8, thank you for the catch! I wrote this entry in a hurry and I missed it completely.

   Regards,

3. 3 Michael McCorry on Nov 3rd, 2005 said:

   Thank the moons for this post. After looking for about 30 mins, this is the first page I’ve found on this subject that explains in plain english exactly what is causing the problem, and how to fix it. In my case it only appears to occur on a Linux server (I’ve tried it on two other IIS servers and they worked fine - unfortunately, they’re not my production servers). Thanks Joaquín. I’ll try it out tonight. *fingers crossed*

4. 4 intenter on Jan 6th, 2006 said:

   Bless you for this post!
   It was just encoding!
   So, XMLHttpRequest accepts UTF-8… But the rest of the page in other encoding….Does browser convert data from UTF-8 into another encoding?

5. 5 Joaquín Cuenca Abela on Jan 7th, 2006 said:

   Hi,

   Yes, indeed, the exception comes from mlang.dll, I guess that when it tries to do the conversion.

   But I have not really tested it, as all my pages are in UTF-8, so I don’t really need any conversion. If you are using ISO latin 1, it’s also accepted by XMLHttpRequest, but again, you should be extremelly careful with the name you give the encoding (respect uppercase characters, hyphens, …). For iso latin 1, the charset must be ISO-8859-1

   Cheers,

6. 6 Marcos B.L. on Feb 15th, 2006 said:

   Funny captcha … and great tip, thank you for saving me from my last two hours of frustation.

7. 7 Raj Kanagaraj on Apr 17th, 2006 said:

   This article saved me tons of time. I was about to give up. Thanks a lot.

8. 8 Joe on Sep 8th, 2006 said:

   Phew… unlike the former commenters, I have already spent two (!) days over TCP dumps of http requests from both Firefox and MSIE.

   I was looking for some hint why on earth IE falied where Firfo just worked. And then I noticed the supid “error big negative number”, nicely tucked away in a try{} catch{} block.

   Going to have someone change the apache conf - glad that finally there *is* an explanation - thanks a million!

   Oh, and by the way, if you need dumps of your tcp traffic, tcpflow is a nice command line utility (compiles fine on Mac OSX).

9. 9 Philipp Jardas on Dec 18th, 2006 said:

   Thanks for that concise description of the problem. I hope MSIE would be that verbose… =) For your general amusement: In our current setup we use an Oracle Application Server which does not only send different default encoding headers on different platforms, it even send ISO-8859-1 as “ISO-8859_1″ (note the underscore) which wrecked the pages when requested via AJAX, but not when requested directly. You have to manually set the content type in your servlet or JSP or whatever you are using.

10. 10 Ot4eto on Feb 13th, 2007 said:

    The Exact command is:
    http_request.setRequestHeader(’Content-type’, ‘text/plain;charset=UTF-8;’);

    where http_request is instance of XMLHttpRequest object.

11. 11 Eugene on Mar 23rd, 2007 said:

    Thank you!
    This post saved my nerves
    It was just encoding, damn!

12. 12 Kuroki Kaze on Apr 2nd, 2007 said:

    THANK YOU MAN!!!!!! It was the encoding…. i had serious troubles with russian language pages (hehehheehe)

13. 13 Pyronhell on Apr 3rd, 2007 said:

    You can set the content-type with php:

    At line 1 of your requested file with XMLHttpRequest
    (change text/html with text/plain if required).

    See ya!

14. 14 loony on Apr 10th, 2007 said:

    Add a file called .htaccess to your websites rootdirectory if you are using apache (or your isp uses apache) and it’s delivering the wrong charset (like utf8 instead of utf-8 as IE expects it) with the following content:

    AddCharset utf-8 .php

    (or any other extension that might be useful in your context.

    See
    http://msdn.microsoft.com/workshop/author/dhtml/reference/charsets/charset4.asp
    and
    http://www.w3.org/International/questions/qa-htaccess-charset
    for more information on character encoding issues!

15. 15 Tushar on Apr 27th, 2007 said:

    throughs an error System error 1072896658

    I have declared the object as
    var xmlhttp = new ActiveXObject(”Msxml2.XMLHTTP”);

    it works for IE version 6.0.2600 but not for IE version 6.0.2800.

    Pls help me

    i coudnlt find out what this error means.

16. 16 Matias P. on Aug 29th, 2008 said:

    Joaquin,

    Thank you very much for the excelent post… It make my day.
    I am form Argentina, greetings.
    I have translated the solution to spanish

    Regards.

    Español/Spanish:

    Problema del IE6 (Internet Explorer 6) Error del sistema -1072896658,:

    Es muy probable que la página que esté llamando el JavaScript, tenga mal la codificación, en vez de “UTF8″ hay que usar “UTF-8″.

17. 17 RycAm on Oct 23rd, 2008 said:

    in case using php. The charset must also be set correctly: default_charset = “utf-8″
    And not default_charset = “utf8″.
    easy, but I missed it during 1 long day.

18. 18 zunebest on Apr 28th, 2009 said:

    “But I have not really tested it, as all my pages are in UTF-8, so I don’t really need any conversion. If you are using ISO latin 1, http://www.zuneconverter.net it’s also accepted by XMLHttpRequest, but again, you should be extremelly careful with the name you give the encoding (respect uppercase characters, hyphens, …).”

Leave a Reply