Sage 100

Just throwing this out there, don't really expect an answer. Client having SY0CTL.SOA corruption issues since Nov. Weird errors like R/A record missing when they don't own RMA. UFAR the file and we're OK for a bit, but that bit is getting shorter and shorter. Was on client's machine tonight and ufar'd, got in. Tried to go into backup payroll company, error and kicked out. Could not get back in - B/R rec in use in sy0ctl file. So tried to rename sy0ctl from his machine and told the file was in use. Logged onto Sage server and renamed. Went back to his machine and tried to run, error file missing, as expected. Then tried to rename back from his machine - told that the .SAV file was in use, which is obviously BS. So I had another copy of the sy0ctl on his C drive from the UFAR, so I clicked COPY and then attempted to paste it into the SOA folder. Got nothing. No error, but also no copy. Just NOTHING, as if I hadn't clicked Paste at all. So pretty much has to be some stupid network issue, but has anyone ever seen weirdness like this? I've emailed the IT guy, but not holding out hope.

Beth, unfortunately I don't have an answer but I do have a customer account just like this. SY0CTL gets mangled about once a month. It happens so frequently that we scheduled a batch file job to run every night to copy the file into a backup directory on a nightly basis so we can copy the backup over the corrupted file after rebooting the server. If you find the cause, please share. We are convinced it is an environmental issue but their IT guy thinks we are wrong and won't do anything to try to find the issue. Small network, maybe 10 workstations total. Only 3 users in Sage 100 Standard. If you find an answer, please share. It's a headache I would like to escape.

Very similar except we have fewer workstations, but same number of users in Standard. Well, if nothing else, it's nice to not be alone.

anti-virus/malware.

What about the server going bad? Seems like a few years ago I had something similar and they finally upgraded the server. They were off Sage maintenance and on an older version, so it was also a way to get them to re-purchase.

Server is pretty new, but of course that doesn't mean it can't have something going bad.

@ShawnSlavin - have a possibility - Volume Shadowing. Last week had that as an issue on a local machine (locking a file) and now it may be the issue with this SY0CTL problem. Do NOT know for sure yet, but definitely looking at it.