SAP Gui 8.00 crashed after update to patch 1

[michael_vk]

Dear colleagues,

I've an issue with SAP Gui 8.00, after update to patch 1, Gui not started. In Windows logs, I've seen below info:

Faulting application name: saplogon.exe, version: 8000.1.1.1161, time stamp: 0x6424c151

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x000001ea1b064d70

Faulting process id: 0x28e0

Faulting application start time: 0x01d965eea834a020

Faulting application path: C:\Program Files\SAP\FrontEnd\SAPGUI\saplogon.exe

Faulting module path: unknown

Report Id: ad3707df-f08c-4b2f-bf06-a66a5b9d97d7

Faulting package full name:

Faulting package-relative application ID:

[lucas_machado]

Hello Michael,

Could you check if this issue is reproducible without using any security software? For example Windows Defender...

In addition, this issue is workstation specific? Or occur in all workstations?

Best regards,

Lucas Machado

[TChrisS]

Hi,

I am seeing the same issue with both saplogon.exe and saplgpad.exe immediately upon execution.

Patch 1 is working fine on a Windows 10 virtual desktop and on a Windows Server 2019 server. But on another Windows Server 2019 server, I'm getting the 0xc0000005 exception. If I uninstall SAP GUI 8.00 and reinstall the initial version, it works fine. But, reinstalling patch 1 breaks it again. If I copy folder SAPGUI64 from 50160634_2\SAP_GUI_for_Windows_8.00_Comp._1_\PRES1\GUI\Windows\Win64\ to the server and executed saplogon.exe from there it launches. This server will be part of a Citrix farm and is more locked down than my virtual desktop or the server where patch 1 is working. I'm guessing that changes in patch 1 are trying to access something on the server that isn't being allowed. But, that is just a guess.

Thanks,

Chris

[steve_m_taylor · Accepted solution]

We had the same issue and SAP came back with the following solution which you may like to try.

Please could you check the following Registry Key whether the crash is solved or not: - Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SAP\SAPGUI Front\SAPFrontendServer\Security

"UseComHjkngWA" = "0" (DWORD 32-bit)

After adding this key, the problem was solved for us.

Steve

[michael_vk · Accepted solution]

Hi Steve,

I've installed patch, added new Registry Key and ... SAPGui started!

Thank you for the solution.

Michael.

[michael_vk]

Hi Lucas.

Thank you for your response.

This issue occurs on my workstation with Windows 10. On another (virtual desktop) this problem didn't occur. Both workstations have security software. The situation is similar to the one described by Chris.

Michael.

[manuf]

Patch level 2 was released and solved this issue. More info also here

https://blogs.sap.com/2023/01/20/sap-gui-for-windows-8.00-is-coming-on-27th-of-january-2023-new-feat...

[henning1]

Hi,

see also note 3320385. “SAP is currently working on a solution to this issue with highest priority."

https://launchpad.support.sap.com/#/notes/3320385

Best regards,

Henning

[TChrisS]

Hi,

I have 64-bit SAP GUI installed on the server where I was having the issue. Creating the DWORD at the following location solved the issue for me.

HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAPGUI Front\SAP Frontend Server\Security

Thanks for the solution.

Chris