The error that Wayne's post references is almost certainly the same error that Alnoor offered a solution for. The error 200 is being returned when the program tries to create object SY_ReportEngine. This is the thing that manipulates the Crystal DLL. It is probably bombing because it cannot load the Crystal object up, just as described in the 4.40 and 4.50 post from Wayne.
In the 2014 version it appears that it's no longer using the same DLL. In this version it tries to instantiate ""Sage100ERP.Reporting.dll"", which is in the mas90\HOME folder. I am a little out of my area here, since I have not actually dealt with the same problem, but you might try registering this file. The regcom.bat registers neither the Crystal DLL nor this one which is why Alnoor recommended doing it manually.