I'm facing the below error in IE 11, I'm calling a webapi, though webapi response is coming fine but also getting the below error on console:
SCRIPT7002: XMLHttpRequest: Network Error 0x2eff, Could not complete the operation due to error 00002eff.
Please give any suggestion, what could be the root causes of this error, I'm not getting this error in other browsers (Chrome and Firefox)
You've said that the error occurs when you call a webapi.
As far as I'm concerned, maybe this due to a large amount of data to transfer.
When you handle large data with single ajax request, it may make the browser crashing.
For more about the error,you may refer to the similar thread.
IE11 HTTPS AJAX XMLHttpRequest: Network Error 0x2eff, Could not complete the operation due to error 00002eff
Related
When I load my test site (Laravel/Vue) I'm getting the alert:
The FetchEvent for "http://127.0.0.1:8000/index.php" resulted in a
network error response: the promise was rejected.
Other posters here with a similar problem usually had a service worker involved, so I turned off that part of the code and cleared the caches - but the problem remained.
My first problem is that I just don't know where to look to try and find the source of the problem. How do I find the FetchEvent for ...index.php?
Thanks/Tom
That error message logged to the chrome console from a long-pending request after around 15 minutes.
It looks client-side error because server processing still worked.
I did not find any article related to this error message.
can any buddy let me know how to solve this issue?
According to the chromium source I think it means that a spdy ping timed out.
...
{net::ERR_EMPTY_RESPONSE, "http.response.empty"},
{net::ERR_HTTP2_PING_FAILED, "spdy.ping_failed"},
{net::ERR_HTTP2_PROTOCOL_ERROR, "spdy.protocol"},
...
Source https://chromium.googlesource.com/chromium/src/+/lkgr/components/domain_reliability/util.cc#48
Chrome sends such pings before and after a request.
Source https://groups.google.com/d/msg/spdy-dev/HFjAbFRd-N0/p-Edt-lneGsJ
I got an AJAX error while running Drupal 7.
"An AJAX error occured.
HTTP result code: 500
Debugging information follows:
Path: system/AJAX
StatusText: error
Response text:"
There is no response text. I have looked everywhere and tried a couple of things, but nothing works. Anyone have an idea on how to fix it?
Thanks
Check your watchdog table, if nothing there check the php error log.
Also use Firebug's console to check what is returned after the ajax request for any clues.
Can also try disabling third party modules one at a time to find out what is causing the error.
There is a log entry saying that there is an error on client side, however, the errors are not shown in Firebug.
Where can I see error details?
What you are seeing in an internal error generated by the google drive framework. It's not necessarily a critical error--the framework seems to discard the error.
Firebug does not show an indication of an error, because the message you're seeing is generated by the console.log function (i.e. it's not a javascript compilation error.)
If you could share the code, perhaps it would be easier to say how the error was generated.
I have full control on both server side and client side.
Recently, I am using AjaxControlToolkit.AsyncFileUploader. However under some circumstances, the AsyncFileUploader triggers browser to show an alert box with the word "Unknown Server Error".
I tried to locate all exceptions in Global.asax and tried all three major browsers (FF, IE, Chrome). But it is very strange that
No server side exception can be found in method Application_Error in Global.asax
No client side exception can be found in FireBug, IE Developer Toolbar and Chrome internal debugger.
No error log in Window Event log
So what can I do for this Unknown Server Error?
Thanks!
I fixed the problem already. I set breakpoints on all events header and run the application. Finally I found some events is not triggered which should be triggered.
After fixing this problem, the "Unknown Server Error" is gone.
However, I still don't know how to get more information about the "Unknown Server Error".