Sage 100

I have a client that has 4 batches in SO marked ""Print/Update"" and they can't update it they have 40+ users in the system and it is their busiest time of the year (they distribute to retail) tis is Sage100 2013 ADVANCED is there a way to reset that status without booting everyone out? I've tried: ""reset status"" on the batch printing screen rebooting the users computer killing that users task in master console and in the task manager looking at the GL_companyAcitveBatch - the status there is null Any help is appreciated. I don't want to kick all users out if I can avoid it

Any info on what the symptoms are when they try to update? Are the batches marked private?

no one is actually updating the batches. but they were all marked as Print/Update and they needed to get in and update them. I had him re-bot again and while he did that, I saw a task listed for that user (Invoice printing) in master console that still needed to be killed but I could not kill it through master console. Once I located and killed that task through Windows Task Manager, the batches were available again.

Try the batch status field in GL_CompanyActiveBatch.M4T using DFDM.

Maybe the date-updated and time-updated fields in GL CompanyActiveBatch are triggering your messages.

Thanks, the Status field was empty in GL_CompanyActiveBatch. after searching in windows explorer, I found that the batch files in SOxxx directory were locked by windows and there were .LCK files matching those batches too, but those were also locked (windows had them locked). I had earlier tried killing the task in master console that had everything locked, but it would not kill. I used the PID number listed in master console and matched that up to the PID number in task manager and did end-task. and that resolved it finally.

@DavidOverholt, we have used the same technique to determine a task to kill with Sage 100 Advanced. Another tool that has been useful is Computer Management (not Server Manager) > Shared Folders > Open Files where we can see and close Sage files that appear to be locked at the server level. This has saved us from having to get people out and restart the server.