SAP GUI Memory issues on Windows Terminal Server 2003!!

Hi All
We are currently experiencing serious issues with our terminal servers and SAP GUI. It appears that SAP GUI is consuming a large amount of memory inorder to run, which in term is causing our terminal servers to page more.
I am not sure where to start with this issue so any help would be great!
Thanks
Phil
Loads of points if someone helps me solve this!!!

Citrix won´t help much, it´s "just" a different protocol between the client and the server, Citrix itself will use even more memory.
Why are you sure, that the reason for this is the SAPGUI and not any other Office program?
Let´s calculate:
I´m writing this message on a TS too. My Outlook (2003) consumes ~ 32 MB memory (incl. virtual), I have 4 SAPGUI windows open which consume 64 MB and some telnet sessions (no Word, Excel etc.)
Let say roughly 128 MB all in all.
If you have 2000 users with 20 servers, means, 100 users on one server, that would be 12,8 GB memory - not caclulated other services running on that box (printserver etc.) including the operating system itself.
If your users have Internet Explorer (or other browsers) open too, you will need to add that amount too. 128 MB per user is the minimum.
If users use BEx (or other .NET based BI developer tools), that amount will doubled (at least).
SAP recommends a PC with at least 256 MB memory to run a SAPGUI with acceptable performance, do you have that much per users? How big are your single servers?
Markus

Similar Messages

Install SAP GUI 7.20 on Windows terminal server

Hi,
I would like to install SAP GUI 7.20 on a Windows Terminal Server and configure it so that all users on the terminal server share a common configuration. As the installation is now all users have to define the systems in GUI the first time they start it, but I would like to do this globally. Is this possible?
Best regards,
Thor-Egil

> estimated 20 or more users who will be using the WTS to do their specific transaction. How much ram do we need to put in the WTS to handle 20 or more users?
This depends on what the users will do on that system. I suggest you contact the hardware vendor for a sizing of the machine.
> and follow up question, do you recommend using terminal servers?
It's an easy way to centralize the administration, you have got only one SAPGui installation.
Markus

Tips to install Sap Gui On Windows Terminal Server 2003

Does anybody know any method to install SapGui on Windows Terminal Server 2003 to share it to many users ?
The problem is: when I try to install Sap Gui 6.40 via Control Panel-Add/Remove Programs it tells me that I must change the mode with "change user /install". I dont know the reason why it reports me that if I do it via Control Panel. And if I do that and then I launch the installation again it reports me the warning again.
What should I do ?
Thanks in advance for your help.

We have SAP R3 4.6C.
We want to optimize the bandwidth in a 802.11b radio. Because of that we dont want to run any application in the hand-held.
We'll intend to launch a remote desktop on a dozen hand-helds connecting the Windows 2003 Terminal Services server. In this server we could run SAP GUI, WebSapconsole or the browser.
Its important to note that the hand-held computers must only show the designed windows (sized to 16x20), removing title bars, transaction bar, menu bars, tool bars, status bars, etc. For this purpouse I think we can use WebSapconsole.
With this method we have noticed that when a error or warning is displayed it hides some part of the screen instead of presenting in the status bar.
I hope you all your doubts are clear now, if not just tell me.
Thank you.
PS. Sorry for my english.

SAP GUI Compatibility issue with Windows 2008R2 64 Bit

Hi Gurus
Is anyone experienced connectivity issue with SAP GUI (32bit) on Windows 2008R2 64bit? Except base version of 7.3 every Service Pack failing
to connect, Strange thing was it was working with SP5 in WINDOWS 7 64bit.
Your inputs greatly appreciated.
-giri

Hi Giri
Yes, You can do the normal installation on windows 2008 / 2008 R2 systems. we are using in our environment. is this any error message while installation or SAPGUI execution time?
Refer the SAP Note 66971 - Supported SAP GUI platforms
BR
SS

Windows terminal server 2003 cluster

We have a FOG with three Solaris 10 x86 servers, SRSS 4.2, SRWC 2.3 with the latest SRSS 4.2 patches. All Sunrays have the latest firmware.
Kiosk settings points to a windows 2003 terminal server cluster. The two nodes in the windows cluster have latest SRWC 2.0.
The cluster entitles, two terminal servers and a session manager server, we use roaming profiles.
When pointing kiosk settings to the cluster FQDN the sunray sessions are routed to just one server in the windows cluster. But if we RDP to Cluster's FQDN from a regular desktop the windows cluster load balances properly.
I do need help understanding how SRSS handles sessions? specifically if nodes are behind a cluster with session manager. Could it be that the session manager it's incompatible with SRSS in kiosk mode since it tries to route sessions at the mean time SRSS is doing the same task?
Thanks,
RE
Edited by: estrar on Dec 5, 2010 5:43 PM

Hi Estrar,
Short answer: 2003 Session Directory does not do load balancing.
Long answer (to the above and your other questions):
The Sun Ray Server doesn't do anything with regards to load balancing the windows sessions. To the Sun Ray Server, or more appropriately the windows connector, it's just making the connection you tell it to.
With regards to the windows client "working", am I correct in guessing that you ran subsequent instances of MS-RDC to "prove" that it worked?
Most likely what happened there is that the PC, thus MS-RDC, received different IP addresses back from DNS for the FQDN with each launch. This is basically round robin, not load balancing. But I'd have to understand how you've done the FQDN of the cluster in DNS.
The most common initial reaction is that the DNS server is setup incorrectly (I'll plead guilty that I've had the same reaction). It is true that some DNS servers can be configured will return the same IP on the first dns query. This is called a cyclic ordering and results in the IP address of the resolved name every client to be identical. For example, if a DNS server is set for cyclic ordering, every first request for the IP of server A for xyz.com will be the same on all clients. The second query from the same client should result in server B being resolved, if not, then you do have a DNS problem.. However, in the case of Sun Ray Server, the "second query from the same client" would be the second session coming up, since, as far as the DNS server is concerned, all the Sun Ray session are coming from the same client. Therefore, even with cyclic ordering, round robin should work even better in a Sun Ray environment then a "fat" client environment. You can check the documentation for specific DNS servers on how to set a random order for round robin (which should be the default), but chasing down cyclic ordering of RR entries as a cause to this "issue" is basically a red herring in a Sun Ray environment.
More than likely the same IP being returned everytime is a side effect of the name service caching daemon (nscd). The job of nscd is to speed up name resolution. However, ncsd will break any round robin scheme as it caches the first server returned by the first query from the caller (i.e. the host doing the name lookup, aka the Sun Ray server) and all applications on the caller will use that address for the lifetime of the cache. The default lifetime of the nscd cache is 3600 seconds (an hour). To disable the name service caching daemon, run the following command on every Sun Ray server in the host group (aka FOG): svcadm disable system/name-service-cache
An über smart colleague mentioned the possibility of another problem that could exist even if nscd is disabled and the hosts are on the same subnet as the caller . This has to do with default behavior of the Solaris resolver library putting servers that reside on the same subnet as the caller at the top of the sort order. You can read the notes in the man page for "gethostbyname" and also the man page for nss(4) for more information, but both reference how this behavior can break round robin. The fix is to edit /etc/default/nss and uncomment (or add) the statement SORT_ADDRS=FALSE
While those two things will allow a Solaris based Sun Ray server (or any Solaris client) to properly recognize round robin entries, it still holds true that 2003 Session Directory does not do load balancing. The only role of session directory is to ensure that you don't get routed to a different terminal server in case you have an existing session on another server. Round Robin + Session Directory may be all you need, but bear in mind that it is not "load balancing". Users could still connect directly to one of the IP addresses vs the round robin DNS name and that would defeat the round robin scheme in place.
Load balancing is a separate component in 2003, either using an external device like F5's BigIP or using Windows Network Load Balancing (NLB) service.
The type of load balancing solution that can be used depends on what is meant when you use the term "cluster". If the cluster is a real implementation of Windows 2003 Clustering (i.e.the type of cluster you'd use for SQL, Exchange, etc) then you can't use NLB and would have to use an external load balancer. Sun Ray Windows Connector supports either IP based or token based load balancers, though we don't certify any third party products in this regard.
"Cluster confusion" occurs because Session Directory itself is supported by Windows 2003 Clustering in order to provide a highly available directory service. Easy to see how this would be desirable with a large number of terminal servers. However, NLB does not work, nor is it supported on Windows 2003 Cluster.
To further the confusion, when NLB is enabled on the NIC that is handling RDP traffic, one of the configuration tabs is "Cluster Parameters". But it is important to realize that this has nothing to do with Windows 2003 Clustering and is in fact incompatible with it. NLB makes use of independent servers (i.e. not clustered), which the primary requirement of those servers is that they are on the same subnet.
Finally, it is easy to get confused between 2003 and 2008 session directory when it comes to load balancing, but they are very different. 2008 "session directory" does do load balancing. In fact, to underscore this distinction/feature, Microsoft has renamed Session Directory to TS Session Broker. (See http://technet.microsoft.com/en-us/library/cc772418%28WS.10%29.aspx)
To summarize, with Windows 2003 you have two choices when it comes to load balancing and session directory.
1) Have a HA implementation of Session Directory and use an external load balancer
2) Have non-HA implementation of session directory and use NLB to do load balancing.
Good how to article on setting NLB on 2003 with terminal services here:
http://www.brianmadden.com/blogs/brianmadden/archive/2004/11/29/how-to-configure-windows-network-load-balancing-for-pure-terminal-server-environments.aspx

Networking issues with Windows SBS Server 2003

I have 3 G5 running on a recently installed 10.4.8, they were all previously running 10.3.9. They all connect to a network drive with folders that have color labels on them (only 2 blue and green). In 10.3.9 the labels were fine, now when the machine connects to the server the labels do not refresh utill you have been throught them and selected them all. I have tried delabeling and then relabeling them in 10.4 but it does not help. I have also tried it on another site and it does exactly the same. It also does not seem to matter what protcol you use to connect to the server (AFP, SMB, TCP/IP).
Anyone come across this before and know any fixes?

I dont really have much to offer here except that we use afp with our SBS server and this hasnt come up... on any of our 10.4.x machines.

Running Windows Terminal Server 2003 with old version of Adobe. got the message it was no longer supported and it stopped working. Trying to install XI and it gets about 70% done and stops. Ran the cleaner on the 9.3 version to remove it. We use this

Installing Adobe Reader XI and it is stopping at about 70%. No error, it just stops. If I hit cancel and try it again, I get the 2203 error.

You are right: CS5 installs Flash Player 10.1 beta. You cannot install an older version of Flash Player unless you completely uninstall the beta version first:
download the 10.1 uninstaller from http://labs.adobe.com/downloads/flashplayer10.html#uninstallers and save it to disk;
from a Command Prompt, run the downloaded uninstaller with the -force option.

Sap gui on windows terminal server

Hi,
are there best practices to install sap gui 7.30 on a Windows terminal Server 2008 r2?
Regards
Zulma

hi Zulma,
Please follow the step by step guide.
SAP GUI 7.30
Example
How To Install SAP GUI 7.30 on Windows 8
SAP GUI for Java 7.30 Release Notes
Regards,
Jamil

Installing SAP GUI 7.30 in windows server 2008 r2

Hi guys,
Need help in, which patch to be downloaded for SAP GUI 7.30 for windows.
We have installed EHP6 ERP 6.0, the next step is to install GUI.
So, we found that 50120297_6 SAP GUI 7.30 for windows is the GUI we are looking for & downloaded it.
There are some patches to be downloaded too. So, below are screenshot which contains patch list.
Please suggest us which patches to be downloaded. Correct me if anything we have done wrong.

Hi Rafikul,
Thanks for the reply.
Below is the screenshot of SAP Notes 66971,
which shows no patch detail's for Windows server 2008 r2
One question that:
Does we to install all patch from 0 to 8, or only latest patch number 8 is sufficient.

Is BPC 7.0 compatible with Windows Terminal Server 2008?

Is BPC 7.0 compatible with Windows Terminal Server 2008? We are having printing issues when on WTS 2003.

BPC 7.0M SP08 was released on September 1st and now supports the client install on both Server 2008 and Windows 7 so yes, you should be able to use terminal server in Windows 2008 if you install SP08. It also has limited support for Office 2010, full support will come with SP09. SAP Note 1490544 is the central SP08 note, and 1504400 is the download note.
-Brian

B1 pelo WTS (Windows Terminal Server)

Boa tarde a todos...
Estou com um problema aqui na empresa que trabalho, foi implantado o B1 na unidade central e agora estamos implantando na filial de Porto Alegre....
Os usuarios de Porto Alegre irão acessar a base de dados que fica na central em São Paulo via WTS (Windows Terminal Server )...
Acontece que estamos enfrentando um grande problema com velocidade, visto que o acesso de Porto Alegre ficou extremamente lento.
Alguem ja passou por uma situação parecida?
Saberiam como melhorar essa questão da velocidade?
Ou alguma outra sugestão para essa implantação?
Edited by: Rui Pereira on Aug 6, 2008 1:54 PM
Edited by: Rui Pereira on Aug 27, 2008 5:02 PM

Oi
Não existe uma forma de alterar o SAP B1 para melhorar limitações de conetividade remota.
O WTS possui os seus próprios requisitos mínimos de comunicação e consoante o tamanho dos documentos e a quantidade de usuários conetados a performance vai ser mais reduzida.
Caso a rede seja utilizada para outras atividades, como armazenamento de arquivos (Word, Excel, etc...) isso irá afetar ainda mais a performance da comunicação remota.
Normalmente os valores recomendos são:
Windows Terminal Services .
-Bandwidth per user = 20 - 40 Kb
-Memory per user = 50 - 70 MB
Nota: Estes valores são meramente indicativos e a documentação mais recente da Microsoft deve ser consultada relativamente a largura de banda recomendada tal como referido na nota SAP 675004.
Paulo Calado
SAP Business One Forums Team

SAP GUI Install Issues on computers using VISTA

Installed SAP GUI many times on Windows XP computers, but having issues on your new VISTA system?
There are two major issues for SAP GUI on VISTA, here is an overview of how to solve them:
1. The unzipping wizard native to VISTA is lousy. Download the WinZip demo (www.winzip.com) or one of many free archiving tools. Make sure to unzip the SAP GUI file WITH FOLDERS. Use Windows Explorer to drill down through the unzipped GUI as shown. Double click SapGuiSetup.exe to start your installation...
2. The saplogon.ini file MUST be placed in the SAP GUI installation folder, not into C:\Windows.
The folder is:
C:\Program Files\SAP\FrontEnd\SAPgui
or for 64bit:
C:\Program Files (x86)\SAP\FrontEnd\SAPgui
Restart SAP GUI to properly display your server list. Contact your Hosting Center if you continue to have issues. Our email is sap at csuchico.edu

Troy -
There is also this link recently which may be of help.
SAPgui 720 PL1 upgrade causing IE 7/8 issues
Running this resolved that users issue.
C:\Program Files\sap\sapsetup\setup\"sapregsv.exe mshtml.tlb"
In your case it may be under the x86 folder since you are 64bit.
C:\Program Files (x86)\sap\sapsetup\setup\"sapregsv.exe mshtml.tlb"
Regards,
Zecher

Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
-install using the plugin
-install using LVRTE.exe
-install after rebooting the server
But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
Is there any compatibility issues with the new Run-Time Engine 6.1 ??
Thanks for your help
Cyrille

Cyrille,
What is the error that you get when trying to install the run-time engine?
Are you installing it from the LabVIEW CD, or did you download it from the web site?
To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
Also, try running the installer from the command prompt window, and use the following syntax:
setup.exe/l*v
This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
Thanks
Zvezdana S.
National Instruments

Cannot quit Visual FoxPro (Windows Terminal Server 2008 + Citrix XenApp 5 + VMWare vCenter 5.1)

Hi everybody:
This is not the typical question about this error, because the problem here is not about how to quit (CLEAR EVENTS then QUIT). The really and weird problem is that our application do no execute the error trapping routines (Try/Catch and ON ERROR) and tries
to directly Quit.
I have never seen something like this before, error trapping routines not executed.
I try to explain the problem better:
- The user click on the Citrix icon of our App
- Citrix shows the executed processes (establishing connection, applying user config, loading profile, etc)
- The Application (VFP 9 SP2) is started and in any moment, while loading, occurs an error that is not handled by error handlers, and it executes a "kind" of a Quit command, that we detect because have a ON SHUTDOWN to catch it, then the App shut
down and the user must click the Citrix icon and start all over again, up to 7 times, when the App really load and work.
- I think that it is useful to make clear that no QUIT command is really causing this, just the behaviour of the QUIT when an error occurs, but just while loading. If the App get completely loeaded, then everything works as expected
Infraestructure:
- Windows Terminal Server 2008 + Citrix XenApp 5 + VMWare vCenter 5.1
- There are up to 50 concurrent users max in every virtualized server
- More than 10 GB of free disk space / Up to 4 GB ram
- RAM Memory is never used to the max
- CPU (Intel Xeon) is never used to the max (up to 90% in some cases)
- Data (DBFs for temporal work) ar on local drive, not over network (to avoid network known problems with smb2-3)
- There are connection to a Oracle 11 database for permanently storing the data
About the errors:
- They are not always the same or in the same place. In example, in one execution could fail the query of SET("Printer",2), in other execution could fail a SET PROCEDURE TO xxx ADDITIVE (sometimes already loaded), in other could fail a "DO
WHILE .T." in a init event.... completely crazy, and in all cases the errors are not thrown, not a single error code, the App just try to quit, as if ALT+F4 where pressed.
- All this does not happen allways to everyone, but happens many times in the day to many many users as to be worried
- The same user can have this error many times a day, but not allways
- Some of the problems started when migrating to Windows Terminal Server 2008, but didn't notice nothing special in the beginning, but a year later (last 2014) problems tend to go worse
Tried solutions:
- For the "SET PROCEDURE TO xxx ADDITIVE" error, a "IF xxx $ SET('PROCEDURE')" check was added
- The "SET('Printer',2)" check was moved out of initialization code, so it executes when user want to print the first time. In this case was neccesary to talk with IT guys to map a default printer after the App runs, and not in background, as it
was.
- Other checks and modifications was made to minimize posibility of errors
- Adding a timeout of 5 secs in the start of the program, to force a wait
- Restart of virtual servers (not the phisical) every 3 weeks
What I suspect:
- Some Microsoft optimization (memory?, process execution?) in WTS-2008 may interfere?
- Some VMWare memory management may interfere with WTS-2008?
- Some Citrix management may interfere with both?
- Server degradation because of day to day use
Results until now:
- Apparently, adding the timeout to force 5 secs delay and the restart of the server have made a notable enhancement in App start and running
with far fewer
errors
Has
this happened to anyone?
Thanks! o_O
Fernando D. Bozzo / Madrid (Spain)

I never had this type of problems, but somewhat similar start up problems. I'd say it indicates resource problems. Low RAM can cause many unpredictable things. In my case loading much data at the begin of an application caused out of memory errors, which
were reported and logged normally, though.
I made a small tool using Windows API functions GetPerformanceInfo and GetProcessMemoryInfo, you'll find declaration and usage like usual at the News2News site. It's a bit lengthy and cluttered, but pretty much what you find there anyway, so I'll not post
my utility code.
I could quite clearly see how many users degraded available memory per session and at some time no further instance of the application was possible on the server. In my case RDP was used to start the app, Citrix will be quite the same, in the end the application
runs on some server and users see the remote running application.
Bye, Olaf.
Olaf Doschke - TMN Systemberatung GmbH
http://www.tmn-systemberatung.de

Swing app in JDK6 continues to rendering slow in Windows Terminal Server

Hi,
Because Swing apps create interfaces internally and not using default OS APIs,
when running into a Windows Terminal Server client, there is no way to optimize
rendering. Windows Terminal Server and Linux FreeNX use a mechanism to send
to client only commands to render the windows. But, because the way Swing works,
not totally integrated to OS APIs, it's not possible for terminal servers to do this,
and these servers render Swing like images, something like VNC do, very slower than.
I have tested native apps and AWT apps, and the difference is very significant,
something like 50-70% faster.
Is there some project in Swing APIs or java.net open-sources to better this?

We are also seeing this issue with a Compiere implementation. With 10 distributed sites across the US, our client wanted to use Windows Terminal Services to simplify the client desktop management of the Swing application.
But performance is terrible...and screen painting issues a real problem. We are also on JDK5 still, so I'm discouraged to see that JDK6 doesn't appear to offer much improvement?
Is there any project afoot to address this issue for installations using terminal services?
Thanks,
Peter

SAP GUI Memory issues on Windows Terminal Server 2003!!

Similar Messages

Maybe you are looking for