No email after reinstalling SMTP service in IIS on Ex2003 server

I must apologise first as I posted this question in the Windows Server forum and reallised that it is probably an Exchange issue if anything - sorry administrator.

I have an exchange 2003 server SP1 running on 2003 server domain controller (SP applied and removed as it stopped the exchange server sending internally or receiving)  - i know not best pratice!

I have noticed that whenever the server is rebooted incoming email was lost in the system.
This was resolved by restarting the SMTP virtual server in ESM when new email would be received and delivered correctly.
However any email received by the exchange server before the SMTP server was restarted would be lost with no NDR report.

So as it seemed to be an issue specific to the SMTP server i decided to reinstall it through Add/remove Programs, Windows Components, Application Server, IIS, SMTP Service.

The SMTP Server is now showing in ESM however now it is not possible to send email internally, externally or to receive email - although i can telnet email in.
Also the POP and NNTP servers do not start in ESM either.

I have reapplied Exchange Service Pack1 with no improvement and am beginning to face the prospect of reinstalling Exchange.

Any help with this would be gratefully received.

(max points available as this is urgent!)

Pete
petesulliAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

eatmeimadanishCommented:
Event log messages would help.  Unfortunatly many users are finding that there were problems with their exchange server that they were unaware of until they installed SP1.  It seems sp1 uncovers many of these.  The real delemna is this, do you want to patch the system and get it working again without facing the real issue, or do you want to nip this in the bud and fix it completely?  If I had to answer as if I was in your shoes:

I would backup the stores after stopping the services gently.  I would copy them off site and have at least two different methods of backup in addition to an entire system backup.  I would then (yes I said it) format and reinstall.  Remounting the stores and applying service pack 1.  This is alot of back work, but can be faster then troubleshooting a messy problem.  You may even want to consider uninstalling exchange and removing it from AD to start fresh.

If you can not suffer any more down time, try installing Exchange on another server some place (even a virtual machine if need be) and use that as a swing computer in order to reinstall the other.  
petesulliAuthor Commented:
Thanks for quick reply - I was afraid you would say that!

In the short term i would like to patch this as time is in v short supply atm but I see what you mean about a fresh install.

If i try and send email this is the typical message in the Application log.

Event Type:      Warning
Event Source:      MSExchangeMTA
Event Category:      X.400 Service
Event ID:      290
Date:            30/06/2005
Time:            21:02:54
User:            N/A
Computer:      ITWSERVER
Description:
A non-delivery report (reason code unable-to-transfer and diagnostic code unrecognised-OR-name) is being generated for message C=US;A= ;P=ITW Hi-Cone;L=ITWSERVER-050630183515Z-8. It was originally destined for DN:CN=MPRODGER,CN=RECIPIENTS,OU=HICONE,O=ITW HI-CONE§ (recipient number 1), and was to be redirected to . [MTA DISP:RESULT 16 136] (12)

Could it be something to do with DNS or corrupt addresses?
eatmeimadanishCommented:
This error also occurs in the situation where IIS was re-installed after the Exchange installation. When you re-install IIS the SMTP default Virtual Server for IIS is installed again, and this is causing a conflict with Exchange. At the moment you want to send or receive SMTP messages Exchange will use the IIS SMTP and this virtual server will not know what to do with the messages. So if you re-install IIS, also re-install Exchange server and its service packs to have the proper SMTP Virtual server again.  
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

petesulliAuthor Commented:
I have telneted localhost with the following reply:

ehlo
250-itwserver.HICONE01.CO.UK Hello [127.0.0.1]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250 OK


Compared with what should be there it looks like i'm missing a few verbs!
Is this just confirmation of a reinstall?
If so whats the best way to reinstall IIS before the Exchange reinstall - i.e. should i go through Add/remove Windows Components, Application Server and untick IIS, etc.?
eatmeimadanishCommented:
Yes.  Uninstall Exchange first.  Then IIS through windows components in Add/Remove.  Then install IIS.  Then install Exchange.  
petesulliAuthor Commented:
Just to clarify, can i not reinstall IIS and then reinstall Exchange?

Or must I uninstall Exchange, reinstall IIS and reinstall Exchange?

If so will the Exchange uninstall remove all components and edb data?

You can tell i'm getting nervous now!
eatmeimadanishCommented:
What you will want to do is copy the .edb and .stm files (off of the server if possible) but to a different directory after stopping the services.  Then you will want to uninstall exchange and delete it's directories (ONLY AFTER YOU MADE SURE YOU HAVE MULTIPLE BACKUPS). You will then uninstall IIS.  Then reinstall IIS following the method outlined by the exchange install.  Then you will install Exchange to a fresh new directory (make sure you keep the site name the same).  When this is done you will want to stop the exchange services.  Copy the backup of the .edb and .stm files back into the MDBDATA directory and then start Exchange and mount the stores.  This should get you up and running again.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
petesulliAuthor Commented:
Thanks for your help.

Its time to bite the bullet!!

Enjoy the points!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.