I am struggling with how Submitter Mode has a significant impact on a record being locked? It is a licensing function not locking function. I suppose if you have more people that can write to record (with read license) then locking could be more frequent but AR System design wise I don't think this should be much of a factor.
Jason On Tue, Sep 22, 2015 at 7:40 AM Rick Westbrock <rwestbr...@24hourfit.com> wrote: > I notice that part of the solution is changing the setting of Submitter > Mode Locked. That is not a trivial change to make to your configuration. > BMC is suggesting that you change from Submitter Mode Changeable to Locked > which can affect custom workflow that might happen to change the value of > the Submitter field for whatever reason. It does bring the advantage > however that a user with a read-only license may modify a record for which > they are the Submitter which can help reduce your licensing requirements or > add the flexibility for read-only users to update tickets which they > submitted. > > I just thought I would point that out as I ran into a problem in the past > when moving a client using custom apps from a server with submitter mode > Changeable to a shared server with submitter mode locked as we had to > recode parts of the applications to not change the Submitter field. > > > -Rick > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Brian Stone > Sent: Tuesday, September 22, 2015 4:06 AM > To: arslist@ARSLIST.ORG > Subject: Re: ITSM 8 - Requested record is locked > > Brad, > > Below is from BMCs KA KA401899, Hope it helps. > > Brian > > > Randomly encountering "Requested record is locked by another user, please > retry. (ARERR 566)" error message upon accessing a record. > > LP: BMC Remedy AR System Server 8.1.00 > DR: AR System 8.1.00 > > SQL Server 2008 > > Details: Randomly encountering "Requested record is locked by another > user, > > please retry. (ARERR 566)" error message upon accessing a record. > > Issue Summary: Remedy Error (ARERR 566) > > > Solution > > Add/modify below parameters in ar.cfg file and restart arserver service. > > Select-Query-Hint: NOLOCK > Next-ID-Commit: T > > and change Submitter-Mode: 2 to Submitter-Mode: 1 > > So the expected final settings are > > Select-Query-Hint: NOLOCK > Next-ID-Commit: T > > Submitter-Mode: 1 > > Problem > > Randomly encountering "Requested record is locked by another user, please > retry. (ARERR 566)" error message upon accessing a record. > > LP: BMC Remedy AR System Server 8.1.00 > DR: AR System 8.1.00 > > SQL Server 2008 > > Details: Randomly encountering "Requested record is locked by another > user, > > please retry. (ARERR 566)" error message upon accessing a record. > > Issue Summary: Remedy Error (ARERR 566) > > > Solution > > Add/modify below parameters in ar.cfg file and restart arserver service. > > Select-Query-Hint: NOLOCK > Next-ID-Commit: T > > and change Submitter-Mode: 2 to Submitter-Mode: 1 > > So the expected final settings are > > Select-Query-Hint: NOLOCK > Next-ID-Commit: T > > Submitter-Mode: 1 > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the > Answers Are, and have been for 20 years" > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
