upgrade stuck during the beginning of process

[medbena]

the upgrade from IPS 4.7.19 to 5.0 beta 10 hangs at the beginning of the process and generates an error message.
I can neither retry nor continue the upgrade, nor can I go back to version 4.7.19 by uploading a buckup. here is the error

Table 'monsite_forus.core_social_promote' doesn't exist #0  
/home/monsite/public_html/forums/system/Db/Db.php(1838): IPS\Db->query() #1
/home/monsite/public_html/forums/system/Application/Application.php(1766): IPS\Db->renameTable() #2
/home/monsite/public_html/forums/applications/core/sources/Setup/Upgrade.php(565): IPS\Application->installDatabaseUpdates() #3
/home/monsite/public_html/forums/applications/core/sources/Setup/Upgrade.php(369): IPS\core\Setup\Upgrade->step1() #4
/home/monsite/public_html/forums/applications/core/modules/setup/upgrade/upgrade.php(60): IPS\core\Setup\Upgrade->process() #5
/home/monsite/public_html/forums/system/Helpers/MultipleRedirect/MultipleRedirect.php(104): 
IPS\core\modules\setup\upgrade\upgrade->IPS\core\modules\setup\upgrade\{closure}() #6
/home/monsite/public_html/forums/applications/core/modules/setup/upgrade/upgrade.php(90): IPS\Helpers\MultipleRedirect->__construct() #7
home/monsite/public_html/forums/system/Dispatcher/Controller.php(139): IPS\core\modules\setup\upgrade\upgrade->manage() #8
/home/monsite/public_html/forums/system/Dispatcher/Setup.php(261): IPS\Dispatcher\Controller->execute() #9
/home/monsite/public_html/forums/admin/upgrade/index.php(38): IPS\Dispatcher\Setup->run() #10 {main}
/home/monsite/public_html/forums/applications//setup/upg_/queries.json - query #0
 

[Marc]

5 hours ago, medbena said:

I can neither retry nor continue the upgrade, nor can I go back to version 4.7.19 by uploading a buckup

A little confused by the statement there. What is stopping you from going back to version 4.7.19? Have you upgraded your live site?

[Miss_B]

6 hours ago, medbena said:

Table 'monsite_forus.core_social_promote' doesn't exist #0  

Try to re-add the aforementioned table and see if it would help.

6 hours ago, medbena said:

nor can I go back to version 4.7.19 by uploading a buckup

May I ask as to why you can't revert back to 4.1.9? 

[Joey_M]

I had this exact error message when I forgot to disable the third-party apps/plugins I used. Are you sure you've done this? The upgrade was flawless for me when I remembered to do this key step.

[medbena]

3 hours ago, Joey_M said:

I had this exact error message when I forgot to disable the third-party apps/plugins I used. Are you sure you've done this? The upgrade was flawless for me when I remembered to do this key step.

Yes I forget to disable  third party apps.

How to disable apps when I can't access to adminCP

11 hours ago, Marc said:

Have you upgraded your live site?

Yes

 

10 hours ago, Miss_B said:

May I ask as to why you can't revert back to 4.1.9? 

I tried to go back but could not restore any backup giving this error message:

Error: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON

Thanks to all

[Jim M]

4 minutes ago, medbena said:

I tried to go back but could not restore any backup giving this error message:

Error: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON

Thanks to all

You would want to ask your hosting provider for assistance here with our backup if you attempted an upgrade of your live site. It is not recommended to upgrade live sites unless you are comfortable with errors that may come during a Beta phase.

[Miss_B]

19 minutes ago, medbena said:

I tried to go back but could not restore any backup giving this error message:

Error: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON

That error indicates that the server is returning HTML instead of JSON. Can you check the response headers and status code of the server's response to see if there's any error being returned? 

The backup file, how was generated and how did you try to restore it? Can you give us some details on that? 

[Marc]

Please also ensure you are reverting both SQL and files back to their original state. Also if you updated PHP or anything like that, make sure those are switched to what was previously working