we have a Struts 2 application. It has a web page that works fine in all browsers except IE 11. The page hangs while loading and stops responding. How to troubleshoot the page hung issues in IE 11 ? Please give some tips.
You could use a virtual machine to achieve so. Refer to Microsoft virtual machines download page for more information. The only problem is that you will be able to test IE8 as the minimum version. There is a specific VM with Windows 7 and Internet Explorer, so if you can use a VM you will be able to test your app.
Other possible solution is to use IETester, it has some bugs, but you can even download a debug bar for it.
Hope it helps.
Finally, we were able to resolve the hung issue in IE browser. We did the following :
In IE, we opened the F12 Developer Tools and went to the Debugger tab.
Clicked on the page that was getting hung.
In the Debugger tab, it showed the line number that was resulting in error. The error was something like "method not supported". The code was
document.form.submit="post".
Made changes in code to solve the error. I modified tag with property method="post" instead of "get".
This fixed the issue.
Related
Umbraco 7.6.6, running under IIS 8.5 on fully patched Windows Server 2011 R2 Standard, 64bit.
Our content editors notice that often when they create a new article (which has some graphics specified) the system hangs after they try to browse to a different article... or indeed anywhere in the front-end site, too. It only affects them; other users are still able to browse and/or create content.
F12 dev tools shows that browser is pending the result of this type of call:
http://whatever.com/media/1101/thumbnail_pmc-1x2.jpg?width=500&mode=max&animationprocessmode=first
If I try to view that thumbnail without the querystring data, it loads instantly... while the first call is still hanging in it's unresponsive tab:
http://whatever.com/media/1101/thumbnail_pmc-1x2.jpg
DEBUG level Umbraco logs just show this:
2017-10-10 17:02:53,120 [P2816/D6/T57] DEBUG Umbraco.Web.UmbracoModule - Begin request: http://whatever.com/media/1101/thumbnail_pmc-1x2.jpg?width=500&mode=max&animationprocessmode=first.
No errors in the umbraco logs, no errors in IIS logs, nothing in event viewer.
Best I can tell, something is going wonky in the browser. Can anybody please advise on how I can troubleshoot further?
Thanks!
I have a web app with asp.net mvc 5 on running on iis 7.5. I have a photo upload page that I made with DropZone (a javascript ajax upload plugin). In my asp.net controller during certain errors, I return an httpstatuscode of 500 with a status description with a descriptive error. DropZone then displays this descriptive error. Everything works as it should on desktop devices, however when used on an iOS device it displays a generic "Internal Server Error" message.
I'm lost at how to troubleshoot this issue. I've placed javascript alerts throughout my javascript code to try and figure out what the issue is but that didn't reveal anything helpful. I've tried using the MIHTool ipad app and the HttpWatchBasic ipad app to try and set breakpoints but that was not helpful either.
Is there a way to remotely debug an asp.net web app from an iPad? (I have visual studio 2013 premium) Or does anyone have any ideas what may be causing a different status code to be sent?
UPDATE: It appears that iOS devices ignore any custom xhr.statusText and uses the standard default statusText (i.e. code 500 is Internal Server Error). As a work around (which I hate doing, but since this is primarily for use on company iPads I didn't have much choice) I've returned a different 500 class code for each possible exception and then in the javascript code check the status code and assign my own custom error message in the javascript code.
Quickest and easiest way to see the actual exception is to turn off custom errors in your Web.config - you'll then be able to view the actual stacktrace on the iPad.
If you'd like to be able to debug the exception, you should be able to trigger it by accessing the site from the iPad by hitting your windows development machine while running in the debugger. You'll need to configure IIS express to allow remote connections (editing application host.config), adding a urlacl, and opening the Windows firewall if necessary. There are numerous guides in setting this up online.
If you want to actually debug the JS in mobile Safari, this is possible from the Mac version of Safari - see http://webdesign.tutsplus.com/articles/quick-tip-using-web-inspector-to-debug-mobile-safari--webdesign-8787 for details.
If I debug with Firefox and some image is missing, then I am able to see the following error on the console; That's what I want in Internet Explorer (10), but I'm not getting any errors:
"NetworkError: 404 Not Found - blahblahblah/myapp/img/clear.png"
So if I'm debugging with IE I'm not getting these important notifications. I've tried to enable all the stuff related to enabling script debugging like disable friendly http errors, enable script debugging and so on. But on the Console for IE (F12) the error never appears.
The only way to be notified is by going to the Network tab at the console and click on the "Start capturing" button, so there I am able to see the 404 lines, but that's not the best way as I'd like the errors to be sown like Firefox does, in the Console error log.
Thanks in advance.
At the moment the IE11 F12 tools don't display network errors in the console. It's something that is high on our backlog that we hope to get to soon.
This is just the difference between the various browser's development tools. Internet Explorer has always had a particularly weak set. The best in my opinion is Chrome's, though Firefox with Firebug is not bad. Firefox on its own is weaker than Internet Explorer, in my opinion.
Regardless, you can debug with whatever browser you want, so probably your best bet, if you like the Firefox dev tools better, is to just switch your debug browser to Firefox in Visual Studio. Just click the "Play"-style arrow button that shows "Internet Explorer" currently and choose another browser installed on your system.
I've designed an SSRS report in SQL Server 2008 R2. I'm displaying the report in an MVC application using the ReportViewer control.
It is working fine in Firefox and Chrome and below IE10 browsers. However, in IE 10 the report is not getting displayed.
If I changed browser mode to IE10 Compat View in the IE Developer Tools (F12), it is working fine. Please check the attached images:
I have gone through several forum's posts, most of them suggesting to keep an meta tag in master file:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIEX">
where X is the IE Version. Some other forum threads suggests to install Service Pack 2 for SQL Server, which I tried but still no luck.
We can not suggest to end user (some of whom may be non-technical) to change the browser mode in Developer Tools.
Please help me display the report in latest IE browsers (IE10 or above) by default.
I've had a similar problem plaguing me for awhile now, and I've never truly been able to get IE10+ to display a report without using compatibility mode. I did discover a workaround though.
Instead of displaying the report in the Report Viewer, I set the display mode to open the report in another program. It appears that your report could be exported to Excel, so I would set the report to open in Excel.
In c# it would look something like this:
rp.ReportDisplayMode = "Excel";
While debugging a JavaScript program I was writing with Firebug, the Script panel stopped working and I got the following message:
I went through all menus and sub-menus I could find but didn't see a option to re-enable this feature. The console.log() command doesn't work in Firebug as well (while it does work in the built-in devtools' console).
How can I re-activate the Firebug Script panel? What may have caused this?
This may have different causes. One of them is described in issue 5646, which is related to going back and forward in the browser history.
In such cases it normally requires a browser restart to work again.
Note that Firebug up to version 1.12 is based on an old debugger API exposed by Firefox called JSD, which is unmaintained and buggy. Since version 2.0 Firebug uses a new debugger API, which fixes this problem.
Coincidentally, I just "fixed" the same problem with my Firebug.
I went through re-installs, options resets and such and nothing helped.
After some investigation it boiled down to the content of the page I was debugging.
I have a function called by jQuery when page load is finished:
<script>
$(onPageLoad);
</script>
Now, this function asks user to enter his name using prompt() function. It appeared that Firebug wouldn't activate script panel until prompt() is closed. That is not a problem when you have just one page opened since you just close the dialog and everything works. However, it is a problem when you have two same pages opened. Script panel is non-operational until you close both prompts.
I was facing this problem recently. I found that my Firebug was not getting updated because my Firefox was stuck on 29.x. Once I updated my Firefox the new Firebug got installed. It supports only Firefox 30+.
Note: I was using OSX v1.9.3.
I was having same problem, and, thanks to Roman Guralink, I figured out that the the dialogue Firefox prompts you to insert the master password was the cause. When you set a master password for all password stored, FFox usually opens a dialogue to ask it just after program started. BUT, sometimes this dialogu goes behind the main window, and you don't notice it is there.