on 09-19-2011 5:44 PM
Hello,
I´m doing an installation of SAP ERP EHP5 in IBM iSeries but at the beginning of it the SAPInst stops with an error during the phase 4 of 27 - Install common system files
When I checked the last lines of some log files I see the following lines:
sapinst.log:
...
INFO 2011-09-19 16:01:17.12
Account 105 already exists.
INFO 2011-09-19 16:01:17.13
Account r3group already exists.
INFO 2011-09-19 16:01:17.15
Account r3group already exists.
INFO 2011-09-19 16:01:17.23
Account r3group already exists.
ERROR 2011-09-19 16:01:17.159
MOS-02001 Call of command "CRTSAPUSR USER(*SAPADM) UID(105)" failed. Exception is "255".
ERROR 2011-09-19 16:01:17.161
MOS-02001 Call of command "CRTSAPUSR USER(*SAPADM) UID(105)" failed. Exception is "255".
ERROR 2011-09-19 16:01:17.757
FCO-00011 The step createAccounts with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_System|ind|ind|ind|ind|6|0|NW_SAPHostAgent|ind|ind|ind|ind|0|0|createAccounts was executed with status ERROR ( Last error reported by the step :Call of command "CRTSAPUSR USER(*SAPADM) UID(105)" failed. Exception is "255".).
INFO 2011-09-19 16:01:18.318
Creating file /tmp/sapinst_instdir/ERPEhP5/AS-ABAP/DB4/CENTRAL/__instana_tmp.xml.
sapinst_dev.log:
...
TRACE 2011-09-19 16:01:18.846 [syuxctask.cpp:560]
CUnixProcessManager::waitpid(pid_t pid, int * pStatus, int options)
lib=syslib module=syslib
Child process 1024 returned 0
TRACE 2011-09-19 16:01:19.642
SAPInst calls the LogInquirer. The output of the LogInquirer can be found in file sapinst_loginquirer.log.
TRACE 2011-09-19 16:01:19.855 [iaxxgenimp.cpp:707]
CGuiEngineImp::showMessageBox
sapinst_loginquirer.log:
TRACE 2011-09-19 16:01:19.666
SAPInst calls the LogInquirer because of an error in execution of step |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_System|ind|ind|ind|ind|6|0|NW_SAPHostAgent|ind|ind|ind|ind|0|0|createAccounts.
TRACE 2011-09-19 16:01:19.715
Call block:CallBackInCaseOfAnErrorDuringStepExecution
function:CallTheLogInquirer
is validator: true
WARNING 2011-09-19 16:01:19.719 [iaxxejshlp.cpp:150]
Could not get property IDs of the JavaScript object.
ERROR 2011-09-19 16:01:19.720 [iaxxejsctl.cpp:492]
FJS-00010 Could not get value for property .
TRACE 2011-09-19 16:01:19.854
A problem occurs during execution the inquirer callback. SAPinst will switch back to the standard behaiviour.
Can you help me please how can I solve this problem during this installation?
Thank you,
Joao Dimas
Hi João,
Currently we have no solution for your problem. We assume that maybe your installation user does not fit. Our suggestion is to check the installation documentation how to create the installation user for sapinst.
The installation user should be able to call CRTSAPUSER USER(*GROUP) GID(102) succesfully.
If this works please use this user to continue your installation.
If it does not work please open a customer message, so that we can take a look at your system.
Kind Regards
Joachim
member of the SAP on i team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi João,
ok,so, you do have a different issue than the expected too many special authorities ...
Are you sure, that the SAPINST user has authorization to R3group ? Has it *ALLOBJ and *SECADM ?
Is the problem reproducible with QSECOFR and then running the command manually ?
Volker Gueldenpfennig, consolut international ag
http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de
Hi João,
The joblog entry
'Too many elements in list for parameter SPCAUT.'
on a call of CRTSAPUSR has the reason, that the user profile of the CRTSAPUSR call already has to many special authorities set.
Please verify the SPCAUT entries for the user profiles R3OWNER, R3GROUP and SAPADM.
You can do this by calling DSPUSRPRF for every of the three profiles.
Press page down until you see the list of 'Special authority' (contains entries *SAVSYS or *JOBCTL).
If the list of any of the three users already contains 7 or 8 entries you will get the error.
SAP itself creates user profiles only with the special authorities *SAVSYS and *JOBCTL. Any additional entry will give the SAP system more rights against the OS than necessary (security leak). Especially rights like *AUDIT and *SECADM should not be set. Even the famous *ALLOBJ is just an easy way to make a system running, without finding the real error; it just masks a permission problem.
If you find such a long list you can remove some of the entries with CHGUSRPRF.
As I already mentioned only *SAVSYS and *JOBCTL are necessary. If you are nervous about hidden permission problems you can keep *ALLOBJ for now, but should try to find the problem to remove it as fast as possible. All other option can be removed.
After that you can repeat the CRTSAPUSR Call for SAPADM. It now should work, and your installation too.
Kind Regards
Joachim
member of the SAP on i team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Joachim Kern,
Thank you very much for your explanation!
What I done was, first I changed the special authorities for SAPADM and put *SAVSYS, *JOBCTL and *SECADM (I had to put the SECADM because if not it show me an error)... therefore this error was solved about the running of command CRTSAPUSR USER(SAPADM) UID(105)
But once again the sapinst stopped and now it shows another error very similar to the first error.
When I try to run manually the command:
CRTSAPUSR USER(*GROUP) GID(102) it show me the following error:
Not authorized to user profile R3GROUP.
I also changed the special authorities for R3GROUP; GROUP and R3OWNER to the value *SAVSYS, *JOBCTL but even so the error keeps!
Can you help me... how can I solve this error now...!?
Thank you
Joao Dimas
Hi
I have a similar issue, while doing a unicode upgrade (import phase) I get an error with CRTSAPUSR, it fails because the sapinst passes the GID parameter to CRTSAPUSR.
It looks like the version in library SAP_TOOLS will receive the parameter and note #1357153 may help.
I will be testing this fix later.
Thanks
Hello Matthew Milne and all others,
This problem is already solved... I will try to explain what were the main problems in my case!
The first error was the installation user, I didn´t create it well, like is mentioned in installation guide! I created a SAPADM user and I started the installation through it and so as you imagine some specific features/parameters for a SAP system installation were not defined, one of them was the special permissions of that user (SPCAUT).
So... in way to solve this problem, first I had to create the SAP installation user (SAPIUSR) like it described in installation guide in section "Preparing a Windows User Account and IBM i User Profile" with the following command:
CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(SECOFR) TEXT('Test User for SAP Installation') SPCAUT(USRCLS) LANGID(ENU) CNTRYID(US) CCSID(500)
After that, I check the sap installation user SAPIUSR if it has all specific authorities (SPCAUT):
*ALLOBJ
*AUDIT
*IOSYSCFG
*JOBCTL
*SAVSYS
*SECADM
*SERVICE
*SPLCTL
I had to also checked the user SAPADM. It should have only the spec. authorities:
*JOBCTL
*SAVSYS
I started again the SAPInst and the errors no longer appears!
Thank you,
João Dimas
Hi João,
did you try the failing command yourself and checked for the error ?
CRTSAPUSR USER(*SAPADM) UID(105)
... that should give us ideas on your issue ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi João,
I would at least search for the command ...
wrkobj *all/CRTSAPUSR
... then use the latest installation, that was created now ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de
OK Volker, I ran that command for search... and that show me the following output:
CRTSAPUSR *PGM SAPINST000 CLLE 06/27/10 20:23:33
CRTSAPUSR *CMD SAPINST000
CRTSAPUSR *PGM SAPINST001 CLLE 06/27/10 20:23:33
CRTSAPUSR *CMD SAPINST001
CRTSAPUSR *PGM SAPQASIND CLLE 08/31/10 19:27:33
CRTSAPUSR *CMD SAPQASIND
CRTSAPUSR *PGM SITMP CLLE 08/31/10 19:27:33
CRTSAPUSR *CMD SITMP
But how to check some detail information about this...!? I don´t get it...
Kind regards,
Joao Dimas
Hi João,
I would guess, that you are installing QAS right now - I would use:
addlible SAPQASIND
... and try the crtsapusr again ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de
Hi João,
ok,now, I can not help any more - it is consulting now.
I'm sorry,
Volker Gueldenpfennig, consolut international ag
http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de
Hi Volker,
I already did what you recommended, which was:
ADDLIBLE SAPQASIND
Next I run:
CRTSAPUSR USER(*SAPADM) UID(105)
waiting for reply to message on message queue SAPADM
I checked which message was waiting for a reply:
DSPMSG SAPADM
I replied Yes (Y) after I read the sap note 1045022 - Job hangs and job log states: CLASSICUSERCONCEPT not set
... and the output for the CRTSAPUSR was the following:
Too many elements in list for parameter SPCAUT.
Can you help... now!?
Best regards,
Joao Dimas
Hello,
I have more information about the error...
I did all I said in my previous message and so after that I find more details regarding that output message "Too many elements in list for parameter SPCAUT."
Message . . . . : Error found on CHGUSRPRF command.
Cause . . . . . : The system detected errors in the command.
Recovery . . . : See the previously listed messages in the job log. Correct
the errors and then try the command again. *N instead of a command name
means that the name had not been determined before the error was found.
How can I see the job log of this error, and more information about the error?!
Kind regards,
João Dimas
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.