[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 134
  • Last Modified:

ASP_0113 and ASP_0147 Errors

I have a production server running Microsoft IIS 7 (Version 7.0.6000.16386) on Windows Server Web (2008) Service Pack 2.  During the month (or perhaps 2 months), some of our older web pages using ASP Classic have been throwing 500 Server Errors.  In the IIS log it shows "ASP_0147|500_Server_Error" and "ASP_0113|Script_timed_out" errors.  I've narrowed it down to certain ASP pages that are creating server XMLHTTP objects [Server.CreateObject("Microsoft.XMLHTTP") ] in order to "POST" data to an on-line credit card merchant processor.  About 90% of the time these pages work just fine.  The other 10% of the time, they are throwing one of these two errors.  These pages have been in production for many years and have worked flawlessly until recently.  Nothing on the server has been reconfigured.  The only update has been the usual Windows Updates from Microsoft, which have been dutifully applied when they come out.  I'm at a loss as to what is causing these issues.  I'm toying the idea of rewriting these pages using ASP.NET, but that will some take time.  Is there anything I can do or check on the server to figure out what is going on?  Side note:  The server is actually running as a Virtual Machine on VMware.  I've added more memory and a second processor to the virtual machine thinking it was simply a low resource issue.  But, that did not help.
0
wheelsm
Asked:
wheelsm
  • 2
1 Solution
 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
if you use Chrome, open up the developer tools (F12) when this happens and click on the NETWORK tab, you'll see a list of all of calls being made to and from the server. If you're getting a 500 error message while making an ajax call, it should be colored red. Click on it, then you can get more details about the error, hopefully narrowing down what could be causing the issue
0
 
wheelsmPresidentAuthor Commented:
Hi Big Monty.  Thank you for the suggestion.  I'm on the road right now, but will try this when I get back into the office.  It will be hit and miss trying to get more details since the problem occurs randomly.
0
 
wheelsmPresidentAuthor Commented:
For posterity, I figured I better post the resolution to this issue.  It turns out the issue was caused by Microsoft's Dynamic RPC Ports (TCP 49000 - 65535).  These ports were being blocked by my firewall.  The solution was to open these ports internally.
0

Featured Post

[Webinar] Improve your customer journey

A positive customer journey is important in attracting and retaining business. To improve this experience, you can use Google Maps APIs to increase checkout conversions, boost user engagement, and optimize order fulfillment. Learn how in this webinar presented by Dito.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now