Hi, when I try to rebuild the node permissions, or deactivate the Content Access module I either get the white screen of death or this:

Fatal error: Maximum execution time of 240 seconds exceeded in C:\Inetpub\wwwroot\includes\database.mysql.inc on line 153

I have tried setting max_execution_time in php.ini to different values (999,9999,0) but still get the same 240 seconds in the error message. Anyonw knows how I can get around this?

My drupal installations contains arount 6 000 nodes. I think the Content Access moduel might be responsible for the long wait, but when trying to deactivate this module, as I said I get the exact same timeout. I would be extremly grateful If anyone could take the time to help me with this one since I'm out of ideas myself.

Comments

vm’s picture

after changing the max execution time, you did restart apache ?

Also double check that you are editing the correct php.ini file, I've found two in my WAMP and noticed one doesn't do anything , is sort of a backup per sey.

gnucifer’s picture

Yes, I also checked with phpinfo() to se that the setting was changed. Runnung IIS by the way, could be that perhaps?

vm’s picture

I've not enough experience with IIS, sorry.

Any change you are running php in safe mode ?

http://us2.php.net/set_time_limit

gnucifer’s picture

Thank you! Using set_time_limit() actually worked. That saved me alot of time!

gnucifer’s picture

Must be IIS. I'm now trying to solve this by moving the installation to my private machine running apache, run the heavy stuff there and moving it back. I niether have the time nor energy to dig into the strange behavior of php and IIS. But I will try using set_time_limit() as well, thanks for the tip.

bestknight’s picture

I am writing about Drupal 5.x - In my case I had to hack modules\node\node.module (core drupal) to get things to work. Search for the value 240 in the file - round line 2964 in Drupal 5.6.

gnucifer’s picture

Ok, but got it to work (I think, at least rebuild the permissions). Good to know though.

Sk8erPeter’s picture

I'm using three Drupals on my local server via IIS 7.5 without a problem, and it's very fast.

The only "bug" (?) I experienced with it is that Audio module's import feature, which is a batch process, doesn't work correctly on IIS, the batch process breaks with an "Access denied" problem, and this doesn't occur on Apache (interesting, I didn't solve the enigma yet :P).

I just wrote that for other people who are uncertain about using IIS, and maybe these posts discouraged them from using it - but Drupal works like a charm on IIS too.