Sage 100

I installed Sage 2018 Advanced for a client running Sage 2015 Advanced and now some of their scripts are failing in 2015 at the same command: retval = oSOBI.nInitReportEngine() Have not done any data migration - only installed 2018. They are not using CS/ODBC. Anyone have any ideas?? Thanks.

Portal's down again. I made an inquiry this AM about when we might expect some stability on the portal. I know they're in the process of replacing it. Maybe it's related to that.

We think it is a Crystal conflict - need to figure out what that is

EDITED: If this is an external script, which i'm assuming it is based on the ""n"" prefix in your method, it is because of the crystal report runtime compatibility issues. See my post about this here https://90minds-com.socialcast.com/messages/39153076?ref=stream Make sure you determine the path of pvxcom.exe so you can copy pvxwin32.exe.config to the appropriate directories. Use Task Manager with the path column included to view the path for pvxcom.exe once your script has instantiated the Providex.Script object. You'll want to copy the pvxwin32.exe.config file from the 2018 server's MAS90\Home directory to all folders containing pvxcom.exe, then rename the copied pvxwin32.exe.config file to pvxcom.exe.config.

Did you copy over pvxwin32.exe.config to v2015?

Also, i've seen pvxcom.exe in the workstation install's MAS90\Home directory and C:\Program Files (x86)\Common Files\Sage\Common Components so make sure to copy pvxwin32.exe.config from the 2018 server's MAS90\Home directory to and rename it to pvxcom.exe.config in any locations you have found it in on the PC with 2018 installed.

@KevinMoyes Yes I did that, but that isn't helping with the script. It DOES allow 2015 to print properly. Just talked with my client and @DavidSpeckII was CORRECT - it is now working since I copied the pvxwin32.exe.config file to the c:\program files (x86)\common files\Sage\common components folder AND renamed it to pvxcom.exe.config.