When this happened to did you see how many were actually logged in? Have you looked to see if you had "ghost" sessions taking up license. Do you have other applications that use a license such as InSync

There were 20 people logged in. We haven't changed anything or added any new processes, so I'm unsure why this would just start out of nowhere. We have custom code running pvxcom objects, but we haven't changed anything about any of our processes in the past year and this just started happening.

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.

You reset the session files?

Yes, I did everything in the article besides change the port. I'm assuming you are referring to this step:

To refresh the Application Server Configuration files in caase they were corrupted:

1. Stop the Application Server and close the Application Server Configuration application.
2. On Server go to the Task Manager and kill all PVXWIN32.exe's.
3. On the Sage 100 server, rename the following files:
   • ..\MAS90\MAS_System\SY_Console.m4t
   • ..\MAS90\MAS_System\SY_Workstation.m4t
   • ..\MAS90\Home\Lib\_Appserv\Locate.pvk
   • ..\MAS90\Home\Lib\_Appserv\Sessions.pvk
4. Go to All Programs and find the Application Server Configuration and Open it, once it has created the files you can close it.
5. Restart the Application for Sage 100 ERP Advanced or Premium
   1. From the Windows Desktop at the Sage 100 ERP server, click Start
   2. On the Programs menu, point to the Sage Software or Sage program folder
   3. Select click Application Server Configuration
   4. Click the Server tab. Clear the KeepAlives check box
   5. Click the Clients tab. On the Re-Connect list, select None

We have been running as an Application for some time. I think when we ran as a service we had similar errors, but I don't recall the exact errors. When we ran as an application it stopped happening. I'm trying to remember when this started, but it seems like this has been happening randomly the past couple of weeks, although today and yesterday have been really bad.

If changing to application was the fix, this is the long term solution (Option II):

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

Did you copy the current activate.pvx to the local workstation folder, where you are getting the error?  In spite of the Sage documentation, this is NOT automatic, and can limit the number of connected users on a terminal server to below the actual Live license count.

AV Exclusions:

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

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.