x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Replies 22 replies
  • Answers 1 answer
  • Subscribers 108 subscribers
  • Views 10842 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
47
topics
95
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
965
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
JellyRolls

Crystal Reports 2016

SOLVED
Posted By

With Sage 100 2018, Crystal Reports Designer 2016 is now included. Sage warns us to uninstall all existing Crystal Reports Designer versions prior to installing CR 2016. This is the warning from a KB article:

Caution: Avoid using incompatible versions of Crystal Reports to create or modify reports or forms for Sage 100 ERP. For example, do not use Crystal Reports 10 to create or modify reports for Sage 100 versions 2013 and higher, and do not use Crystal Reports 2011 to create or modify reports for Sage 100 2018 and higher.

What is not mentioned is whether CR 2016 is backwards compatible - that is, can we create or modify reports or forms in 2016 and have them be backwards compatible to Sage 100 versions 2017 and below (Crystal 2011)? We have clients on versions ranging from 2014 thru 2018. Can we uninstall CR 2011 and use CR 2016 to modify forms/reports on the older versions?

Has anyone tried this or know the answer?

TIA

  • +1 in reply to JellyRolls
    verified answer

    Yes, I successfully modified forms on Sage 100 2015 using Crystal Reports 2016. You still need to add the pvxwin32.exe.config from the 2018 version and place in the ..\mas90\home folder on the 2015 version for it to work on your own installation. If using Advanced or Premium versions, make sure you also include the file in the ..\mas90\home folder that gets created after running wksetup.

    If you are modifying forms for your clients, your clients do not need the pvxwin32.exe.config file. You would just replace their .rpt file with your modified .rpt file.

  • 0 in reply to Sage100ERPHelper

    I am trying to upgrade Sage Fixed Assets 2018 on a Terminal Server where we run Sage 100 2016 Premium.   Fixed Assets says it needs to install Crystal Reports 2016 and of course Sage 100 2016 needs Crystal Reports 2011 which is what is currently installed.  My question is: if I uninstall CR 2011 and let Fixed Assets install CR 2016, how will I get the "pvxwin32.exe.config" file to keep my CR 2011 working on Sage 100 2016 since I'm not installing Sage 100 2018 anywhere?   Sorry for the long question.

  • 0 in reply to Blarney

    Hi, In the scenario above you have you will not need pvxwin32.exe.config.  After completing the Fixed Assets upgrade and Crystal Reports 2016 install. Rerun Sage 100 workstation. 

    John Nichols

    Sage

  • 0 in reply to Blarney

    I installed the Sage Fixed Assets 2018.1 upgrade on two workstations on a network with several other users, all of them, including the two with SFA are running Sage 100 2017. These two users get an "Unable to cast COM" error when running any report in Sage 100. If I try the fix to swap the "pvxwin32.exe.config", the two work but none of the other users do. Rerunning the workstation set up did not fix the problem. 

  • 0 in reply to mstockford

    Pvxwin32.exe.config was created to address Sage 100 2018 and Crystal Reports 2016 runtime compatibility issues.

    Copying the file (Pvxwin32.exe.config)from a 2018 installation to a previous release of Sage 100 will also resolve the issue (limitations to only supported versions (2016-2017)).

    Could you clarify "but none of the other users do"

    Workstations that have not had the Sage Fixed Assets 2018.1 upgrade installed should not be affected  by the version of Crystal Runtime installed by the Fixed Assets client. Crystal Processing is performed on client side except for deferred printing or the System is Terminal services.  

    John Nichols

    Sage

  • 0 in reply to jcnichols

    This didn't work. After completing the Fixed Assets upgrade (there was no separate CR 2016 install) and running Sage 100 Workstation and choosing 'reinstall,' the "unable to cast COM" error occurred whenever printing.

  • 0 in reply to jcnichols

    The problem I'm having is there is no MAS90 folder on the local stations. When I tried replacing the pvxwin32.exe.config file on the server with one from a separate installation of Sage 2018, the two that originally had a problem worked fine, but all the other users that didn't have Fixed Assets installed can no longer print anything. So two people can work, or eight people can work, but not all 10.

  • 0 in reply to jcnichols

    Respectfully, this is incorrect advice.  One needs pvxwin32.exe.config and does not need to rerun Sage 100 workstation.  Here's what worked:

    Given Sage 100 Premium 2016 and Fixed Assets 2017.1 on a Terminal Server (2012R2), first upgrade Fixed Assets to 2018.1.  Then place pvxwin32.exe.config on Terminal Server in "..\MAS90\Home" directory. 

    I followed these steps. Right after installing FAS 2018.1, printing is broken with the Unable to cast COM error.  Right after copying pvxwin32.exe.config, printing worked from both applications.   The answer to where to get pvxwin32.exe.config is it is attached at the bottom of the KB article referenced above (

    NateSage100 said:
    Error occurs when printing in older version of Sage 100 after installing Sage 100 2018
  • 0 in reply to mstockford

    You should have a "..\MAS90\Home" folder on the local stations that now have FAS 2018.  That is where you want to place pvxwin32.exe.config, not in the server's "..\MAS90\Home" --   The folder on the workstation will be under whatever folder you used to install Sage 100 Workstation. For example C:\Sage\Sage 100 Workstation\MAS90\Home.

  • 0 in reply to mstockford

    With Sage 100 2018 and Sage Fixed Assets 2018 both products include a config for the individual product EXE to resolve the Crystal compatibility issues. There should be no need to copy files. If you are having issues with Sage 100 2018.1 and Sage Fixed assets 2018+ please log a call into our support team.

    If the installation is a previous version of Sage 100 (2016 or 2017) and Sage Fixed Assets 2018+ do not copy the config file from Sage 100 2018 unless instructed by our Sage support team.

    Please try the following steps.

    Rerun Sage 100 workstation setup.      

               If that does not resolve the issue

    register these dlls in this order:

      

    1. C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\reportsourcebridge.dll
    2. C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\rptcontrollers.dll

    John Nichols

    Sage

     

*Community Hub is the new name for Sage City