Sage 100

MAS 200 SQL version 3.74 (don't ask, it's a long and boring story). Starting last Friday the Inventory Options period keeps changing from period 12 to period 11. At the same time, the next automatic Sales Order # and next automatic Sale Order Invoice # is resetting to a value that was used a month or so ago. Very strange. Has anyone ever seen this or have any idea what would cause this? There are only 2 users that have access to the options menus and both insist they haven't touched the options. It has happened 3 times since Friday.

We have a customer who had a slightly different problem. But just in case... Periodically the GL would revert back to Dec 2012, including data! Turns out the server at one time had a shadowing function running that was configured, but turned off. When they rebooted the server, the files left in the shadowing function replaced the current files. Took over a month to track that one down.

Thanks Clark. I will check. I should add that this installation is running on an Applianz server, and users access it via remote desktop.

I'd probably guess something similar to Clark. Can't remember an issue where these change on their own.

I remember the next PO # was once screwed up by something in SY0CTL but only on Quick Prints. Might try looking for that in the KB, but it was a very long time ago...

Do they have the Bar Code module? There is an old unfixed bug of that era that bites you bad when choose Unattended Bar Code Transaction Import. Don't have to run it just choose it (actually don't). Choosing it writes an [I/MABCx] key to the BC0 file (table). That is the B/C Parameters file now has an unexpected and bad I/M options record in it. You're okay at that point until you restart MAS. You may know that upon start up of legacy MAS, the options records for all modules are copied into SY0CTL. So once I stepped thru that code and saw it was copying GL, AP, AR, IM, etc - all of them had their module option keys copied into SY0CTL. Everything was fine until gets to BC. That's where it copies not only the [B/CABCx] keys but also the illegitimate [I/MABCx] key that got in there because you selected Unattended Bar Code Import earlier. So the point is upon start up that bad I/MABCx from BC0 overwrites the good I/MABCx from IM0 and therefore it overwrites your I/M Setup Options. Fielded this call a bunch of times on MAS 200 SQL. About the Next SO and Invc # , you might want to look at all the xx0 Options tables (except S/O) with DFDM to see if any of them erroneously have [S/OABCx] keys.

@AlnoorCassim - They used to have the bar code module, but uninstalled it (and payroll) last May. I will check the SY0CTL table for bad records. I noticed when I execute the remote desktop session that the rdp icon is wpdserver (5).rdp. Notice the ""5"" in parenthesis. Is that the open sessions... sessions inadvertently left open? I am using the same logon as the other 2 administrators. i'm wondering if this could cause an issue. See attached pdf.. notice the rdp session minimized in the bottom left corner of the screen shot.

Doug SY0CTL will probably be clean at the moment. Although its not likely make sure with DFDM you don't see a BC0_Parameters for that company db despite the fact that B/C has been uninstalled. The wpdserver(5).rdp just means it's the 4th duplicate file name of wpdserver.rdp. It doesn't mean there are other open sessions running. After you go into your session you can check Task Manager / Users tab to see how many sessions are running. You can also add the Session ID column to the Processes tab.