on 03-02-2013 3:29 PM
OSS Note Note 162266 - Questions and tips for R3SETUP on Windows NT / W2K
also talks about the same error and probable solution.
Termination due to authorizations
Message:
1314 A required privilege is not held by the client.
Cause:
R3Setup must change the user context during the installation. For this, a special authorization is required for the machine on which the installation is executed. The installation user receives this authorization during the CDINST step, that means, while the files are being copied from the CD to the installation directory.
The error message mentioned above usually occurs if the actual installation is not executed by the user who started the CDINST step.
Solution:
To avoid the problem, you should delete the installation directory and the directory temp\R3Setup and restart the installation from the CD. Ensure that you have local and domain administration authorizations and that you log off after the CDINST step and log on again as the SAME user.
Alternatively, you can also manually assign the required authorizations to the installation user. Proceed as follows:
You can also check oss note Note 79767 - Inst. terminates in password assignment for sapr3
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please check oss note 731977
Symptom
Error 1314 - A required privilege is not held by the client
Solution
During Installation should you experience following error please
ensure to check the following:
Error 1314 - A required privilege is not held by the client
Can you make sure that the user you are using to install the portal acts
as part of the operating system rights. If not, you will have to grant these rights and then log off and log on again.
Then retry the install.
If this doesn't work please try to Set the following user rights to the Administrators group.
This can be assigned by opening the Administration Tools -> Local Security Settings and then adding the admin group/user
to the below rights:
1) Act as part of the operating system
2) Increase quotas
3) Replace a process-level token
Also I have seen the above error in the following scenario:
The problem can be something to do with the fact that you are installing
EP6 on the same server as a W2K Domain. This appears to cause
the task to run under different user priviliges to the local
administrator. A way around this is to borrowing a second machine
connect ing onto the same Domain, and installing EP6 on that second
machine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
The problem is at the CreateProcessAsUser step.
Suggest yo to disable the UAC and Password policies on the server and restart the installation.
Cheers
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abu,
Can you please attach the sapinst_dev.log for further analysis ?
You can see it in your C:\program files /sapinst_instdir/NW701/AS-ABAP/ADA/central
Thanks and Regards,
Vimal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abu,
The
Note 731977 - Message 1314 seems to be of more specific to your issue.
Please try to execute the points 1 to 3 and see whether it helps.
Thanks and Regards,
Vimal
I checked the Note 731977 - Message 1314
Which user sets up the portal?
All the policies were correct, ie Act as operating system, Replace a process-level token, I didnt increase quotas.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
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.