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
@tric, good luck, i just sent over my number.
I've had the unofficial hotfix on 86 servers for 2.5 days. The original issue is gone (NLA Service timeout) but we now get the occasional bluescreen/crash (lesser frequency than the original issue). Not sure if these new issues are related to the hotfix or if the original issue was just masking some other (unrelated) issues we have.
Ultimately, I am hoping these new issues are related to the fact that the hotfix is still in development. And, that the official release will be more stable (having been hardened and tested more).
@Jamie, Last ETA I got from Microsoft was 11/27.
We have found out that the problem occurs when accessing files on a certain server running Windows 2003. This certain machine was not up to date with Microsoft patches so we updated last night. Today we had no server hang
Unfortunately we could not provide Microsoft with a memory dump yet. Ther is simply no way to have a memory dump when booting via PVS an dwithout a memory dump Microsoft would not give the private fix.Only since yesterday we were able to change two servers successfuly to hard disk boot. Two more were changed today, another two will be added tomorrow and Thursday.
I've mailed our Microsoft contact today to get news on the availablility date. I will keep you posted when I get the answer.
Stephan
I've mailed our Microsoft contact today about the availablility date and just got an answer: unknown to him . I will keep you posted when I get any news.
Good news for all those still trying to track down this fix. It is now an official release but remains only privately available (you have to call Microsoft and request it). Here are the details:
KB Article Number(s): 976674
Fix #288827
Download Name: 399350_intl_x64_zip.exe
Hotfix Name: Windows6.0-KB976674-x64.msu
This hotfix is still "not publicly available through the Microsoft website as it has not gone through full Microsoft regression testing". However, that is the standard disclaimer for all private hotfixes.
Since this is an official release, it no longer has the "Test Mode" requirement.
First off, Thank you David for keeping us all informed on the work you have done, in regards to this issue.
I was able to contact Microsoft and download this fix, however I was not able to find and was not provided any documentation on this fix, do you have any documentation on this KB Article?
Thanks again
I contacted microsoft UK and they were SO unhelpful it was unreal. Bascially they were unwilling to disclose the hotfix to me and said it would only be avialble once it is public on the support site. Would anyone who has downloaded this be kind enough to email or upload this to some of my webspace (I'll provide you with web address username/password etc - just send me a message)
Many thanksMike
Downloaded and installed hotfix Windows6.0-KB976674-x64.msu now the server is freezing up every two seconds, I had also installed all the latest Microsoft updates 13 in all, except for IE8.
So, either the hotfix is not good or it was over written by one of the MS updates...
@Novell2NT, Unfortunately, I don't have any information about the fix except what I have been able to determine on my own (and posted previously). Best I can tell, its a bug with rdbss.sys similar to that of KB972596.
@Novell2NT, I haven't had a chance to install (or even test) the official release yet. I probably won't until 12/5. I'll post the results for comparison.
The hotfix plus all the MS updates made the problem much worse... I was able to restore my VM, pre-Hotfix and updates.
When my partner tried to re-apply the hotfix after a crash, the system said the file or files it was trying to replace were newer then the file or files that the hotfix were applying. This makes me think that the MS updates over wrote the HotFix.
Well, that was my fun story for the day, hope you guys have better luck.
(forum acted up, sorry if double posts)
My contacts have not provided this fix nor mentioned the patch was available. They seemed to be fairly comfortable with stating early December. I have sent an inquiry to two seperate contacts and am awaiting their response (will probably be late tonight).
So far, the private hotfix provided has still been operational without incident. I will post their feedback, plus any info once we receive our final patch.
The customer that is affected has been receiving standard patching except for a few patches, mainly for Office 2007, the Win2k8 patches are: KB969947 (in testing), and other KB's are in pending deployment: KB944036, KB972036, KB672145, KB971644.
I installed the official release of the hotfix on 2 of my clients servers last night and first thing this morning one of them hung - NOT HAPPY!
we've pulled that server out of the farm for now. I'll get in touch with my Microsoft support guy and will post any progress updates.
I was really hanging my hat on this one; we need this fix to work!
All-
I followed-up with my contact. I'm being told KB976674 is not my issue and is a seperate issue for a deadlock between the Cache and SMB module.
So do not worry if your issue is not resolved by this patch, as I'm being told the private fix is still on schedule.