I'm not sure why it is happening, but we saw the same thing a few years back. After we imported, we ended up searching for all the records that had been updated and did a modify all. We set the status to current for the modify all and saved. That fixed the issue for us.
Todd Arner From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Natalia Cuesta Sent: Wednesday, September 30, 2015 1:04 PM To: [email protected] Subject: Re: So why did this happen (alternat title: How to lock out all of your users) ** Hi, I cleaned the Remedy cache but the issue continues. NC De: Action Request System discussion list(ARSList) [mailto:[email protected]] En nombre de Richter, Howard (CEI-Atlanta) Enviado el: miércoles, 30 de septiembre de 2015 13:00 Para: [email protected]<mailto:[email protected]> Asunto: Re: So why did this happen (alternat title: How to lock out all of your users) ** Hey William, We just did the same thing and I saw the same issue. I think it had something to do with the Remedy cache. By the way how are you doing? hbr Howard Richter, Senior System Administrator From: Action Request System discussion list(ARSList) [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of William Rentfrow Sent: Wednesday, September 30, 2015 1:58 PM To: [email protected]<mailto:[email protected]> Subject: [arslist] So why did this happen (alternat title: How to lock out all of your users) ** We have a Remedy 7.6.04 system which as been replaced by another vendor. It is being phased out. As part of that process we are greatly reducing licenses and changing users to floating from fixed. I did a search in the User form where 'Application License' LIKE "%Fixed%". Then I exported the Request ID and Application License of all of those users. In the ARX file I replaced "Fixed" with "Floating" and then re-imported all of them, using the option to update old record with the new data. Everyone who got updated now gets a 623 "Authentication failed" error when trying to login - which is weird, because we use LDAP for authentication. None of the password should have changed. The import process could have (and should have) updated the user's user_cache entry, but not in a way where I'd expect them to get locked out. IF I update their user record somehow it fixes the problem for the individual user. Weird.... William Rentfrow [email protected]<mailto:[email protected]> Office: 715-204-3061 or 701-232-5697x25 Cell: 715-498-5056 Click here<https://www.mailcontrol.com/sr/NZE2DbrwERjGX2PQPOmvUml+xXZX6IbqqQDWdchmMj+EVx5gfG4Jgy5lweXHVMAEajZFfUOps2KDL!bKPtQR4w==> to report this email as spam. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ ---------------------------------------------------------------------- The information contained in this communication may be confidential, is intended only for the use of the recipient(s) named above, and may be protected under state or federal law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please forward the communication to [email protected] immediately and destroy or delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
