Bravo 7555
asked on
sometimes email stops working
Hey guys,
Running a SBS08 box and it seems that at periodic times maybe once a month or once every other month email stops working for some odd reason. The fix is just to reboot the whole server and it comes right back up but I really am trying to figure out what its happening and if I can prevent that from happening. Any suggestions or has anyone experienced this before??
Running a SBS08 box and it seems that at periodic times maybe once a month or once every other month email stops working for some odd reason. The fix is just to reboot the whole server and it comes right back up but I really am trying to figure out what its happening and if I can prevent that from happening. Any suggestions or has anyone experienced this before??
Are there any errors or relevant events recorded in the event log at the time this happens? If so, please post the details.
ASKER
THis was the firs trigger;
Log Name: Application
Source: MSExchangeFDS
Date: 10/27/2010 9:09:33 PM
Event ID: 1003
Task Category: General
Level: Warning
Keywords: Classic
User: N/A
Computer: Nxxx.xxx.local
Description:
Process MSExchangeFDS.exe (PID=6840). Temporarily unable to connect to Active Directory to read configuration data for object OAB (60). Will wait for %5 seconds and retry.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeFDS" />
<EventID Qualifiers="32772">1003</E ventID>
<Level>3</Level>
<Task>1</Task>
<Keywords>0x80000000000000 </Keywords >
<TimeCreated SystemTime="2010-10-28T01: 09:33.000Z " />
<EventRecordID>533042</Eve ntRecordID >
<Channel>Application</Chan nel>
<Computer>xxx1.xxx.local</ Computer>
<Security />
</System>
<EventData>
<Data>MSExchangeFDS.exe</D ata>
<Data>6840</Data>
<Data>OAB</Data>
<Data>60</Data>
</EventData>
</Event>
than this followed 20 minutes later leading to multiples warnings for the next couple of hours until i rebotted
Log Name: Application
Source: MSExchange ADAccess
Date: 10/27/2010 9:23:54 PM
Event ID: 2121
Task Category: Topology
Level: Warning
Keywords: Classic
User: N/A
Computer: xxx.xxx.local
Description:
Process MSEXCHANGEADTOPOLOGYSERVIC E.EXE (PID=2736). Exchange Active Directory Provider found SRV records for domain controllers in domain htu.local.
The query was for the SRV record for _ldap._tcp.dc._msdcs.htu.l ocal
The following domain controllers were identified by the query:
njsrv01.htu.local
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
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange ADAccess" />
<EventID Qualifiers="32772">2121</E ventID>
<Level>3</Level>
<Task>3</Task>
<Keywords>0x80000000000000 </Keywords >
<TimeCreated SystemTime="2010-10-28T01: 23:54.000Z " />
<EventRecordID>533078</Eve ntRecordID >
<Channel>Application</Chan nel>
<Computer>xxx.xxx.local</C omputer>
<Security />
</System>
<EventData>
<Data>MSEXCHANGEADTOPOLOGY SERVICE.EX E</Data>
<Data>2736</Data>
<Data>xxx.local</Data>
<Data>_ldap._tcp.dc._msdcs .htu.local </Data>
<Data>x.xxx.local
</Data>
<Data> type in the command line:
hh </Data>
<Data>tcpip.chm::/sag_DNS_ tro_dcLoca tor_messag eHa.htm</D ata>
</EventData>
</Event>
Ideas?
Log Name: Application
Source: MSExchangeFDS
Date: 10/27/2010 9:09:33 PM
Event ID: 1003
Task Category: General
Level: Warning
Keywords: Classic
User: N/A
Computer: Nxxx.xxx.local
Description:
Process MSExchangeFDS.exe (PID=6840). Temporarily unable to connect to Active Directory to read configuration data for object OAB (60). Will wait for %5 seconds and retry.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeFDS" />
<EventID Qualifiers="32772">1003</E
<Level>3</Level>
<Task>1</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2010-10-28T01:
<EventRecordID>533042</Eve
<Channel>Application</Chan
<Computer>xxx1.xxx.local</
<Security />
</System>
<EventData>
<Data>MSExchangeFDS.exe</D
<Data>6840</Data>
<Data>OAB</Data>
<Data>60</Data>
</EventData>
</Event>
than this followed 20 minutes later leading to multiples warnings for the next couple of hours until i rebotted
Log Name: Application
Source: MSExchange ADAccess
Date: 10/27/2010 9:23:54 PM
Event ID: 2121
Task Category: Topology
Level: Warning
Keywords: Classic
User: N/A
Computer: xxx.xxx.local
Description:
Process MSEXCHANGEADTOPOLOGYSERVIC
The query was for the SRV record for _ldap._tcp.dc._msdcs.htu.l
The following domain controllers were identified by the query:
njsrv01.htu.local
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
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange ADAccess" />
<EventID Qualifiers="32772">2121</E
<Level>3</Level>
<Task>3</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2010-10-28T01:
<EventRecordID>533078</Eve
<Channel>Application</Chan
<Computer>xxx.xxx.local</C
<Security />
</System>
<EventData>
<Data>MSEXCHANGEADTOPOLOGY
<Data>2736</Data>
<Data>xxx.local</Data>
<Data>_ldap._tcp.dc._msdcs
<Data>x.xxx.local
</Data>
<Data> type in the command line:
hh </Data>
<Data>tcpip.chm::/sag_DNS_
</EventData>
</Event>
Ideas?
Looks like it might be trying to get the OAB from another computer. Have you ever had another DC or Exchange server in htu.local as well as this SBS box? I fancy something may not have been cleaned out properly if you have.
ASKER
No, this was a brand new domain that was built up.
What is an OAB?
What is an OAB?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hmmm...very good find!
I have one more question and I apologize if its sounds dumb in the statement I am pasting below, what does TDI mean? How do i know if Im using it?
I"f you are encountering any sort of connectivity issue that is only fixed through a reboot, and are running a program that uses TDI please install this hotfix"
I have one more question and I apologize if its sounds dumb in the statement I am pasting below, what does TDI mean? How do i know if Im using it?
I"f you are encountering any sort of connectivity issue that is only fixed through a reboot, and are running a program that uses TDI please install this hotfix"
TDI is a Transport Driver interface - a driver installed by some older firewalls - have you added any such software to SBS? TDI is being phased out and replaced by Windows Filtering Platform but MS have a patch for you if it is the TDI driver causing the problem. That patch is at: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961775&kbln=en-us and you should use the Vista version on SBS2008.
There is a guide to TDI at: http://www.komodia.com/index.php?page=tdi.html but it doesn't tell you what products use it. Have you added any significant anti-virus, firewall or other products to SBS?
There is a guide to TDI at: http://www.komodia.com/index.php?page=tdi.html but it doesn't tell you what products use it. Have you added any significant anti-virus, firewall or other products to SBS?
ASKER
It may be a result of the Trend Micro Worry Free Suite that is running on the server... that has a firewall agent as part of the suite
What do you think?
What do you think?
Yes, I think it's worth trying with Trend disabled- if only for diagnostic purposrs
ASKER
why would I need to disable Trend?
ASKER
I installed the hotfix last night and will update you in a week or so if the update worked.
ASKER
Its been over a month now and no issues (finger crossed).