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
We have obtained the private hotfix from Microsoft and are currently testing. Unfortunately, as previously stated, there is no useful KB number to reference. However, I can tell you that it updates C:\Windows\System32\drivers\rdbss.sys and C:\Windows\System32\ntoskrnl.exe to to version 6.0.6002.22224. Also, since the fix is still in development/testing with Microsoft, we had to put the server into test mode (bcdedit -set testsigning on) in order to install it. This is unfortunate if you need to test the hofix in production and/or expect to use this early release to fix your production environment. If you are in dire need, as we are, you might not care. I'd rather the desktop background say "Test Mode" than have servers sprodically hang throughough the day.
We've got news today from Microsoft they are finalizing the fix. With a little luck we could have a solution by Friday, the supporter told me. I will keep you posted.
Kind regardsStephan
This is good news, please keep us posted...
Thank you
I hope he's right. My tech's told me recently:
"I received an email that the fix seems to have been cleared for release first week of December. If there is any change we will be notified then."
We have tested clean for over 48 hours with the private hotfix installed and the SMBv2 client components on a Terminal Server disabled (we disabled the SMBv2 client components because it seems as though we are able to reproduce the issue faster... and have been using this server as our test server with Microsoft). Sounds like this hotfix will be the solution for many (and has been confirmed to work by several). We are going to re-enable the SMBv2 client components and re-test for at least another 48 hours. If that works, we will let Microsoft know that the private hotfix is the answer to our problems. At that time, we will be pressing for an official hotfix (or, at least, an ETA as others have posted).
We have been able to consistently reproduce the issue on our test server (SMBv2 client components disabled) within 12 hours without the private hotfix.
Thanks for testing. Is there a KB articel for issue jet.
Hi there, long time reader, first time poster...I'm having the same issues on Windows 2008 SP1, which someone was wondering about in an earlier post on this thread. I've a call open with MS and another open with Citrix. Both of whom are looking for a complete mem dump. However I'm also using provisioning server 5.1. I've been trying to see if I could force a complete memory dump by using a private image on one server, no joy so far. I've tried redirecting the dump to a physical drive on the server (we have a C: vdisk and D: physical) but still no luck. I will try dumping the image back to physical disk in an effort to get a mem dump if I get no joy.
I've tried two hotfixes KB956438 and KB972596. Also I've disabled SMB2/mrxSMB2 with the SC commands. I released a new image with all this yesterday and it happened within two hours of users logging on. Anyone had any luck since their last post? jeauxk is there any chance of getting your incident ID to try and get MS to send me the same hotfix? Cheers,Ian
Hi Ian,
I can't speak for everyone, but after the private hotfix that MS gave us for our incident a few weeks back, (which hopefully will soon be released publically), we have had no issues. We just recently re-enabled SMB 2.0 and OpLocks to make sure that those two still weren't an issue and things look good after that too. If you need, I can send you over our incident ID as well.
Good Luck!Jamie
@Ian: Will be glad to, please make enable access to email you via forum, or post a comment to me w/ your email address.
Jamie and JeauxK, thanks for your quick responses. I've put a comment on both your pages with my email address. Hoping they send me the fix and it gets rid of this issue once and for all.
Cheers,Ian
I got the mentioned private fix from microsoft last week. And after testing it for 2 days I was able to run 25 users on one server without this massive impact we had before but we still facing system hangs within the session 1-3 times a day for 30sec - 4min per user?
I'm still in contact with ms but anyway does anyone facing the same issues?
Any help would be appreciated.
Best Regards,
Matthias
If possible could someone please provide me with all details for the private hotfix which is has been the most recent topic of conversation? I too am experiencing this issue and would like to see if the hotfix corrects the issue for me.
RegardsRob
Hi there,
I did also contact Jamie and JeauxK for their incident numbers with MS.
We are experiencing the problem for a few weeks now. I've tried nearly everything to get rid of that problem, but it seems like there is no fair chance without that fix.
If someone would please send me a corresponding incident number... you're welcome!
Thanks,
Patrick
Hi Patrick,
I sent you over a reply. I hope that it helps!
Just out of curiousity, has anyone heard anything more concrete on the public release date for this fix?
Jamie
@rob, please send a comment with your email address, or enable access to send messages via the forum.