I'm sharing this here in cause anyone else has this issue, it's happened to me twice now in three weeks and it took a little research to figure out a solution.
Scenario: Client installs third party application that has a newer runtime then the installed Sage 100 for crystal reports
Fix
Find a copy of the pvxwin32.exe.config from the 2018 install, copy to another location, find the dependentAssembly information related to crystal reports engine and then change the "newVersion" to the related version of the crystal report runtime. This is the guessing part of the game. the version does not match the information in the control panel install. Example I have SAP Crystal Reports runtime engine for .NET Framework (32-bit) installed on my machine, but the number is 13.0.4000 in the file and in visual studio if you look at it there. Today i had one that they had installed 13.0.25 and I found that to be 13.0.3000 (if memory serves me). Both times I updated the highlighted version information below, had them install the new runtime this other application uses to machines without it, and they were able to start printing from both Sage 100 and the other application.
Thought I would share and also have a place to find it a year from now when I run into it again...
------------------------------
Chris Mengerink
Director
DWD Technology Group
Fort Wayne IN
260-399-8653
------------------------------