Hi Michel Donais,

You may have needed to wait a bit. Did you manage to get this resolved?

I was eventually able to succeed recently. But it's been a joyride.

FWIW, I had waited for one full hour without success, during a shutdown. So I took 2 days to find a solution.

I created a new copy from a previous non-shared accountant backup, added it successfully to 365 and tried sharing that one, but since I already have a business with the same name, the system said I wasn't able to share that new one.

I then tried opening it back in 2022.3 to unshare it, but it was already converted, so the system would go in a loop for 15 minutes, then eventually I closed it back forcibly and reopened it, but the system said it wasn't compatible.

I then deleted most of the data I could find (except for 365 - now I have 2 databases), and retried opening the Old version. I couldn't share it back on 365, but I tried unsharing it, and after 5 minutes with Windows telling me the app wasn't responding, it eventually unshared my old copy.

So I reopened the new copy that's now in 365, and I shared it back, it didn't work at first (call support) because it was too early on, I waited a day, tried sharing it back, and then it worked.

At that point, I have the old copy that's defunct, and a new copy for 2023.1, and I shared it back anew to my accountants. So I'll finally be able to delete my 2022.3 copy of the software.

Thanks for sharing these details Michel Donais, hopefully they help prevent issues for others. DeneshS and the support team have also put together this video with tips on how to remove duplicate files to resolve the error "Sage 50 has found a problem in your company file and is unable to upgrade it (MySQL5.6.10)" when converting a company to a newer version of Sage 50 Canada: