Sage 100

I have a client MAS 200 4.30.0.13 (PM2000, ACSG Multi-Company AP, AP-1063) getting the error ProvideX:Initialization; ProvideX Development Application Environment; CS Workstation Activation; 1 user limit exceeded. NO VALID ACTIVATION FOUND! (see screen shot below) on several MAS Users, in various company codes. The error is odd because it is NOT occurring when the MAS User is launching MAS 200, but while they are in MAS 200 doing processes, like A/P Invoice Data Entry, not necessarily when opening a new window/screen or changing processes. (for example the error has occurred during invoice data entry, the error pops up and the MAS User is kicked out of MAS 200. The User can then restart MAS 200, and only the invoice which was being entered is lost). The error only seems to be occurring in Accounts Payable for various company codes on multiple MAS 200 Users. It does not appear they are using Task Manager to kill any MAS 200 tasks/process prior to the error occurring. Just checking to be sure it is not related to the add-ins. It is odd because I've never seen the 'CS Workstation Activation' part before. The problem is intermittant, but consistant, like once or twice a day. The client IT was deploying Keysa Network monitoring agents, but not sure of Keysa's current status - it was causing other problems a couple weeks ago.

Are they connecting via Terminal Services / Citrix? Otherwise, have you seen this write-up (need to be logged into the Portal to view it)? Looks to be hardware/infrastructure related. https://partners.sagenorthamerica.com/irj/go/km/docs/sageKM/Sage%20MAS%2090%20and%20200/Gated%20Customers/Warr_Svc_Support%20Plan/1758.html

Is this via a wireless connection by chance?

This is a direct connect, and not wireless. The KB is for 3.50, but the point being it is network related is possible, and may be releated to their Keysa network monitioring.

I've usually seen this type of thing with a rights issue in the home\lib\keys - could Keysa be somehow changing rights if even briefly?

I spoke with client IT. The Malware agent has not been deployed, only an agent which allows remote access and VNC. They said it was not an 'active' monitoring agent, so it may be something else. Eset nod32 is the AV and (per IT) the exclusions have been set. But I still suspect Keysa.

I add to check the NIC power settings too on these workstaions. Also, had an issue for the longest time with a client that would loose the connection to MAS randomly during the day. Turned out after much finger-pointing that the switch/router needed a software update. I'll get the brand/model for you @KennethPhillips if it will help.

I think @MoiraGoggin may have this pegged. I too have seen this before and it was network related. Check out Old KB ID 1758. It came up fine on atlas.