Knowledge Management

Question:
We have found a rather unusual problem with the SAPGui version 6.2 (patch 56 and prior) and rendering headers when Windows XP SP2 is installed.
For instance we have been receiving “page cannot be displayed” or a simple blank white window in the onscreen report presented by KOB1. Normally a fairly simple header should be displayed in this frame, it is actually some HTML text sent by SAP to that window.
The strange thing is that this is dependent on how SAP is launched; if SAP is started with either SAPLGPAD.EXE or SAPGUI.EXE (with suitable arguments) the problem persists. However if you start the SAPGui with SAPLOGON.EXE you don’t get the problem – this is all on the same system, same saplogon.ini file, same server, same user ID, same report and data, etc. Not even a restart – to test this all you need to do is close the logon pad and any sessions and start up again and presto, you’ve replicated the problem.
We’re reluctant to roll out SAPLOGON.EXE to all users however this appears to be the only solution that has been workable; application of seemingly related notes such as OSS 829984 have had no effect on this process.
I’m wondering if anyone has seen this before and if so why the GUI would behave differently when SAPLOGON.EXE were the launching program; has anyone else seen this happen at all?
Thanks
DT
Answer:
I have managed to resolve this issue and am posting the resolution below in case someone else runs into the problem after rolling out XP Service Pack 2.
The problem is caused by the restriction of “MK Protocol” which has been somewhat more restricted in XP SP2. SAP seem to be aware of this and have added a specific registry key to preclude the SAP Gui from using it when it is launched via SAPLOGON.EXE. It appears however that they have neglected to preclude SAPLGPAD.EXE and SAPGUI.EXE (and any other programs that are used to start the SAPGui).
The result is that you can receive “page not displayed” in some screens including some areas of SAP Mail and transactions such as KOB1 (it appears that some frames are rendered in HTML) but only when SAP is launched with something other than SAPLOGON.EXE.
Solution:
To fix this problem the exemptions for SAPGUI.EXE and SAPLGPAD.EXE need to be added to the “FEATURE_DISABLE_MK_PROTOCOL” key in IE’s registry structure.
1. Start Registry Editor (Start -> Run -> regedit.exe)
2. Select the following key in the Windows registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_DISABLE_MK_PROTOCOL]
Select "New" -> "DWORD Value"
Value Name: saplgpad.exe, Value: 0x00000000
Also:
Select "New" -> "DWORD Value"
Value Name: sapgui.exe, Value: 0x00000000
If there are other programs being used to launch the SAPGui then these should also be added; this will stop the SAPGui using “MK Protocol” when it is launched via these programs.
Answer:
We had the same problem. It was resolved with SAP Note 738927 - HTMLViewer: moniker protocol is disabled in WinXP SP2