Author Topic: Loading a Page causing FastCGI Error  (Read 371 times)

Offline Glenugie

  • Level 10
  • *
  • Posts: 64
  • Reputation: +0/-0
    • View Profile
    • The Land of Ennui
Loading a Page causing FastCGI Error
« on: March 06, 2010, 10:49:14 AM »
Okay, so anyone that has seen my game knows it runs on a frameset, and I use javascript to redirect these frames, but occasionally (I haven't been able to find a way to reproduce it reliabily) when I do this to one of the frames I get the following Fast CGI Error:
Quote
FastCGI Error
The FastCGI Handler was unable to process the request.

Error Details:

* The FastCGI process exited unexpectedly
* Error Number: -2147467259 (0x80004005).
* Error Description: Unspecified error

HTTP Error 500 - Server Error.
Internet Information Services (IIS)

Since I haven't been able to define a common variable in each of the cases of this happening, I haven't been able to decide what the cause might be, and I'm hoping that someone here might have an idea what the problem is?

I've received several bug reports for this problem from players, and the best detail I've gotten out is that it occurs more often causing one of the frames to change in rapid succession (For instance going through a series of battles very quickly.

I really don't know what to do with this, so any help would really be appreciated, thanks in advance.

~Glenugie~

Offline dsheroh

  • Level 21
  • *
  • Posts: 235
  • Reputation: +6/-0
  • Perl Vicar
    • View Profile
    • Psi Rangers
Re: Loading a Page causing FastCGI Error
« Reply #1 on: March 06, 2010, 11:06:30 AM »
I've never encountered that error myself, but I was able to find a discussion of debugging it at http://blogs.iis.net/rickjames/archive/2007/10/16/fastcgi-debugging-quot-the-fastcgi-process-exited-unexpectedly-quot.aspx and also a suggestion by that article's author that one of the common reasons for encountering it (at least under IIS) is if:

1) the FastCGI process (e.g. php-cgi.exe) exits after N requests AND

2) InstanceMaxRequests > N AND

3) You have lots of load (i.e. requests are queueing while waiting for FastCGI processes to become available)

This would explain why it tends to occur when you're doing lots of quick changes - that both makes you more likely to hit the limit on the number of requests per process and to submit another request before the new fastcgi process has started up.

 


SimplePortal 2.3.3 © 2008-2010, SimplePortal