• Register
    • Help

    striker  0 Items
    Currently Supporting
    • Home
    • News
    • Forum
    • Wiki
    • Support
      • Manage Subscriptions
      • FAQ
      • Support For
        • VaultWiki 4.x Series
        • VaultWiki.org Site
    • What's New?
    • Buy Now
    • Manual
    • 
    • Support
    • VaultWiki 4.x Series
    • Bug
    • Error Updating to 4.1.0 Stable from RC3 on XF 2.1

    1. Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

      VaultWiki allows your existing forum users to collaborate on creating and managing a site's content pages. VaultWiki is a fully-featured and fully-supported wiki solution for vBulletin and XenForo.

      The VaultWiki Team encourages you to join our community of forum administrators and check out VaultWiki for yourself.

    Issue: Error Updating to 4.1.0 Stable from RC3 on XF 2.1

    • Issue Tools
      • View Changes
    1. issueid=6088 August 13, 2020 5:50 AM
      medic917 medic917 is offline
      Junior Member
      Error Updating to 4.1.0 Stable from RC3 on XF 2.1

      I got this error when upgrading using new files only when upgrading from 4.1.0 RC 3 to 4.1.0 build 001 on XF 2.1.x

      Code:
      XF\Db\InvalidQueryException: MySQL statement prepare error [1064]: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'END WHERE `chapterid` IN () LIMIT 0' at line 3 in src/XF/Db/AbstractStatement.php at line 228
      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 39
      XF\Db\Mysqli\Statement->prepare() in src/XF/Db/Mysqli/Statement.php at line 54
      XF\Db\Mysqli\Statement->execute() in src/XF/Db/AbstractAdapter.php at line 94
      XF\Db\AbstractAdapter->query() in src/addons/vw/vw/_core/controller/db/xf2.php at line 117
      vw_DB_Controller_XF2->query_write() in src/addons/vw/vw/_core/model/db/mysql/vw.php at line 1386
      vw_DB_MySQL_Model->shutdown_or_run() in src/addons/vw/vw/_core/model/db/mysql/vw.php at line 983
      vw_DB_MySQL_Model->update() in src/addons/vw/vw/_core/model/cron/deferred/rechapter/vw.php at line 109
      vw_Cron_Deferred_ReChapter_Model->column_asort() in src/addons/vw/vw/_core/model/cron/deferred/rechapter/vw.php at line 36
      vw_Cron_Deferred_ReChapter_Model->run() in src/addons/vw/vw/_core/model/cron/deferred/vw.php at line 64
      vw_Cron_Deferred_Model->exec() in src/addons/vw/vw/Handler/Job/Defer.php at line 30
      vw\vw\Handler\Job\Defer->run() in src/XF/Job/Manager.php at line 253
      XF\Job\Manager->runJobInternal() in src/XF/Job/Manager.php at line 195
      XF\Job\Manager->runJobEntry() in src/XF/Job/Manager.php at line 111
      XF\Job\Manager->runByIds() in src/XF/Admin/Controller/Tools.php at line 120
      XF\Admin\Controller\Tools->actionRunJob() in src/XF/Mvc/Dispatcher.php at line 350
      XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 257
      XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 113
      XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 55
      XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2184
      XF\App->run() in src/XF.php at line 391
      XF::runApp() in admin.php at line 13
      I also checked error logs and gave more details

      Code:
      XF\Db\InvalidQueryException: MySQL statement prepare error [1064]: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'END WHERE `chapterid` IN () LIMIT 0' at line 3 src/XF/Db/AbstractStatement.php:228
      
      
      Stack trace
      
      UPDATE  `vw_chapter` SET `chapterorder` =  CASE `chapterid` 
      		
      	 END  WHERE  `chapterid` IN ()  LIMIT 0
      ------------
      
      #0 src/XF/Db/Mysqli/Statement.php(196): XF\Db\AbstractStatement->getException('MySQL statement...', 1064, '42000')
      #1 src/XF/Db/Mysqli/Statement.php(39): XF\Db\Mysqli\Statement->getException('MySQL statement...', 1064, '42000')
      #2 src/XF/Db/Mysqli/Statement.php(54): XF\Db\Mysqli\Statement->prepare()
      #3 src/XF/Db/AbstractAdapter.php(94): XF\Db\Mysqli\Statement->execute()
      #4 src/addons/vw/vw/_core/controller/db/xf2.php(117): XF\Db\AbstractAdapter->query('UPDATE  `vw_cha...')
      #5 src/addons/vw/vw/_core/model/db/mysql/vw.php(1386): vw_DB_Controller_XF2->query_write('UPDATE  `vw_cha...')
      #6 src/addons/vw/vw/_core/model/db/mysql/vw.php(983): vw_DB_MySQL_Model->shutdown_or_run('UPDATE  `vw_cha...', false)
      #7 src/addons/vw/vw/_core/model/cron/deferred/rechapter/vw.php(109): vw_DB_MySQL_Model->update(Array)
      #8 src/addons/vw/vw/_core/model/cron/deferred/rechapter/vw.php(36): vw_Cron_Deferred_ReChapter_Model->column_asort(Array)
      #9 src/addons/vw/vw/_core/model/cron/deferred/vw.php(64): vw_Cron_Deferred_ReChapter_Model->run(Array)
      #10 src/addons/vw/vw/Handler/Job/Defer.php(30): vw_Cron_Deferred_Model->exec()
      #11 src/XF/Job/Manager.php(253): vw\vw\Handler\Job\Defer->run(G)
      #12 src/XF/Job/Manager.php(195): XF\Job\Manager->runJobInternal(Array, G)
      #13 src/XF/Job/Manager.php(111): XF\Job\Manager->runJobEntry(Array, G)
      #14 src/XF/Admin/Controller/Tools.php(120): XF\Job\Manager->runByIds(Array, 8)
      #15 src/XF/Mvc/Dispatcher.php(350): XF\Admin\Controller\Tools->actionRunJob(Object(XF\Mvc\ParameterBag))
      #16 src/XF/Mvc/Dispatcher.php(257): XF\Mvc\Dispatcher->dispatchClass('XF:Tools', 'RunJob', Object(XF\Mvc\RouteMatch), Object(XF\Admin\Controller\Tools), NULL)
      #17 src/XF/Mvc/Dispatcher.php(113): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(XF\Admin\Controller\Tools), NULL)
      #18 src/XF/Mvc/Dispatcher.php(55): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
      #19 src/XF/App.php(2184): XF\Mvc\Dispatcher->run()
      #20 src/XF.php(391): XF\App->run()
      #21 admin.php(13): XF::runApp('XF\\Admin\\App')
      #22 {main}
      
      
      Request state
      
      array(4) {
        ["url"] => string(24) "/admin.php?tools/run-job"
        ["referrer"] => string(121) "https://website.com/admin.php?tools/run-job&only_ids=58234&_xfRedirect=https%3A%2F%2Fwebsite.com%2Fadmin.php%3Fadd-ons%2F"
        ["_GET"] => array(1) {
          ["tools/run-job"] => string(0) ""
        }
        ["_POST"] => array(3) {
          ["_xfRedirect"] => string(38) "https://website.com/admin.php?add-ons/"
          ["_xfToken"] => string(8) "********"
          ["only_ids"] => string(5) "58234"
        }
      }
    Issue Details
    Issue Number 6088
    Issue Type Bug
    Project VaultWiki 4.x Series
    Category Install / Upgrade
    Status Duplicate
    Priority 2 - Fatal / Database Errors
    Affected Version Unknown
    Fixed Version (none)
    Milestone (none)
    Software DependencyAny
    License TypePaid
    Users able to reproduce bug 0
    Users unable to reproduce bug 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. August 13, 2020 1:53 PM
      pegasus pegasus is offline
      VaultWiki Team
      I believe that we've covered this particular error before in our discussions. This refers a job that failed under a previous version.

      Whenever you upgrade VaultWiki, VaultWiki will look for failed jobs and try to execute them again, in case there was a related bug that was fixed in the new version. This is normal behavior. It occurs after the upgrade is successful; each job is tested one time.

      In this case, the job itself doesn't appear to have a bug, but the process that queued up the job didn't include all the necessary information that the job needs. So the job will fail every time, no matter what we do.

      In your database's vw_defer table, you will find a row where defer = 'rechapter'. You must remove this row manually, or you will see this message after every upgrade. Before you delete it, please write down the content of the dateline field as it will be useful for determining if we need to worry about more of these.

      I don't remember if we've removed the record in the past when we encountered it, or decided to ignore it. If we ignored it, that's why it's here again now. If we already removed it, and here's another one, then something is still queueing up bad 'rechapter' jobs occasionally. If it's the latter, we should try to find the problem.
      Reply Reply  
    2. August 15, 2020 12:01 AM
      medic917 medic917 is offline
      Junior Member
      I don't recall deleting this one and didn't see anything in my logs that says so, so I'll keep an eye for it next time I upgrade.
      I saved the contents for the rechapter row for the future if needed, thanks for the heads up!
      Reply Reply  
    + Reply

    Assigned Users
    Loading Please Wait
    Tags
    Loading Please Wait
    • Contact Us
    • License Agreement
    • Privacy
    • Terms
    • Top
    All times are GMT -4. The time now is 10:44 AM.
    This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Learn more… Accept Remind me later
  • striker
    Powered by vBulletin® Version 4.2.5 Beta 2
    Copyright © 2025 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2025 DragonByte Technologies Ltd.
    Copyright © 2008 - 2024 VaultWiki Team, Cracked Egg Studios, LLC.