This sounds rather serious. Since I expected to be updating to that version this weekend, I'm wondering what you might have done to get around it, if anything. What's the server OS, and are you seeing the message there too, or just on the clients?

BTW, do you have the link for the 2019.1 update?  It seems to have been banished, along with 2019.0 full install.

Update: Tested a clean Connection Manager-only install on Win10 (1903) and am not seeing the error you mention, so I guess you're either talking about server only, or it's some sort of upgrade issue where something outdated is being left behind.

If you have the data on a server and are accessing it from the 8 workstations, you will probably need to install 2019.2 on all the workstations, and also do a 'server only' instal on the server.

I'm sure that's what he's doing, or he wouldn't have mentioned the server at all. It doesn't explain what he's talking about. I couldn't reproduce the problem with Win10 and Server 2016.

Good morning,

So we got the issue resolved. Had to remove and reinstall the framework..  

So if you get a failure during the framework installation, then uninstall the 2012 runtkmes, and run the Sage installation again. 

Thanks

Richard

Those frameworks are extremely annoying, btw. Due to the way they're installed, TWO reboots are required to install them, all before you can actually install Sage 2019.2. I know of no other product that handles this so poorly.