Well, this should be quite the question... I'm pretty green to Exchange overall. I came from a company that had a hosted mail solution and I haven't tinkered with exchange since 2003. So here's what I have going on:
- We're currently running SBS 2011 with Exchange 2010.
- Exchange was using every last bit of memory resources
- I edited the min and max values for how much memory exchange could have based on the instructions here: http:/
NOTE: Its important to note here that I had to add a configuration for my server, the configuration wasn't there to begin with. I'm actually thinking this may be where all of this started to break down...
- I then restarted all of the exchange services so that the memory would free up and the new settings would take effect
- Upon services coming back online, I sent a quick email from outside of our domain to my exchange mailbox and it went through without issue....except that now no mail is coming through
- I checked the event logs to see if I could figure out why exchange stopped sending or receiving mail and I get the following error:
Error: 12014
Microsoft Exchange could not find a certificate that contains the domain name [domain name].com in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Windows SBS Internet Send [Server name] with a FQDN parameter of [domain name]. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.
To fix this error I follow the instructions found here: http:/
- Restarted the exchange services for all new settings to take effect
- Upon restart I do not get any additional 12014 errors...however I still can't send or receive mail
- I glean event viewer again and see that now I'm getting these errors...
Error: 5015
Microsoft Exchange cannot find a route to the source transport server or home MTA server CN=Microsoft MTA\0ADEL:4c34303a-3828-44b0-8ff2-ef3a14134d3e,CN=Deleted Objects,CN=Configuration,DC=[DC name],DC=local for connector CN=Windows SBS Company Web Connector [OLD DOMAIN CONTROLLER],CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=[Domain Name],CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=[Domain Name],DC=local in routing tables with timestamp 8/22/2013 4:33:36 PM. Microsoft Exchange is ignoring the source transport server
So I'm a bit lost to say the least. To throw out a few educated guesses...
- I added a new configuration to ADSI. The only values I messed with were the values indicated in the article above (min/max buffer settings for exchange). I've since deleted the entire configuration (remember it wasn't there to begin with) to make sure AD isn't trying to read from some bad entries or something like that.
- Nothing changed with any network devices. No firewall changes were made, no updates or maintenance of any kind have taken place. So I do not believe this is a network related issue...
Anyone have any idea how I can troubleshoot this further?