Hi,
We are encountering some strange problems with a XenApp 5.0 farm that runs on Windows Server 2008 SP2. The farm consist out of 2 XenApp 5.0 servers with a single server that hosts the web interface. Underneath the OS we run VMware ESX 3.5 update 4. Usually everything runs ok but's the performance is very bad. The XenApp servers have 2 vCPU's and 4GB memory. We use roaming profile with folder redirection for some folders.
WE publish the desktop to our users so we installed all application on the 2 servers en use NTFS permissions for application access.
The problems:- Performance is not ok. When users are typing in Word (Office 2007) or other applications the characters will display with some latency, not always it happens sometimes.
- One server becomes unresponsive. Application that are allready started work very slow. New application which are started from the Start Menu won't appear. After some minutes the server goes further and all application will appear. It looks like the server is sleeping for a while. When that happens the System log shows the following errors:
7011 - A timeout (30000 miliseconds) was reached while waiting for a transaction response from the RasMan service. 7011 - A timeout (30000 miliseconds) was reached while waiting for a transaction response from the NlaSvc service. 7011 - A timeout (30000 miliseconds) was reached while waiting for a transaction response from the CryptSvc service. 10010 - The server {AAC1009F-AB33-48F9-9A21-7F5B88426A2E} did not register with DCOM within the required timeout.
Kind regards,
Onno van den Berg
Hi
We now have the results back from our Microsoft case. The issues was with another driver (Our backup software) locking the system up. See below for explination from Microsoft engineer
CpsFsJnl.sys has called KeWaitForSingleObject in the context of the kernel’s processing of an I/O request via the client side portion of the SMB I/O stack (via rdbss!RxShadowIoHandler).
In short, this Symantec driver decided to wait and has been stuck for over 7 hours, effectively blocking everything else in the system.
So it was something to do with the rdbss.sys but was caused by another app
Thanks
We havn't had a system hang for weeks now. For us KB976674_v3 definately resolved the issue.
We use Provisioning services on IBM blades, 32bit. No virtualization.
RegardsStephan
Is there an official release yet? I really need to get my hands on a 64bit version as soon as possible. The issues started again and they are back to be pretty frequent.
It does look like you can download the update from Microsoft as of the 4th.
http://support.microsoft.com/kb/KB977675
Sorry, wrong link.
http://support.microsoft.com/kb/KB976674
Let us know how it works out Toby, as I am still logging everyone out at the end of the day. Maybe once a week I run into any problems this way, but better safe than sorry...
Same Problem Here - Running Windows 2008 64-bit and XenApp 5. Servers are VMs using VMware ESX 3.5. This is happening on both of our Citrix servers randomly and usually daily. I downloaded and applied the KB976674 last night on both servers, and unfornutanely one of the servers had the same issue today. I get the NlaSvc and CryptSvc timeouts in eventviewer. I believe this is because those services run under the same svchost process as the termservices service.
Also how do you verify the version of the rdbss.sys file. When I look at the properties on my the version information is blank. The modified date is 11/27/2009 7:46 AM.
Darren, What are the specs of your Citrix VM's?
2 vCpus @ 8GB RAM
Citrix XenApp Advanced Edition v 5.0
Windows 2008 x64 SP2
Usually between 20 - 25 users per server.
CPUs are 2.66Ghz
The mention of KB976674 v3 ...it's this hotfix, right? : http://support.microsoft.com/kb/976674/
Seems to match up with this Citrix Support Forum thread : http://forums.citrix.com/thread.jspa?threadID=253462&start=0&tstart=0
The Microsoft patch didn't work for me either. I am running XenServer 5.5 FP1 and my Citrix servers are Server 2008 32bit. I am out of ideas at this point........
I have applied the MS patch and still have the problem occasionally.
Two things that have helped our situation - I had previously edited the registry setting HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\autodisconnect because of a problem opening files on the network - this settings was set at 0 for some reason. My edit solved the opening files problem, but I don't know if it made the lockup problem worse. I changed it again to match other windows servers at a setting of 15 decimal or 0x0000000f in hex. I don't know if this change made any difference or not.
The second thing (which I know has made a big difference) is we used to log off disconnected idle sessions whenever we noticed them. I would check randomly througout the day and log off these sessions = sometimes logging off 3 or more at the same time or very quickly one right after the other. Now I only log off one session at a time - I wait at least a minute or two before logging off another session. Since doing this I have only had the problem on one server one time in 3 weeks.