- Posted by miketeye on May 20, 2008
Share on Facebook
I have had to deal with one of those needle in a haystack kind of errors for the past few days and after finally pin pointing the source of the error, I felt the obvious need to document the problem, just in case it saves someone else the time and headache it took me to figure it out.
Basically, the problem occurs when you use a MS Ajax SldeshowExtender control on a page with <script> tags which importing javascript files into the asp.net page.
The dreaded Internet Explorer, operation aborted error was persistently occuring even after I had striped the page bare of all components.
Eventually, after hours of troubleshooting, I pinned the problem down to the google analytics tracking code inserted before the closing </body> tag on the page.
When I took out the tracking code, the error ceased. But I still needed the tracking code so I moved the <script> tag which imported the javascript file from google to
the the <head> </head> section of the page, and left the other <script> tags at the position just before the closing body tag. </body>.
It is possible that there is an element naming clash between the SlideShowExtender javascript files aand the google analytics js files. The Internet Explorer Operation aborted error occurs when a child element attempts to modify a parent element. So moving the <script> import from google to the top might have fixed the problem because, at the time it is downloaded, the element name clash does not happen.
This might not be the exact solution for everyone, but I think it provides pointers and clues to help you fix a similar problem when you encounter one.
