Quantcast
Channel: Exchange Server 2010 forum
Viewing all articles
Browse latest Browse all 15005

No Access to EMC or EMS - Resource-Exhaustion-Detected Error 2004 - Pagefile Configuration???

$
0
0

Hi all and thank you in advance for your help and shared knowledge.

I am experiencing problems accessing EMC or EMS in Exchange 2010. When trying to access EMC I receive the following error:

"The attempt to connect to http://myserver.domain/PowerShell using "Kerberos" authentication failed: Processing data from remote server failed with the following error message: The type initializer for 'Nested' threw an exception. For more information, see the about_Remote_Troubleshooting Help topic."

When trying to access EMS:

"Processing data from remote server failed with the following error message: The type initializer for 'Nested' threw an exception. For more information, see the about_Remote_Troubleshooting Help topic.

*CategoryInfo :OpenError: <System.Manageme....RemoteRunspace:RemoteRunspace> [], PSRemotingTransportException

*FullyQualifiedErrorId : PSSessionOpenFailed"

While looking through the event logs I find the following event corelated to the above errors.

Event ID 2004 Resource-Exhaustion-Detect

"Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: store.exe (7352) consumed 8072130560 bytes, w3wp.exe (7332) consumed 684277760 bytes, and Microsoft.Exchange.RpcClientAccess.Service.exe (5004) consumed 612663296 bytes."

This is where it gets a little screwy. Recently I moved the pagefile off of C: and moved it to D: (because of disk sizing) the pagefile deleted properly and I was then able to reallocate to D: no problem. With this configuration when logging into the server a message would pop up saying "Windows created a temporary paging file on your computer because of a problem that occurred with your paging file configuration when you started your computer. The total paging filesize for all disk drives may e somewhat larger than the size you specified." Funny thing is when I search for pagefile.sys it is in the D: directory and is the correct size.

Over the weekend I split the pagefile putting 1GB on C: and 23GB on D: everything allocated properly and the error message at login was gone. After a reboot I searched for pagefile.sys and the results show a pagefile on only C: for 1GB. Like the OS is not creating the pagefile for D:.

Tonight I am going to go back to having the pagefile on D: only and deal with the error message. Hopfully this will correct the problem.

Anyone have any thoughts on this? Am I thinking about this correctly? Why would I get these error messages regarding the pagefile? (Should have no problem moving the pagefile) I am also not experiencing any authentication errors across the network so I don't think it is a DC problem.

Here is a outline of the exchange envionment:

Dell PowerEdge R610

Windows Server 2008 R2 x64 SP1

Exchange Server 2010

16GB RAM

Thanks everyone, as I am going to work on this tonight any suggestions would be great. I will also post my results from my current plans.

Mike


Viewing all articles
Browse latest Browse all 15005

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>