Http Error 400 0 64
Contents |
Server Web App Gallery Microsoft Azure Tools Visual Studio Expression Studio Windows Internet Explorer WebMatrix Web Platform Installer Get Help: Ask a Question in our Forums More Help Resources Blogs Forums HomeLearnTroubleshootChapter 4. iis timer_entitybody Diagnosing HTTP ErrorsTroubleshooting HTTP 400 Errors in IIS Troubleshooting HTTP 400 Errors sc-status 500 sc-win32-status 64 in IIS By Mike LaingNovember 27, 2012Tools Used in this Troubleshooter: Network Monitor HTTP Error logging This material
Sc-substatus
is provided for informational purposes only. Microsoft makes no warranties, express or implied. Overview After sending an HTTP request to an IIS server, an HTTP client (such as Internet Explorer) may
Sc-win32-status 0
display the following type of error message: The webpage cannot be found. HTTP 400 Most likely causes: There might be a typing error in the address. If you clicked on a link, it may be out of date. What you can try: Retype the address. Go back to the previous page. Go to Bing and look for the information you want. If sc-status 400 the HTTP client is Internet Explorer, and the Show Friendly HTTP Error Messages option is turned off, the error may resemble the following: Bad Request In these scenarios, IIS has rejected the client's HTTP request because the request did not meet the server's HTTP parsing rules, or it exceeded time limits, or failed some other rule that IIS or HTTP.sys require incoming requests to adhere to. IIS sends the HTTP 400 - Bad Request status back to the client, and then terminates the TCP connection. Troubleshooting Methods When troubleshooting an HTTP 400 condition, it is important to remember that the underlying problem is that the client has sent a request to IIS that breaks one or more rules that HTTP.sys is enforcing. With that in mind, you will want to see exactly what the client is sending to IIS; to do this, capture a network trace of the client sending the bad request. You can analyze the trace to see the raw data that the client sends to IIS, and to see the raw response data that IIS sends back to the cli
Tips/Tricks Top Articles Beginner Articles Technical Blogs Posting/Update Guidelines Article Help Forum Article Competition Submit an article or tip Post your Blog quick answersQ&A Ask a Question View Unanswered Questions View All
Sc-win32-status 995
Questions... C# questions Linux questions ASP.NET questions SQL questions VB.NET questions discussionsforums All timer_connectionidle Message Boards... Application Lifecycle> Running a Business Sales / Marketing Collaboration / Beta Testing Work Issues Design and Architecture connection_abandoned_by_reqqueue ASP.NET JavaScript C / C++ / MFC> ATL / WTL / STL Managed C++/CLI C# Free Tools Objective-C and Swift Database Hardware & Devices> System Admin Hosting and Servers Java .NET Framework Android https://www.iis.net/learn/troubleshoot/diagnosing-http-errors/troubleshooting-http-400-errors-in-iis iOS Mobile SharePoint Silverlight / WPF Visual Basic Web Development Site Bugs / Suggestions Spam and Abuse Watch features Competitions News The Insider Newsletter The Daily Build Newsletter Newsletter archive Surveys Product Showcase Research Library CodeProject Stuff communitylounge Who's Who Most Valuable Professionals The Lounge The Insider News The Weird & The Wonderful The Soapbox Press Releases Non-English Language > General Indian Topics General Chinese http://www.codeproject.com/Questions/795553/WCF-IIS-Log-sc-statusequals-and-sc-win-statusequal Topics help What is 'CodeProject'? General FAQ Ask a Question Bugs and Suggestions Article Help Forum Site Map Advertise with us About our Advertising Employment Opportunities About Us Ask a Question All Questions All Unanswered FAQ WCF: IIS Log sc-status=400 and sc-win32-status=64. [Clinet application does not respond] Rate this: Please Sign up or sign in to vote. See more: C# IIS WCF I have deployed WCF services on IIS 7.5. When i request to Service, It hangs up client application, nothing respond from WCF Service. When I visit IIS Log I got sc-status=400 and sc-win32-status=64. This case is reproduced on production environment. I tried to reproduce on my machine, but i can't. Moreover i am failed to find some helping material by googling. Can any body provides in detail, whats root cause, and how can i reproduce at my machine. Bellow is IIS log for your information 2014-07-10 00:07:21 53.90.35.187 POST /SyncService.svc - 8000 - 53.90.36.144 - 400 0 64 129764 2014-07-10 00:55:05 53.90.35.187 POST /SyncService.svc - 8000 - 53.90.36.144 - 200 0 64 78 2014-07-10 01:45:18 53.90.35.187 POST /SyncService.svc - 8000 - 53.245.9.162 - 200 0 64 639 2014-07-10 02:00:17 53.90.35.187 POST /SyncService.s
my colleague's solaris server, they are not able to import several libraries in order to do so. Thus, they had use socket programming to send out the SOAP request. Everything was doing fine and well on development server, SIT http://softwareengineering-in-a-can.blogspot.com/2010/04/iis-logs-400-0-64.html server, and our local machines. The wierd thing happens when the swing-over to UAT. When the https://forums.asp.net/t/1518896.aspx?Website+stops+working+after+few+requests function was called to send the SOAP request and in the while loop that waits for server response, it kept waiting... waiting... waiting... After several attempts to find faults in the java, web service and JDK versions. There was still no good explanation nor solutions. I went onto the web service machine and dug up the IIS Logs and found a couple of lines that http error showed the request reaching the web service machine but with an error code 400 0 64. After some research, i found out that the error code represents Bad request. Another vague error message -_-. I almost wanted to give up, until i went into the HTTPERR folder and open up the logs and saw something that caught my attention. There was a request coming into the server via port 9090, but the response was sent to a random port number. http error 400 Bingo! In my client's environment, firewalls will block all the traffic going into the servers unless the need arises and we have to write in service requests to open up the port. 1 more problem resolved and hope this post will help anyone that hit this error. Posted by Gary at 9:16 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: c#, CodeProject, java, web service No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) About Me Gary Singapore A software engineer that aspires to be a solution architect someday. View my complete profile Labels .NET (12) AJAX (2) architecture (4) c# (10) CodeProject (27) facebook (2) IIS error (1) iOS 4.1 (1) java (2) jQuery (5) LinQ (2) McAfee sidewinder (1) ms sql (1) N-Tier (1) nodejs (2) non programming (1) OSX (1) performance (4) personal (1) python (1) sharepoint (9) SharePoint 2007 (2) sharepoint 2010 (9) silverlight (1) WCF (2) web service (6) wiki (2) windows phone 8 (2) WSE3.0 (1) Xcode (1) Blog Archive ► 2013 (6) ► November (1) ► June (1) ► May (4) ► 2012 (3) ► November (1) ► June (1) ► January (1) ► 2011 (12) ► December (1) ► October (1) ► September (3) ► July (1) ► May (4) ► March (1) ► February (1) ▼ 2010 (32) ► December (1) ► November (1) ► October (1) ► September (2) ► August (
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/General ASP.NET/Configuration and Deployment/Website stops working after few requests Website stops working after few requests RSS 18 replies Last post Mar 26, 2010 01:48 AM by ank_dotnetdev ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Support Options Advanced Search Reply ank_dotnetde... None 0 Points 18 Posts Website stops working after few requests Jan 27, 2010 09:01 AM|ank_dotnetdev|LINK Hello every1, I developed and deployed a web application using ASP.NET,C# successfully. The application was running perfectly until few days back. [NOTE: It still works fine on local machine (tested using both development server and IIS)] What happens now is: The website opens perfectly. After few operations which involves database interactions, in all the pages, the pages stop responding. I mean, after a few clicks, if I try another operation the page starts postback for unlimited time period and never gets rendered and a following message is given: The connection was reset: Firefox 3.5... IE cannot display the web page: IE 7, 8 There is no database connectivity issues. I checked event logs on the web server and found few unhandlled exceptions, I corrected those. Now the event log doesn't show any error. But the problem is same. I tried accessing the page from web server's browser, everything works fine. Even my boss can browse all pages with no problem (both have Win Server installed). Other machines (mostly XP) can't browse after sometime(as described above). I checked the memory usage, cpu time - NO ISSUES. Any help would be greatly appreciated. Ankur Reply jeff@zina.co... All-Star 70248 Points 10442 Posts Re: Website stops working after few requests Jan 27, 2010 09:08 AM|jeff@zina.com