travishemi
asked on
Emails sit in the Q
I am running Exchange 2007 on Server 2003, Also have a BES server on the network. Everyone can connect to thier store but emails just sit in the Queue and arent realeased. I have 3 error that poped up "Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site", "ScHasServerExpired returned error", and "Microsoft Exchange OLEDB was unable to do Schema propagation on MDB startup HRESULT = 0x80040e19. This is a Live Exchange server and anyhelp would be appreciated.
My first thought is that you appear to be having trouble pulling information out of Active Directory. All the information you are erroring out on is provided via AD. Is the local Domain controller up? Does it have a Global catalog role configured in AD Sites and Services? Have you attempted to run DCDIAG and NETDIAG on your server to verify connectivity to the domain?
PS. Its typically good practice to anonymize your information posted to ensure that you don't inadvertently post information that could be used to exploit your organization.
PS. Its typically good practice to anonymize your information posted to ensure that you don't inadvertently post information that could be used to exploit your organization.
ASKER
no errors on dcdiag and on netdiag I get
DNS test fail
Could not open file c:\windows\system32\config \netlogon. dns
Also at approx. the same time there is a DNS error Event ID 409
The DNS server list of restricted interfaces contains IP addresses that are not configured for use at the server computer.
Use the DNS manager server properties, interfaces dialog, to verify and reset the IP addresses the DNS server should listen on. For more information, see "To restrict a DNS server to listen only on selected addresses" in the online Help.
The last time that error showed up (4 1/2 months ago) was the last time Exchange started acting up but it resolved itself
DNS test fail
Could not open file c:\windows\system32\config
Also at approx. the same time there is a DNS error Event ID 409
The DNS server list of restricted interfaces contains IP addresses that are not configured for use at the server computer.
Use the DNS manager server properties, interfaces dialog, to verify and reset the IP addresses the DNS server should listen on. For more information, see "To restrict a DNS server to listen only on selected addresses" in the online Help.
The last time that error showed up (4 1/2 months ago) was the last time Exchange started acting up but it resolved itself
Based on that I would expect you are having an issue with your DNS server which is why you are unable to access Active directory. It sounds like at some point your DNS server was limited down to asingle IP address but that IP is not bound to any interfaces so theserver is effectilvely no longer answering requests.
Based on the error message you reported here is a link to the appropriate Microsoft support article on how to resolve the DNS issues:
http://support.microsoft.com/kb/326911
I would suggest resolving that issue then running the following on a command prompt:
net stop netlogon
net start netlogon
That will make sure you DC is registered successfully in DNS. I would then try my Exchange server and verify that the queues are starting to empty. If that doesn't resolve it you will likely need to bounce the Exchange topology service though typically I would just suggest a straight up reboot to ensure everything is cleaned up.
Based on the error message you reported here is a link to the appropriate Microsoft support article on how to resolve the DNS issues:
http://support.microsoft.com/kb/326911
I would suggest resolving that issue then running the following on a command prompt:
net stop netlogon
net start netlogon
That will make sure you DC is registered successfully in DNS. I would then try my Exchange server and verify that the queues are starting to empty. If that doesn't resolve it you will likely need to bounce the Exchange topology service though typically I would just suggest a straight up reboot to ensure everything is cleaned up.
ASKER
tried the solution but didnt work, still same error
Are there any errors in your System or Application log related to Exchange? Have you run the Exchange 2007 mail flow troubleshooting tool? You can reach it via the Tools menu in the Microsoft Exchange Console.
I see several additional references to bouncing the Information Store to rebuild the schema public folder tree. Have you stopped and restarted the Exchange Information Store service since the problem developed or rebooted the server?
ASKER
The errors I am getting other than the DNS is the ones above in the original post
Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site",
1. I have stopped and restarted information store
2. I have restarted but AD server and Exchange server
3. I have uninstalled my NIC card and reinstalled it on the exchange server (was getting error about incorect setup, they are now gone)
4. Forced replication between the AD server and the Exchange server and was successful.
5. Stopped start DNS
6. checked and confirmed setup of both servers IP configuration
I have ran the mail flow troubleshooting and get the following 2 errors
1. Messages in "Local Delivery" queue are in retry
2. Messages pending local delivery
Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site",
1. I have stopped and restarted information store
2. I have restarted but AD server and Exchange server
3. I have uninstalled my NIC card and reinstalled it on the exchange server (was getting error about incorect setup, they are now gone)
4. Forced replication between the AD server and the Exchange server and was successful.
5. Stopped start DNS
6. checked and confirmed setup of both servers IP configuration
I have ran the mail flow troubleshooting and get the following 2 errors
1. Messages in "Local Delivery" queue are in retry
2. Messages pending local delivery
ASKER
I get this message on the AD server right before i get the DNS 409 error
The DNS server could not signal the service "NAT". The error was 1168.
The DNS server could not signal the service "NAT". The error was 1168.
ASKER
Just wanted to say thanks for your help, DNS wasnt the answer but it led me down the right path to find out that the Exchange server had lost all permissions to access the transports and that is why DNS was failing.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Request
Url: https://mail.pronghorncontrols.ca:443/owa/default.aspx
User host address: 207.229.10.150
Exception
Exception type: Microsoft.Exchange.Data.St
Exception message: Cannot open mailbox /o=PRONGHORN/ou=First Administrative Group/cn=Recipients/cn=mho
Call stack
Microsoft.Exchange.Data.St
Microsoft.Exchange.Data.St
Microsoft.Exchange.Data.St
Microsoft.Exchange.Data.St
Microsoft.Exchange.Data.St
Microsoft.Exchange.Data.St
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
System.Web.HttpApplication
System.Web.HttpApplication
Inner Exception
Exception type: Microsoft.Mapi.MapiExcepti
Exception message: MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=1010) Diagnostic context: ...... Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 6252 Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2008-07-09 03:01:50:16 Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 2 Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 1722 Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 390 Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 2 Lid: 8856 dwParam: 0x6BA Msg: EEInfo: prm[0]: Unicode string: exchange.pronghorn.local Lid: 8856 dwParam: 0x6BA Msg: EEInfo: prm[1]: Unicode string: EXCHANGE Lid: 23065 EcDoConnectEx called [length=73] Lid: 17913 EcDoConnectEx returned [ec=0x3F2][length=56][late
Call stack
Microsoft.Mapi.MapiExcepti
Microsoft.Mapi.ExRpcConnec
Microsoft.Mapi.ConnectionC
Microsoft.Mapi.ConnectionC
Microsoft.Exchange.Data.St