Software

Ask something
Discussion Locked

Getting 4238 in Event Log

0 helpful
6 replies

by dstover

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are running Exchange Server 5.5 and are receiving tons of 4283, 9215, and 4282's in the event log relating to the MTA. Microsoft's support site does not seem to have much on these. Does anyone have any idea what is going on here? Have 3 X.400 connectors (1 to London).....

6 replies

by dklippert

The 400 connections are probably contributing to the problem, as you know. You don't mention your patch level, but one common thread in the literature is:

"Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5 Service Pack 3. This problem was first corrected in Exchange Server 5.5 Service Pack 4"

by dstover

I failed to mention we are at service pack 4 on Exchange. Could the problem be bandwith or a time issue? Our server is in Fort Worth, Texas....the other mail servers are in London, San Francisco, and Washington D.C.

by brasslet

You don't mention any operational problems (such as non-delivery of messages or excessive time to deliver).

Have you run the Performance Optimizer since adding your connectors? Forgetting to run this can lead to a lot of strange errors. Even if you have run PO, check registry setting at HKLM\System\CurrentControlSet\Services\MSExchangeMTA\Parameters\TCPIPControl blocks (assuming you're running X.400 over TCP/IP). In your case, the number should be at 40 (10 * number of X.400 connectors) + 10.

The only other thing that comes to mind is the possibility that your diagnostics logging for the MTA etc.. is turned up and you're seeing normal retries. If your bandwidth is suspect, as you mention, the MTA may need to retry every now and again to deliver

This discussion is closed to new replies.