Sage 100

What's the trick to getting people out to rebuild files? I find that if I want to rebuild SO that having nobody appear in Master Console as being in SO really doesn't mean anything. I typically have to get everyone all the way out of Sage to the Windows desktop. I theorize this is because Sage somehow remembers that the user was in SO even though the Master Console may show them as having backed down to Library Master. Since Sage throws an error that you can't rebuild because someone is in the system - doesn't it know who that someone is and shouldn't they also be displayed on Master Console?

Sometimes it's not just that module that is affected. Like if you're rebuilding SO sort files, it can also affect the Qty On SO in IM, so no one can be in IM, either, which then means they can't be in WO, BM, IM, or PO, either, since those all touch IM.

I think so too. It just doesn't seem like it happens that way all the time. I'm fairly certain I've had everyone showing at the launcher and still had problems.

I have one client who repeatedly has to reboot the server in order to do a sort rebuild at month end on the weekend when no one else is logged in. In their case, I think it is their shipping software, which uses a Shipping Data Entry login - I think killing it doesn't kill the lock Sage puts on the IM files.

It's relatively easy to see open threads local to the server... just search for the pvxwin32 / launcher / pvxcom... processes in Task Manager. Finding locks on files that originate over the network might be discovered using Computer Management's ""Open Files"" listing.

Dang Kevin, I just needed to know that for a client and couldn't find it, so made 'em reboot the server. Then I saw your post. :-)