Upgrade Wizard not showing in version 7.9.8

Hello, I want to upgrade from version 7.9.8 to newer version but I’ve got a problem.

Navigating to upgrade wizard it’s easy, but there is an error (500 internal server error). There is no error in suitecrm.log file, no error in upgradeWizard.log file besides this:

Mon, 04 Jun 2018 10:35:41 +0200 [UpgradeWizard] - setting session variables…
Mon, 04 Jun 2018 10:35:45 +0200 [UpgradeWizard] - [At end.php]
Mon, 04 Jun 2018 10:35:45 +0200 [UpgradeWizard] - About to repair the database.
Mon, 04 Jun 2018 10:35:56 +0200 [UpgradeWizard] - database repaired
Mon, 04 Jun 2018 10:35:56 +0200 [UpgradeWizard] - Start Rebuilding the config file again
Mon, 04 Jun 2018 10:35:56 +0200 [UpgradeWizard] - Finish Rebuilding the config file again
Mon, 04 Jun 2018 10:35:56 +0200 [UpgradeWizard] - Begin upgrade_connectors
Mon, 04 Jun 2018 10:35:56 +0200 [UpgradeWizard] - End upgrade_connectors.

Check picture below to see the 500 internal error:

Here is response picture:

P.S. This is the same error as https://suitecrm.com/suitecrm/forum/suitecrm-7-0-discussion/19205-cannot-create-or-edit-users-from-user-management#67165

Can you find your web server log? It’s usually called php_errors.log or errors.log.

What are your versions of OS, Web server, PHP, and database? Thanks

Even in Local environment.

OS version: Windows 10,
Web Server: Apache24,
PHP: PHP 7.0.8,
Zend: Zend Engine v3.0.0,
Database: MySQL.

In my logs it shows this:
[spoiler][Fri Jun 08 08:51:38.879370 2018] [:error] [pid 10832:tid 1940] [client ::1:55630] PHP Fatal error: Cannot declare class Account, because the name is already in use in C:\xampp\htdocs\upgrade\LindexKS\LindexCRM\modules\Accounts\Account.php on line 369, referer: http://localhost:8080/upgrade/LindexKS/LindexCRM/index.php?module=Users&action=index[/spoiler]

Also it displays it on client interface.

You should turn off display_errors in your php.ini, so the errors only show in the logs, not on the screen. That is the recommended setting.

I will continue with this thread on your other post here


we don’t need two threads, now that we are down to one single error :slight_smile:

Yes, you can dissable public write access on this one. Thank you.