Solved

High memory usage/Exchange problems with Small Business Server 2008

Posted on 2009-04-06
7
5,420 Views
Last Modified: 2012-05-06
I have a server running SBS 2008. The server has 8GB RAM. Almost every two weeks email stops working, and numerous application errors show up in the logs. A reboot fixes it, and everything will work fine for another two weeks. The server is running as a DC with Exchange/Sharepoint/SQL/RWW, etc. From looking at the logs it seems as if some kind of AD or DNS service shuts down, although when I remote in the Active Directory Domain Services service is running and the server was consistently using about 90+% available RAM (sometimes 98-99%), mostly for Exchange, SQL, and IIS. I limited the Sharepoint instance of SQL to use only 256MB and now RAM usage stays around 85%.

Restarting AD/DNS/Exchange services does not solve the problem and I end up having to reboot. I'm not sure that high memory usage is even the problem, just trying to eliminate possibilities. I have not had the problem since limiting SQL memory usage but also I have resorted to rebooting the server during the night once every 7-10 days so email does not go down in the middle of the day.
Microsoft said this would be fixed in an update for Exchange but the server still had the problem after the patch was installed.

Here are some of the errors from the Application Log:

Log Name:      Application
Source:        MSExchange ADAccess
Date:          3/15/2009 7:13:22 AM
Event ID:      2102
Task Category: Topology
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.com
Description:
Process MAD.EXE (PID=2476). All Domain Controller Servers in use are not responding:
server.domain.com
 


Log Name:      Application
Source:        MSExchange ADAccess
Date:          3/15/2009 7:14:10 AM
Event ID:      2121
Task Category: Topology
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      server.domain.com
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2252). Exchange Active Directory Provider found SRV records for domain controllers in domain domain.com.
 The query was for the SRV record for _ldap._tcp.dc._msdcs.domain.com
 The following domain controllers were identified by the query:
server.domain.com

 Common causes of this error include:
 - Host (A) records fore each server are missing  in DNS or contain incorrect IP addresses.
 - Domain controllers registered in DNS are not connected to the network or are not running.
 For information about correcting this problem,  type in the command line:
hh tcpip.chm::/sag_DNS_tro_dcLocator_messageHa.htm



Log Name:      Application
Source:        MSExchange Autodiscover
Date:          3/15/2009 7:15:54 AM
Event ID:      1
Task Category: Web
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.com
Description:
Unhandled Exception "Could not find any available Domain Controller."
Stack Trace:    at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential)
   at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType)
   at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId)
   at Microsoft.Exchange.Data.Directory.ADGenericReader.GetNextResultCollection(Type controlType, DirectoryControl& responseControl)
   at Microsoft.Exchange.Data.Directory.ADPagedReader`1.GetNextResultCollection()
   at Microsoft.Exchange.Data.Directory.ADPagedReader`1.GetNextPage()
   at Microsoft.Exchange.Data.Directory.ADPagedReader`1.<GetEnumerator>d__0.MoveNext()
   at Microsoft.Exchange.Autodiscover.Providers.Outlook.OutlookAutoDiscoverProvider.SimpleConfigCache`2.Freshen(ADSystemConfigurationSession session)
   at Microsoft.Exchange.Autodiscover.Providers.Outlook.OutlookAutoDiscoverProvider.UpdateCacheCallback(Object stateInfo)



Log Name:      Application
Source:        MSExchangeMailboxAssistants
Date:          3/15/2009 7:07:56 AM
Event ID:      10003
Task Category: Managed Folder Assistant
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.com
Description:
Could not get the server configuration object from Active Directory. Microsoft.Exchange.Assistants.ServerIneptException ---> Microsoft.Exchange.Data.Directory.ADTransientException: Could not find any available Domain Controller.
   at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential)
   at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType)
   at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId)
   at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId)
   at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator)
   at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCtor, CreateObjectsDelegate arrayCtor)
   at Microsoft.Exchange.Data.Directory.ADSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties)
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults)
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindServerByFqdn(String serverFqdn)
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindLocalServer()
   at Microsoft.Exchange.InfoWorker.Assistants.ExchangeServer.<>c__DisplayClass2.<TryGetServer>b__0()
   at Microsoft.Exchange.Assistants.Util.<>c__DisplayClass2.<CatchMeIfYouCan>b__0()
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Assistants.Util.CatchMeIfYouCan(CatchMe function)
   at Microsoft.Exchange.InfoWorker.Assistants.ExchangeServer.TryGetServer(). Check for domain controller network connectivity issues or incorrect DNS configuration.



I also receive this error in the System log:

Log Name:      System
Source:        Microsoft-Windows-GroupPolicy
Date:          3/15/2009 7:07:16 AM
Event ID:      1054
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      server.domain.com
Description:
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name Sysytem (DNS) is configured and working correctly.


Anyone have any ideas about what is causing this?
Thanks!
0
Comment
Question by:csandlin
7 Comments
 
LVL 15

Expert Comment

by:abhaigh
ID: 24080728
0
 
LVL 21

Accepted Solution

by:
suppsaws earned 500 total points
ID: 24084988
0
 
LVL 1

Author Comment

by:csandlin
ID: 24099120
Thanks suppsaws, that looks like it may work. I installed the fix and will reboot tonight and see what happens. Will keep you posted.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
LVL 1

Author Comment

by:csandlin
ID: 24107038
I applied the patch and rebooted last night. Looks like now the server is only using 4.7G of memory instead of 7+. Also before the patch the amount of used memory would creep up constantly. I'll keep checking it and report back.
0
 
LVL 15

Expert Comment

by:abhaigh
ID: 24107059
expect the store to use as much ram as it can

this is by design
0
 
LVL 1

Author Closing Comment

by:csandlin
ID: 31567072
This seems to have helped a lot. It seems as if there are other memory issues with  the SBS but this fixed the immediate problem.
0
 
LVL 2

Expert Comment

by:tech_tonic
ID: 24900118
Hi guys, I'm also having this exact same problem, but when I tried to apply the hotfix, an error message was returned: "The update does not apply to your system". I'm guessing someone else has already applied this hotfix.
I am only running 4GB of ram on this server though, would this be the problem?
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Find out what you should include to make the best professional email signature for your organization.
A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question