Exchange 2013 on Hyper-V, 2 proc, 8GB, 1 mailbox, out of memory error

Hi,

Have set up a test Exchange 2013 on Server 2013 in a Hyper-V environment. Hyper-V is hosted on a fresh install of Server 2013 (DC) with a single user. The DC has 16GB memory, 4 processors, the VM has 8GB memory and 2 processors allocated. There is a single mailbox with a single mail user defined.

The VM is constantly unresponsive, and running out of memory. I appreciate that I've used the minimum memory requirements for Exchange, but I'd still have expected this to run fairly comfortably given the low volume of activity it should be experiencing. Having read some of the other posts, I noticed noderunner.exe was taking up large amounts of memory in the first instance (2GB+). Disabling the Microsoft Exchange Search Host controller service removes the problem temporarily, but until an attempt is made to log onto the one mail account via OWA. At this point, several w3wp.exe instances are spawned, each taking around 500MB and, again, the server runs out of memory. The OWA site becomes unavailable (constant "waiting for response" message).

Any ideas of where I should be looking to optimize or what changes I need to make? I upped the VM memory to 10GB, however this didn't seem to help - noderunner just ate it...

Thanks,

Dave

November 7th, 2013 6:12pm

Hi,

Its not recommended to install Exchange Server on DC. Is there any third-party firewall or AV program runing on the server? If so, please temporarily disable it and see whether the issue persists.

Thanks,

Simon

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

Free Windows Admin Tool Kit Click here and download it now
November 8th, 2013 1:01pm

Hi Simon,

Thanks for the reply; Exchange isn't hosted on a DC; it's hosted on a VM on the DC (unless that's the same difference?) - it's basically just a test environment at the moment.

There is no additional software on either the DC or VM; the DC is Server 2013 with a minimal config required to act as DC and host Hyper-V (AD DS, DCHP, DNS, Hyper-V), and the VM contains nothing but Server 2013 and Exchange 2013. It's literally the minimum required to get the environments to run.

Cheers,

Dave

November 9th, 2013 7:08am

What is your Hyper-V version you have not mentioned that is fourm. Please let us know the version of hyper-v. Have you read Prerequisites for Exchange 2013 on Virtualization???

Please read below ink

http://technet.microsoft.com/en-us/library/jj619301(v=exchg.150).aspx

http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx

http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx

http://social.technet.microsoft.com/wiki/contents/articles/16730.installing-microsoft-exchange-server-2013-prerequisites-on-windows-server-2012.aspx

Free Windows Admin Tool Kit Click here and download it now
November 9th, 2013 7:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics