Last modified: 2006-01-15 20:07:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 4623 - Installation fatal error "Maximum execution time exceeded" in Database.php
Installation fatal error "Maximum execution time exceeded" in Database.php
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-01-15 16:46 UTC by tom
Modified: 2006-01-15 20:07 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description tom 2006-01-15 16:46:08 UTC
On installing mediawiki i get this :

Fatal error:  Maximum execution time  exceeded in
c:\webserver\wiki\includes\Database.php on line 374
Comment 1 Rob Church 2006-01-15 17:33:24 UTC
I'll refer you to the mailing list
( since that's a better
forum for individual support, and this is a bug tracker.

When mailing them, provide information as to what stage in the installation you
receive the error, and what version of MediaWiki you are trying to install.
Information on your version of PHP and database server might be useful, too.
Comment 2 tom 2006-01-15 20:07:15 UTC
i have php version 4.42, the  SQL Server ist winMySQLadmin 1.3 and 
apache webserver version 1.3.17. I am trying to install mediawiki 
version 1.5.5.

i get this error after i click the install button after filling the 

Note You need to log in before you can comment on or make changes to this bug.