That has been an ITSM <feature> for several versions now - the requirement to remove the support staff function completely and restore it in order to make significant changes to the permissions. I think it has something to do with needing to delete their User record from both the User table and the user_cache table and then re-add them in order to get them back in sync. We had to do that about once a month (maybe 10% of the user base over three years) for 300+ users in ARS 7.1 / ITSM 7.0.02/3. IN every case, all of the CTM:People, User, and CTM:PeoplePermissionGroup records appeared to be correct, and there did not _appear_ to be a problem in the user_cache table, but if we hijacked the account password and tested it had lost all of its permissions. Since upgrading to 7.6.04.01 Don only remembers having to do this once, and he thinks it may have been a legacy 7.1 problem that surfaced shortly after the upgrade for an infrequent user. So maybe, just maybe, it was fixed by 7.6.04.0x.
Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Peters, Ron Sent: Thursday, March 08, 2012 3:59 PM To: [email protected] Subject: Re: Account issue and arerr 330 ** Thanks. I wouldn't think that I'd have to open the hood for a simple people record permission modification. We're not doing anything special here and I assigned the user the same permissions that all our other support (non-admin) folks have with no luck. We did figure out the answer and I think it was stupid. We had to use the "Change to Non Support" function on the user. This of course requires that there are no active tickets for the user. I then had to re-assign all their tickets temporarily to myself which then changes the status of each one to assigned. After that, I changed them to non-support, then changed them back to support and added the proper support group/permissions. The final step was to re-assign all their tickets back to them. <vent>This convoluted procedure tells me that behind the scenes, they're playing fast and loose with roles/permissions and aren't taking care of the details in a clean fashion. This should be a simple role/permission adjustment. Much like Microsoft cars, pull over, shut the car off, re-start the car and continue driving when you lose signal on an AM radio station.</vent> From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of LJ LongWing Sent: Thursday, March 08, 2012 11:20 AM To: [email protected]<mailto:[email protected]> Subject: Re: Account issue and arerr 330 ** Ron, Admin of course has access to everything. You need to figure out what permissions the need OTHER than Admin to be able to update the records in question. You should be able to check the permissions on the fields to figure out what they may be missing. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Peters, Ron Sent: Thursday, March 08, 2012 12:08 PM To: [email protected]<mailto:[email protected]> Subject: Account issue and arerr 330 ** Hello all, I have an individual user that was set as an administrator with a fixed license. We were doing some changes and the person doesn't need administrator any more so we set the privs the same as any other typical support person (Incident/Change user, asset viewer). I then changed their license from a fixed to floating. They then could not update any of their tickets. I changed their account back to a fixed license, no luck. Then added administrator back and now they're working. I still need to remove administrator/fixed licensing from their account. How can I do that while making the account continue to work? We're on AR 7.5 ITSM 7.6 Thanks. These are the errors: You do not have write access to field : Notes (ARERR 330) You do not have write access to field : z1D_Contact (ARERR 330) You do not have write access to field : Customer (ARERR 330) You do not have write access to field : z1G_Customer_Search_Type_Msg (ARERR 330) You do not have write access to field : z1G_Contact_Name_Format (ARERR 330) You do not have write access to field : Customer Search Type (ARERR 330) You do not have write access to field : z1G_Display_CustomerInfo_Dlg (ARERR 330) You do not have write access to field : z1G Reopen Incident (ARERR 330) You do not have write access to field : z1G Enable Decision Tree (ARERR 330) You do not have write access to field : z1D_Last_Name (ARERR 330) You do not have write access to field : z1D_First_Name (ARERR 330) You do not have write access to field : z1D_Name_Format (ARERR 330) You do not have write access to field : z1G_HPDShowVendor (ARERR 330) You do not have write access to field : z1G_HPDShowFinancials (ARERR 330) You do not have write access to field : z1G_HPDShowDateSystem (ARERR 330) You do not have write access to field : z1D_PreviousAssignedCompany (ARERR 330) _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
