If you are logging clientside errors, your may see two errors show up with Ajax applications. The first error is with IE: "Automation server can't create object" and the second error was Mozilla: "NS_ERROR_NOT_AVAILABLE". Now I will tell you what causes them.
Automation server can't create object
Well this error commonly will show up with IE6.0 in your logs. This is a really simple error to reproduce. Set your security level to high and then enable active scripting (JavaScript). Run your application. If you get an error, that means you are not using try catches when you are setting the ActiveX object. So if you see this error you just need to add try catches around your declaration. Basic example is below:
try{
this.req=new ActiveXObject("Microsoft.XMLHTTP");
}
catch(e){
}
NS_ERROR_NOT_AVAILABLE
This error took a little investigation on my part. So I did a search on bugzilla and came up with this link:https://bugzilla.mozilla.org/show_bug.cgi?id=238559#c0
So you do not have to search through the whole page I posted the problem with Mozilla and why it causes the error:
<quote from https://bugzilla.mozilla.org/show_bug.cgi?id=238559#c0>
Mozilla calls onload() for all HTTP transactions that succeeded. The only time it calls onerror() is when a network error happened. Inside the onerror handler, accessing the status attribute results in this exception: Error: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXMLHttpRequest.status]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file:///Users/chuck/errtest.html :: anonymous :: line 114" data: no] Source File: file:///Users/chuck/errtest.html Line: 114</quote>
Now an easy fix for now is to add another try catch in your onerror function when you are reading the status property. This will stop the error occuring, but thanks to this, you will not have all of the information that you could have with IE.
Error Handling
On of the best things you can do is implement error handling on your clientside applications. Logging them to the server can let you spot problems that you may never see. You may never new about these errors on your site if they never came up in testing. Logging problems will allow you to see them. I am doing a talk on this at The Ajax Experience in May.
Eric Pascarello
Coauthor of Ajax In Action
Moderator of HTML/JavaScript at www.JavaRanch.com
Author of: JavaScript: Your Visual Blueprint for Dynamic Web Pages
Hi Eric, I noticed a difference between IE and Mozilla with innerHTML. It looks like innerHTML content length is limited in Mozilla.the problem with mozilla seems not to be on innerHTML, but accessing XML DOM element's contents. I've resolved the problem by not using XML as response, but a plain/text reply, and use .responseText instead of getting an elements contents from .responseXML well, in fact i've had other information than the html data that i should transmit, and i've used JSON for both other data and the html string.
var status = "";
try{
status = yourXHRVariable.statusText;
}
catch(e){
status = "Trouble accessing it";
}
Eric
扫一扫
2645
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
