?
Solved

Exchange 2003 mail receipt problem

Posted on 2006-11-09
13
Medium Priority
?
301 Views
Last Modified: 2008-01-09
After a corruption I managed to mount my mailbox store database and re-connect the mailboxes to the users. Though my configuration is same as before, we couldn't receive external emails. I tried to download our pop3 emails which are externally hosted using IGetMail as usual, but IGetMail gives a message "Cannot convert server name to an IP address. Possible incorrect server name" on a regular basis. It sometimes starts to download few emails and gets interrupted. The annoying thing is even those messages that managed to reach our exchange server couldn't be delivered to the corresponding client mailbox. (the clients use outlook 2003 in cached mode).

From the client software side, when we click send/receive we used to get MS Exchange Error, object couldn't be found. Then I set the offline address book to update automatically, then the error message disappeared, but the exchange receipt task hangs at 97%.

From our DC side I get "RPC communication error and LDAP failure". I've never troubleshoot these kind of errors.
 
My Exchange server is down for the past 6 days, please help me to resolve these problems ASAP. Who ever solves this problem will get all the 500 points.

Best Regards,
0
Comment
Question by:URWB
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 4
13 Comments
 
LVL 11

Expert Comment

by:NetoMeter Screencasts
ID: 17907923
Hi,
Are the Exchange services running? What error messages do you get in the event log?
Reinstalling the exchange server (the video bellow demonstrates the Exchange 2k reinstall but there is no difference for the E2k3 reinstall):

http://www.netometer.net/samples/reinstalle2k/step1/step1.html

Best Regards,

Dean
0
 

Author Comment

by:URWB
ID: 17908427
Thank you NetoMeter,

I reinstalled the exchange with no error messages perfectly. The problem came after I exported the mailboxes and reconnected to the server. The error messages are the ones I mentioned above.
0
 
LVL 11

Expert Comment

by:NetoMeter Screencasts
ID: 17908457
Your DC is a separate machine and you get errors on it too?

Can you doublecheck the IP settings for the Exchange and the DC?
It is a good idea to run DCDIAG and NETDIAG and post the erros here. Did you perform a telnet test - sending an email manually to the Exchange server like this:
http://www.netometer.net/samples/telnet/step1.html

Dean
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 

Author Comment

by:URWB
ID: 17908718
Dear Dean,

I did the dcdiag and netdiag test for both machines. The error I get (on exchange side) is on trust relationship and LDAP error. But after I do netdiag/fix from the exchange side and dcdiag/fix from the dc side the problem gets fixed. But the message delivering problem persists.

Rahel
0
 
LVL 11

Expert Comment

by:NetoMeter Screencasts
ID: 17908767
Well, let's eliminate at the beginning the client side and IGetMail from the problem.
First can you try to send and e-mail between the users internally using OWA?
If the emails are dispatched correctly then proceed with the telnet test. Telnet on port 25 to your exchange server and send manually a message to a user. Check from OWA  whether the message is delivered. After that check the message delivery from the Outlook client.

Dean
0
 

Author Comment

by:URWB
ID: 17913526
Now all MS exchange services start automatically and IGetMail downloaded all external emails. The problem now is the MS Exchange MTA service starts and then stops, notifying that some services start then stop. It must be due to it that the emails couldn't be delivered to individual mailboxes. Now we even can't exchange internal emails.

Do you have any idea on what to do?

Many thanks
0
 
LVL 11

Expert Comment

by:NetoMeter Screencasts
ID: 17914384
Raise the logging level for the MTA and post the errors in the Application log.

Dean
0
 

Author Comment

by:URWB
ID: 17924341
In the event viewer I get the following error message:

Product: Exchange
Event ID: 9405
Source: MSExchangeMTA
Version: 6.0
Component: Message Transport Agent
Symbolic Name: MTA09405
Message: An unexpected error has occurred which may cause the MTA to terminate. Error: {error code}. [{Value} {Value} {value}] (16)
0
 

Author Comment

by:URWB
ID: 17929169
It seems the experts abandoned my questions.

I managed to resolve one of the above problems (starting up the MSE MTA) by uninstalling then reinstalling the smtp service and exchange server 2003. Now locally we can exchange emails, but the external emails downloaded by IGetMail still don't reach the individual mailboxes. Also the local emails are also deleted automatically, after the arrival to the mailbox. May be these two problems have common issues, but couldn't trace it. With the pace I am fixing the problem now I don't think I will finish in a month time.

Can anyone save me from this hell?

Sembee, I normally see your exchange solutions and you are quick in replying them. I am a regular user of your site and I found your solutions very useful; would you please extend your helping hands on this issue too?

Thank you.
Rw
0
 

Author Comment

by:URWB
ID: 17945987
I solved the above problem by unchecking the option that prevents the emails to be left in local mailboxes to avoid duplication from IGetMail Administration window. Now all emails come and go through peacefully.

Many thanks and please close this question.
0
 

Author Comment

by:URWB
ID: 18137328
Please close the question. Thank you.
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 18177004
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Find out what you should include to make the best professional email signature for your organization.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
Suggested Courses

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question