Event 104 is logged after you create a new database in Exchange Server 2007

Consider the following scenario:

• Microsoft Exchange Server 2007 is running on a Windows Server 2003-based server.
• You create a new database in a storage group that resides on the mount point that has sufficient free space.
• The mount point root that hosts the mount point has fewer than 20 megabytes (MB) of free space.

In this scenario, the indexing of the new database does not work correctly. In the CatalogData directory in the storage group that is used for the new database, you find only some of the files that should be present in this directory.

Additionally, when the MSSearch service tries to create catalogs for the new database, the following event is logged in the Application log:

Event ID: 104
Raw Event ID: 104
Record Nr.: 32084
Category: General
Source: MSExchange Search Indexer
Type Error
Message: Exchange Search Indexer failed to enable the Mailbox Database Storage Group 2\Mailbox Database (GUID = f2cddfad-167a-4329-bc22-6a0f8e418f9a) after 1 tries. The last failure was: System.ComponentModel.Win32Exception: Unable to SetProperty on catalog ExSearch-f2cddfad-167a-4329-bc22-6a0f8e418f9a-6d25762a-59ca-4163-8b25-d905b31aa421. Error -2147215320 from msfte.dll
at Microsoft.Exchange.Msfte.CFTEAdmin.SetProperty(CatalogState catalogInfo, PropertyScope propertyScope, String propertyName, Object propertyValue)
at Microsoft.Exchange.Msfte.CFTEAdmin.CreateCatalog(CatalogState catalogInfo)
at Microsoft.Exchange.Search.Globals.CreateCatalog(CatalogState state)
at Microsoft.Exchange.Search.Globals.RecreateCatalogAndPropertyStore(CatalogState catalogInfo)
at Microsoft.Exchange.Search.Globals.CheckAndInitializeCatalog(CatalogState catalogInfo)
at Microsoft.Exchange.Search.Driver.MonitorAndUpdateMDBList(). It will retry after 0 minutes.

To work around this behavior, make sure that more than 20 MB of free disk space are available on the mount point root.

This behavior is by design.

For more information about mount points, click the following article number to view the article in the Microsoft Knowledge Base: