Search results for 4-revision-3

please note… any use of sarcasm in this blog are completely intentional. Thank You

Well more today from our Support help at Misys Client Care. They called…actually they have only been calling back after our systems have been down for an hour or more. Either way, they called back to say…well let me try adding a regedit then and then reboot all your servers…joy.

Anyways…to hopefully save someone else the trouble here is what happened:

Users were complaining about one of two things. The first symptom I saw was annoying but kind of simple to notice. We use a published application and when users tried to connect using the published application it would seem to “hang” and never complete the connection or error out. Actually, it just sat there and looked like this:

The second issue, which actually became the more prevalent problem looked like this: The message said simply: “Cannot connect to the Citrix MetaFrame server. Unable to contact the MetaFrame server browser. There may be network problems, or you may need to configure or correct the server address in the Server Location field.”

Let me cover a few basic things… This has happened several times since our migration to Windows 2003 and Citrix Presentation Server 4, this was a come and go sort of problem that did not seem to affect every user, I can verify that there are no network problems, and most importantly users can connect directly to single servers in the farm (however we have very few people set up to connect directly this way).

Since users could connect directly to servers and not through the published application the Citrix Knowledge base articles I found didn’t seem to help much. So we went to the Microsoft Knowledge base to so some searching and stumbled on this article: http://support.microsoft.com/kb/312362/EN-US/

At first glance it seemed strange but so far this registry edit has worked. It seems that the paged pool memory was getting depleted when the server was under heavy load. No we did not have the same errors in our log files, but the symptoms seemed like it could describe what what happening. Either way, I’m pretty confident in our solution and will keep track of related issues and report here to confirm this was in fact the solution.
Hope this helps.