OnDemand User Group
Support Forums => Windows Client => Topic started by: DDP021 on September 29, 2020, 06:18:10 AM
-
We are using the Windows admin client 10.1.0.5 for adding new CMOD user access requests. We've found that only one of our CMOD Admins can do any requests at one time when ADDING new users. If more than one Admin attempts to add new user requests (different users) at the same time, we'll receive an error indicating that the UID number already exists. I know its a timing issue but was wondering if there is anyway to avoid this? At times we can have many requests pending and it would be nice to have multiple Admins being able to process requests at the same time. As indicated, this only happens when trying to add new users. Updating existing users isn't an issue.
-
Have you considered using ARSXML ?
It could be a life saver in this instance when you have a lot of users to add.
It is very fast to execute and it could be a life saver when defining a lot of objects to CMOD such as users, groups, applications, etc...
-
Seconding ARSXML for batch adding definitions, but that still feels like a bug in the client. Either the UID # needs to be incremented at the time an Admin requests to create a new user, or the UID # needs to be assigned at the time the Admin clicks 'Ok'.
I'd open this as a PMR/SR and report it as a bug.
-JD.
-
Will do Justin....We receive our requests via an access form submission system. Most times they are just one off adds. But at times they can come in clusters which would make it nice if more than one person can process them at one time. Before we realized what was happening it was baffling when we received the User id or UID already exists..Because we knew the id didn't exist it pointed to something related to the UID....Checking, we determined someone else was trying to do the same thing at the same time. Once we waited until they completed their task and then did a F5 on our session, we could process the request. It seems when you go to do the add, it grabs the next UID number. If someone else goes to add an id, at the same time, it also tries to use that same UID number. Then we see the error.
-
If you run into that issue again, you should be able to tweak the UID# field and try clicking OK again... I suppose you could try that a few times if you have lots of people trying to add a bunch of users at the same time.
-JD.
-
I ran into this issue a few years ago. There is an IBM technote on it; https://www.ibm.com/support/pages/node/286565