Error Message: Cannot Have Concurrent User Updates

[DavidThomson1]

A number of my admins have come to me with the same problem.  When they are performing tasks within the Security Console such as unlocking users or clearing incorrect passcodes, they get the message "There was a problem processing your request: Cannot have concurrent user updates".  One of them sent me a screenshot of this happening (see the attached image).  This appears to be happening to multiple admins and multiple users.  It also seems to happen at random and will sometime clear on it's own after a few minutes but other times it stays and the admin cannot help the user.  Based on the message I assumed more than one admin was attempting to help the same user at the same time but they state that's not the case and it's just one admin help one user.

I've check the system logs and I can see lots of entries mentioning “com.rsa.common.ConcurrentUpdateException: Multiple administrators attempting to update data at the same time” but the times don't seem to match up with when the message appears, so I'm not sure if they are related or not.

Also, there are no scheduled tasks such as backups and cleaning of unresolved users during the times these admins are working.

Has anyone seen this issue before and know how to resolve it?  We currently have RSA AM 8.3.0.6 installed.

[SpencerMay]

David Thomson‌ I know it's been a while but did you ever find a resolution to this?  We had the same issue this morning.

[GeorgeMaher · Accepted solution]

Hello Spencer,

The resolution that was provided to David was to check how many Admins are logging at the same time and checking if they are editing the user at the same time by following the below steps:

1.Please open the Security Console, click Access > Active User Sessions.
2.Use the search fields to find the sessions that you want to close. These fields are case sensitive.
3.Select the users whose sessions you want to close.
4.Click Close Sessions.
5.Click OK.

If you still have the problem, please resynchronize the token again of this specific user as a workaround.