Uploaded image for project: 'Plugins'
  1. Plugins
  2. CONTRIB-3707

Error Writing to MSSQL when changing block settings

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 2.2.2
    • Block: AJAX Marking
    • None
    • MOODLE_22_STABLE

      Hi Matt

      Thanks for this release. It fixes the previous problem! Really appreciate it!

      Another one for you, which occurs when I click the 'show group nodes' symbol in the settings:
      A Moodle error occurred:
      Error writing to database
      Debug info:
      SQLState: 42000
      Error Code: 102
      Message: [Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near 'course_module_config'.
      UPDATE mdl_block_ajax_marking course_module_config INNER JOIN mdl_course_modules course_modules ON (course_modules.id = course_module_config.instanceid AND course_module_config.tablename = 'course_modules') INNER JOIN mdl_block_ajax_marking course_config ON (course_config.instanceid = course_modules.course AND course_config.tablename = 'course') SET course_module_config.groupsdisplay = NULL WHERE course_config.id = '4' [array ( 0 => '4', )]
      Stacktrace:

      • line 397 of \lib\dml\moodle_database.php: dml_write_exception thrown * line 252 of \lib\dml\sqlsrv_native_moodle_database.php: call to moodle_database->query_end() * line 368 of \lib\dml\sqlsrv_native_moodle_database.php: call to sqlsrv_native_moodle_database->query_end() * line 737 of \lib\dml\sqlsrv_native_moodle_database.php: call to sqlsrv_native_moodle_database->do_query() * line 123 of \blocks\ajax_marking\actions\config_save.php: call to sqlsrv_native_moodle_database->execute()

      Dan

            mattgibson Matt Gibson (Inactive)
            d.kennedy Daniel Kennedy
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.