Hi Bret,
thanks for the suggestion - I may do that if I don't get anywhere with some other approaches.
In this case it seems unlikely that this is the issue, as the table in question mdl_message_read is part of the core Moodle messaging system and it seems unlikely that this has been changed.
Interestingly, I have left this installation alone for 4 hours I refreshed the browser and I got back to the initial upgrade screen in Moodle!
I continued and I got further this time
System Converted NTEXT to NVARCHAR(MAX) columns in MS SQL Server database - 222/314. 5.33 sec 70.7%
Error writing to database More information about this error Debug info: UPDATE mdl_question_attempts SET questionsummary = questionsummary, rightanswer = rightanswer, responsesummary = responsesummary [array Image may be NSFW.
Clik here to view.
] Error code: dmlwriteexception Stack trace: • line 446 of \lib\dml\moodle_database.php: dml_write_exception thrown • line 242 of \lib\dml\mssql_native_moodle_database.php: call to moodle_database->query_end() • line 672 of \lib\dml\mssql_native_moodle_database.php: call to mssql_native_moodle_database->query_end() • line 216 of \lib\db\upgradelib.php: call to mssql_native_moodle_database->execute() • line 2338 of \lib\db\upgrade.php: call to upgrade_mssql_nvarcharmax() • line 1530 of \lib\upgradelib.php: call to xmldb_main_upgrade() • line 356 of \admin\index.php: call to upgrade_core()
So this is reporting the same problem...but with a new table.
It may not be a real problem at all - it just may be taking such a long time converting ntext to nvaarcharmax data type that the Moodle upgrade script is getting a bit confused.
I then clicked the continue button and got ‘Site is being upgraded, please retry later.’ = same as before.
I'll retry at the end of the working day and post back on my experiences.
All the best,
Michael
