The mailbox for has exceeded the maximum mailbox size. This mailbox cannot send or receive messages.Incoming messages to this mailbox are returned to sender. The mailbox owner should be notified about thecondition of the mailbox as soon as possible.

Details
Product: Exchange
Event ID: 8528
Source: MSExchangeIS Mailbox Store
Version: 6.5.6940.0
Component: Microsoft Exchange Information Store
Message: The mailbox for <distinguished name> has exceeded the maximum mailbox size. This mailbox cannot send or receive messages.Incoming messages to this mailbox are returned to sender. The mailbox owner should be notified about thecondition of the mailbox as soon as possible.
   
Explanation

By design, a mailbox can be configured to limit or prohibit mailbox activity if limits are exceeded. You can modify the current setting on the Limits tab of a specific mailbox.

   
User Action

Modify the current storage limits on the Limits tab of the mailbox.

Related:

The service could not bind instance %1. The data is the error code.For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.

Details
Product: Exchange
Event ID: 115
Source: IMAP4SVC
Version: 6.5.0000.0
Message: The service could not bind instance %1. The data is the error code.For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
   
Explanation
This error may be seen in the application log after you configure and attempt to start additional virtual servers for the Simple Mail Transfer Protocol (SMTP), Post Office Protocol version 3 (POP3), or Internet Message Access Protocol Version 4 rev1 (IMAP4) services in Exchange 2000 Server. Also, the virtual servers that you added do not start.

This issue can occur because TCP/IP, which includes the SMTP, POP3, and IMAP4 protocols, requires a unique socket for each instance. A TCP/IP socket is composed of an Internet Protocol (IP) address and Transmission Control Protocol (TCP) port pair. To generate a unique socket, either the TCP port or the IP

address of each instance must be unique to the given virtual server.

   
User Action
Provide a unique IP address for each additional virtual server.

Related:

The Microsoft Exchange Mail Submission Service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.

Details
Product: Exchange
Event ID: 1009
Source: MSExchangeMailSubmission
Version: 8.0
Symbolic Name: NoActiveBridgeheadServer
Message: The Microsoft Exchange Mail Submission Service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
   
Explanation

This Warning event indicates that the computer that is running the Mailbox server role cannot submit messages to a computer that is running the Microsoft® Exchange Server 2007 Hub Transport server role. Additionally, there are Hub Transport servers in the same Active Directory® directory service site as the Mailbox server that can respond to the request. This event may occur if any of the following conditions is true:

  • The Microsoft Exchange Transport service is not running on a Hub Transport server.

  • The MAPI RPC connection is blocked between the Mailbox server and Hub Transport server.

  • The Hub Transport server has reached the maximum number of submission threads that the server can have open at the same time to send messages from mailboxes. This behavior may occur if the computer that is running the Mailbox server role has multi-processors and the computer that is running the Hub Transport server role is a single-processor. In this configuration, the Mailbox server may submit more e-mail traffic than the Hub Transport server can process.

In Exchange 2007, a new notification service called the Microsoft Exchange Mail Submission service runs on the mailbox server and notifies an available Hub Transport server in the same Active Directory site in which the service is running that messages are available for retrieval from a sender’s Outbox. The Microsoft Exchange Mail Submission service tries to distribute message submissions equally across all available Hub Transport servers that are available in the same Active Directory site in which the service is running.

The Microsoft Exchange Mail Submission service obtains a list of Hub Transport servers in the same Active Directory site as the mailbox from which a Store driver retrieves messages. A round-robin process determines which bridgehead server is notified. The store driver on the Hub Transport server that is notified retrieves the message and adds the message to the transport pipeline by putting it in the Submission queue on the Hub Transport server that was notified. If no bridgehead servers are available, messages cannot be added to the transport pipeline.

For more information, see Transport Architecture.

   
User Action

To resolve this warning, follow one or more of these steps:

  • Make sure that the Microsoft Exchange Transport Service is enabled and running on the Hub Transport server.

  • Make sure that no firewalls filter network data or block MAPI remote procedure call (RPC) traffic between the Mailbox server and Hub Transport server.

  • Make sure that the Mailbox server and the Hub Transport server are not deployed in a perimeter network.

  • If this frequently occurs, consider whether you should add more processors on the Hub Transport server. You can also increase the value of MaxConcurrentMailboxSubmissions by using the Set-TransportServer cmdlet. For more information, see Set-TransportServer.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

The search index files for Mailbox Database %1 (GUID = %2) are invalid. They will be deleted and recreated in %3 minutes or soon after the Microsoft Exchange Search Indexer service is restarted.

Details
Product: Exchange
Event ID: 113
Source: MSExchange Search Indexer
Version: 8.0
Symbolic Name: InvalidMDBSearchIndex
Message: The search index files for Mailbox Database %1 (GUID = %2) are invalid. They will be deleted and recreated in %3 minutes or soon after the Microsoft Exchange Search Indexer service is restarted.
   
Explanation

This Warning event indicates that the search index files for a mailbox database are too old and will be deleted. The event description will state the mailbox database GUID and will state how many minutes remain before the search index files are deleted. The index files for a mailbox database will be deleted when the following is true:

  • The index is disabled on the mailbox database for more than seven days

  • Exchange Search service is turned off for more than seven days

  • The database is restored from an older backup

When the warning occurs, online mode searches for mailboxes on the affected mailbox database may take longer to return results until the index files are recreated. The event could be caused because of the following:

  • The store is down

  • The mailbox database is offline or dismounted

  • The Exchange server is down

   
User Action

To resolve this warning, do nothing–wait until the index is recreated. After %3 minutes (the length of time stated in the event description), be aware that Exchange Search will be busy crawling the mailbox database and CPU usage should be high.

In Exchange Management Shell, run the command test-exchangesearch to verify that Exchange Search is enabled and is searching emails for a user mailbox in the mailbox database. For more information about how to run the command, see Test-ExchangeSearch.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Object with directory name {directory name} does not have a CCMAIL e-mail address and will not be added to the Lotus cc:Mail directory.

Details
Product: Exchange
Event ID: 77
Source: MSExchangeCCMC
Version: 6.0
Component: Connector for Lotus cc:Mail
Symbolic Name: MSG_DIRSYNC_NO_CCPROXY
Message: Object with directory name {directory name} does not have a CCMAIL e-mail address and will not be added to the Lotus cc:Mail directory.
   
User Action
Verify that the mailboxes are configured correctly. Review the E-mail Addresses property page of this mailbox. Verify that Ccmproxy.dll files are present and that the mailbox has a valid Lotus cc:Mail address.

Related:

The Microsoft Exchange entry with CCMAIL e-mail address {name} at {address} could not be written to Lotus cc:Mail because it conflicts with an existing Lotus cc:Mail post office named {name}. Choose a unique name and update the CCMAIL e-mail address.

Details
Product: Exchange
Event ID: 67
Source: MSExchangeCCMC
Version: 6.0
Component: Connector for Lotus cc:Mail
Symbolic Name: MSG_DIRSYNC_CCMAIL_PO_EXISTS
Message: The Microsoft Exchange entry with CCMAIL e-mail address {name} at {address} could not be written to Lotus cc:Mail because it conflicts with an existing Lotus cc:Mail post office named {name}. Choose a unique name and update the CCMAIL e-mail address.
   
User Action
Verify that the mailbox is configured correctly. Review the E-mail Addresses property page of this mailbox. Verify that Ccmproxy.dll files are present and that the mailbox has a valid Lotus cc:Mail address.

Related: