Sage 100

Caution for Sage Fixed Asset 2018.1 users with Sage 100 Sage Fixed Assets 2018.1 uses the Crystal Reports 2016 runtime. If the Fixed Asset client is installed on a workstation that is pre-Sage 100 2018 it will blow up forms and reports. The only fix I have found so far, at least with workstations that previously had Crystal 2011, is to uninstall Crystal 2011 then install Crystal 2016. You then need to copy a valid pvxwin32.exe.config file from a valid Sage 100 2018 install and replace the existing Sage 100 pvxwin32.exe.config file on the workstation.

Thanks for the heads up. Crystal is starting to be a pain.

Crystal's version incompatibilities have always been a pain. The Sage 100 world hasn't felt it in a while because Sage got lazy and stayed on Crystal 2011 for so long.

This is a huge pain in the butt for larger sites with lots of custom reports.

I didn't see this before I posted the same problem that we encountered. We will try your solution. Thanks.

Does this work for 100 Standard as well as Advanced? I don't see a pvxwin32.exe.config anywhere on the Standard workstation.

Standard won't have a local workstation client so you should try renaming the exe.config file on the server and then pasting the 2018 config file to it.

I did that, and it worked for the user with FAS 2018, but will that disrupt report printing for other users?

Kathryn its possible I'd test it if I could, we don't have many fixed assets clients with 100 standard to be able to test it. For premium/advanced sage the following are the exact steps we do to get it to work, but no promises. I expect this would be applicable with other sage products that also use crystal 2016. Someone more gifted than I could probably explain why these help, or trim down the steps. 1) uninstall any old sage or any version crystal not 2016 2) install crystal 2016 3) install fixed assets 8.1 4) uninstall Sage erp 5) install sage erp 6) **place the pvxwin32.exe.config, one from a currently working sage 2018 erp attached, in the home folder of the sage server and (after launching it once) the workstation (this is the same as the fix for when you first install sage 2018 for crystal) 7) repair sage fixed assets *on Terminal Server it did require us to log off and back on. **in tests this did not break the non fixed assets workstations at all.

UPDATE: For Standard installations, replacing the pvxwin32.exe.config file will resolve the issue for the FAS workstation, but break the other workstations. I tried installing Crystal Report 2016 full version on one of the non-FAS workstation, and it still requires the old copy of the config file to run properly. *sigh*

This is a posting from Sage Fixed Assets support. I have a client with this situation, but haven't tried this fix yet. Please let us know your results. Posting: Yes, there is a known issue with install the Sage Fixed Assets 2018.1 which is updating the Crystal runtime to SP21 over a program (not just Sage 100) using an older Crystal Runtime - The trick is to uninstall both programs, install SFA first, then install the Sage 100 over that - which will break the SFA ability to run reports. Then See KB ID: 89033 for details on the fix - it is still a little rough and there may be some extra step (some of which I am going to add in a minute) to be added - but the 2 other times I been through this with Sage 100, the current steps worked.

Since there has been so much conflicting information about if and how Sage Fixed Assets v2018.1 with Crystal 2016 can work with Sage 100 versions 2017 and earlier, I called Sage Fixed Assets support and their official recommendation for now (they are still testing to find a solution) is that the client for Sage Fixed Assets v2018.1 must be on a different computer than Sage 100 version 2017 and prior to have Crystal printing work for both products. My client who is running the single user version of Sage Fixed Assets and had installed v2018.1 herself and I talked about it and since they only used fixed assets for book and not tax, we decided to uninstall 2018.1 and installed 2017.1 and her printing from both products is working again. I attached the KB that support sent.

I have Sage Fixed Assets 2018.1, Crystal Reports 2016 and Sage 100 2017 on my laptop installed and working together using the steps we previously described. We have been able to get the two working together on about 3 clients so far. I can't think of any of our clients that run Fixed Assets that don't also run Sage 100 on their workstations. For Sage to say don't install the two is unrealistic as a workaround! But typical.

I just had a client call with this exact situation after upgrading their FAS to 2018 - they are using Sage 100 version 2017 standard. When the FAS tech that helped them upgrade FAS was DONE upgrading he simply said ""you will need to upgrade your Sage100 to version 2018, (end of story, the tech was done!) This was a single user install of FAS on just one workstation. I logged in and renamed the pvxwin32.exe.conig file in the MAS90\HOME directory on the server and put the version 2018 pvxwin32.exe.config file in it's place. I can confirm this breaks it for all the other workstations. I'm wondering if we could install crystal reports version 2016 on the other workstations and then put the 2018 version of pvxwin32.exe.config in the MAS90\Home directory on the server?