| Yukiji,
Could you tell us please what version ALL-IN-1 you are using?
I suspect from the option string MGT MUA C that it is V2.4 or
earlier? (V3.0 has 'CU'). Have you tried this /NOCUSTOM? (i.e.
customized forms lying around?)
I would suggest that you either set trace on, (or if V3.0, turn on
debug), and check where, exactly, during the field validation, this
error message is returned.
Regards
DaveT
|
|
Dave,
> Could you tell us please what version ALL-IN-1 you are using?
> I suspect from the option string MGT MUA C that it is V2.4 or
> earlier? (V3.0 has 'CU'). Have you tried this /NOCUSTOM? (i.e.
> customized forms lying around?)
Oh, sorry. Our system is ALL-IN-1/Japanese V2.4 with up to K604
and no customisation.
> I would suggest that you either set trace on, (or if V3.0, turn on
> debug), and check where, exactly, during the field validation, this
> error message is returned.
Just opening UAF form by entering UAF on any menu form causes
the same error. So Gold % shows me no significant messages.
Being a CSC Support, I myself have source lists. I could find
there is a single line to return OA$_NOADMPRIV which is in OARMS,
and the only possible cause is the user creating user has OA$N
on PROFIL.AD$MIN[OA$USER]. I am puzzled...
Regards, Yukiji
|
| Hi Yukiji,
Yes - you're right - the only source of OA$_NOADMPRIV is from OARMS
(and this remains the same on V3.0; I don't have a V2.4 system).
So, I'm puzzled. It would indeed seem that the .admin field contents
are not 'Y'. Could there be some internationalization problem, that
Profile field values are being stored as something else? What does:
<get profil.ad$min:u[oa$user] - the untranslated value, give you?
You could also check the state of the profil.dat data file - has it
been converted lately? is the right one being referenced....?
Cheers
DaveT
|