PS: We have more than 700 user accounts on our Limesurvey instance. Having a model of 1 separate LS instance per user is not sustainable for us.

This was a totally separate conversation between Jelo and me. We were NOT suggesting for you to have one installation per user/account. We were just discussing that probably not even the Limesurvey Professional hosting has single installations of LS with that many surveys. Just to put things into relation. This is also just a guess, I have no idea what LS Professional is hosting.

Sorry for the confusion.

Increasing the php timeout didn't make a difference.

I then decided to set debug to 2 in LS's config.php, hoping to get more feedback about the problem, and after that change, the data integrity check ran and generated the results page as expected. I was also able to delete all the old tables reported, with no issues.

After that, I set debug back to 0 and tried running the integrity check again. And again the problem showed up: no results (empty page) and no errors in the browser console nor the system logs.

I recommend to open a bug ticket. Systeminfos can be generate via clicking the version number at the bottom. Could be an issue with the upgrade routines. What database is used?

Thank you. I'll open a bug ticket about it.

---

LimeSurvey 3.14.5+180815
Server OS: CentOS 6.9 (2.6.32-696.30.1.el6.x86_64)
PHP 5.6.36
Web server: Apache 2.2.15
DB: MySQL Ver 14.14 Distrib 5.5.60, for Linux (x86_64) using readline 5.1
DB version number: 355

---

gslines wrote: Increasing the php timeout didn't make a difference.

I then decided to set debug to 2 in LS's config.php, hoping to get more feedback about the problem, and after that change, the data integrity check ran and generated the results page as expected. I was also able to delete all the old tables reported, with no issues.

After that, I set debug back to 0 and tried running the integrity check again. And again the problem showed up: no results (empty page) and no errors in the browser console nor the system logs.

Arg .

An error with debug=0 only … awfull error …

Maybe you can try to set the error log on files : www.limesurvey.org/manual/Optional_settings#Logging_settings

And see if something happen in your server log file too …

And report the issue with all information you can …