"Unable to cast COM object of type" error in Sage 100 2017 after installing Sage Fixed Assets 2018.1

I installed Sage Fixed Assets 2018.1 on two workstations out of several, all running Sage 100 2017 Standard. Those two now get a Crystal error when printing or previewing anything. There were two knowledgebase articles with this same error when printing on earlier versions, after installing Sage 100 2018. I installed the SP recommended by the one, and it didn't fix it. Swapping out the pvxwin32.exe.config file with a 2018 one, fixed it for the two users that had the problem, but then all the other users couldn't print anything, so I had to change it back. Rerunning workstation setup didn't help. I ran across these steps from another reseller:

The fix to this is to install Crystal Reports 2016 on the workstation for all workstations that had Crystal Reports 2011 previously installed.  Just copying the pvxwin2.exe.config file to ..\mas90\home did not work.  I have been unable to test this with a workstation that did not have crystal reports 2011 installed to see if the config file trick will work without fully installing Crystal 2016.

 

Uninstall Crystal 2011

Install Sage Fixed Asset client update 2018.1

Install Crystal 2016

Rename pvxwin32.exe.config on the workstation

Copy a valid Sage 100 2018 pvxwin32.exe.config file to the ..\Mas90\home folder on the workstation

Reports should run in both Sage Fixed Asset client and Sage 100 2017 client on same workstation

 

Alan

I uninstalled any older Crystal Reports and installed the Crystal 2016 Designer, but since this is Standard, not Advanced, there is no ..MAS90\home folder on the workstation, so I couldn't continue and I'm stumped. Help!

  • 0

    Hi, If rerunning Sage 100 workstation setup did not resolve the issue (Sage 100 Standard on a network), you'll need to obtain a 2018 pvxwin32.exe.config and copy it the Sage 100 Standard Server \mas90\home directory.

    John Nichols

    Sage

  • 0

    Hi John,

    I'd sure like your opinion on something interesting re this issue that I've recently discovered. We have a customer who reported this issue but he's on Sage 100 Advanced 2015. Your KB 89164 it specifically states "Sage 100 must be on versions 2016.1 and higher." so I was a little leery, however I was committed to try to help so I figured I'd give it a shot. What I did was copy pvxwin32.exe.config to the server and workstation and, lo and behold, it worked!

    Obviously those files didn't exist back in 2015, but just having them there allowed Sage 100 2015 to work with SFA 2018.1. Do you think that will work on other systems or did I just get lucky? And yes, we checked on the other 3 workstations running both Sage 100 and SFA and that fix worked for them. At the same time the 8 or 9 other PCs that only ran Sage 100 were unaffected. And we never did need to apply the Crystal patch.

    Curiouser and curiouser..

  • 0 in reply to rclowe

    Hi Cullen, 2015 will work. I'm limited to only supported versions but I did go back to 2015 to verify the solution works - I did not verify anything prior to the 2015 release. The other 'Advanced' workstations should not be affected as the run time version of Crystal is local to the workstation. Hope this helps. Thx John