Sage 100

Thank you Sage Fixed Asset people very much!!!! Sage FAS installed a demo on client's server yesterday and client now getting error message when printing Crystal. See below. On v2016 STD. Thoughts as I dive in? Oops, sorry. So pissed I forgot to attach.

You don't have the error but I'm guessing it's this. Error:""Unable to cast COM object..."" in Sage 100, after installing Sage Fixed Assets Client 2018.1 Products Sage Fixed Assets Sage 100 Region North America Description Error:""Unable to cast COM object..."" when printing any report on Sage 100 2017 and prior versions, after installing Sage Fixed Assets Client 2018.1 Error:""Unable to cast COM object of type 'CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass' to interface type 'CrytsalDecisions.ReportAppServer.Controllers.ISCRReportSource'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{98CDE168-C1BF-4179-BE4C-F2CFA7CB8398}'failed due to the following error: No such interface supported (Exception from HRESULT:0x80004002 (E_NOINTERFACE)). Disclaimer Backup Warning Use caution when working with the below product functionality. Always create a backup of your data before proceeding with advanced solutions. If necessary, seek the assistance of a qualified Sage business partner, network administrator, or Sage customer support analyst. Cause Sage Fixed Assets 2018.1 installs Crystal Reports Runtime SP21 Resolution Upgrade Sage 100 to version 2018 Sage 100 2018 include Crystal Report Runtime SP21 Select the 2016-2017 version of Sage 100 configuration from the chart below see resolution 1 Replace the existing pvxwin32.exe.config located in the ""2017"" installation of Sage 100 Standard ...\mas90\home\ with a copy of the same file from Sage 100 Standard 2018 2 Replace the existing pvxwin32.exe.config located in the ""2017"" installation of Sage 100 Standard ...\mas90\home\ with a copy of the same file from Sage 100 2018. The pvxwin32.exe.config will reside on the Server not individual workstations. AND Install the FSA client on each workstation running Sage 100 . This will update the Crystal Runtime to SP21.A Installing the client is not a licensing issue, only users with a license should be provided credentials to access SFA. 3 Replace the existing pvxwin32.exe.config located in the ""2017"" installation of Sage 100 ...\mas90\home\ with a copy of the same file from Sage 100 2018. The pvxwin32.exe.config will reside on BOTH the Server and Individual workstations. AND Install the FSA client on each workstation running Sage 100. This will update the Crystal Runtime to SP21. * installing the client is not a licensing issue, only user with a license should be provided credentials to access SFA. Install the FSA client on the Sage 100 2017 Server. This is required for A/P and P/O Fixed Assets (F/L) Installing the FSA client on the Sage 100 2017 Server requires a copy of the 2018 pvxwin32.exe.config to the server to process deferred printing. 4 The scenario assumes the SFA client is installed on the same TS instance as the Sage 100 Standard. Replace the existing pvxwin32.exe.config located in the ""2017"" installation of Sage 100 Standard ...\mas90\home\ with a copy of the same file from Sage 100 Standard 2018 5 The scenario assumes the SFA client is installed on the same TS instance as the Sage 100 Workstation. Replace the existing pvxwin32.exe.config located in the ""2017"" installation of Sage 100 ...\mas90\home\ with a copy of the same file from Sage 100 2018. The pvxwin32.exe.config will reside on BOTH the Server and Individual workstations. Install the FSA client on the Sage 100 2017 Server. This is required for A/P and P/O Fixed Assets (F/L) Installing the FSA client on the Sage 100 2017 Server requires a copy of the 2018 pvxwin32.exe.config to the server to process deferred printing. * Note installing the SFA client on workstations that do not access SFA can be substituted by installing SAP Crystal Report SP21 x32 on the workstation. http://downloads.businessobjects.com/akdlm/crnetruntime/clickonce/CRRuntime_32bit_13_0_22.msi If the configuration in use is not listed above please Contact Sage 100 Support. Note: Sage 100 must be on versions 2016.1 and higher. Please refer to Integrated Solutions Compatibility Matrix in Additional Resources. Related resources Error:""Load report failed"" Running Standard reports Error: ""Unable to cast COM object of type"" when printing in prior Sage 100 versions after installing Sage 100 2018 Integrated Solutions Compatibility Matrices (ISCM) for Sage 100 Category Printing and Reporting Reports Entitlement Open Attachments pvxwin32.exe.config SFA 2018_1 with Sage 100 2016 and 2017 resolutions.pdf ID:89164Last Modified Date:2-14-2018

You forgot the error message, but I thin it is the same fix if you have Sage 2018 and an earlier version installed. You have to copy the pvxconfig file from one to the other?

Well, @MaryJoKrueger has a much better explanation than mine! haha :)

Please share that with Jennifer Warawa - it ties in perfectly with the same issue I already have her tracking down. By the way, it took two weeks, but she finally responded.

See Sage 100 kb89164 for the steps depending on what combination you are installing.

What MORONS!!!!! Client is now on Sage 100 Std PU 5 now they have a 2016 version of pvxwin32.exe.config. Was not there under PU1. Am not sure what version of SFA was installed (client uninstalled it per SFA tech support instructions, but I am guessing v2018.1). I am thinking I need to do option 2 from table? The problem is that client does NOT have v2018 installed. So they do not have a v2018 std pvxwin32.exe.config. I copied MY v2018 ADV pvxwin32.exe.config but now get a error 200 sy_reportCommon.pvc line 629. It also gave me a cryptic error about not have JC installed so I am guessing once again that I cannot copy MY pvxwin32.exe.config to their system. I am going to the bar. Will be back later tonight.

When I dealt with this last week, I ended up copying a pvxwin32.exe.config file from my system to their local mas90\home folder and the mas90\home folder on their server. Also ran the SAP Crystal Report SP21 x32.msi on his workstation.

I have done the same thing and it worked. This is my Standard v2018 file in case there is some difference in the file between Standard and Advanced.

@ShariEckersley - Thank you. @MaryJoKrueger Is SP21 specific to Crystal 2011?

Yes, it's what you install on all Standard Sage 100 workstations instead of having to install the fixed asset client on all those workstations regardless of whether they access fixed assets or not. Info about it and the link to the file is in kb89164.

Thanks to everyone. Resolution 2 resolved issue. Client was on v2016. Installing the SFA client on his workstation killed Sage 100 Crystal printing. Copied the .config file to the server and installed the msi on the workstation did the trick. And a big shout out to SFA tech support for breaking it in the first place, then telling client to call Sage 100 tech support.