Sage 100

 View Only
Expand all | Collapse all

I just upgraded a system to V2013 and now when th

  • 1.  I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:33
    I just upgraded a system to V2013 and now when they are attempting to print G/L Financial reports it pops with a message ""Module P/R not on file"" then closes. Anyone seen this? It sounds familiar but can't remember the fix. I have checked usually suspects in Sy0ctl.soa. Any other ideas? Note that they do not have the PR module but did in the past. Last resort is to install the P/R Module.


  • 2.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:36
    Do they have any modifications?


  • 3.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:38
    I've seen this before. Let me check I think it had something to do with jobs ops rouge file issue.


  • 4.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:38
    Are they using job ops


  • 5.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:39
    Jim, use DFDM to verify no Payroll lower case L or R (l or r) records. Also check SY_Module. Otherwise Payroll Services on?


  • 6.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:39
    Yep..


  • 7.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:39
    I had something similar recently and was able to resolve by copying the live company data to a ""tst"" company and then copying it back to the live company. Probably worth a try.


  • 8.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:40
    Give me a minute I will get you the answer.


  • 9.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:41
    I heard about this happening when job ops is installed. Any 3rd party or mods?


  • 10.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:42
    I have seen it and here is the fix if your client has JobOps - we just encountered this last week. Here is the fix. I recommend making a backup of the file first. 1. Access Data File Display and Maintenance - SY_ClassEnhancement.M4T file 2. Locate and select record SYS158JT410001.SYS158SY_REPORT 3. Remove the selected record - Remove the record where StandardClass$ is set to SY_REPORT only remove this exact record.


  • 11.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:50
    Yep that's it. Sweet Mary..GJ


  • 12.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:52
    @MaryMays That was it. Thanks to you and other for responses!! I will add it to our 90 Minds KB


  • 13.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 15:58
    @JimWoodhead this fix is already posted in the JobOps group (although the problem was not quite the same).


  • 14.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 16:03
    I was working through my resources. You got to love 90minds for a quick fix that takes 10 minutes or less!!! Now the 90 minds KB will have it too! The funny thing about this error is that GL had nothing to do with JobOps, go figure. But I knew I had seen it I just couldn't remember where...


  • 15.  RE: I just upgraded a system to V2013 and now when th

    Posted 03-12-2014 16:05
    It does have to do with JobOps as their developer code is 158.