MTA issues, but fixed with restart of service?
From: TheSingingCat (meowmeowmeowmeow_at_meowmeowmeow.com)
Date: 11/22/04
- Next message: TheSingingCat: "Re: MTA issues, but fixed with restart of service?"
- Previous message: DennisC: "Question regarding Public folders in 5.5 and 2003"
- Next in thread: TheSingingCat: "Re: MTA issues, but fixed with restart of service?"
- Reply: TheSingingCat: "Re: MTA issues, but fixed with restart of service?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Nov 2004 22:11:05 GMT
In my on going trials and tribulations of exchange server mailbox migration,
I ran into an issue today that after moving a small sample of users over to
the new server (from 55 to 03), mail failed to be sent / received from them
(both internall and out).
I checked the event log and noticed a lot of Event IDs 270s and 290s and
2025s with the MTA service. I read a few Q articles about it and some
suggested that it was due to AV running, other suggestion was to restart the
MTA service. I disabled the AV, restarted the MTA and fired an external
message to myself @ the office. It arrived... "oh" I thought, "I guess it
was the AV, I better check out hte symantec site" but just for the heck of
it, I started the AV service again and repeated the message. This one came
in also... "huuuhhhh?"
Why would simply restarting the MTA after moving a couple of mailboxes over
from one server to another (in the same site) resolve this? And above that,
wth was the problem in the first place and will it happen again? I don't
want to have to restart the MTA several times a day if indeed there is a
deeper problem.
Does this make sense?
1---------
Event ID: 290 - MSExchangeMTA - Category: X.400 service
A non-delivery report (reason code transfer-failure and diagnostic code Omit
any diagnostic code) is being generated for message C=us;A=
;P=company;L=NTSERVER0411222147XN328X35. It was originally destined for
DN:/o=company/ou=CALGARY/cn=RECIPIENTS/cn=userid§ (recipient number 1), and
was to be redirected to . [MTA DISP:RESULT 19 136] (12)
2--------
Event ID: 2025 - MSExchangeIS Private - Category: Transport Delivering
The delivery of a message failed due to error 80040111. A non-delivery
report is being sent to the message's originator.
3--------
Event ID: 270 - MSExchangeMTA - Category: X.400 Service
A permanent error has occurred with Entity
/O=COMPANY/OU=CALGARY/CN=CONFIGURATION/CN=SERVERS/CN=NTSERVER/CN=MICROSOFT
PRIVATE MDB. Entity is a Message Object is a Normal Priority Message.
Object: 0600003C. Message ID: C=us;A=
;P=company;L=NTSERVER0411222147XN328X35 Content length: 5192, External
Trace information (first 100 bytes) =
3080638061801302555300006280130120000013064E4153434F5200003180800D3034313132323231343734375A8201008302060000000000,
PDU dump reference 22 [MTA SUBMIT 15 74] (14)
-------- This one sounds particularly bad doesn't it? -----------
There were no other errors in the event log, the server fires up fine,
people are able to access their mailbox, just stuff goes berzerkazoid when
they tried to send / receive. Any insight *greatly* appreciated here. I am
little hesitant now to do some big ass mailbox move in off hours only to
have my phone go crazy the next day.
Regards,
tsc
- Next message: TheSingingCat: "Re: MTA issues, but fixed with restart of service?"
- Previous message: DennisC: "Question regarding Public folders in 5.5 and 2003"
- Next in thread: TheSingingCat: "Re: MTA issues, but fixed with restart of service?"
- Reply: TheSingingCat: "Re: MTA issues, but fixed with restart of service?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
