Sage 100

 View Only
Expand all | Collapse all

We have a client running Sage 100 2014 Standard fr

  • 1.  We have a client running Sage 100 2014 Standard fr

    Posted 10-10-2016 14:43
    We have a client running Sage 100 2014 Standard from a server. Until recently the one Windows 10 workstation that they had gave them no problems with the PDF converter and paperless office. After the system did the automatic ""Anniversary Update"" they are now getting errors when printing to paperless office.Here are examples of their errors: ""Unable to print AP_ManualCheckRegister.rpt. The custom page size is invalid."" They also get this error: Error 88 Invalid/unknown property name O/S Error Error in File PO_PurchseOrder2.rpt Invalid page margins Program SY_REPORTENGINE.PVC Statement 736 Class SY_ReportEngine Method PrintOut


  • 2.  RE: We have a client running Sage 100 2014 Standard fr

    Posted 10-10-2016 14:52
    My experience has been that the pdf converter just won't convert the pages properly. Perhaps you could somehow get the new Sage 100 PDF Converter installed, which is for v.2015 and above.


  • 3.  RE: We have a client running Sage 100 2014 Standard fr

    Posted 10-10-2016 15:44
    Did you uninstall/install wksetup again? I was getting errors too but more of the 'unable to process lock file' after this update but no lock files found. wksetup fixed it.


  • 4.  RE: We have a client running Sage 100 2014 Standard fr

    Posted 10-10-2016 17:53
    I have also had to setup the Sage port again, the null and one note which attaches itself to null seem to interfere.


  • 5.  RE: We have a client running Sage 100 2014 Standard fr

    Posted 10-11-2016 11:07
    The registry permission hack solves the ""Anniversary Update"" issues for us. HKCC\Software - full control For this specific error, disassociating the report from a specific printer, and looking for any objects in the report that extend past the margins, should do it.


  • 6.  RE: We have a client running Sage 100 2014 Standard fr

    Posted 10-11-2016 12:30
    Ran into this a few days ago, Win10 with updates shows a standard Crystal SO form-rpt that should print, give error of page header or footer was too big/small to print. Beside the standard Sage 100 PDF converter stuff - which I tried first. The solution was, for some strange reason, the Crystal SO form had picked up the users default printer in the form. I had to go to Crystal designer and check the page setup and change the form back to ""no printer"" and then it worked.


  • 7.  RE: We have a client running Sage 100 2014 Standard fr

    Posted 10-12-2016 10:15
    @JimSteele changing the printer to ""none"" worked perfectly. Now the big question is how do you do this for ALL of the reports in the system without doing it individually? Anyone have any ideas?


  • 8.  RE: We have a client running Sage 100 2014 Standard fr

    Posted 10-12-2016 10:17
    I think there should be no default printer for ALL reports unless specifically selected. If you figure something out, let me know.


  • 9.  RE: We have a client running Sage 100 2014 Standard fr

    Posted 10-12-2016 10:25
    Chuck, I don't know the rhyme or reason behind why the printer changed from ""no printer"" to ""a default printer on someone's PC"". Only advice I would have would be to check a backup and see if the .rpt's usually found in the reports folder under MAS_XXX (company code), have a printer assigned to the .rpt or if it is ""no printer"", might make it easier to replace instead of going into each one.


  • 10.  RE: We have a client running Sage 100 2014 Standard fr

    Posted 10-12-2016 10:53
    Back in the day, many moons ago, Alnoor gave me good advice regarding the ""no printer selection"" Since that time, I always select the ""no printer field"". I am puzzled why Sage make this the default setting for all rpt forms. Also, why is the bottom margin set a .66"" instead of .25. It doesn't make sense.


  • 11.  RE: We have a client running Sage 100 2014 Standard fr

    Posted 04-17-2019 08:13
    I know this is quite old but I am running into the issue of Invalid Page Margin on all forms and reports for a client after updating a PDF solution they use.  At first it appeared to only be with this tool called UniPrint.  Paperless functionality still works but if we use Export to PDF, we get the same issue.  Was there a solution without editing every crystal form?

    ------------------------------
    Larry Bradford
    Accounting Technology LLC Consultant and Owner
    Accounting Technology, LLC
    Fairfax VA
    703-913-3500
    ------------------------------