Sage 100

 View Only
  • 1.  SAGE100 Standard v2014...getting the Error 200 SY_

    Posted 07-18-2016 06:33
    SAGE100 Standard v2014...getting the Error 200 SY_ReportCommon.pvc 627. I have read all the threads about reinstalling workstations...but it is also happening on the SERVER...do I need to reinstall completely??? That would be a pain since they have mods and ScanForce....


  • 2.  RE: SAGE100 Standard v2014...getting the Error 200 SY_

    Posted 07-18-2016 07:05
    Can you install the workstation on the server?


  • 3.  RE: SAGE100 Standard v2014...getting the Error 200 SY_

    Posted 07-18-2016 07:34
    already did that...error still there


  • 4.  RE: SAGE100 Standard v2014...getting the Error 200 SY_

    Posted 07-18-2016 07:42
    Can you install Crystal on the server?


  • 5.  RE: SAGE100 Standard v2014...getting the Error 200 SY_

    Posted 07-18-2016 10:26
    spent an hour with Sage support and no fixes....OK!!!


  • 6.  RE: SAGE100 Standard v2014...getting the Error 200 SY_

    Posted 07-18-2016 10:28
    This is not an exact match. It is for an older version. It also is not the same error #. That being said, perhaps it could be helpful if you haven't already tried - http://www.s-consult.com/2012/04/09/error-200-in-sy_reportcommon-pvc-line-611-in-4-5-and-line-596-in-4-4/


  • 7.  RE: SAGE100 Standard v2014...getting the Error 200 SY_

    Posted 07-18-2016 10:50
    I had seen this before and mentioned it to the SAGE support...we ran the batch command to register ALL DLL....still not working


  • 8.  RE: SAGE100 Standard v2014...getting the Error 200 SY_

    Posted 07-18-2016 15:02
    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.