Exchange problems 2003 small business server
I have had a client server that has been teetering on the edge for a while, they have been avoiding upgrade for three years with no real maintenance being performed.
last week they had networking issues that appeared to be due to spanning tree, but turned out to be power related (dont ask) in the process of trying to resolve I shut the server down to install a new nic and it never came back up as the PSU had died (one of a pair of hot swaps, the other having died a few months ago and nobody thought to replace it?)
once the server was back online I have looked at it remotely and the exchange data bases where not mounting due to being corrupt, so when through all possible checks etc before running eseutil /p which completed successfully on both priv1 and pub. In order to get eseutil to run properly for the pub1.edb I had to install a hotfix. when the repair was done I tried to mount the Stores but the exchangeinformationstore service would not start, so went through the task of removeing all patches and rerunning SP2 install and all windows updates etc but now even though the stores are now mounted and I can connect on OWA and view all mail etc I can not send? mail goes into the draft or outbox folder and that is where it stays. server has been restarted plenty of times, I have rerun the connect to internet wizard but I can still not send?
the server does also have GFI mailsecurity and GFI mail essentials installed but nothing should have been changed.
I have tried looking at message tracking on exchange but it will not run "tracking database not available or message already left" tracking is enabled and I have checked permission on the log folder?
I have tried to telnet to the server on port 25 (firewall off) but I get "could not open connection to host" SMTP service is running?
last week they had networking issues that appeared to be due to spanning tree, but turned out to be power related (dont ask) in the process of trying to resolve I shut the server down to install a new nic and it never came back up as the PSU had died (one of a pair of hot swaps, the other having died a few months ago and nobody thought to replace it?)
once the server was back online I have looked at it remotely and the exchange data bases where not mounting due to being corrupt, so when through all possible checks etc before running eseutil /p which completed successfully on both priv1 and pub. In order to get eseutil to run properly for the pub1.edb I had to install a hotfix. when the repair was done I tried to mount the Stores but the exchangeinformationstore service would not start, so went through the task of removeing all patches and rerunning SP2 install and all windows updates etc but now even though the stores are now mounted and I can connect on OWA and view all mail etc I can not send? mail goes into the draft or outbox folder and that is where it stays. server has been restarted plenty of times, I have rerun the connect to internet wizard but I can still not send?
the server does also have GFI mailsecurity and GFI mail essentials installed but nothing should have been changed.
I have tried looking at message tracking on exchange but it will not run "tracking database not available or message already left" tracking is enabled and I have checked permission on the log folder?
I have tried to telnet to the server on port 25 (firewall off) but I get "could not open connection to host" SMTP service is running?
RMOMCSE
Verification: users can receive e-mail, but not send?
are you using a smart host to send and also is your external firewall locked down to the IP of the server, in the process have you changed the Ip addresses of your seerver, try telneting off your server to the smart host and see if the problem is there.
Right back to basics.
1. I the SMTP Service running? (Windows Services)
if yes
2. Is the SMTP Virtual Server in Exchange System Manager enabled?
if yes
3. Is the SMTP Virtual Serve bound to the correct IP Address (Properties of SMTP virtual server)
if no to any of the above correct and try again. you are on the right track testing by telnetting to port 25.
1. I the SMTP Service running? (Windows Services)
if yes
2. Is the SMTP Virtual Server in Exchange System Manager enabled?
if yes
3. Is the SMTP Virtual Serve bound to the correct IP Address (Properties of SMTP virtual server)
if no to any of the above correct and try again. you are on the right track testing by telnetting to port 25.
ASKER
RMOMCSE:
No not sending or receiving.
IntegrityOffice:
using DNS to route
I am not ablt to telnet to the server on 25 to confirm that exchange SMTP is up but suspect this is due to GFI
aoakley
1. Yes
2. No : tried start but get - the service has returned a service-specific error code (shown below)
Virtual Server 1: The specified mail queue directory is not valid. Cannot start the SMTP Service.
3. No : the smtp wa bound to All unassigned. tried changing it to the LAN IP of the server but same message?
No not sending or receiving.
IntegrityOffice:
using DNS to route
I am not ablt to telnet to the server on 25 to confirm that exchange SMTP is up but suspect this is due to GFI
aoakley
1. Yes
2. No : tried start but get - the service has returned a service-specific error code (shown below)
Virtual Server 1: The specified mail queue directory is not valid. Cannot start the SMTP Service.
3. No : the smtp wa bound to All unassigned. tried changing it to the LAN IP of the server but same message?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
aoakley:
looks like the queue folder got corrupted when the databases fell over and was showing up as an unknown file. renamed it and created a new folder and all working OK
Great call and thanks for your help... its always the littlest things that cause the most grief :D
looks like the queue folder got corrupted when the databases fell over and was showing up as an unknown file. renamed it and created a new folder and all working OK
Great call and thanks for your help... its always the littlest things that cause the most grief :D