Issues updating SAP GUI 7.50 to PL 8

[former_member383109]

Hi

I'm trying to update SAP GUI 7.50 PL 5 clients to PL 8 using the SAP Installation Server, which is version 9.0.97.0.

The clients are prompted with a pop-up and asked if they want to update SAP, but some of them are failing.

The ones that do fail are asked again if they want to update. If they keep clicking Yes then eventually the update installs.

If I check the log files, I can see the following error when the failure occurs:

NwAWUServc 1E Update service failed in launching SAPSetup: Error starting process <"\\server\SAP GUI Installation Server\Setup\NwSapSetup.exe" /silent /package /update> Error message: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. Error code 0x000036b1 (14001).

It's strange that eventually the update installs if they keep clicking Yes on the prompts; normally if there's an issue then it flat out will not work e.g. a required component missing from the system.

Any advice is appreciated.

Regards

James

[david_winter2]

With some help from SAP support we traced my issue to the server share - deduplication on the server volume/drive was the cause. We were using server 2012 built in duplication settings. I set up an exclusions for the Installation server folder and it worked.

[david_winter2]

Hi Jan,

Did you install the vc9_redist_x86 on the server or client PC? I've installed on the client but I still get the issue on 1809. I've been installing C++ libs but still cant get nwsapsetup to work, this really hinders updates on workstations as user are prompted to update but it fails and users give up after one or two attempts but it works after 4 or more.

David

[jsamul]

Hi,

Yes, I am still getting the error on 1809 even with the runtimes provided with the SAP GUI, not sure what is wrong.

The error in NwSapAutoWorkstationUpdateService.log says:

NwSapSetup.exe /silent /package /update> Error message: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. Error code 0x000036b1 (14001).

[jude_bradley]

If you are running NWSapSetup according to the guide, this would be done via a Windows server, so the case of running via Linux would not arise.

The best advise is to follow the installation guide and follow the "create installation server" scenario.

[jsamul]

Hi,

It seems the issue is indeed caused by the wrong configuration of shared folder with SAP GUI setup files.

Sadly the mandatory settings are mentioned only the part "Installing and Configuring the Automatic Workstation Update Service" even those seems to apply to general use of the shared folder, not only the AWUS.

Windows server as operating system with the following local security policy:

• Accounts: Guest account status = Enabled
• Network access: Let ‘Everyone’ permissions apply to anonymous users = Enabled
• Share is NULL-session accessible

These settings could not be applied in general for all our shared folders for security reasons so we had to setup a separate Windows Server for just one shared folder with the SAP GUI setup files.

What a waste, but It seems to work so far, does not matter if the setup files are started manually or by AWUS, the side-by-side error seems to be gone.

[jsamul]

Hi,

there seems to be some VC runtimes distributed directly with the SAP GUI client under the System folder.
Those seems to solve the side-by-side error if installed prior to the NwSAPSetup.exe.
Not sure how those differ from the official runtimes from MS.

Thank you.

[jsamul]

Hi Jude,

the U drive is mapped network share on a file server.

Why do I have to install the vcruntimes on the file server to be able to run the exe files from the network share?

Seems odd to me. The execution of the files is done on local client computer even if the files are stored on the network share, or not?

What if the network share is on the linux server? I would not be able to install vcruntimes there.

The SxsTrace log file in the previous post is from the local client computer.

In the log file you can see that I had to run the NwSAPSetup.exe three times in the same command line session on the local client computer to make it run correctly.

First time the NwSapSetupEngine.DLL failed, second time it was OK and NwSapSetupATLCommon.DLL failed, and for the third time both these DLL files were OK and the NwSAPSetup.exe ran correctly.

Thank you

[jude_bradley]

I see from the trace it give the harddisk "U"

INFO: Did not find the assembly in WinSxS. INFO: Attempt to probe manifest at u:\SW_STORE\SAPGUI\SRVTEST\Setup\NwSapSetupEngine.DLL. INFO: Manifest found at u:\SW_STORE\SAPGUI\SRVTEST\Setup\NwSapSetupEngine.DLL.

What or where is this path? On your workstation, or a server?

If a remote server, are the files installed there too? Since SAPgui is a 32bit application, the 32bit versions of the redistributables must also be installed on wherever the "U" location is.

[jsamul]

I have similar issue when running NwSAPSetup.exe from the network share of SAPGUI 750 on Windows 10 1809 with installed VC++ Runtimes:

I have to run the NwSAPSetup.exe serveral times to pass the Side-by-Side configuration error.

This is the SxsTrace log file in which you can see the DLL files cause the errors: sapgui750.txt

Not sure how to get rid of this error.

Any help would be appreciated.

Thx.

[david_winter2]

Thanks James, I actually get the error when running nwsapsetup /package etc during installation as well as workstation update service- as you mention it take 3 to 5 attempts and then works, this is on Windows 10 1709 and 1803 builds. I'll try some trace logs and open a ticket with SAP.

[former_member383109]

Hi David

I didn't get to the bottom of it so I'm not using the automatic update system anymore. I've built a package/exe file, hosted it on a file share, and run a logon script to deploy it. Works much better.

[jude_bradley]

Are these files installed on the client

http://www.microsoft.com/en-us/download/details.aspx?id=26368

[former_member383109]

Hi Jude

Thanks for your reply.

All the clients are Windows 10, so I don't think this is the issue.

[david_winter2]

Hi James, did you resolve this in the end? I'm having the same issue.

[jude_bradley]

Please check note Installation problems with SapSetup Version 9.0

Attention: SAPSetup version 9.0.96.0 and higher reguires Universal C Runtime (UCRT), which is available with KB299922Download here: https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows

Windows 10 doesn't need this patch as UCRT is part of it.