Home ยป Exchange Server ยป The Action Can't Be Completed Because the File is Open in NodeRunner.exe

The Action Can't Be Completed Because the File is Open in NodeRunner.exe

On an Exchange Server 2013 server that is installed with the Mailbox server role, when you attempt to delete the files and folders for a database or database copy that has been removed, you may receive an error.

exchange-2010-removing-database-files-01

exchange-2010-removing-database-files-02

The action can’t be completed because the file is open in noderunner.exe

Inside the folders that previously contained the database you will see various subfolders and index files relating to search services.

exchange-2010-removing-database-files-03

The issue is that even though the database has been removed the search/index files are still locked by the noderunner.exe process and can’t be deleted.

Using Process Explorer we can see that noderunner.exe is a child process of the Microsoft Exchange Search Host Controller (HostControllerService) service.

exchange-2010-removing-database-files-04

exchange-2010-removing-database-files-05

To clear the file lock you can restart the HostControllerService service using PowerShell.

You should now be able to delete the files and folders successfully.

In my own scenario the HostControllerService began consuming a large amount of CPU for a short period of time after the restart, but then calmed down to normal levels again after a few moments.

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.
Category: Exchange Server

26 comments

  1. Aakash says:

    Thanks. This was useful.
    So what is the right way to delete the Exchange files after we remove the MB Database? Do you suggest restarting the host controller service all the time.

  2. Tim says:

    But you know what, the files will be generated later again!

    Pretty scary…I believe the FAST cache should be cleared somewhere but MS just didn’t release any information about it…

  3. Vant Seto says:

    The problem exists with the final release of Exchange 2013 Enterprise. Stop the service, delete the entire folder, start the service and the folder is recreated. You can’t get rid of these files.

  4. JeanLuc says:

    It appears with Exchange 2013 SP1..
    I deleted when the service was stopped. I’m afraid to look for process monitor.. may be it search these files again….

  5. Tom says:

    Paul, I’ve run into a similar issue, but I can’t perform a database reseed because it’s showing that a process has locked the edb file. The process that seems to have it locked is microsoft.exchange.store.worker.exe. I can’t seem to find a way to remove that lock. Tried restarting the service mentioned above, tried to restart the information store (after failing all DBs over), but it’s still showing it’s locked by the same process. I tried to rename the EDB file since it’s only 4GB, but it said the microsoft.exchange.store.worker.exe process had it locked. Any thoughts on removing that lock?

      • Tom says:

        I just tried your suggestion and it still wouldn’t reseed – the file remained locked by the store.worker.exe process. Bizarre! I finally got a reseed going by failing over all DBs and rebooting the server. Not much of a long term fix, but at least it’s something for now.

  6. Shawn says:

    Looks like this is still an issue with SP1. I’ve stopped FastSearch, Host Controller and Store and once they’re started again, the files and file structure reappear.

    Any news on this?

    • Mark Dickson says:

      Sorry to post on an old article, but I’m using a new install of Exchange 2013 SP1 CU6 and I’m having this same issue with removed database files that keep coming back even after successfully deleting with the Search Host Controller service disabled.

  7. Adam says:

    I’m seeing this issue on some 2013 CU8 installs. I’m trying to delete the initially created database folders and some servers have deleted them correctly, but some won’t. FastSearchIndex is locking the folder. I can stop the service, delete the folder, start the service, and the folder comes right back with the index files.

    Anyone see a solution for this?

    • Adam says:

      I found the issue on my servers. The only way to get the search host to release the database folder completely is to create a new database on that specific server. Once I created another database and mounted it, the initial mailbox database folder could be deleted normally.

      Hope this helps someone.

  8. Doug says:

    This happens to a random database in our environment about once a month and requires a full removal of the copy, dismount, remount, deletion of the old .edb and log folder, then add the copy back and reseed. We have redundancy across 2 data centers for each database but this is getting ridiculous. It happens at random to different databases and is quite cumbersome to repeat on a monthly basis. I have the server health script running and it appears that one database will just gradually get more and more out of sync with the active copy until it can’t keep up and goes into a failed state. Other databases that sync between the same two servers but don’t have the same issue. Once that one database is fixed, about a month later one of the other databases that was working fine during the last database issue will then do the same thing. So we know it’s not a specific database issue, it appears to be an Exchange 2013 issue. So far, I have not been impressed with Exchange 2013 at all and it’s extremely frustrating for a company with over 130k mailboxes amounting to 110TB of mail data.

Leave a Reply

Your email address will not be published. Required fields are marked *