Update 6/15/2017: Added a clarification that .Net Framework 4.7 has shipped and that we are still validating this release with Exchange Server.
We wanted to post a quick note to call out that our ...
Updated Jul 01, 2019
Version 2.0
Blog Post
I updated to Exchange 2016 CU5 from CU1 and also got the latest .NET 4.7 Framework (Didn't know about this issue at the time).
I have an issue with is database content indexing and I cannot fix it. I've tried many methods available online but nothing works. I'm getting MSExchangeFastSearch warning ID 1010 (An operation attempted against a FAST endpoint exprienced an exception. This operation may be retried. Error details: Microsoft.Exchange.Search.Fast.PerformingFastOperationException: An Exception was received during a FAST operation. ---> System.ServiceModel.FaultException: error CS2001: Source file 'Temp\tmpBA4D.tmp' could not be found).
I have also noticed the ContentIndexState within EMS was set to unknown (missing registry file) for some reason after the CU5 update it had nuked the registry file needed for the status of my mailbox database indexing! So I had to recover it from a backup. I then changed the status to 3,3 which means database crawling (attempting to rebuild) but still getting MSExchangeFastSearch Event ID 1010 warnings in Event viewer.
Webmail users are unable to search their mailbox since it looks for the cached indexing folder on the Exchange server, also users who have Outlook set to online mode. Lucky for me not many people user webmail! So as a temporary fix for Outlook users I have enabled Cached mode, which downloads a copy of their mailbox the local disk and I then rebuilt the Index within Outlook. This will then look at the local copy of the mailbox for the Index content.
I have also experienced an Issue when I restarted the server the Microsoft Exchange Transport Service stopped working and would not start, turns out my Veeam truncated to many transaction logs? never happened before until I updated to CU5 and .NET 4.7 so I had to move the mail.que file to another disk and it then started working.
I wish I never bothered to update! I don't want to attempt to downgrade to .NET 4.6.2 in case it messes things up more (I will wait for an MS update to fix it). I presume the problems I am having are related to the .NET 4.7 update but I'm not sure. If any of you guys are experiencing similar problems since updating to .NET 4.7 please can you comment. Or even better if you have a solution to my problem without downgrading .NEt please comment.
- I've read you're issues but we also have an Exchange 2016 CU5 on Windows Server 2016 and it also did accidentally install the .NET 4.7 version. I've rebooted the machine and we have no issues. Nothing in the event viewer and all client connections are running well. I'm waiting for Microsoft to update this post and to finish checking before I revert the update because that will be a hassle for now and everything is working. I'm wondering if we're running into issues when updating to CU6.
- Hi Peter,
Thanks for you reply. I think the issue I have was nothing to do with the update as you said your mail server is working fine even with .NET 4.7 installed.
I think the issue may be with my mailbox database, so my plan is to dismount the database and stop the following services "MS Exchange Search Host Controller" and "MS Exchange Search" delete the content index cache from the root of the database folder and run a couple of switches using ESEUTIL to check for errors etc. and then re-mount the database and start both services, then see if the problem persists. If it does I will have to create a new mailbox database and move all my mailbox's over. then attempt to re-build the content index cache.