By Augusto Ellacuriaga on

I started getting this error message even though I included this line in php.ini: max_execution_time = 300.

Fatal error: Maximum execution time of 300 seconds exceeded in /home/xxxxxxxxx/public_html/sites/all/modules/views/includes/handlers.inc on line 171

The site just freezes up and apparently goes into a loop. The first error came at 30. I also tried, 60, 90, 500 and 300 with no luck

Any help will be appreciated.

Thanks

⋅ Categories: Drupal 6.x

Comments

Augusto Ellacuriaga’s picture

Augusto Ellacuriaga commented

Anyone can shed some light?

jainrutgers’s picture

jainrutgers commented

its seems some Views is causing that problem. Find that faulty view and disable it. And then try.

Chetan

Augusto Ellacuriaga’s picture

Augusto Ellacuriaga commented

Hi jainrutgers,

Indeed, there was something with views that was causing the problem. I had to manually disable views via phpMyadmin and was finally able to login. However, the problem came back when I went to the modules page. I checked again and apparently the views module was active. I removed for the second time and completely uninstall the module.

Thanks for your feedback.

Cheers :)

jainrutgers’s picture

jainrutgers commented

You welcome :)

RKopacz’s picture

RKopacz commented

Anybody have any understanding as to why views was causing this error? I know this thread is two years old but I was having a similar problem on a local dev environment with WAMP and determined that views was the culprit. I had to manually disable the module and finally moved the whole thing to a remote testing server, where it is working properly.

Any thoughts on how to correct the local server config to get it working properly? I spent most of the weekend trying various options, to no avail.

Augusto Ellacuriaga’s picture

Augusto Ellacuriaga commented

I think one of the main problems back then was the way the server was setup. Unfortunately I was using a VSP that did not handle drupal that well. Since then, we moved to a dedicated server and never had that issue back. Not too much help, but that was pretty much all we did.

Best,