Sage 100

 View Only
Expand all | Collapse all

So this is an interesting one. We have a customer

Michelle Taylor

Michelle Taylor02-25-2016 14:07

Cooper Black

Cooper Black02-25-2016 14:08

Cooper Black

Cooper Black02-25-2016 14:10

Jeff Fiddelman

Jeff Fiddelman02-25-2016 14:24

  • 1.  So this is an interesting one. We have a customer

    Posted 02-25-2016 14:01
    So this is an interesting one. We have a customer on MAS 90 V3.71. They got an error today when running the payroll tax calculation that says all users must be out of data entry before running tax calc. All users are out. We have restarted the MAS server and all workstations. We confirmed that the shared folders and files on the server do not reference the Sage share. We can run the tax calc in other companies within this MAS install. We have rebuilt Keys, Lines and Sorts. Something is locked somewhere. Any thoughts? TIA


  • 2.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 14:07
    Any files in the Lock folder?


  • 3.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 14:08
    I'll check


  • 4.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 14:10
    No lock folder


  • 5.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 14:12
    Check open files on server in shared files - computer management ??


  • 6.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 14:14
    @JeffFiddelman - we checked that and cannot find anything in the shared files area


  • 7.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 14:15
    Check PR0, record type 1 for a value in position 48. It should be blank.


  • 8.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 14:22
    Thanks @KathrynScofield. We apparently did look for that as well.


  • 9.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 14:23
    the 371 program attempts to open and lock the following company files - perhaps one is missing: PR6 PR9 PRB PRI PRJ PRK PRL PR_02 You can look in windows first, and if they are all there, you can try to open each one in syzcon with something like Open (1) ""..\prxxx\pr6xxx.soa"" and if it opens, try lock(1) if it locks, then close (1) and try the next file.... my guess is that one of them is missing or damaged.


  • 10.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 14:24
    We ended up copying the company data, ABC, out to XYZ and then deleted ABC. Then we recreated ABC and copied XYZ back over to ABC. The problem disappeared. No idea why.


  • 11.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 14:24
    probably a missing file ???


  • 12.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 14:25
    Probably. I think @JeffFiddelman may have been right on target. I should have asked hours ago. thanks to all.


  • 13.  RE: So this is an interesting one. We have a customer

    Posted 02-25-2016 16:05
    Heads up. I had a client getting a bad record in the PR0 on occasion and unable to resolve. I solved their issue by copying, deleting and copying back. None of the problems I had would have been an issue in 3.71 but in 2015 I lost all of the listing of PDFs in Paperless and had to play to get forms back. Again, none of this would be an issue in 3.71 but when I read something like this a year from now... my own comment here will help me. :)


  • 14.  RE: So this is an interesting one. We have a customer

    Posted 05-24-2017 09:23
    I have a client who is getting an error during tax calculation that says PRJ is in use. Weird. KB says to delete and manually reinitialize the file. Will try that, also will see if the server has the file open/locked. Simple Task manager kill, I'm hoping.


  • 15.  RE: So this is an interesting one. We have a customer

    Posted 05-24-2017 10:00
    Figured it out. One of the employees was not set up for the deduction code that was being imported. Added the deduction code to the employee master file and the tax calculation worked.


  • 16.  RE: So this is an interesting one. We have a customer

    Posted 05-24-2017 10:25
    @CooperBlack way to go! When I worked at Sage, during the Jurassic years this was somewhat common issue from versions 1.x through 3.x. If the std resolution didn't work, the solution was to do exactly what you did with SVDATA to copy company data to another company then back to original (it was SUDATA for 1.x and 2.x). At one point I figured out issue was the [P/R ABCx] record in PR0 (where x was 6 or 9 or something) was short and expanding the record worked. But since that wasn't easy to walk someone thru over the phone, and a copy of all PR0 records were stored in Sy0ctl.soa (the system always used the copy), it was still easier to do the SVDATA.