Do you remember what the error messages were exactly? We can often look to other sources likes logs to determine the problem.
A bit like surgery with a shotgun and a blindfold. Uninstalling FactorySQL and FactoryPMI was probably unnecessary. It would have been better to determine the cause of the problem with MySQL and Kepware. Sounds like something went wrong between the unified installer, existing installs, and silent MySQL and Kepware installers - something that we can troubleshoot. Also, you shouldn’t usually have to delete the directories. It often works, but that’s a bad sign.
This is a good time to point out potential danger when uninstalling FactoryPMI without thinking about it - projects get lost that way. The installer does a gateway auto-backup during the install. It’s rare, but I’ve seen a few cases where big upgrades create backward compatibility issues. If you contact us, we can help you out of that situation. If you uninstall, automatic backups get removed with the rest of the application - that’s what an uninstall does. In that case the user saw that his application didn’t work exactly as it had before and immediately went the “uninstall then reinstall” route. He didn’t have a recent backup either. In any event, upgrading FactoryPMI by stopping the service then running the installer works great. No need to uninstall.