Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SAP GUI 1

Status
Not open for further replies.
Jan 15, 2001
193
AU
I have posted this in the VB thread as well but...I have a test server that runs SAP GUI OK when I test a user from the console (in a seamless Window session) but the same user gets a "cannot reference OCX" error when they run it from a client machine in a seamless window.

The OCX is registered on the server, do I need to do this on the client too?
 
Stop looking all! Here's the beef FYI...MetaFrame 1.0 and subsequent releases are supported by SAP starting with SAPGui release 4.5b (SAP Note 138869). However, to ensure proper functionality MetaFrame 1.8 and Citrix ServicePack 2 is recommended. As WinFrame does not support Active-X controls, WinFrame is not supported.
It is recommended to have at least MetaFrame 1.8 and Citrix Service Pack 2 installed.
Run a client installation (ie NOT server install) and the installation it is recommended to have the SAP client patch #124 installed.

The "secret" trick is to add the following registry keys:
1. Create a key under
[HKLM]\SYSTEM\CurrentControlSet\Control\Citrix\Wfshell\TWI named anything (e.g. "SAPGUI"). The name doesn't matter because everything is enumerated.
2. Then create two values in this new key. Values:
"ClassName" = "SAP_FRONTEND_SESSION", REG_SZ
"Type" = 1, REG_DWORD.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top