Font Forum

Auto-update; afterwards, starting Maintype results in a big red error box stating "data error". This is, regrettably, repeatable. No version numbers available as Maintype can only be terminated, but before auto-upgrading I was on 12.0.0.1293.

So is my database borked? My groups, collections, everything?

Felix.

Playing with FMSconfig (safe mode etc.) did not chnge the "data error", but at least I can offer post-update version info:

felixkasza wrote: ↑Thu Nov 16, 2023 11:16 am Auto-update; afterwards, starting Maintype results in a big red error box stating "data error". This is, regrettably, repeatable. No version numbers available as Maintype can only be terminated, but before auto-upgrading I was on 12.0.0.1293.

So is my database borked? My groups, collections, everything?

Felix.

It is most likely due to a corrupt database, but it is hard to tell from here.

You could try to uninstall the latest version, keeping the database, and then reinstalling version 12.0.0.1293. You can download it from here:
https://www.high-logic.com/previousrele ... 0.1293.exe

If that shows the same error, then all you can do is restore a backup if you made one recently.

Band-Aid: Uninstall, leave DB and vault intact during uninstall, install last-known-good version. In y case that was 12.0.0.1293 64bit.

Oh, and now FMSproxy shows up as connected in FMSconfig.

So it seems an issue with the latest update. To further look into this issue we need to know the exact error message. The text "data error" is not known by our developers.

I also updated to Maintype 12.0.0.1300 from 12.0.0.1293 using the built-in updater and broke in the same way. This is the error message:



The following had no effect (the error persisted):
- Stopping the font service, starting MainType (now the error says font service isn't running), starting the font service (back to data error)
- Reinstalling from the official website (12.0.0.1300), clearing all database and cache
- Reinstalling from the official website (12.0.0.1300), retaining data
- Reinstalling from the official website (12.0.0.1300), using a third party uninstaller to remove every stray registry key and file
- Rebooting, both while MainType was installed and while it wasn't installed

This thread helped me to find the only solution, which was to manually install the 12.0.0.1293 version from the above links. I could import the database that was backed up from the new version, so no real data loss but I had a solid hour when I panicked that I corrupted and lost all data.

I wonder if it is a fault with the new version? It's rather surprising that "data error" isn't known as an error - maybe it would help to add more diagnostic information to the Oops window like a stack trace. Just a suggestion though!

I am sorry to hear you have issues with the latest update. Since this is no longer a coincidence, we do suspect some issue within the software. I hope we can find a solution soon, but right now we are not able to reproduce the problem, so it might take some time.

Windows 10, identical issue, same screen. Had to preserve database and settings, uninstall, reinstall earlier version.

Here is an update that should solve the problem:

https://www.high-logic.com/tmp/maintype ... 05-x64.exe

Let us know your results.

The previous update might not have solved the problem, so please try this update:

https://www.high-logic.com/tmp/maintype ... 10-x64.exe

Let us know your results!