| Event Id | 4287 |
| Source | MSExchangeMTA |
| Description | An internal MTA error occurred. Contact Microsoft Technical Support. Error code=<error code> [<value> <value> <value> <value>] (14) |
| Event Information | According to Microsoft: CAUSE : This behavior can occur if you use Fully Qualified Domain Names (FQDN) or NetBIOS names to configure the connectors. RESOLUTION : To resolve this behavior, on both Exchange servers, configure the X.400 Connector to use the IP address of the remote MTA, and then restart both MTAs. This information from some newsgroups may help you: ------------------------------------------------------------------------------ The Microsoft Exchange Server disk may be full or a disk error may have occurred. The message transfer agent (MTA) service will stop if the disk is full. If the Microsoft Exchange Server disk is full, delete any unnecessary files. If you suspect a disk error, run Chkdsk. Verify that the \Exchsrvr\Mtadata directory exists. Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt. If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. ------------------------------------------------------------------------------ |
| Reference Links | Mail Not Flowing Through X.400 Connectors and Events 4282, 4283, 4284, 4287, 1209, and 1198 Occur |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.