Your submitter mode is probably the culprit.
The Submitter Mode options are:
* Locked — Enables users who have their name in the Submitter field to
modify requests without a write license. This does not apply to users with a
Restricted Read license who cannot modify requests under any circumstances. In
the locked submitter mode, after the entry is submitted, the value in the
Submitter field cannot be changed.
* Changeable — Requires users to have a write license to change any
record, including requests for which they are the submitter.
https://docs.bmc.com/docs/display/public/ars81/Enabling+submitters+to+modify+requests
If you have it set to Changeable, then users without a write licenses cannot
modify records - even their own.
Thanks,
-David J. Easter
________________________________
From: Joe Castleman <[email protected]>
To: [email protected]
Sent: Monday, April 8, 2013 1:16 PM
Subject: Re: Write permissions errors with read (floating) license
Yes, among other things we are fetching the ordinal date and populating the
home page. There are push fields on window open actions from the Home Page,
though certainly not to all of the fields for which it is giving us errors.
I did notice a discrepancy between the legacy server and the new server, old
server had submitter mode = locked and the new one had submitter mode =
changeable. When I have a chance to reboot I'll change it to locked, at least
for consistency's sake. But I'm not sure whether it would make a difference in
this case?
Interesting note about the license allocation circa 7.6, because even when
people don't get ARERR 331, they are acting like the float-read-warning is
totally unfamiliar to them. But we have the same number of floating licenses,
and users, that we always did.
If I can get my mind "unwrapped around the wheel" I'll take a look through the
user log file.
Thanks,
Joe
On Mon, 8 Apr 2013 21:07:24 +0200, Misi Mladoniczky <[email protected]> wrote:
>Hi,
>
>The FLOAT-WRITE is grabbed as soon as the user performs any activity.
>
>The FLOAT-READ-WARNING is not displayed until the user tries to save something
>requiring a FLOAT-WRITE. And it is only displayed the first time this happens.
>
>If you get message as soon as you login, I bet that you have some code that
>actually performs a write, such as a Push-Fields.
>
>BMC has "fixed bugs" in the license allocation, and this might cause license
>usage to increase. I think the major thing happened in 7.6, but I am not
>sure...
>
>Turn on your user log, and check your license usage. Is it correct?
>
> Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
>
>Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11/12):
>* RRR|License - Not enough Remedy licenses? Save money by optimizing.
>* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
>Find these products, and many free tools and utilities, at http://rrr.se.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://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"
