- Exchange
- Windows Server 2012
- Microsoft IIS Web Server
Exchange 2013 just stopped receiving emails
I installed windows updates this morning and right after that, exchange now longer is receiving emails. Outbound is fine. Here's what I did so far.
1. Rebooted the server twice.
2. Individually restarted the transport and IS services.
3. I checked to make sure the databases are mounted.
4. I can log into the ECP just fine, all receive and outbound connectors are there.
5. Checked on mxtoolbox, and everything is fine, no DNS changes made.
6. I checked my firewall, and it's receiving the external emails and it's passing the email to exchange.
Short of uninstalling the windows updates, not sure what else to do.
1. Rebooted the server twice.
2. Individually restarted the transport and IS services.
3. I checked to make sure the databases are mounted.
4. I can log into the ECP just fine, all receive and outbound connectors are there.
5. Checked on mxtoolbox, and everything is fine, no DNS changes made.
6. I checked my firewall, and it's receiving the external emails and it's passing the email to exchange.
Short of uninstalling the windows updates, not sure what else to do.
now after trying to click on different options in the event viewer, I get this message
![get exchange]()
Has anyone encountered this strange behavior before?
Has anyone encountered this strange behavior before?
You are having issue with the transport services. Are they up and running? Did you change any IP address?
I ran this test: https://testconnectivity.microsoft.com
And here's where it failed, and the error it gave me.
Additional Details
The server returned status code 451 - Error in processing. The server response was: Temporary local problem, please try again!
Exception details:
Message: Error in processing. The server response was: Temporary local problem, please try again!
Type: System.Net.Mail.SmtpExcept
Stack trace:
at System.Net.Mail.DataStopCo
at System.Net.Mail.DataStopCo
at System.Net.Mail.SmtpClient
at Microsoft.Exchange.Tools.E
Elapsed Time: 1698 ms.
And here's where it failed, and the error it gave me.
Additional Details
The server returned status code 451 - Error in processing. The server response was: Temporary local problem, please try again!
Exception details:
Message: Error in processing. The server response was: Temporary local problem, please try again!
Type: System.Net.Mail.SmtpExcept
Stack trace:
at System.Net.Mail.DataStopCo
at System.Net.Mail.DataStopCo
at System.Net.Mail.SmtpClient
at Microsoft.Exchange.Tools.E
Elapsed Time: 1698 ms.
yes, the transport service is up and running, and no, I have not made any changes to any IP addresses on the server
I have restarted the transport service manually as well 3 or 4 times
I have restarted the transport service manually as well 3 or 4 times
Outgoing is working but incoming is not. Sounds like BackPressure.
Check your drive space. If you are running out of space, Exchange will protect itself by no allowing incoming emails.
Look in your Application Logs for 15004, 15005, 15006, and/or 15007. If you see those then it's backpressure. You'll need to free up space.
Also make sure all Exchange services are running.
Check your drive space. If you are running out of space, Exchange will protect itself by no allowing incoming emails.
Look in your Application Logs for 15004, 15005, 15006, and/or 15007. If you see those then it's backpressure. You'll need to free up space.
Also make sure all Exchange services are running.
Try rebooting the Exchange server. Sometimes an update will be installed, but sort of hangs Exchange until a reboot is performed and the update can finish installing.
Try this:
go to this folder: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\
You will see a folder called "Queue"
Rename that folder and reboot both transport services and see if it works
go to this folder: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\
You will see a folder called "Queue"
Rename that folder and reboot both transport services and see if it works
I have over 200GB of space on my C drive and over 500GB of free space on my E drive, database drive
alll services are running
Checking event viewer now
alll services are running
Checking event viewer now
With that much free space it isn't backpressure then. What version and patch level are you at?
Run "Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion" in and Exchange PS command window.
You should be at least CU17 or CU18.
Run "Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion" in and Exchange PS command window.
You should be at least CU17 or CU18.
At this point I'd remove the Windows Updates and see if that has any effect. Windows updates have been known to break Exchange every now and then.
What .NET version are you running?
What .NET version are you running?
when I type that command, I get this error: "the term 'get-exchangeserver' is not recognized as the name or operable program"
Did you try this?
go to this folder: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\
You will see a folder called "Queue"
Rename that folder and reboot both transport services and see if it works
go to this folder: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\
You will see a folder called "Queue"
Rename that folder and reboot both transport services and see if it works
Im seeing event ID 40025 numerous times in my app log, even before I did the windows updates. Is that a reason to be concerned?
I just tried that, and a new queue folder was automatically created.
I'm waiting now to see if emails start coming in, nothing yet, but it's only been about 1 min.
I'm waiting now to see if emails start coming in, nothing yet, but it's only been about 1 min.
I opened the queue-viewer and i get this message: "the term get-queue is not recognized as the name of a cmdlet, etc......
I think something is wrong in your transport services. I had this issue before.
Here is what you need to check
1- Are you using IMAP or POP3 services? if you do then check the binding of those services and make sure you have the right IP address.
2- Check your SMTP connectors see if you have different IP address.
3- Check the DNS as well, on the ECP panel go to Server>Server>Double click to name of the server DNS lookup and also IMAP and POP3.
But honestly you problem it's your transport rule
Here is what you need to check
1- Are you using IMAP or POP3 services? if you do then check the binding of those services and make sure you have the right IP address.
2- Check your SMTP connectors see if you have different IP address.
3- Check the DNS as well, on the ECP panel go to Server>Server>Double click to name of the server DNS lookup and also IMAP and POP3.
But honestly you problem it's your transport rule
So I ran this command: Add-PSSnapin Microsoft.Exchange.Managem
and that allowed me to actually type the get- commands
Why is this happening, as I ran across this at least 3 or 4 months ago, and it's been happening now for over a year now.
I'm running the standard edition
Version 15.0 (build 1156.6)
and that allowed me to actually type the get- commands
Why is this happening, as I ran across this at least 3 or 4 months ago, and it's been happening now for over a year now.
I'm running the standard edition
Version 15.0 (build 1156.6)
Login to the ECP Servers>Name of the server>DNS lookup> and you will see the IP address binding the ports.
Do the same with IMAP and POP3
Do the same with IMAP and POP3
in ECP, under servers, after I edit my server, both pop3 and imap4 , have "all available IPv4 and IPv6" for TLS and SSL for the connections
under DNS lookups, for both external and internal, it just says "all network adapters, all available IPv4"
User your internal dns 192.168.1.2
External 8.8.8.8
On imap use your exchange IP.
Same if pop3
Also check all your incoming connectors make sure they span your exchange server.
External 8.8.8.8
On imap use your exchange IP.
Same if pop3
Also check all your incoming connectors make sure they span your exchange server.
I looked into the message tracking log and here's a snippit of it, what is a shadow server?
I looked at the other logs and this started right after windows updates today
#Software: Microsoft Exchange Server
#Version: 15.00.1156.000
#Log-type: Message Tracking Log
#Date: 2017-11-02T18:00:40.526Z
#Fields: date-time,client-ip,client
2017-11-02T18:00:40.526Z,,
2017-11-02T18:00:40.635Z,1
2017-11-02T18:00:40.713Z,,
2017-11-02T18:00:44.932Z,,
2017-11-02T18:00:45.107Z,1
2017-11-02T18:00:45.135Z,,
2017-11-02T18:00:45.135Z,,
2017-11-02T18:00:45.198Z,,
2017-11-02T18:00:45.244Z,1
2017-11-02T18:00:45.276Z,,
2017-11-02T18:00:45.309Z,,
2017-11-02T18:00:46.229Z,,
2017-11-02T18:00:46.338Z,1
2017-11-02T18:00:46.385Z,,
2017-11-02T18:01:08.463Z,,
2017-11-02T18:01:08.572Z,1
2017-11-02T18:01:08.651Z,,
2017-11-02T18:02:04.963Z,,
2017-11-02T18:02:05.088Z,1
2017-1
I looked at the other logs and this started right after windows updates today
#Software: Microsoft Exchange Server
#Version: 15.00.1156.000
#Log-type: Message Tracking Log
#Date: 2017-11-02T18:00:40.526Z
#Fields: date-time,client-ip,client
2017-11-02T18:00:40.526Z,,
2017-11-02T18:00:40.635Z,1
2017-11-02T18:00:40.713Z,,
2017-11-02T18:00:44.932Z,,
2017-11-02T18:00:45.107Z,1
2017-11-02T18:00:45.135Z,,
2017-11-02T18:00:45.135Z,,
2017-11-02T18:00:45.198Z,,
2017-11-02T18:00:45.244Z,1
2017-11-02T18:00:45.276Z,,
2017-11-02T18:00:45.309Z,,
2017-11-02T18:00:46.229Z,,
2017-11-02T18:00:46.338Z,1
2017-11-02T18:00:46.385Z,,
2017-11-02T18:01:08.463Z,,
2017-11-02T18:01:08.572Z,1
2017-11-02T18:01:08.651Z,,
2017-11-02T18:02:04.963Z,,
2017-11-02T18:02:05.088Z,1
2017-1
in regards to the pop3 and imap4 sections, shouldn't those just be "all available IP addresses", as I think that's setting who has access to email the exchange server, right?
![pop3]()
sweet, after I added the DNS entries, emails are now coming in, but I had not seen that, and restarted the server, ouch :(
Oh well, at least I believe it's fixed, I'll see what happens after the restart.
Oh well, at least I believe it's fixed, I'll see what happens after the restart.
yes, thanks, it's working now, but the problem is, all the emails from 6 am to 11:50 am are gone, how do I get all those emails people sent us to come in?
Emails have a 1 hour TTL to be delivered. If it doesn't reach the destination will be dropped.
So you won't get those email.
Now what I can recommend to you is eat a third party email continuity and filter to hold your emails if it something happen to your exchange.
This company provides good service.
Securense.com
So you won't get those email.
Now what I can recommend to you is eat a third party email continuity and filter to hold your emails if it something happen to your exchange.
This company provides good service.
Securense.com
so besides they check for viruses, I suppose we can have them store our emails for days/weeks, before they are deleted, just in case something like this happens again?
-
![]()
received a Solution
Issue accessing OWA Exchange 2013 -
![]()
wrote an Article
![]()
Exchange 2016: Insufficient access rights to perform the operation. Enabling Remote Mailbox.
-
![]()
created a Video
![]()
Exchange 2019 - Changing your URL's in Exchange
-
Explore Cloud Class® ![]()
70-662 - Deploying Microsoft Exchange Server 2010
Premium Content
You need an Expert Office subscription to comment.Start Free Trial