Sage 100

Unable to cast COM object error when viewing Sage Reports after installing Logicity I've seen some threads about this error when installing FAS, In this case I installed Logicity. I assume it has something to do with different versions of Crystal runtime programs in Sage and Logicity. Running Sage Standard 2016 and Logicity v1.9 (free) **If I understand the resolutions correctly from other threads on this topic, I should copy the pvxwin32.exe.config file from my local copy of Sage 100 Std 2018 to the customer's Sage 100 2016 mas90/home folder.** Is that accurate?

Have only tried replacing that file when the Crystal Reports 2016 is installed on the workstation. Do you know the version of Crystal that was installed with Logicity? It may be better to download the Crystal update (URL from the Sage KB article) - SAP Crystal Report SP21+ x32 on the workstation. http://downloads.businessobjects.com/akdlm/crnetruntime/clickonce/CRRuntime_32bit_13_0_22.msi This is the update for Crystal Report 2011. There may be a similar update for the specific version of Crystal Reports that is installed with the CRC/ Nucleus system.

Status Update - still no resolution. It appears the conflict between Logicity 1.9 and Sage 100 2016 is the CR runtime versions Logicity 1.9 uses CR runtime SP 22. Sage 100 2016 appears to use CR runtime SP 13. My next step is to uninstall Logicity 1.9 and see if I can install a legacy version compatible with CR runtime SP 13. Any ""wisdom"" out there? ""Wisdom is the accumulation of many mistakes

I have Logiciy installed on the server only (running Sage 100 std 2016). Does it work to install the Sage 100 2018 version of pvxwin32.exe (CR runtime sp21) on the server only to try and make that compatible with the Logicity CR runtime sp 22 running on the server only. Or will this create conflicts with the work stations running CR Runtime 13 (Sage 100 2016)?

It looks like Logicity version 1.8 uses the CR runtime SP13. The logicity rep sent me the link to download legacy versions of Logicity. https://www.logicitysuite.com/downloads.html

SOLVED! I found the right version of Logicity that is compatible with the Sage 100 2016 CR runtime. Now both work. Below are the detailed notes if you're interested: Whenever you install another application that uses the Crystal Report Runtime engine, you have to be careful of conflicts with the Sage version of CR Runtime. As of July, 2018: Sage 100 2016 uses Crystal 2011, runtime SP 13 Sage 100 2018 uses Crystal 2016 runtime SP 21. https://support.na.sage.com/selfservice/viewContent.do?externalId=50666&sliceId=1 Logicity v 1.8008 uses CR runtime 13 (1.8009 patched up to a higher CR runtime) Logicity v 1.9 uses CR runtime 21 https://www.logicitysuite.com/version-change-log.html The trick is to install a version of Logicity compatible with Sage 100 https://www.logicitysuite.com/downloads.html By default, Logicity will install another instance of SAP Crystal Runtime that shows in Control Panel / Programs and Features. The Sage 100 crystal runtime does not show in Programs and Features. However, you have the option of not installing the CR runtime with Logicity. It's already there for Sage, so you don't need another instance. I also recommend unchecking the checkbox to associate .rpt files with Logicity