Connecting with NC 8.1.12.56235 gives "the number of concurrent users signed into the system has exceeded the system limit"

[PReinie]

The message gives a choice to click 'here' to continue. Clicking here tries to run a Java applet which takes a minute or more to complete and it might have something to do with updating. (The NC version doesn't change, staying at 8.1.12.56235.)

The next time I connect with NC I have to go through the same process.

The updater is installed.

If I use Pulse Secure 5.1.8 (61601) to connect I got a message to upgrade, which it did as now the version is 5.1.12 (61915) and I'm not asked again to upgrade and it takes seconds to complete the connection.

What might be going on with NC?

The users and I are all non-admins but the updater runs as admin. We're using IE11 on Win 7 Pro.

The above all started today, 20171020.

[zanyterp]

That should not impact whether you are connecting from Network Connect or Pulse
What do you see in the events log?
Are you connecting to the same role with both clients?

[PReinie]

There was so much constantly accumulating stuff in the event log I could make any sense of it.

Apparently corporate published/posted the update and once I accepted the update, PS moved to v12 (and still is at v12) and the problem no longer occurs but I think it's because corporate has since removed the update.

What do you mean by "connecting to the same role"? What is a role?

[mspiers]

The error message in the title is covered by https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB2388 , you must have hit the soft limit as you could continue to connect.

A Role is part of the configuration on the PCS that Pulse/NC connect to and is defined by the administrator, more information is in the Admin Guide starting at https://docs.pulsesecure.net/WebHelp/PCS/8.3R1/Home.htm#PCS/PCS_AdminGuide_8.3/User_Roles_Overview.h...

The Event log is a log file on the PCS availble to the administrator that records any notable events which would include the license count being reached or failures to contact an authentication server, for example.

The Pulse client has a debug log that records messages from only the Pulse client and its components.

As there are many different configuration options available it is usually best to contact your administrator if you have any issues and they can contact us explaining what the user problem is along with what they have configured if they are not able to resolve the problem - without knowing what is configured on the PCS we can only guess and make general suggestions about reported problems as the configuration controls what the expected behaviour is.

Regards,

--

Matt