cancel
Showing results for 
Search instead for 
Did you mean: 

Installation error on Windows 2008 R2 with SWPM 1.0 SP3

boobboo
Contributor
0 Kudos

Hi,


I am trying to perform a HANA distributed install on Windows 2008 R2

using the Software Provisioning Manager (SWPM10SP03_4-20009707.SAR).

Upon selecting the Business Suite on HANA, EhP2 for CRM system copy option, I

then enter the parameters for the ASCS instance part of the installation.

Once the installation starts it hits an error regarding adding groups

to other groups - this is not possible in a local installation on Windows

and the installation crashes. This is not the 1st time this has

happened to me, I have faced this issue before and the only resolution I have

found is to use an older SWPM - although this is not advisable in this

instance as the operation is for a system migration to HANA.

I have turned off the requirement for the password complexity through

the local security policy, I have restarted the SWPM several times from the

beginning and rebooted the server, nothing seems to work. Also the

fixes from SDN and other sources have not worked either. I have tried simple

passwords, deleting the groups and recreating them again but nothing

works.


I have attached the log files and below is the error.


Modifying the GROUP CGAWSSAP91\SAP_EC1_GlobalAdmin failed. SOLUTION:

Modify the account manually and choose OK to continue. If you choose

Cancel, the installation will be aborted. The detailed error message is

as follows:

modlib.jslib.caughtException:

Caught ::ESyException in module call: At line 1366 file

d:\depot\bas\720_rel\bc_720-

2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxc_adsi_account.cpp

Call stack:

d:\depot\bas\720_rel\bc_720-

2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\ejs\ejscontroller.cpp: 164:

EJS_ControllerImpl::executeScript()

d:\depot\bas\720_rel\bc_720-

2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\ejs\jsextension.hpp: 873:

CallFunctionBase::call()

d:\depot\bas\720_rel\bc_720-

2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\osmod\iaxxbaccount.cpp:

355:

CIaOsAccount::addMember_impl()

d:\depot\bas\720_rel\bc_720-

2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\syxxbgroup.cpp: 197:

*** syslib entry point CSyGroup::addMember(const PSyAccount &

(CGAWSSAP91\SAP_EC1_GlobalAdmin)) ***

d:\depot\bas\720_rel\bc_720-

2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxcgroup.cpp: 653:

void CSyGroupImpl::addMember(CSyAccountImpl * pAccount)

d:\depot\bas\720_rel\bc_720-

2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\syslib\synxc_adsi_account.cpp

: 1337: SyWindows::CSyADsGroup::addMember(const SyWindows::CSyADsPath &

WinNT://S-1-5-21-391787842-3485798936-93383475-1021)


Unable to add account

WinNT://S-1-5-21-391787842-3485798936-93383475-1021

to group WinNT://WORKGROUP/CGAWSSAP91/SAP_LocalAdmin. The group name

could not be found.

.

Thanks


Chris

Accepted Solutions (0)

Answers (2)

Answers (2)

Sriram2009
Active Contributor
0 Kudos

Hi

Kindly refer the SAP Note 929929 - Latest SAPinst Patch

Thanks

Ram


boobboo
Contributor
0 Kudos

Ram,

SAPInst has been superceded by the Software Provisioning Manager (SWPM), and also does not support installations for HANA - so this not does not apply

Chris

daniele_dutra
Explorer
0 Kudos

Hi Chris,

As per the sapinst logs, you are performing a Distributed System installation, and this requires a Doman installation type instead of local. This is mentioned in the Installation Guide chapter 3.4 - Domain or Local Installation:

You have to perform a domain installation if one of the following applies:

- You install a distributed system.

- You install a high-availability system with MSCS.

- You want to use Single Sign-On

- You use a common transport host for several SAP systems running on different computers.

Local installation is only possible for standard systems. I believe this is causing your current issue as SWPM expects this to be a domain install.

Best Regards,

Daniele

Former Member
0 Kudos

Hi Chris,

The issue is related to windows local policies.  Even though your user may have local administrative rights, you need to check your security settings.  Solution is in SAP Note 731977

I found by adding the local administrative group to these "User Rights Assignments" resolves the issue you are facing.

-Act as part of the operating system

-Replace a process-level token

Kindest regards,

James

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Please make sure of this restriction- SAP does not support to use local users to install an SAP system in a distributed environment.

For more information, please refer to SAP note 1282975.

Thanks

Sunny

boobboo
Contributor
0 Kudos

I am not sure this note applies for the following reasons

1. HANA does not install on Windows, only Linux - so the ability to perform a local ASCS install should be available as the servers do not share users

2. I am not using virtual hostnames in any way either

3. I have hit this issue when performing a Windows CE installation which was a DB/CI installation and did not require domain users

Thanks

Chris

Former Member
0 Kudos

Hi chris,

  Did you try to add the user manually and tried to continue with the installation?

I faced similar kind of issue few weeks before. I manually created the account with the needed privileges  and continued.

Thanks and Regards,

Vimal

boobboo
Contributor
0 Kudos

The problem is that the installation is trying to add a group to another group, which is not possible for local Windows security groups.

Chris

sunny_pahuja2
Active Contributor
0 Kudos

1. I do agree that HANA cannot be install on Window. But in distributed installed, you can install PAS/ASCS on window and HANA on Linux.

But initially, you wrote that you are trying to do system copy for EHP2 CRM.

Thanks

Sunny

boobboo
Contributor
0 Kudos

Sunny,

I did say it was a distributed install for HANA with Windows, as a Linux system is the only possible HANA database system, it was implied that the Windows was for the ASCS. Also statement about CRM EhP2 was describing the menu path I took from within the SWPM, which should indicate which particular way I was installing the system so there would be no confusion on my installation choice.

Thanks

Chris