XF 2.0 2.0.2 transition error

[FARKHOSTİNG]

I get the following errors when updating to Xen 2.0.2

XF\Db\Exception: MySQL query error [1146]: Table 'xxx_xen.xf_ban_ip' doesn't exist in src/XF/Db/AbstractStatement.php at line 212

    XF\Db\AbstractStatement->getException() in src/XF/Db/Mysqli/Statement.php at line 196
    XF\Db\Mysqli\Statement->getException() in src/XF/Db/Mysqli/Statement.php at line 78
    XF\Db\Mysqli\Statement->execute() in src/XF/Db/AbstractAdapter.php at line 79
    XF\Db\AbstractAdapter->query() in src/XF/Install/Upgrade/AbstractUpgrade.php at line 22
    XF\Install\Upgrade\AbstractUpgrade->executeUpgradeQuery() in src/XF/Install/Upgrade/1000051-100rc1.php at line 18
    XF\Install\Upgrade\Version1000051->step1() in src/XF/Install/Controller/Upgrade.php at line 169
    XF\Install\Controller\Upgrade->actionRun() in src/XF/Mvc/Dispatcher.php at line 249
    XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 89
    XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 41
    XF\Mvc\Dispatcher->run() in src/XF/App.php at line 1889
    XF\App->run() in src/XF.php at line 328
    XF::runApp() in install/index.php at line 14

 

[Chris D]

Updating from which version? That table certainly should have existed for some time.

 

[Chris D]

Wait this suggests you’re updating from a 1.0.0 beta version, is that correct?

 

[FARKHOSTİNG]

Updating from which version? That table certainly should have existed for some time.

xf 2.0.1 to 2.0.2

 

[FARKHOSTİNG]

Wait this suggests you’re updating from a 1.0.0 beta version, is that correct?

I did not have a table I migrated from 1.5.16 to version 2.0.1

 

[Chris D]

It’s not really possible for it to be running that code.

Please don’t attempt to do anything further. Instead could you please submit a ticket and include Admin login and access to MySQL such as through PhpMyAdmin.

 

[FARKHOSTİNG]

It’s not really possible for it to be running that code.

Please don’t attempt to do anything further. Instead could you please submit a ticket and include Admin login and access to MySQL such as through PhpMyAdmin.

I sent a ticket

 

[Chris D]

Thanks.

This should be sorted now. For some reason your xf_upgrade_log table must have been empty. I put the expected data in there and it was able to proceed with the upgrade from version 2.0.1 to 2.0.2 (rather than 1.0.0 to 2.0.2).

 

[FARKHOSTİNG]

Thanks.

This should be sorted now. For some reason your xf_upgrade_log table must have been empty. I put the expected data in there and it was able to proceed with the upgrade from version 2.0.1 to 2.0.2 (rather than 1.0.0 to 2.0.2).

Thanks

 

[Eagle]

Thanks.

This should be sorted now. For some reason your xf_upgrade_log table must have been empty. I put the expected data in there and it was able to proceed with the upgrade from version 2.0.1 to 2.0.2 (rather than 1.0.0 to 2.0.2).

I'm not sure what's the best way to describe but I'll try anyway. I have the same problem while upgrading from 2.1 to 2.2. I did some research and I found this thread but I didn't want to create a new thread, or ticket so thought i'd ask. After read what you wrote, I've checked database and I've realized that xf_upgrade_log was empty. I really don't remember when it happened.

Nevertheless, I've tried a lot of things to upgrade but the problem still exists. I suppose XenForo operates this way. So I mean, XenForo is using xf_upgrade_log table to upgrade. And if table is empty, causing this error when run the upgrade. I hope I make myself clear. So, anyway, what should we do now? I'd appreciate it if you help.

 

[Chris D]

You would need to execute a query similar to this:

INSERT INTO `xf_upgrade_log` (`version_id`, `completion_date`, `log_type`) VALUES (2010070, 1721692800, 'upgrade');

Before running this query you must replace 2010070 with the correct 2.1 version that you were successfully running.

Here's a list of versions and corresponding version IDs:

Version string	Version ID
2.1.0	2010070
2.1.1	2010170
2.1.2	2010270
2.1.3	2010370
2.1.4	2010470
2.1.5	2010570
2.1.6	2010670
2.1.7	2010770
2.1.8	2010870
2.1.9	2010970
2.1.10	2011070
2.1.11	2011170
2.1.12	2011270

For example, if you were running 2.1.12 you would execute the following query:

INSERT INTO `xf_upgrade_log` (`version_id`, `completion_date`, `log_type`) VALUES (2011270, 1721692800, 'upgrade');

The other numerical value doesn't matter, that's just a date.

 

[Eagle]

@Chris D The current version is v2.1.6 Patch 1

As far as I understand, I should run the following SQL query:

INSERT INTO `xf_upgrade_log` (`version_id`, `completion_date`, `log_type`) VALUES (2010670, 1721692800, 'upgrade');

is that correct?

Meanwhile we have a fairly large forums and I can only do that between 02.00 - 03.00 a.m. Then I'll share the results of experiment.

 

[Chris D]

Yes that’s correct

 

[Eagle]

Yes that’s correct

And the problem is solved. It's all right now, thank you for your support.