sap windows gui issue

[junwu]

Hi,

I have some problem with the sap windows gui.

it's my personal computer, which hasn't been used for one year.

it was working, recently i try to open sap gui from that computer to connect to sap system, it just quit...

i have reinstalled and patched to latest, it still doesn't work

if i try to connect to an inaccessible server, it shows the standard connecting screen and error message, which is fine.

if i try to connect to an accessible server, the whole gui just disappeared immediately when i click the entry to connect. where can i find the error log for this? how can i troubleshoot this? i also checked the windows event, nothing there.

can someone throw me some lights?

Best regards,

Jun

[robert_wiegand · Accepted solution]

Hello Jun,

We had this exact problem. Ultimately, it wasn't an SAP GUI issue. The problem was just visible in the SAP GUI when selecting a system from the logon pad. The GUI would crash. No errors and the installation check would finish with no errors.

The problem was related to an old piece of software being removed as part an installation for new software. The software in question was unrelated to SAP. The software was: Business Call Center_User Interface 32.015, which is probably not the case for you, but probably some piece of software was removed.

The removal of this software removed some Windows 7 DLLs which SAP needed to function. I don't know the file names of these DLL file as my software techs found them and resolved the issue. They had to compare DLLs from a good PC with the broken PC and found the missing ones. Appearently, the SAP GUI will look for the missing DLL and if doesn't find it, it trys a different one, that causes this problem.

Reinstallation of the SAP GUI did not fix the issue. My techs created a workaround to put the missing DLLs back and re-register them.

I hope this helps. This took a few weeks to figure out for us.

[junwu · Accepted solution]

Hi Robert,

Thanks for the update.

I just reinstalled the OS.

Best regards,

Jun

[robert_wiegand · Accepted solution]

Update:

I spoke to our tech and found out that the DLLs where not removed. It was the pointers to the DLLs in registry that where removed.

Below is example of the REG fix they implemented by putting back these keys. Unfortunately there are alot more keys than are shown below. Plus the keys may be different depending on the application. Although, most of the keys in questions were related to OLEDB.

[HKEY_CLASSES_ROOT\CLSID\{039EA4C0-E696-11d0-878A-00A0C91EC756}]

[HKEY_CLASSES_ROOT\CLSID\{039EA4C0-E696-11d0-878A-00A0C91EC756}\InprocServer32]
@=hex(2):43,00,3a,00,5c,00,57,00,49,00,4e,00,44,00,4f,00,57,00,53,00,5c,00,73,\
00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,73,00,6a,00,74,00,\
65,00,73,00,34,00,30,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Both"

[HKEY_CLASSES_ROOT\CLSID\{039EA4C0-E696-11d0-878A-00A0C91EC756}\TypeLib]
@="{2358C810-62BA-11d1-B3DB-00600832C573}"

[HKEY_CLASSES_ROOT\CLSID\{06210E88-01F5-11D1-B512-0080C781C384}]
@="PSFactoryBuffer"

[HKEY_CLASSES_ROOT\CLSID\{06210E88-01F5-11D1-B512-0080C781C384}\InProcServer32]
@=hex(2):25,00,43,00,6f,00,6d,00,6d,00,6f,00,6e,00,50,00,72,00,6f,00,67,00,72,\
00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,53,00,79,00,73,00,\
74,00,65,00,6d,00,5c,00,4f,00,6c,00,65,00,20,00,44,00,42,00,5c,00,6d,00,73,\
00,64,00,61,00,70,00,73,00,2e,00,64,00,6c,00,6c,00,00,00
"ThreadingModel"="Both"

Like you said Jun, it's just easier in some cases to re-install the OS. Do not apply these keys to your registry, because this is a sub-set of the keys. This is just an example of what we needed to do to resolve our issue. Anyone running into this issue will need to determine what the correct keys are. You could use a tool like RegShot to compare reg versions if you know the offending application that is stripped the reg keys. Knowing the app is half the battle.

rbw