Exchange Server 2007 Transport not working - Microsoft Exchange can't connect to the queue viewer server

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:

"C:\Users\Sysadmin>nslookup
Default Server:  UnKnown
Address:  fe80::2452:b628:555c:2950

>"

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?

Much appreciated

Rod
Craig RutherfordAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Craig RutherfordConnect With a Mentor Author Commented:
Hey guys, I've solved it.

Turns out IT WAS the Security System.

We have an Endpoint security running from our N.able system... endpoint is nothing but Panda Security for Exchange Servers.

I DID uninstall Panda but i found that one file, named "PSExTransportAgent.dll" was still in the system. After deleting it, Transport service wouldn't startup anymore. I then went to Exchange Management Shell and run a get-transportagent command - found a "Panda Security for Exchange Servers Routing Agent" in the list. I ran a "disable-transportagent "panda security for exchange servers routing agent"" command and the problem has been fixed.

Why this agent was blocking the port 25, I have no idea, I'm going to contact the manufacturer about this issue.

Thanks for the help anyways.
0
 
dhruvarajpCommented:
increase diagnostic logging for exchange transport
http://blogs.technet.com/b/ferris/archive/2010/05/03/howto-increase-the-logging-levels-in-exchange-2003-2007-and-2010.aspx 

This will give us at lides of what is going with transport

Thank you
Dhruv
0
 
Craig RutherfordAuthor Commented:
I have increased to medium level. Is it enough or should i change it to high or expert? I kind have only a few hours to troubleshoot this issue :-)
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
dhruvarajpCommented:
ok.. yes do it to expert
ans restart the transport service
0
 
Craig RutherfordAuthor Commented:
done... there are aroung 40 events being loggeed every 20 seconds... all informational
0
 
Craig RutherfordAuthor Commented:
and they are the same events being logged before... should i be looking anywhere else other than the application log?
0
 
dhruvarajpCommented:
there are aroung 40 events being loggeed every 20 seconds... all informational..

i suspest these events tell that trasnport services started and stopped again

am i correct ?
0
 
dhruvarajpCommented:
what is the size of the  transport database ?
..
0
 
Craig RutherfordAuthor Commented:
it was huge... 1.4 gb ... but i renamed the queue folder so it would get recreated... it recreated fine, a brand new tiny database of 2mb (mail.que)... but it didnt solve the issue...

but look - did u see the item number 2? the fact that the tmp.edb keeps coming up and disappearing? yes I agree with you, i believe the service keeps restarting (even though when I refresh the services.msc, it doesnt show anything about a service being stopped and started)

any ideas?
0
 
dhruvarajpCommented:
i think the transport service is hitting the backpreasure

http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/understanding-back-pressure-feature-exchange-server-2007.html 

reaching the stage five.. again... and this is going in cycle

0
 
dhruvarajpCommented:
i guess a user is a culprit here.. you might not have the max message size limit.. and someone is trying to
send a huge email .. you have outbox full.. tansport service is not able to deal with the uncommted transcations in the database..

0
 
dhruvarajpCommented:
this is another article for backpreasure
http://technet.microsoft.com/en-us/library/bb201658(EXCHG.80).aspx 


Dhruv
0
 
Craig RutherfordAuthor Commented:
ill have a look at those articles... im sure I had the max message size limit size set... if it is the outbox issue, how can I fix it? login to each user to find out who has a big message in their outboxes?
0
 
dhruvarajpCommented:
aslo there might be client older that 2003 sp2 .. that does not reject emails larger they are allowed to send
.
0
 
dhruvarajpCommented:
if you have set the max size.. you have a clinet who has PRE outlook 2003 SP2

..
0
 
Craig RutherfordAuthor Commented:
everyone is on a terminal server with microsoft office 2003 sp3 :-)
0
 
dhruvarajpCommented:
all this is happening so quickly .. i am not sure
if your network trace will give hint of the ip address that is giving maximum connextions

you can try to take multiple network traces of the HUB server to look for the user ip address ..
once you figure the user.. disable mailbox
0
 
Craig RutherfordAuthor Commented:
maybe i should just login to every single user via OWA and check their outboxes... if there are no big messages there then I suppose we crossed one item out of the list of possibilities
0
 
Craig RutherfordAuthor Commented:
but if it was a backpressure, wouldnt an event id 15002 be logged?
0
 
Craig RutherfordAuthor Commented:
ive tried disabling backpressure... nothing
0
 
Craig RutherfordAuthor Commented:
I have checked every single user's mailbox... there are no stuck messages on outbox that are any  bigger than 50kb... and I have tried disabling backpressure and nothing... any other ideas?
0
 
dhruvarajpCommented:
hmm.. we need to take the dump of the transport exe and have msft analyze it and they will expalin what happned

0
 
Craig RutherfordAuthor Commented:
also, I have just tried disabling EVERY SINGLE mailbox but the administrator... restarted transport service, still nothing, e-mail won't leave the mailbox, new emails wont come in
0
 
Craig RutherfordAuthor Commented:
any ideas? im getting crazy here
0
 
Craig RutherfordAuthor Commented:
anyone??
0
 
nera2001Commented:
Thank you Black-Knight!
I had the same issue after deinstalling Spamfighter for Exchange and your Solution did it perfect also for me!

Thank you again!
0
 
ScottyControllerCommented:
After uninstalling Trend Micro Worry free from our SBS 2011 server I experienced the same issue.  This solution did it perfect for me

Thank you!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.