Well it looks like Our old problem has come back with SP1 for 2008 R2
After spending a while looking, i found the following KB…
Link to KB
http://support.microsoft.com/kb/2263829
To get the file, you need to contact Microsoft, but they just email you the file.
I have just applied it to the 1st machine i have seen with the problem, but hope i wont see too much of this problem again.
« Connect to ##SSEE database Show users that have access to mailboxes on Exchange 2007/2010 »
Also struggling with this issue since two weeks! We have three hyperv host servers, and we initially installed 2008r2 sp1 to them due to this problem. After sp1, the vm network issue appeared every day! Thanks for the link, I just installed this to the first host.
only too pleased to help. its fixed my problem servers.
FWIW, I am seeing this exact problem, but only on a child VM that is running Exchange 2010. However, in my case, the hotfix does not resolve the issue. The easiest way to cause a failure is to start a backup of the Exchange VM using ARCserve and part way through backing up the C: drive, the network connection on the VM dies and you need to reboot the VM to get it to work again. At first I thought it was an ARCserve issue, but appears to be more load related than anything else….having said that, if you backup Exchange databases only, no problems. So, the load of backing up Exchange Information Store is higher than when backing up files on C: drive, but this still works okay.
The rate of backup of C: drive, prior to failure, is about 1.1GB per minute. The rate of backup of the Exchange IS runs closer to 3GB per minute.
I have the same exact problem hotfix not resolve my problem please when found solution to send me.
the other things to check are the network settings. Disabling TCP offload and other things like that might help.
Not in my experience…to date, I am unable to find a way to resolve this problem. I reckon I have burned a week of my time turning off TCP offload and many similar settings; nothing stops the Hyper-V networking stack from failing. I’m not so sure that it is purely network load related as (stated above), I can make this fail when using ARCserve to backup my Exchange 2010 VM. But it only fails part way through backing up the C: Drive. If I remove the ‘Client Agent for Windows’ and leave the Exchange agent only on the VM, then I can backup the Exchange DB over and over, without a problem. And the rate of data transfer over the (virtual) network when backing up the Exchange DB is much greater than when you backup the C: drive with thousands of little files.
So, this makes me think that it is maybe some sort of file i/o problem with the VHD? An SMB (does ARCserve Backup use SMB?) problem? A combination of both the high file i/o and network load? Maybe a bug in the Hyper-V Integration Services? Something is not right and I can’t believe that there isn’t more noise out there about this. I have 2 servers, at different locations that both experience this problem, albeit the symptoms and recovery are a bit different.
The other server loses the networking stack in the VM, but you have to reboot the host to recover as the VM crashes and becomes unresponsive during the reboot. So, this is more serious insofar that the whole host needs a reboot to correct the failed network on a single VM.
I would love to hear from anyone who is experiencing the same problem and share ideas. My email is b r e n d a n (at) p r i v a t e u n i v e r s e (dot) c o m (dot) a u
I have managed to work around this problem by removing the a/v software on the child VM. This adds weight to my previous theory that the problem is i/o related as opposed to a straight out network load problem.