If you are on a terminal server, make sure you copied over the current activate.pvx to the local workstation path.

Otherwise:

https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=222924450019875&page=1&position=1

I am running as an Application. This fixed it for about 3 hours and then it started again this afternoon.

Not to overlook the obvious, but when you get that message, do you:
1. Check Master Console (MC) and make a note of Accounting Dates and PIDs (and of course, User Count)?
2. Check Application Server Configuration (ASC) and make a note of Connect Times and S.PIDs?
3. Check Windows Task Manager on the Application Server and look for PVXWIN32 processes that don't match the PIDs in MC and/or the S.PIDs in ASC?*
Things I look for when this sort of thing happens:
A. Accounting Dates in MC that are unusually old.
B. Connect Times in ASC that are unusually long.
* Re Task Manager - of course, this is easier to do after getting all users out of the system - then you can stop the application and if there are any leftover PVXWIN32s - voila! There's your problem children.

One more quick idea.  In User Maintenance there is a checkbox for "Spawn Tasks from Application Server".  You should be 100% consistent with this setting for all users.  Either have it enabled for all users (which is our typical setup for Advanced / Premium) or disabled for all users.

If you added a new user recently, and didn't set this checkbox to match other users, that could explain your errors.

Upon further investigation, it does look like we are running out of licenses, but I'm confused about how this is calculated. We typically have 70-100 Sage processes running, and have for years. Never have had any issues. I'm trying to figure out why Master Console says we have 19 active, but *info looks like we have 33 active? At this point I feel like I'm going to have to write code to keep a history of SY_Console, so I can find which processes are being orphaned or I don't fully understand how Sage calculates a license usage. When I look in Windows task manager I am seeing roughly 10 more pvxwin32.exe than are showing in Master Console which I'm thinking is the issue, but I'm not sure why this is all of the sudden happening.

We did change this last night to make them all the same (they were inconsistent) but the issue popped up again today.  

Do any of your custom processes run in MAS90 mode?  Those will consume licenses, but may be missing from the Master Console.

How would I know that? We have C# routines that are hooking into the BOI. Some of these run directly on the Sage server and some are run on other workstations.

I don't do external BOI scripting, but I believe if the connection goes straight to the server's pvxwin##.exe, that would be MAS90 mode (bypassing the service). 

If it includes server / port (or triggers a local workstation pvxwin##.exe), that should be connecting through the Advanced service properly.

We do believe we have found the issue. After removing all users from the system and testing with our BOI stuff, it appears as if that is consuming the licenses. We recently did start doing some additional testing and that was pushing us over the usage. I had been looking in Master Console at the "Active Users" and had always assumed this was the number of licenses being used, but then I discovered *info and we were able to pinpoint the issue.

Thanks for all of your help!! 

Curious if you had any Sage "lock up" type conditions when you exceeded or hit you max users.

Our new Sage 2023 just froze all our users. I noticed our user count was pegged.

On our old system Sage 2014, the user would get an error message advising the max user limit.

Hopefully Sage 2023 handles this condition just a gracefully.

A note about user preferences.

Our original Sage 2014 install consisted of a providex Sage 2014 server, and all the workstations had Sage installed on each workstation (typically Windows 7 or Windows 10) on the same 1gb lan as the server.

We would occasionally get the error in your post.

We fixed the problem by modifying the preferences in each user configuration. On the Preferences tab, we checked the Spawn task on application server. This fixed the error.

On our current Sage 2023 terminal server/rdp environment we unchecked the Spawn tasks on application server for all users.

We don't get those errors.

We have 103 seat licenses in our environment..

A note about user preferences.

Our original Sage 2014 install consisted of a providex Sage 2014 server, and all the workstations had Sage installed on each workstation (typically Windows 7 or Windows 10) on the same 1gb lan as the server.

We would occasionally get the error in your post.

We fixed the problem by modifying the preferences in each user configuration. On the Preferences tab, we checked the Spawn task on application server. This fixed the error.

On our current Sage 2023 terminal server/rdp environment we unchecked the Spawn tasks on application server for all users.

We don't get those errors.

We have 103 seat licenses in our environment..