Since the format has collapsed, I will write the explanation again.

Validating migration of existing Mantis server to new server.
But the validation is not working.

The following error is displayed.

・error
"Schema step 193: UpdateFunction ( check_config_serialization )
Config 'status_enum_workflow' for project id 40, user id 0 could not be converted because its data is not valid. Fix the problem by manually repairing or deleting the offending mantis_config_table row as appropriate, then try again.
Error: unserialize(): Error at offset 73 of 1544 bytes occurred because of the string below "

The character code was modified because it was garbled.
After correction, it was displayed on the Web screen without being garbled, but it is said that it cannot be converted because the data is invalid.

The table data was deleted as other correspondence, but it could not be solved.

Are the following Mantis versions compatible?
・Existing Server
Mantis：1.0.6
・New Server
Mantis：1.3.19 or 2.22.0

Please tell me the solution of this phenomenon.

This is often caused by accented characters in serialized data. Without knowing the contents of the offending row I can't help you.

dregad

I’m sorry

The target character string is described below.
An error was displayed if the value data was invalid.

SELECT * FROM mantis_config_table WHERE type = 3;
| config_id | project_id | user_id | access_reqd | type | value
+----------------------+
| status_enum_workflow | 40 | 0 | 90 | 3 | a:15:{i:10;s:56:"40:’S“–ŽÒŒˆ’è,80:·‚µ–ß‚µ,100:‘Ήž•s‰Â,110:Žd—l,120:•Û—¯";i:20;s:86:"60:‘Ήž’†,40:’S“–ŽÒŒˆ’è,80:·‚µ–ß‚µ,100:‘Ήž•s‰Â,110:Žd—l,120:•Û—¯,140:C³Ï‚Ý(trunk)";i:30;s:88:"60:‘Ήž’†,40:’S“–ŽÒŒˆ’è,80:·‚µ–ß‚µ,100:‘Ήž•s‰Â,110:Žd—l,120:•Û—¯,150:“K—pÏ‚Ý(release)";i:40;s:102:"60:‘Ήž’†,10:V‹K,80:·‚µ–ß‚µ,100:‘Ήž•s‰Â,110:Žd—l,120:•Û—¯,140:C³Ï‚Ý(trunk),150:“K—pÏ‚Ý(release)";i:60;s:98:"140:C³Ï‚Ý(trunk),40:’S“–ŽÒŒˆ’è,80:·‚µ–ß‚µ,100:‘Ήž•s‰Â,110:Žd—l,120:•Û—¯,150:“K—pÏ‚Ý(release)";i:80;s:52:"10:V‹K,40:’S“–ŽÒŒˆ’è,100:‘Ήž•s‰Â,110:Žd—l,120:•Û—¯";i:100;s:39:"40:’S“–ŽÒŒˆ’è,10:V‹K,110:Žd—l,120:•Û—¯";i:110;s:43:"40:’S“–ŽÒŒˆ’è,10:V‹K,100:‘Ήž•s‰Â,120:•Û—¯";i:120;s:43:"40:’S“–ŽÒŒˆ’è,10:V‹K,100:‘Ήž•s‰Â,110:Žd—l";i:140;s:30:"20:C³NG,60:‘Ήž’†,155:C³OK";i:150;s:58:"160:“K—pOK(release),30:“K—pNG(release),155:C³OK,190:Š®—¹";i:155;s:51:"150:“K—pÏ‚Ý(release),20:C³NG,140:C³Ï‚Ý(trunk)";i:160;s:40:"190:Š®—¹,20:C³NG,150:“K—pÏ‚Ý(release)";i:180;s:18:"190:Š®—¹,20:C³NG";i:190;s:29:"20:C³NG,160:“K—pOK(release)";}

The following is the character string when garbled characters are resolved. it's Japanese. The appears to be repaired is on the WEB is, would be recognized as "invalid data".

a:15:{i:10;s:56:"40:担当者決定,80:差し戻し,100:対応不可,110:仕様,120:保留";i:20;s:86:"60:対応中,40:担当者決定,80:差し戻し,100:対応不可,110:仕様,120:保留,140:修正済み(trunk)";i:30;s:88:"60:対応中,40:担当者決定,80:差し戻し,100:対応不可,110:仕様,120:保留,150:適用済み(release)";i:40;s:102:"60:対応中,10:新規,80:差し戻し,100:対応不可,110:仕様,120:保留,140:修正済み(trunk),150:適用済み(release)";i:60;s:98:"140:修正済み(trunk),40:担当者決定,80:差し戻し,100:対応不可,110:仕様,120:保留,150:適用済み(release)";i:80;s:52:"10:新規,40:担当者決定,100:対応不可,110:仕様,120:保留";i:100;s:39:"40:担当者決定,10:新規,110:仕様,120:保留";i:110;s:43:"40:担当者 決定,10:新規,100:対応不可,120:保留";i:120;s:43:"40:担当者決定,10:新規,100:対応不可,110:仕様";i:140;s:30:"20:修正NG,60:対応中,155:修正OK";i:150;s:58:"160:適用OK(release),30:適用NG(release),155:修正OK,190:完了";i:155;s:51:"150:適用済み(release),20:修正NG,140:修正済み(trunk)";i:160;s:40:"190:完了,20:修正NG,150:適用済み(release)";i:180;s:18:"190:完了,20:修正NG";i:190;s:29:"20:修正NG,160:適用OK(release)";}

The root cause of the problem is probably multi-byte characters, and a discrepancy in the size of the strings as they are encoded in the serialized data.

It's a bit hard for me to figure out as I don't read Japanese ;-) and I don't have so much time to spend to analyze the string. Anyway I think you have 2 ways of addressing this:

1. try to fix the PHP serialized string manually
2. delete the offending record and, using the the old system as reference recreate the config in the upgraded system.

2nd option is probably simpler...

I thought that was the case, and I tried many things, but it didn't work, so I started a project to get advice.
I will check it again. Thank you very much.

By the way, if you know about compatibility by Mantis version, please let me know. I checked it but couldn't find it.