Archive for December, 2017

How To Fix Exchange Content Indexing in “Crawling” or “Failed” State

December 28, 2017 No comments

Identify the databases affected by running one the cmdlets below:

1. ID only “crawling”

ID generic, anything other than healthy like “Failed”:

2. Stop and restart the “Microsoft Exchange Search Indexer” Service
3. Run the command to start resyncing content on the confirmed database:

Categories: Uncategorized Tags:

432 4.3.2 STOREDRV.Deliver; recipient thread limit exceeded

December 12, 2017 No comments

E-mail delays? Its likely throttling is occuring.
– Check connectivity logs under transport log folder

Error reporting 432 4.3.2 STOREDRV.Deliver; recipient thread limit exceeded.

Add the following code to EdgeTransport.exe.config file located in C:\Program Files\Microsoft\Exchange server\V14\Bin

Restarted the Hub Transport service, wait a few seconds. +1 as needed, Microsoft Support did not recommend anything higher than 7.
I suggest cycling Hub Transport services as needed to flush out any remaining emails queued up.

Additionally, you can check MMC > Queue Viewer for any corrupt e-mails by setting filter for Status = Active.
This will display all the e-mails that are actively being processed by the server, by hitting F5 or refreshing you can identify the e-mails in question (corrupt or poisioned?).

If adding the values did not help, You can use exterme mesures to flushing out e-mails, by adding the following code to EdgeTransport.exe.config:

Restarted the Hub Transport service, wait a few seconds. Once the queue has flushed, return the values to the original or recommended above.

Categories: Uncategorized Tags:

ID messages queued in submission.

December 8, 2017 No comments

Categories: Uncategorized Tags: