csandlin
asked on
High memory usage/Exchange problems with Small Business Server 2008
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/RW W, 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 MSEXCHANGEADTOPOLOGYSERVIC E.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.domai n.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_dc Locator_me ssageHa.ht m
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.Di rectory.Co nnectionPo olManager. GetConnect ion(Connec tionType connectionType, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential)
at Microsoft.Exchange.Data.Di rectory.Co nnectionPo olManager. GetConnect ion(Connec tionType connectionType)
at Microsoft.Exchange.Data.Di rectory.AD Session.Ge tConnectio n(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId)
at Microsoft.Exchange.Data.Di rectory.AD GenericRea der.GetNex tResultCol lection(Ty pe controlType, DirectoryControl& responseControl)
at Microsoft.Exchange.Data.Di rectory.AD PagedReade r`1.GetNex tResultCol lection()
at Microsoft.Exchange.Data.Di rectory.AD PagedReade r`1.GetNex tPage()
at Microsoft.Exchange.Data.Di rectory.AD PagedReade r`1.<GetEn umerator>d __0.MoveNe xt()
at Microsoft.Exchange.Autodis cover.Prov iders.Outl ook.Outloo kAutoDisco verProvide r.SimpleCo nfigCache` 2.Freshen( ADSystemCo nfiguratio nSession session)
at Microsoft.Exchange.Autodis cover.Prov iders.Outl ook.Outloo kAutoDisco verProvide r.UpdateCa cheCallbac k(Object stateInfo)
Log Name: Application
Source: MSExchangeMailboxAssistant s
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.Assista nts.Server IneptExcep tion ---> Microsoft.Exchange.Data.Di rectory.AD TransientE xception: Could not find any available Domain Controller.
at Microsoft.Exchange.Data.Di rectory.Co nnectionPo olManager. GetConnect ion(Connec tionType connectionType, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential)
at Microsoft.Exchange.Data.Di rectory.Co nnectionPo olManager. GetConnect ion(Connec tionType connectionType)
at Microsoft.Exchange.Data.Di rectory.AD Session.Ge tConnectio n(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId)
at Microsoft.Exchange.Data.Di rectory.AD Session.Ge tReadConne ction(Stri ng preferredServer, ADObjectId& rootId)
at Microsoft.Exchange.Data.Di rectory.AD Session.Fi nd(ADObjec tId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator)
at Microsoft.Exchange.Data.Di rectory.AD Session.Fi nd(ADObjec tId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCtor, CreateObjectsDelegate arrayCtor)
at Microsoft.Exchange.Data.Di rectory.AD Session.Fi nd[TResult ](ADObject Id rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties)
at Microsoft.Exchange.Data.Di rectory.Sy stemConfig uration.AD SystemConf igurationS ession.Fin d[TResult] (ADObjectI d rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults)
at Microsoft.Exchange.Data.Di rectory.Sy stemConfig uration.AD SystemConf igurationS ession.Fin dServerByF qdn(String serverFqdn)
at Microsoft.Exchange.Data.Di rectory.Sy stemConfig uration.AD SystemConf igurationS ession.Fin dLocalServ er()
at Microsoft.Exchange.InfoWor ker.Assist ants.Excha ngeServer. <>c__Displ ayClass2.< TryGetServ er>b__0()
at Microsoft.Exchange.Assista nts.Util.< >c__Displa yClass2.<C atchMeIfYo uCan>b__0( )
--- End of inner exception stack trace ---
at Microsoft.Exchange.Assista nts.Util.C atchMeIfYo uCan(Catch Me function)
at Microsoft.Exchange.InfoWor ker.Assist ants.Excha ngeServer. TryGetServ er(). 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-GroupPol icy
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!
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 MSEXCHANGEADTOPOLOGYSERVIC
The query was for the SRV record for _ldap._tcp.dc._msdcs.domai
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_dc
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.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Autodis
at Microsoft.Exchange.Autodis
Log Name: Application
Source: MSExchangeMailboxAssistant
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.Assista
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.InfoWor
at Microsoft.Exchange.Assista
--- End of inner exception stack trace ---
at Microsoft.Exchange.Assista
at Microsoft.Exchange.InfoWor
I also receive this error in the System log:
Log Name: System
Source: Microsoft-Windows-GroupPol
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!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks suppsaws, that looks like it may work. I installed the fix and will reboot tonight and see what happens. Will keep you posted.
ASKER
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.
expect the store to use as much ram as it can
this is by design
this is by design
ASKER
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.
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?
I am only running 4GB of ram on this server though, would this be the problem?
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=2102&EvtSrc=MSExchange+ADAccess&LCID=1033
and this for 2121
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=2121&EvtSrc=MSExchange+ADAccess&LCID=1033