Latency On Application Load (10-15 MIN)

Good Day Everyone –

I have one server in a small two server farm that has a bit of an attitude lately. Nothing has changed except for JDE packages – however this one server takes forever to complete application load with JD Edwards – only when you have the ICA client set for local authority with pass through. Anybody have any thoughts as to why?

We run Windows 2000 Server SP2
Citrix Metaframe XP IMA Core V 1.2
IBM CA V5R2 SIO 9809

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

any errors in the event viewer on this server when users log in?
sysbw1Author Commented:
No, unfortunatly not. I have looked at every messag that I did not understand in event viewer and nothing was related to Citrix.


 Posted by RATokeshi on Tuesday, July 27, 2004    

Troubleshooting Slow Logons 2179 Reads Citrix MetaFrame 1.8
Citrix states in their article: <a href=./ctx/CTX101705 >CTX101705

CTX101705 - Troubleshooting Slow Logons

This document was published at:

Document ID: CTX101705, Created on: Mar 27, 2003, Updated: Aug 13, 2003

Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000, Citrix MetaFrame XP 1.0 for Microsoft NT 4.0 Server Terminal Server Edition, Citrix MetaFrame 1.8 for Microsoft Windows 2000, Citrix MetaFrame 1.8 for Microsoft NT 4.0 Server Terminal Server Edition

This document provides some known issues and their workarounds.

Important: Microsoft Service Pack 4 for Windows 2000 affects slow logons on both the MetaFrame XP and MetaFrame 1.8 platforms. MetaFrame Service Pack Levels do not affect the issue. The issue introduced by Microsoft Service Pack 4 for Windows 2000 has been addressed with patch 824309.

Troubleshooting Steps

Note: Perform Steps 1 through 3 with the same user account.
1. Log on from the Terminal Server console. In a load balanced environment, it may be necessary to log on to multiple Terminal Servers.

2. From a workstation on the LAN, log on to the Terminal Server with an RDP or ICA desktop session. Again, in a load balanced environment, it may be necessary to log on to multiple Terminal Servers.

3. If applicable, from a workstation on the WAN, log on to the Terminal Server with an RDP or ICA desktop session. Again, in a load balanced environment, it may be necessary to log on to multiple Terminal Servers.

Important: Steps 1 through 3 will give you a good idea as to whether or not the logon issue is strictly related to MetaFrame or is more likely a profile, logon script, network, or other user environment issue.

4. For profile issues, remove any references to a profile path from the Terminal Server and/or user profile path within User Manager for Domains, Active Directory users and computers, or Computer Management. Alternatively, create a local account directly on the Terminal Server to ensure the profile is being loaded directly from the server. Retest the logon time.

Note: New user accounts, accounts without a local profile, and anonymous accounts need to generate a local profile upon logon. The creation of the original profile may take time. It may be necessary to log on a second time when troubleshooting a profile issue. See Microsoft Web site to further troubleshoot profile issues.

5. For logon script issues, remove any references to a logon script within User Manager for Domains, Active Directory users and computers, Computer Management, or any sort of computer or group policy. Creating a local account directly on the Terminal Server and testing may be worth the time. If the Novell Client is installed on the Terminal Server, attempt to do a “Workstation Only” logon. Retest the logon time. If a logon script is the issue, it may be necessary to REM (comment out) or input pause statements throughout each section of the logon script. This will help troubleshoot what resource(s) in the logon script are slowing down the logon process.

6. Network issues, such as Font Searching May Cause Slow Logins on Terminal Server are often difficult to troubleshoot and find. Network monitors/sniffers and other third party utilities such as regmon and filemon from can be used for these issues. The issue described was resolved by the following:

In some cases, the logon process on a Terminal Server may be very slow due to an application searching for fonts. Applications that may cause this problem include NWScript.exe and Lotus CC:Mail.

During the logon process, users can encounter a black screen for one to 20 minutes before the logon finally completes. The effect is magnified as the bandwidth is reduced; dial-in users experience the problem much more severely than LAN users.

Network traces on such systems revealed that a process running on the Terminal Server is searching for fonts by name during the logon process and not finding them. Performing the following steps may succeed as a solution:

A. In the system Control Panel, click the Environment tab.

B. In the system variables section, click the variable Path.

C. Add the following to the end of the string in the Value field at the bottom of the panel:


D. Click Set. Your changes take effect immediately.

7. The ICA Clients Bitmap Cache directory has an excessive amount of files stored in it.

Delete the files in the Bitmap Cache directory for the ICA Client that you are using. For details about how to perform this function, see the following sections in the respective ICA Client Administrator’s Guides:

9. Slow logon encountered when using the ICA Win32 Client on a Windows 2000 Server.

Prior to ICA Client build 6.00.963, logons attempted to write to a licensing key on the client device. This caused a delay while the time-out occurred. However, that issue is resolved with the newest client, 6.00.963. Verify that you are running this version or greater.

Users may experience slow logons from Windows 2000 Professional workstations when using the ICA Win32 Web Client Version 6.20.985. The issue may be related to the permissions on the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft \MSLicensing registry key. For the ICA Win32 Client to function properly, the user requires Full permission on this registry key.

Some other symptoms that are indicative of this issue are as follows:

• Logons using the full ICA Win32 Program Neighborhood Client are not affected

• Logons using the ICA Win32 Web Client on other workstation platforms (Windows 95, Windows 98, and so on) are not affected

• Local workstation administrator and power users are not affected
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

sysbw1Author Commented:
Ok – well this has taken an interesting twist. I have found out that my problems started when our Domain underwent  an upgrade to the schema that ships with server 2003. Now, why only one of my local servers has this issue I do not know. Any thoughts on this? Authentication still seems to be done locally with our DC. Argh!
sysbw1Author Commented:
I should also mention - only two of our three citrix sites have this issue.
sysbw1Author Commented:
another update - once I terminate USERINIT.EXE from the management console on a session trying to log in - this thing moves right along like nothing is worng.
Sorry for the delay.  I didn't catch that you actually responded because so many posts I have made have been deleted due to authors not coming back to their threads.  So I started ignoring e-mail from EE.

check out this link:

and this one:  in particular we may need to check the dns resolution which may be affecting user authentication.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.