SAP Gui 7.10 Patch 17 on Windows 7 - SE80 freeze

[andreas_jung2]

Hi,

we have a problem with Windows 7 Prof. and the SAP Gui.

We will be upgrading from WinXP SP2 to Win7, now we have a couple of Test-Win7-PCs to play with and we can't get SAP Gui to run on all of them.

We tried the new 7.20, on some PCs it works just fine, on others it displays black-windows only ... so we switched to the SAP Gui 7.10 Patchlevel 17, which is suppose to be more "bug-fixed", now we have another problem:

The Object-Navigator (SE80) freezes when trying to start it with the new frontend-editor. The old editor and the backend-editor work just fine.

Funnily enough, not all PCs have that problem, some of them work right away, same standard-installation on all of them.

One (maybe) important fact: There is no problem running SE80 with the Admin-User that actually installed the GUI.

Here's the ouput of the trace-file, that is created when the SE80 freezes:

(Error)(26.04.10 11:37:16.895):    CALL METHOD "CreateControl"[DispID=5] OF [#21/0x049F2B18/101/{83658045-6571-3232-7082-797884697868}]
                    #0: LONG "165"
                    #1: STRING "SAPGUI.AbapEditor.1"
                    #2: LONG "1409286144"
                    #3: LONG "164"
IDispatch::Invoke raised exception

We first installed the "SAP Frontend Package 7.10 Compilation 1", which contains SAP Gui Patchlevel 0 and then upgraded to Patchlevel 17. We also tried to upgrade to 14 first and then to 17 - unfortunately the same problem.

Any ideas or suggestions or anything that might help would be highly appreciated.

Thanks

AJ

[Former Member · Accepted solution]

Hey AJ,

I'm not sure if you have already tried the items below but I hope these help:

a. Compare hardware with the workstations that are working with workstations that are not

b. Network analysis (Network Administrator's expertise)

c. Imaged the working workstation to a non-working workstation

d. Install Windows 7 from scratch without upgrading (MSFT upgrades don't always behave the same)

e. System Dumps Analysis (t.code - ST22)

f. Activate trace on working workstation and non- working workstation (t.code - ST05)

g. System process (t.codes - SM50 \ SM51)

Please update this string if any of my options workout for you or not.

Good Luck!

-Bob

[Former Member]

Hi,

Use SAPGUI 7.20 for Windows which is officially support for Windows 7

ardhian

http://sapbasis.wordpress.com

http://inaroka.co.cc

[andreas_jung2]

Thanks Jiri and Ardhian for replying.

We did test 7.20 but it was quite buggy, just like previous SAP GUIs with Patchlevel 0 so I rather go for a well-patched version (in this case 7.10) and according to its documentation, 7.10 Patchlevel 17 does officially support Windows 7.

AJ

[Former Member]

Hi Andreas,

please use SAP GUI 7.20, which is officially supported in Windows 7.

Regards Jiri

[andreas_jung2]

Hi Bob,

thanks for the reply.

a.) all test-PCs are 100% identical

b.) network was working fine

c.) it was (suppose to be) the same image.

d.) I'd love to but I can't - we depend on our provider

e.) no dumps - it's "just" a frontend-thing so nothing happens on the application server

f.) see e.

g.) see e.

We got a new set of PCs with the same standardinstallation and for some reason it works now ... I have no idea what the problem was.

AJ