Sage 100

FRx gurus! Hoping this is not going to be the death of FRx. I have a customer that is still using FRx (and SI but hasn't converted all reports yet). This appears to be happening to all who access FRx, including myself. They are in a Tserver environment and I""m working at the server. They have multiple Tservers depending on load. When trying to launch FRx, we get picture 1 and we'll answer Close pix 3 appears. We can answer OK or Cancel and we get into FRx. Once in, we can run reports. Sometimes we get a Locked String Release (pix 4). Other times we get the standard 8900 Check OFSI... (Pix 2) The ProvideX OLE Server (even though we answer 'Close', doesn't really close, stays running in Task Manager and causes problems upon trying to log out of the Tserver/Server (pix 5). Updates to Windows were run on 6/10 on all applicable Sage machines and hoping this isn't the culprit. I've tried double clicking the PVXCOM in PFile(x86\CommonFiles\Sage\Common Components and that sometimes helps (I think, but not really sure!). Don't have a good grasp on what is working and what isn't. Sometimes we just plow thru the errors and FRx then works. Anybody running into FRx problems or have any suggestions?

@NancyHanson Given the part about updates, you could try reinstalling sage/frx or possibly rolling back before the updates. i know the 1806 update did change some of the registry entries for paperless office so it wouldn't be a stretch to think that it also messed with FRx.

You could look at these

Update to this: Same customer. Found on the 2012 RDS/TServer, if he uninstalls the updates/patches, FRx works as designed. However, once the updates are installed, it breaks. We are now in a test upgrade to Sage v2018 and new 2016 Application and RDS Servers and of course they are fully patched and FRx is throwing fits again. It's not reasonable to leave the servers unpatched. Installing locally for this company isn't feasible, so doing an emergency conversion to SI of remaining reports before the live upgrade. Has anyone tried installing FRx on a patched/updated 2012 or 2016 server and have you been successful? Is it just this company's environment? Have we finally come to the death of FRx?