Sage 100

 View Only
  • 1.  Sage 100 Advanced 4.5.6 with JobOps product updat

    Posted 01-17-2014 10:08
    Sage 100 Advanced 4.5.6 with JobOps product update 6/R2Duke was installed last night now the client receives the object ""report name_ui"" does not exist for the following reports. All other standard reports print fine. General Ledger General Ledger Detail Report Budget and History Report Accounts Receivable AR Aged Invoice Report Cash Expectation Report Customer Sales Analysis Sales Analysis by Sales Person Cash Receipts Report Accounts Payable AP Aged Invoice Report Cash Requirements Report Vendor Purchase Analysis Monthly Purchase Report The reports do exist; I replaced the AR Aged Invoice report with my working copy, verified the database and still have the same issue. Spoke with Sage and they suggested a file was locked and to reboot the server, this did not help.


  • 2.  RE: Sage 100 Advanced 4.5.6 with JobOps product updat

    Posted 01-17-2014 15:11
    Try running the embedded io replacement script. It can't hurt. KB titled: how to replace embedded io files


  • 3.  RE: Sage 100 Advanced 4.5.6 with JobOps product updat

    Posted 01-20-2014 08:52
    @JoanSerr - thanks for the suggestion, unfortunately it did not resolve my issue.


  • 4.  RE: Sage 100 Advanced 4.5.6 with JobOps product updat

    Posted 01-20-2014 10:41
      |   view attached
    OMG, Knew this matter felt familiar. Not the exact same thing but similar and relative. Here are my notes troubleshooting last 4.5 installation, the dll installs to the wrong location. Even if upgrade, reporting dll's install with the workstation setup. Figure appicable either way. Hope this is it.

    Attachment(s)

    docx
    450worksheet.docx   11 KB 1 version


  • 5.  RE: Sage 100 Advanced 4.5.6 with JobOps product updat

    Posted 01-20-2014 11:03
    All those reports you mentioned can be run thru the BI Dashboard as well as the normal way. So when those report are run, an ES program is checked to see if it's being run the normal way or thru the BID. I troubleshot this same exact error for someone on a 4.40.x Job Ops last year and sure enough the problem was her \mas90\ES folder was missing a bunch of programs. just copied over my \mas90\ES programs for the same version / product update into her \mas90\ES folder and all was good. I didn't have Job Ops myself but didn't need it.