Sage 100

Client is on 4.30.23 or so. W2003 Server. They were on XP workstations and they had no problems with this error. As soon as they started putting W7 32 bit machines on the network, they started getting the 5 User Limit Exceeded even though they only had 4 people in the system. No orphaned pvxwin32's. Now they are getting it every other day or so and they are also getting the same error when trying to print reports, journals, etc. I had the outside IT company implement the 'Stop Granting of Opps Locking' on the server and the workstations and it didn't resolve the problem (although I probably should have cleared the locks files at the same time) but more important is they can't stand the slowness so even if it did work, it wasn't an option. I had IT undo the resolution today. I have recommended implementing the XP mode on the W7 and IT is not very happy about it but will do it if I insist. I advised them I would put out calls to my fellow consultants to see if anyone had any other options/suggestions. Any other ideas? Server has 2 gb of memory, could this be a problem? If so why would it cause a problem just when the W7 boxes added? They do have 1 user still on an XP box. Thanks Nancy

I had the same problem. This makes little sense but I re-entered the unlocking keys etc, hit activate on registration screen and they no l

They no longer get the error.

Thanks Debbie! I will try this at one of my clients as well if the Opp Lock fix doesn't work.

Is it 90 or 200?

@NancyHanson are you saying disabling the opportunistic locking caused the system to slow down? I thought disabling the opportunistic locking was supposed to speed things up, not slow it down.

It is MAS90. It slowed it way down.

@ThereseLogeais - OpLocks means the 2nd user/workstation caches the same data file that is being shared over a UNC or mapped drive (which means this is not really an issue with mas 200). So let's say 3 users use S/O Entry all day. If we disable OpLocks, the 2nd and 3rd user run slower in S/O Entry. In the past the slow-down wasn't too noticeable but since Vista and Win 7, because it uses a different version of OpLocks it can be more noticeable. @NancyHanson - you should get the same benefits of OpLock disabling by only making the server-side registry change and rebooting the server again. IOW, revert the workstation settings back to default. This way it won't be as slow as both sides having it disabled. Having said all that, I'm not sure this is the cause of this issue. Go with Debbie's idea first as that's easier than anything else and would be an awesome solution. If it doesn't work, then setting the MAS 90 shortcuts on Win 7 PCs to run in XP SP3 compatibility mode is a good troubleshooting measure. This can be turned off once things calm down. Usually license loss occurs when: 1) A MAS task isn't shutdown properly such as VI import that auto-runs, finishes and it appears to have completed but errored out before proper completion (like when chaining between 2 jobs and 2nd job starts before 1st completes). 2) The client connection is shut-down Do they leave their PCs idle for long periods of time (such as all night long). There are some server settings related to how long it should wait before terminating a client connection (meaning you don't want a MAS task open when this happens).

Is the client using CRM? We had a client experience this when they had Sage CRM integrated to their live company and then made a copy company and copied the CRM data too. It duplicated the CRM user even though that didn't show up in master console. They removed CRM from the test company and the error stopped.

I tried the 'activate the system' resolution today so we'll see how this reacts. Thanks everyone for your suggestions.