MySpace Open Platform

A Place For Developers

Welcome Developers!

in

Welcome!

in

Component returned failure code: 0x80040111

Last post 03-24-2008 8:45 AM by mNeo. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 03-23-2008 12:29 PM

    • mNeo
    • Top 25 Contributor
    • Joined on 02-05-2008
    • Posts 109

    Component returned failure code: 0x80040111

     Error: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXMLHttpRequest.status]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: http://api.msappspace.com/OpenSocial/MyOpenSpace001.Engine.js :: anonymous :: line 277"  data: no]
    Source File: http://api.msappspace.com/OpenSocial/MyOpenSpace001.Engine.js
    Line: 277

    I am seeing this error very frequently. What does this mean?

  • 03-24-2008 2:53 AM In reply to

    Re: Component returned failure code: 0x80040111

     I am having this error as well.. more than frequent now..but what that means? me also asking..

  • 03-24-2008 7:28 AM In reply to

    Re: Component returned failure code: 0x80040111

     From: http://helpful.knobs-dials.com/index.php/%22Component_returned_failure_code:_0x80040111_(NS_ERROR_NOT_AVAILABLE)%22

     

    This happens when you have a XMLHttpRequest onerror handler in which you tried to read the result's status (or statusText) when that value is not available, usually meaning it was broken off, or it failed in a specific way.


    The W3 specs tell you that you shouldn't try to read status in the onerror handler because for some problems it may not be set, and that in this case an error must (!) be raised. This error is specific to Gecko (Firefox, Mozilla) because it adheres to those specs closer than most other browsers. The Gecko specs also tell you not to do this (...as I recall, I can't actually find it right now).


    The cause is often that the browser never got a reponse with a HTTP status to parse out, for example via requests that are broken off on the client, a connection that broke because of some connectivity problem, and sometimes a (seriously) malformed server response.

    The problem can also occur when AJAX is canceled by page unload, e.g. when you trigger AJAX from a form that also causes a page-reload-style submission (often a form with a submit

     

  • 03-24-2008 7:29 AM In reply to

    Re: Component returned failure code: 0x80040111

     Reading further:

    the simplest fix is probably wrapping the status read in a try-catch
    .

     

    Sounds like it is a firefox issue that Myspace simply needs to workaround in their xhtmlhttprequest handling. 

  • 03-24-2008 8:45 AM In reply to

    • mNeo
    • Top 25 Contributor
    • Joined on 02-05-2008
    • Posts 109

    Re: Component returned failure code: 0x80040111

    Thanks for the information, Sebastian. Let's hope MySpace fixes this soon. 

Page 1 of 1 (5 items)