An attempt has been made to read too much data. The length {value} is too large to be read. [{value}{value}{value}{value}] (14)

Details
Product: Exchange
Event ID: 3177
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA03177
Message: An attempt has been made to read too much data. The length {value} is too large to be read. [{value}{value}{value}{value}] (14)
   
User Action
Stop and restart the message transfer agent (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. Check your drives and verify that core *.dat files are in the \Exchsrvr\Mtadata directories. The \Exchsrvr\Mtadata directory with *.dat files may be on more than one drive. Contact Microsoft Product Support Services for assistance.

Related:

An interoperability error occurred with entity {object name}. Session error: user data is too long. Maximum amount of data allowed {value}. Actual amount of data received {value}, Control block index {index name}. [{value}{value}{value}{value}] (14)

Details
Product: Exchange
Event ID: 1223
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA01223
Message: An interoperability error occurred with entity {object name}. Session error: user data is too long. Maximum amount of data allowed {value}. Actual amount of data received {value}, Control block index {index name}. [{value}{value}{value}{value}] (14)
   
Explanation
The diagnostics logging levels of the message transfer agent (MTA) Interface and Interoperability categories should be increased to create interoperability logs.These logs are text logs that consist of the binary contents of communication among MTAs in different sites and between MTA and client applications within a site. They are stored in the \Exchsrvr\Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.
   
User Action
To help Microsoft Product Support Services track down the problem, create log files. See Knowledge Base articles Q163032 and Q168906 for more information. To create Ap*.log files, in the Diagnostics Logging tab of the Server Properties dialog box, select MSExchangeMTA and set the logging level of the Interoperability and Interface categories to Maximum. To create Bf*.log files, set the logging level of the APDU and X.400 Service categories to Maximum.Save all MTA log files (mtadata\*.log), Event Viewer output, and database files. Contact Microsoft Product Support Services.You can enable text event log files (Ev*.log) by modifying the Registry. Contact Microsoft Product Support Services for assistance.

Related:

A resource limit has been reached when attempting to open an association. Number of sessions configured: {value}. [{value}{value}{value}{value}] (14)

Details
Product: Exchange
Event ID: 3120
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA03120
Message: A resource limit has been reached when attempting to open an association. Number of sessions configured: {value}. [{value}{value}{value}{value}] (14)
   
Explanation
The message transfer agent (MTA) may have stopped due to a resource shortage. The MTA is trying to add local resources for remotely hosted connectors, such as the Internet Mail Service or the MS Mail Connector.
   
User Action
When an installation has several gateways and connectors configured, additional resources may be required. You can modify the registry to avoid this resource shortage. Contact Microsoft Product Support Services for assistance.

Related:

Unable to initialize due to a bad configuration. Too many threads were requested. Number requested: {value}. Compile time maximum: {time}. Contact Microsoft Technical Support. [{value}{value}{value}{value}] (16)

Details
Product: Exchange
Event ID: 90
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA00090
Message: Unable to initialize due to a bad configuration. Too many threads were requested. Number requested: {value}. Compile time maximum: {time}. Contact Microsoft Technical Support. [{value}{value}{value}{value}] (16)
   
User Action
Stop and restart the message transfer agent (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. Check your drives and verify that core *.dat files are in the \Exchsrvr\Mtadata directories. The \Exchsrvr\Mtadata directory with *.dat files may be on more than one drive. Contact Microsoft Product Support Services for assistance.

Related: