errno=FSL-01027 Account uid="S-1-5-32-544" does not exist

[Former Member]

I get with SWPM SP 19 follow error by copy the SAp Sytem, Netweaver 7.0 EHP 3:

Account uid="S-1-5-32-544" does not exist.
Failed action: with parameters
Error number 207 error type SPECIFIC_CODE

Log Attached.

Can you help me? Thanks.

sapinst-dev.txt

[Matt_Fraser]

Hi Eugen,

As this question mostly relates to system copies and installations, and the SWPM tool, I have moved it to the "Software Logistics" tag, and added a couple secondary tags. Choosing the best tag is important when posting questions to ensure it gets in front of the right people, though you have some of the best experts already helping you here.

Also, please be sure to search thoroughly before posting, as oftentimes you'll find that others have had the same problem and it has been answered.

Cheers,
Matt

[Matt_Fraser]

I have found a workaround for this bug. While the documentation clearly states, and while it has always been the case in the past, that it is sufficient for the installation user to be an indirect member of the local Administrators group -- i.e., your domain user could be a member of a domain/global group that in turn is a member of local Administrators -- this is what is failing. The workaround is to add your user account (installation user) directly to the local Administrators group, logout and login again, then re-run SWPM (you can 'continue' with your previous option if you don't wish to change any installation parameters). After this, the installation proceeds normally.

It's still a bug, and this is a workaround. You shouldn't have to do this.

I have submitted this information in the feedback comments upon conclusion of the SWPM process. It has been my experience that the Software Logistics group does indeed read that feedback and take it seriously. If you try this workaround and it works for you (after you get the error the first time), I encourage you to share that same feedback at the end of the tool, and to save your installation log (sapinst_dev.log) in case the engineers at SAP get back to you and would like to look at it.

Cheers,
Matt

[Former Member]

Unfortunately, that workaround doesn't work for me. My installation user was a member of the local administrators group all the time 😞

[JPReyes]

Hi Eugen,

There is a few discussion related to this error, most of them point to the installation been done under the wrong user.

Read the installation guide for Windows, and make sure you run the install under the right user, additional to that make sure all necesary users exist.

Regards, JP

[volker_borowski2]

Got my problem solved through a ticket meanwhile.

Seems that sapinst ist doing permissions differently when selecting the export for a systemcopy.

I needed to add permissions manually to my Export-User as SAPINST did not do so by itself.

It was well described in note

2445952 - Correct user account authorization to run SWPM / 70SWPM on Microsoft Windows

and after my ticket, note

2415352 - "Account uid="S-1-5-32-544" does not exist" error in sapinst_dev.log

was updated with a reference to 2445952.

The very same SAPINST was able to install a new system from scratch. The problem was only with the Exportfunction for a system copy.

Hop this might help others as well

Volker

[sunil_bangera2]

Hi,

Login to OS and launch Command prompt with Elevated privileges .Then start the regedit and search for the S-1-5-32-544 or sometime some other number like S-1-5-21-4127812034-820336945-2256232113-1336068 . Delete all the entries and click retry . If it doesn't work then search again for the entry and then reboot the OS and then rerun the SWPM tool with continue with old option. That how i troubleshooted error in my System copy during Import.

Regards,

Sunil Bangera

[former_member284974]

Hello All,

This is just a bug, Stop the SWPM and start again with option "continue with old".

Regards,

Shantanu Sathe

[former_member234424]

Hello,

I was having this same symptom when trying to use the sapinst, But by analyzing logs from other successful installations, I found that the ""Account uid="S-1-5-32-544" does not exist / 207 error type SPECIFIC_CODE" message occurs in all.

I discovered that the cause of the problem was another "Verification of DU manifest at 'Z:\SWPM\SIGNATURE.SMF' failed."

This problem occurs because I am using an old version of sapcar.exe to unpack the swpm.sar package.

After I use a newer version of sapcar.exe, the problem did not occur any more.

See the sap note "2444340 - SWPM failed: Verification of DU manifest at '<Path of SWPM>\SIGNATURE.SMF' failed."

Regards,

Carlos A. Hoepers

[former_member506733]

Hi Carlos,

which versions of SWPM and Sapcar.exe are u using? I am facing the same issue whith SAPCAR_816-80000938.exe and SWPM10SP19_7-20009707. I even tried a newer sapinst version 749.0.2.0. Any help would be nice.

Regards, David

[angus_macaulay]

Excellent! Carlos, many thanks for this tip, it was driving me crazy, and I was on the point of logging a case with SAP, but this solved it for me. David, I used the SAPCAR.exe from latest "SAP Kernel 7.45 Windows Server on x64 64bit" if that is any help to you.

[Former Member]

Hello

we had the same issue with SWPM 19_4. We stopped the SWPM and added the installationuser (domain\xyz) directly to the local "Administrators" group. Afterwards we restart the server and start SWPM again, with "Continue" options. Please check if the SAP system is running, when you continue.

regards

Lukas

[former_member246338]

Hello All,

I am also stuck with the same error "Account uid="S-1-5-32-544" does not exist. Failed action: with parameters Error number 207 error type SPECIFIC_CODE"

Any solution till date...

Regards

Shubham Mittal

[junichiro_tanno]

Hello, I faced same error while install Solman7.2 using SWPM10SP19_5.

I found the solution. OS user "SIDadm" removes from group "Users" and retry it.

Thanks for all.

[former_member266362]

Hi,

I had the same Issue in SWPM while performing a HANA System Copy (Target System).
I was able to finish the Copy while using "Distributed System" and installing each Instance separately:

Hope this will also work for you until SAP fix the Issue in SWPM.

Regards,

Matthias

[Matt_Fraser]

I have to concur with the others. I believe there is a bug in SWPM sp19 pl4 (Windows 2012 R2), and from the conversation here it appears this bug has existed for a while in earlier patch levels as well. I have just encountered this same error myself when attempting a system copy, on the target system installation side. My installation user is a member of the local Administrators group, and the domain users and groups for the installation (sidadm, SAPService_SID, etc) already exist in the domain -- a method for installation we have used dozens upon dozens of times in the past that allows us to not have to give Domain Admin rights just to install software (because believe me, they aren't going to give that to me, and I'm not letting them install the software).

I'm going to check/try a few more things, then I'll submit a Customer Incident about it.

[Former Member]

I also tried it with SWPM versions that definetely worked before. So perhaps it's an issue, that came with Windows Updates?

[Matt_Fraser]

Certainly a possibility. Unfortunately, not something I can reasonably test anymore (all my servers are at the same Windows Update level), but perhaps the folks at SAP can confirm this.

[NowakMatt]

Hello Matt,

have you figured out what is the problem or have you received response back from SAP?

Following by your other answer I have created another local admin user, I disabled firewall and still getting the same error. Please let me know, if you have any update in this case.

Thanks in advance Matt!

[Matt_Fraser]

Hi Mateusz,

Adding myself (i.e., installation user) directly to local Administrators on the server did the trick for me, although Fabian reports that this workaround did not work for him. Because I do not have the issue any longer, I did not submit a Customer Incident to SAP, though I did send them feedback through several channels about it.

We have recently had other weird things happening on our workstations, unrelated to SAP, in which the same workaround resolved the problem -- adding one's own user directly to local Administrators, rather than relying on indirect membership via an AD group. This leads me to concur with Fabian's idea that it may be related to a recent Windows Update.

[Sriram2009]

Hi All.

In SWPM SP19 having some bug. better you can raise the SAP support ticket to fix the issues. or use the SWPM SP18 for this you may request to SAP by rasieing the support ticket.

BR

SS

[volker_borowski2]

Same Problem with SWPM 19 SP 3 on Windows when trying to export an existing SAP System for a system Copy.

Server belongs to a Domain, but SAP Installation is local.
Created new local User SAPMIG according to new SWPM Guide as a member of local Administrators group.

sapinst_dev shows it processes S-1-5-32-544 earlier, but fails to verify existence later

:

TRACE 2017-03-28 14:46:14.789 (MYSERVER\sapmig) [D:/depot/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/syslib/account/syxxccache.cpp:417] CSyAccountCache::addToCache(PSyAccountImpl account)
inserted account (Administrators, S-1-5-32-544, GROUP) into the accountcache.

TRACE 2017-03-28 14:46:14.789 (MYSERVER\sapmig) [D:/depot/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/syslib/account/syxxcnodac.cpp:136] CSyACLImpl::editRight()
Editing rights (rwx): (S-1-5-32-544, GROUP, =rwx)

:

: but then

:

INFO[E] 2017-03-28 14:46:14.789 (MYSERVER\sapmig) [D:/depot/bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/syslib/account/synxcuser.cpp:143] id=syslib.account.isExistingOnOsSucceededFalse errno=FSL-01027 CSyUserImpl::CSyUserImpl(PSyUserData, bool)
Account uid="S-1-5-32-544" does not exist.

:

Looks like a bug in SWPM to me.

Volker

[Former Member]

The export worked as usual for us. We only get these errors during the import.
It looks like a bug to me, too. But why it also doesn't work with older versions, that worked before?

[Former Member]

I even tried SWPM SP17_4 with no success. I have no clue, what's the problem here. I have done the exact same thing a hundred times before and never had an issue. Perhaps the reason is a Windows Update?

[Former Member]

An yes, I even tried it on a second Win 2012 R2 machine, with the same result 😞

[NowakMatt]

Hi Fabian,

did you solve your problem? I have already tried all solutions mentioned previously, but unfortunately without any positive effect.

[Former Member]

No. I hope, SAP is working on a solution, as they were on our system already and analyzed it. I'm not sure if they already know, that there are more clients with the same problem. So perhaps you can open an incident, too.

[Former Member]

Thank you, Gowtam. Unfortunately it didn't work.
With SP19_4 it's exactly the same issue as with 19_3: I got the error right after the selection of the Kernel files. SP18_4 goes a few screens further, but ends with the same errors... 😞

[Former Member]

Hi,

We had the same issue when using 70SWPM10SP19_1 but after using 70SWPM10SP19_4, able to move forward. If you are already using SP19_4 then try with SP18_4 - these two versions worked for us. Hope it helps.

Thanks

[Former Member]

Hi Eugen,

I have the exact same problem. Did you find a solution?

Best regards

Fabian

[awahabma]

Hello can any one help me my ides ecc 6 ehp 7 installation stops at import abap with a similar error. Below is the install log

sapinstalllog.txt

I am using administrator user to install.

I am installing on Windows 2012 R2 - MSSQL version.

Thanks in advance.

[hendrikweise]

Hello,

the error is different, please create a new thread and supply the import logs, e.g

'SAPAPPL0_14.LOG', & 'SAPSSRC_2.LOG'.

Hendrik

[awahabma]

I created a new thread which was deleted by the moderator matt.fraser, I was refered here, saying that it is being discussed here so no need of new thread. This is the only log I got which attached., I could not find the other logs.

[former_member548287]

Hi

Kindly refer the SAP note - 1704753 - Inst.Systems Based on NetWeaver on UNIX with reference "error number 207 error type SPECIFIC_CODE"

BR

SS

[sidhi_rj]

Hello Sri,

We are not using UNIX OS, We are using with Windows 2012 R2.

Regards,

Sidhi Rj

[sidhi_rj]

Hello All,

We have maintained the Administrators group on the required user where we are installing and still we are facing the same issue.

Can you please suggest how to solve this error?

errno=FF-0001.

This was the error number in the logs but with SUID doesn't exist.

Regards,

Sidhi Rj

[hendrikweise]

Can you upload or paste the relevant passage in the sapinst_dev.log, please?

Regards,

Hendrik

[Former Member]

Thank you very much. We will check it!

[hendrikweise]

I can only support Juan's answer.

S-1-5-32-544 is the identifier of group "Administrators". During the execution the installer was not able find/reach this identifier and fails.

If it is a "Domain" installation, ensure the account running the installer belongs to group "Domain Administrators".

If it is a "Local" installation, ensure the account running the installer belongs to group "Administrators".

For more details, refer to the installation guide at section "Required User Authorization for Running the Installer".

Best regards,

Hendrik

[Matt_Fraser]

Hi Hendrik,

I believe this is actually a bug in recent patch levels of SWPM. I just encountered this myself (added my 2 cents as an 'answer' at the end of this discussion thread). I'm preparing to submit a Customer Incident, as it doesn't look like any newer patch level is available than what I tried (sp19 pl4 for Windows x64).

Cheers,
Matt

[Matt_Fraser]

Hendrik,

I found a workaround for the bug -- see my answer at the end of this thread -- and submitted details in the SWPM tool feedback. Basically it does not work for the installation user to be an indirect member of local Administrators; the user must be directly assigned to this group. This has not been the case in the past, and does not match the documentation, so I still maintain it's a bug.

Cheers,
Matt

[Matt_Fraser]

FYI, this also means that Notes 2415352 and 2445952 may need to be updated once the bug is corrected to indicate a certain SWPM patch level is required.