Sage 100

OK so I thought I understood this issue: **Cannot Print on Previous Sage Version After Installing Sage 2018 When Installing Sage 2018 on a System with a Prior Version** Apparently what I didn't realize is that installing 2018 on only one workstation while copying the pvxwin32.exe.config to the old MAS install, breaks all the other workstations that DON'T have 2018!? Is this correct? Is there something I missed?

Pretty much. What breaks the other versions of Sage is the new runtime Crystal program. the .config fixes it for v2018 (or the current version of Sage Fixed Assets). It is an all or none proposition. Sage installed a demo of Fixed Assets for a client (unbeknownst to me) which broke the Sage client for the workstation using SFA. So I installed the .config fix. THAT workstation started working and all the others stopped.

Yes, just figured that out last weekend. Did a test upgrade and installed 2018 on the same server as 2014. Copied .config on the server and was able print just fine from both versions. But that was only on the server. On Monday morning, no one could print from the 2014 version. Had to go upgrade all the workstations with the 2018 wksetup to get them to print from 2014.

My summary of the issue (corrections & clarifications welcome and encouraged) **TL;DR:** Sage 100 2018 and FAS 2018.1 use Crystal 2016 (previous versions use Crystal 2011). The Crystal 2016 runtime is installed to the local workstation. Once that happens, you can't run use Crystal to print from Sage 100 2018 **and** an earlier version on **the SAME workstation** without also copying Pvxwin32.exe.Config (as noted in step 4 below). This, however, will break Crystal printing on any earlier workstations unless they also are upgraded to 2018 workstation. This also applies if someone installs FAS 2018.1 to a workstation that has an earlier (<2018) of Crystal. You are not going to break printing for **everyone** (aka people who don't have Sage 100 2018 installed) **until you move that config file.** **Example: STANDARD upgrade from 2016 to 2018** 1. Install 2018 to SERVER 2. Run 2018 workstation setup on a WORKSTATION which also has 2016 installed 3. This breaks Crystal Printing on **that 2018 workstation** (at this point **2016 workstations can still print**) 4. To fix the 2018 printing, copy the Pvxwin32.exe.Config file from the 2018 SERVER ""..\MAS90\Home"" directory where Sage 100 2018 is installed, into the 2016 SERVER ""..\MAS90\Home"" directory of the previous version(s) where the error is experienced. 5. The issue resolves for 2018 TEST WORKSTATION - **BUT ...** 6. **However**, because you copied the config files to the 2016 folder you break printing for 2016 LIVE WORKSTATIONS NOT YET UPGRADED WITH 2018 WKSETUP 7. Unless those 2016 LIVE WORKSTATIONS (a) also install 2018 WKSETUP (or presumably you remove the Pvxwin32.exe.Config from above which breaks your 2018 workstation but lets 2016 without 2018 installed print ) AND you've moved the config described in (4) above. **Business Issue:** - Generally not a big issue if you are doing an upgrade in one day because you can uninstall 2016 and install 2018 wksetup and everyone can print - The problem appears when a customer wants to test over the course of several days/weeks and wants to run 2016 and 2018 on the same workstation(s) in a production environment. - You can't just give one person 2018 wksetup (and move the config to the 2016 folder) without doing the whole company or the fix above breaks the 2016 people who don't have 2018 wksetup - While this may not seem like a huge issue it is problematic in large installs with 20+ user counts, shipping, receiving because of the time it takes to travel from workstation to workstation and debug minor issues, **Possible workaround on this would be:** - Install 2018 for testing to a standalone workstation that is not used for any prior version - Test on this workstation that has no other Sage version(s) - When ready run wksetup on remaining workstations and remove prior Sage version - The issue with this workaround is other users can't test various workstation issue such as printing, credit cards, etc

Ok - got it - thanks everyone @JeffSchwenk @KennyDaniel @WayneSchulz

I would appreciate if anyone who has experienced this issue would review the above for accuracy. I'm summarizing what I believe the issue is based on the posts here but haven't yet run into it with an upgrade (yet). TIA.

Okay, I upgraded a customer to v2018 all in one day so no Crystal issues with that BUT they also have an older version of FAS installed and now cannot run reports in it. @alanniergarth is there a workaround for getting FAS to work with a v2018 install on the same workstation?? @Sage100UrgentSupportNeeded

This fixed it: https://support.na.sage.com/selfservice/viewContent.do?externalId=86606&sliceId=1

PDF

So sorry. Just saw this notification. did you get this resolved? My initial response would be to suggest upgrading them to the new version of FAS. It is not a terribly painful process.