TinyPortal

Development => Support => Installation => Topic started by: Hellbreather on September 12, 2008, 01:18:10 PM

Title: 30 Second Execution Error with Smf 1.1.6
Post by: Hellbreather on September 12, 2008, 01:18:10 PM
Hi,

I did try a search but nothing has come up.

I have uploaded Tiny Portal 1.0.5 beta and its all good but when I click on apply mod it waits for a long time and I get one of two errors:

FastCGI Error.
The FastCGI Handler was unable to process the request.
--------------------------------------------------------------------------------

Error Details:

The FastCGI process exceeded configured activity timeout
Error Number: 258 (0x80070102).
Error Description: The wait operation timed out.
HTTP Error 500 - Server Error.
Internet Information Services (IIS)

Or:

Fatal error: Maximum execution time of 30 seconds exceeded in \\NAS42ENT\domains\*removed-domain-name&serveraddress*\user\htdocs\Sources\Subs-Package.php on line 1931


I tried to manual install, but it came up with tons of errors (I did follow the instructions) but there were a few that I couldn't find in a few of the files.

Any ideas? (I also tried 0.98)
Thanks
Hellbreather.
Title: Re: 30 Second Execution Error with Smf 1.1.6
Post by: G6Cad on September 12, 2008, 01:39:22 PM
A server setting thats wrong, you need to ask your host to check the cgi settings on the server.
Title: Re: 30 Second Execution Error with Smf 1.1.6
Post by: Hellbreather on September 12, 2008, 01:40:02 PM
What CGI settings do I need to ask them to check?
Title: Re: 30 Second Execution Error with Smf 1.1.6
Post by: G6Cad on September 12, 2008, 02:34:18 PM
Quote
The FastCGI process exceeded configured activity timeout
Error Number: 258 (0x80070102).

That error number should give them the hint
Title: Re: 30 Second Execution Error with Smf 1.1.6
Post by: Thurnok on September 12, 2008, 09:40:06 PM
The IIS implementation of FastCGI has a default of 30 seconds for script execution.  This can be changed via the IIS Manager.  Ask your host to increase the time to at least 60 seconds which is generally thought to be the recommended minimum time setting for script executions on public (non-corporate intranet) internet web servers.