Hi Kevin,

Unfortunately, there is no conversion restart. There isn't a clean way to handle this and still ensure data integrity for the converted data.

This is something we need to look at because if the conversion had stopped when it encountered error 41, it should have allowed a restart.

Thank you,

Kent

Thanks Kent.  I was expecting things to pick up where it left off, which is how things work for conversion errors in normal Sage modules, but I understand this is a special case.

I'll reset and restart (with fingers and toes crossed).

Update:

I was lucky, guessing correctly, and the data I removed allowed the conversion to run to completion on the first retry.  (Re-copy the MAS_### database and folder, manually... company maintenance showed the wrong module versions, but did go through the 4hr conversion when I clicked Convert).

If anyone comes looking for an answer to the Error 41...

This customer imports WT's from spreadsheets, and sometimes forgets to save as CSV first... causing some weird data to get into the JT_WorkTicketHistoryHeader table.  I just removed the extra rows (that had no linked data) before running the v2023 conversion.

Kevin,

Thanks for posting back that the conversion completed and what the issue was.  As I said, this is something we will be looking into.

Kent

Thanks Kent.  Conversion errors with bad data will happen sometimes.  Being able to continue the JT to PM conversion where it left off would likely be helpful for other upgrades in the future.