Exchange Server 2007 Transport not working - Microsoft Exchange can't connect to the queue viewer server
Posted on 2010-08-26
Here is the situation:
I got a call this morning - client has stated that they can't send or receive e-mails.
On the client's outlook, the messages are just sitting on their outbox.
Server is a SBS 2008 with Exchange 2007 SP1 (but I have just updated to SP3 and didn't solve the issue). Server is using a HUB Transport
Here's what I have found and what has been done:
1. Microsoft Exchange Transport service starts up fine, no problems, no erros
2. under "C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\queue" I can see a file named "tmp.edb" coming and up and disappearing every second... you can see it, and all of sudden it disapeaprs, and it keeps going like that (even after creating a brand-new-empty-queue-folder)
3. Exchange Best Practices Analyzer doesn't say anything
4. When I open the Queue Viewer, I get the following error message: Microsoft Exchange can't connect to the queue viewer server on computer "SERVER.CONTOSO.LOCAL". Verify that the Microsoft Exchange Transport service is started. It was running command 'get-queue -ResultSize '1000' -ReturnPageInfo $true -SortOrder '+NextHopDomain' -SearchForward $true -BookmarkObject $null - BookmarkIndex '-1' -IncludeBookmark $false -server 'server.contoso.local'
5. Fix my network wizard doesn't detect a thing
6. Nslookup resolves the following:
Default Server: UnKnown
7. Cannot telnet from internal or external to port 25, to either SERVERNAME, LOCALHOST, IPADDRESS or 127.0.0.1
8. No required services are stopped
9. Server has been restarted several times
10. When the problem started, server was Exchange 2007 SP1. I have tried upgrading to SP3 and didn't make any difference
11. I have tried stopping msexchangetransport service, renaming both the "queue" folder and the whole "data" folder under "C:\Program Files\Microsoft\Exchange Server\TransportRoles" and restarting the service so it would recreate the database - issue still persist
12. I have performed database repair and defrag of the queue database using eseutil. nothing...
13. Removed Antivirus/Antispam etc altogether
14. Disabled Windows Firewall
15. Reapplied permission on transport folder
16. Restarted DHCP and DNS servers
17. Checked send connector settings - all ok
18. Run the "Exchange Troubleshooting Assistant"... the only error that comes up is the same one stated on number 4.
19. No errors on Application or System or DNS logs. Although, the Application logs are filling up (i mean, THOUSANDS) of the following event IDs (all Informational) - 17008, 17010, 16022, 300, 301, 4002, 102 and 1020 (all exchange transport related)
20. I have tried to uninstall and reinstall the hub transport role but it's grayed out
21. I have tried restoring the MsExchangeTransport.exe.config and MsExchangeTransport.exe files from previous versions. nothing...
Other than restoring the system from a backup and losing all e-mails they "sent" (the ones stuck on the outbox), what else can I do to fix the issue?