Joe,
Errors 330 through 333 are generally about PERMISSIONS and not licenses.
330 -- no write access to field where no row level security permissions involved
331 -- no write access to field where there are row level security permissions
involved
332 -- no write access to field and the setting "allow any user to create" is
NOT
set during a create operation
333 -- no access of any kind (read or write) is allowed to the field for the
user
There is another message
8932 -- no write license
that was added as a companion message to also indicate that even if you had
permissions, you don't have sufficient license to perform the operation.
I did notice in the code that this companion message is issued in conjunction to
errors 330 and 332 if it is appropriate -- but I did see that this companion
message is not issued in conjunction with 331 errors.
Now, a license issue doesn't change your PERMISSIONS. In fact, you can write to
a field you have permission to write to without a write license under a variety
of
conditions but you can never write to a field you do not have PERMISSION to
write
to regardless of your license situation.
With all this, I think the focus on licensing is not the right avenue for you.
The problem really seems to be one of permission.
Did a group get overwritten and changed from a Change group to a View group by
any
chance?
Did a group get removed? Everyone who is a member of that group will not have
their definition changed but the fact that the group is missing will make that
permission meaningless for that user.
Did a form you are writing to have its permission model changed?
Did you have a customization that may have been overwritten where you had
changed
the permission and it got reset to the original?
I think these are the types of things most likely in this situation -- from the
messages and what they mean, you are probably dealing with a permission issue
rather than a licensing issue. (again, there are likely some corner cases where
licensing is involved; but they are not the biggest candidates)
I hope this helps,
Doug Mueller
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Joe Castleman
Sent: Tuesday, April 09, 2013 4:10 PM
To: [email protected]
Subject: Re: Write permissions errors with read (floating) license
Well today was much more quiet than yesterday -- I got a few reports that some
users were having the same results; other people let me know that they were no
longer having the problem. However, by yesterday afternoon, I had already sent
out an email explaining what was going on, so some of those affected may have
decided that they did not need to report the errors. Now that you mention it,
I'm not certain that this is a licensing issue.
Thanks again,
Joe
On Tue, 9 Apr 2013 20:45:39 +0200, Misi Mladoniczky <[email protected]> wrote:
>Hi,
>
>I would call that a Window-Open-Action, and that should not require a license,
>and the Submitter-group would not be involved in the receiving form.
>
>Or you might set your fields with a ACTL Set-Fields-Action from the server, in
>which case you should have no problem either.
>
>Are you sure this is a licensing issue? What happened today when more users
>came in?
>
> 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 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"
