Internet Explorer Error 12152
DriverDoc WinSweeper SupersonicPC FileViewPro About Support Contact Errors Troubleshooting › Runtime Errors › Microsoft Corporation › Internet Explorer › Error 12152 How To Fix Internet Explorer Error 12152 Error Number: Error 12152 Error Name:IE Error 12152 Error Description: Error 12152: Internet Explorer has encountered a problem and needs to close. We are sorry for the inconvenience. Developer:Microsoft Corporation Software:Internet Explorer Applies to:Windows XP, Vista, 7, 8 Download NowWinThruster 2015 - Scan your PC for computer errors. Compatible with Windows 10, 8, 7, Vista, XP and 2000 Symptoms of Error 12152 "Error 12152" appears and crashes the active program window. Your PC frequently crashes with Error 12152 when running the same program. “IE Error 12152” is displayed. Windows runs sluggishly and responds slowly to mouse or keyboard input. Your computer periodically “freezes” for a few seconds at a time. These 12152 error messages can appear during program installation, while a Microsoft Corporation-related software program (eg. Internet Explorer) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your 12152 error occurs is a critical piece of information in troubleshooting the problem. Causes of Error 12152 Corrupt download or incomplete installation of Internet Explorer software. Corruption in Windows registry from a recent Internet Explorer-related software change (install or uninstall). Virus or malware infection that has corrupted Windows system files or Internet Explorer-related program files. Another program maliciously or mistakenly deleted Internet Explorer-related files. Runtime Errors such as “Error 12152” can be caused by a variety of factors, so it is important that you troubleshoot each of the possible causes to prevent it from recurring. Runtime Errors Knowledgebase Article ID: 124224 Article Author: Jay Geater Last Updated: 20-07-2016 Popularity: star rating here Download NowError Fix Learn More Tweet Recommendation: Scan your PC for computer errors. How To Fix Internet Explorer
Internet Explorer assumes the connection will close in a minute but Apache2 attempts to close after 5 seconds. The problem is that if the connection is closed and the initial POST fails, Internet Explorer will only send the header but not the HTTP body. Since the Apache2 server is expecting the rest of the data, eventually a timeout occurs and the 12xxx errors. http://stackoverflow.com/questions/4796305/why-does-internet-explorer-not-send-http-post-body-on-ajax-call-after-failure These patches exist in IE7-IE9, http://www.solvusoft.com/en/errors/runtime-errors/microsoft-corporation/internet-explorer/12152-ie-error-12152/ but they aren't by default activated. This hotfix is included in Internet Explorer 7. However, the hotfix must still be enabled as described in the "How to enable this hotfix" section. Internet Explorer 8 This hotfix is included in Internet Explorer 8. However, the hotfix must still be enabled http://hustoknow.blogspot.com/2012/12/microsoft-internet-explorer-12152-errors.html as described in the "How to enable this hotfix" section. Internet Explorer 9 This hotfix is included in Internet Explorer 9. However, the hotfix must still be enabled as described in the "How to enable this hotfix" section. http://support.microsoft.com/kb/895954 http://support.microsoft.com/kb/831167/en-us We could disable keepalive's for all Internet Explorer sessions, but here's one way using SetEnvIf in Apache 2.2 to accomplish it: # Remove after upgrading to Apache 2.4 and we can use SetEnvIfExpr instead of # this funky logic. # # Test by: # curl -v --user-agent 'Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.2; WOW64; Trident/6.0; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET CLR 3.0.30729; BRI/2;)' -H "X-Requested-With: XMLHttpRequest" -k # # ...and all different combinations. # # Based on: http://stephane.lesimple.fr/blog/2010-01-28/apache-logical-or-and-conditions-with-setenvif.html # # Logic below will disable keepalive's on Ajax-based IE browsers. We may see a small performance # hit but better than random 12
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of http://stackoverflow.com/questions/33080095/network-error-12152-websockets-in-edge-and-ie-11 this site About Us Learn more about Stack Overflow the company Business http://forums.asp.net/t/1490184.aspx?Strange+Problem+only+IE+fires+up+error+XmlHttp+12152 Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up internet explorer Network Error 12152: WebSockets in Edge and IE 11 up vote 2 down vote favorite I have a site using websockets secure (WSS) and works very well in chrome. Testing in IE and Edge also works however in the browser console I get Network Error 12152 which will also trigger the websocket.addEventListener("error",function(){}) if implemented. Everything actually works I just get this error which internet explorer error doesnt seem to break anything. Error is triggered When socket is closed from Browser Side Headers in EDGE More Info: Example of the code I use //connect via wss then ws.addEventListener("error",function(event){ // this hits when Socket is closed}) ws.addEventListener("open",function(){ ws.addEventListener("message",function(event){ //do stuff ws.Close() }) }) To Confirm the problem further I went to https://www.websocket.org/echo.html in edge the site which has the ability to test websocket connections. I made it connect to my server. which opens the connection without a problem. However in just the same way I have been getting problems with my code. This site also throws an error when I click the disconnect button. See Image Below. Is this a bug in IE/Edge? My Server isnt disconnecting correctly? I use the above site with the default destination (Their websocket server) and not mine. There are no errors. But when connecting to mine on disconnect there are errors. What could be the problem? Thanks javascript internet-explorer websocket microsoft-edge share|improve this question edited Oct 12 '15 at 13:53 asked Oct 12 '15 at 11:34 SammyG 7611 This is not about ajax post's @JaromandaX, the last
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/General ASP.NET/ASP.NET AJAX + Ajax Control Toolkit/Strange Problem: only IE fires up error [XmlHttp] 12152 Strange Problem: only IE fires up error [XmlHttp] 12152 [Answered]RSS 4 replies Last post Feb 16, 2010 06:18 AM by johngrinder ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Support Options Advanced Search Related Links GuidanceVideos Reply johngrinder Member 24 Points 70 Posts Strange Problem: only IE fires up error [XmlHttp] 12152 Nov 07, 2009 07:27 PM|johngrinder|LINK Hi Folks, i have a very very strange error on my application: i'm using a .NET webservice, which sends some data, nothing complex: its just about firing two numbers to the webservice and receiving the values. Nothing complex, no SSL/HTTPS, nothing. Just a damn simple webservice. So, in FireFox everything works fine. But, when users with IE are trying to get the page, all of them receive error "12152". The strangee thing is: this seems to be purely an IE issue. I've googled already: all people having the same error are driving with SSL/encryption and stuff like that. In my scneario, all these conditions don't fit in. The funny thing is: i went over to webservices when i read about the "page overload" (when handling/processing a full ASP.net page). I though, OK lets move this few functions to a webservice, so the server wouldn't have to instantiate a full ASPX page to process this stuff; but, honestly, the "old version" (via ASPX page) worked out completely uncomplicated, now i have this strange problems. And all this is because i _thought_ a webservice would be more performant. Additional info is: i build my webservice based on Dino Espositos Book, and yes, i followed the text in the book; but now.... thats really strange. Can anyone point me to a usefull information? Regards Reply thirumaran00... Contributor 4964 Points 1731 Posts Re: Strange Problem: only IE fires up error [XmlHttp] 12152 Nov 07, 2009 10:40 PM|thirumaran007|LINK Friend, this should be some firewall problem. after uninstall your firewall software or disable you can try again it will work ! Please remember to click "Mark as Answer" on this post if it helped you With Friendly, Thirumaran Reply johngrinder Member 24 Points 70 Posts Re: Strange Problem: only IE fires up error [XmlHttp] 12152 Nov 08, 2009 03:14 AM|johngrinder|LINK Hi Thiruman, i wanna