Greetings,

Please try adding this line: RetVal = oPRINT.nInitReportEngine() right before the call to oPRINT.nProcessReport().  It worked for me in my test of printing the GL Trial Balance Report to Paperless using the business object.

Thanks,

Kent Mackall

See also https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=83834&sliceId=1&cmd=displayKC&dialogID=43919&docType=kc&isLoadPublishedVer=&stateId=43921&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

Sage 100 2018 uses Crystal Reports 2016 which may be causing conflicts with existing Crystal Reports.

Also - support.na.sage.com/.../viewdocument.do

Kent, thanks for sharing - I added that call but the error message still shows up.

Wayne, thanks for advising - I installed Crystal Reports Support pack 18 but the error still shows up.
Pretty sure all the components were already installed since Sage 100 UI works without the problem.

Got it to work by copying 'pvxwin32.exe.config' file from the Sage 100 Home folder to 'C:\Program Files (x86)\Common Files\Sage\Common Components' and renaming the file to 'pvxcom.exe.config'. Pvx process seems to be missing its corresponding .config file after the CrystalReports migration.

Maybe Sage personnel could advise if this is something that should be put in into our software installer as a long term solution, or Sage is going to fix it with one of the PU?

Would appreciate any insight!
Thanks,
Alex

Hi Alex,

We are taking a look at this and will follow up when we have more information.

Thanks,

Kent

Thanks for this Alex.  You saved me a big headache.

Alex,

Was that Sage 100 2018 Advanced or Standard that you had issue and did the workaround?

Hi,
that was Sage 2018 Standard.
Alex