Sage 100

Payroll issues that are based in the environment Reader's Digest Condensed version: Client on 2014 Standard began having problem in January, when a new computer and user came on board. Computer was provided by new IT provider. Issue is that when processing Payroll, user encounters Error 12 (file ""goes missing"", not the same file each time). Typically during Daily Transaction Register update the error gets thrown. Fix is to re-init the missing file, complete the update, then re-init PR Data Entry files, because data has not been cleared. We've been addressing this as either AV or permissions-related. When the user processes PR from a different computer, no problem. I want to put a document in IT's hands that states that users need full control to the sharepoint on the server (which we keep telling them verbally), but I can't find anything from Sage that clearly states it. IMO, the Appendix in the Installation Guide doesn't make it clear (but not being an IT type, maybe it will to them, but it seems to be TMI). Can someone point me to something else I can send them? KB has a KB article, but addresses Advanced.

What about 'power saving"" options on the new workstation. Could the option shutdown the computer, CPU, network card, etc. during the Daily Transaction Register Update?

I tend to agree with @MichaelMcDonald - it sounds like the new WS hardware issue.

We struggled with a similar issue (PRJ, PR_31, PRB would randomly vanish during payroll processing). Opened several cases with Sage, hit the Tools team a few times. We tried NICs, drivers, A/V, permissions, power management, SMB signing, opportunistic locks, just about everything. Once we moved MAS to a new server, the problem went away, so we never did find the cause. In my case it was a Server 2008 R2 terminal server connecting to a Server 2012 MAS server. They had Abra integration, FAS and BizNet.

Oh, and it was Standard.

Have seen this from time to time and leading candidate has always been AV or Malware scans.

We has this issue at a client also. Each time the Error 12 occurred it was a different file. Never did find the cause.

Wow - how encouraging (not).