Exchange-unable to mount database row fault

Problem Description：

Due to the increase in personnel and business development needs, the current Exchange front and back end and the database for new planning, and according to actual needs to expand the existing database. An error occurred while mounting the database mapiexceptiontoomanymounteddatabases:unable to mount database.

Environment Description :

Windows Server 2012R2 + Exchange CU17

Problem Analysis:

Microsoft Exchange Server 2013 is available in two server versions: Standard Edition and Enterprise Edition. Enterprise Edition can scale to 50 mount databases per server in release to manufacturing (RTM) and Cumulative Update 1 (CU1) versions, and 100 databases per server in Cumulative Update 2 (CU2) and later CU18; The Standard Edition is limited to installing 5 databases per server. The mounted database is the database that is in use . The mounted database can be either an active mailbox database that is installed for use by clients, or a passive mailbox database for log replication and replay that is installed in recovery. Although you can create more databases than the above limit, only the maximum number specified above is loaded. The recovery database does not count towards this limit.

These licensed versions are defined by the product key. When you enter a valid license product key, a supported version of the server is established. The product key can only be used for the same version of the key exchange and upgrade; They cannot be used for demotion. You can use a valid product key to move the evaluation version (Trial version) of Exchange 2013 to the Standard or Enterprise Edition. You can also transfer from the Standard Edition to the Enterprise Edition using a valid product key.

You can also use the same version of the product key to re-authorize the server. For example, if you have two Standard Edition Servers with two keys, but accidentally use the same key on both servers, you can change one of the keys to another key that you publish. You can perform these actions without having to reinstall or reconfigure any content. After you enter the product key and restart the Microsoft Exchange Information Store service, the version that corresponds to the product key is reflected.

No loss of functionality occurs when the trial expires, so you can maintain labs, demos, training, and other non-production environments within 120 days without having to reinstall the Exchange 2013 trial.

As mentioned earlier, you cannot use the product key to downgrade from the Enterprise Edition to the Standard Edition, nor can you use them to revert to the trial version. These types of demotion can only be done by uninstalling Exchange 2013, reinstalling Exchange 2013, and entering the correct product key.

Solution Ideas :

1. Perform the database mount operation in the ECP Web management interface, the error message is as follows:

Failed to mount database "DB17". Error: Activity manager operation failed. Error: Database operation failed. Error: An error occurred while trying to select a database copy for a possible activation action. Error: Database ' DB17 ' was not mounted because an error occurred while verifying that the database copy is active or attempting to activate another copy. Verbose error: mbx04: Activity manager operation failed. Error: Operation failed with message: mapiexceptiontoomanymounteddatabases:unable to mount Database. (HR=0X8004060E, ec=-2147219954) Diagnostic context:lid:65256 lid:10722 storeec:0x8004060e lid:1494--Remote context Beg--lid:37952 dwparam:0x3c1 a048e lid:39576 storeec:0x977 lid:35200 dwparam:0x1970 lid:58864 storeec:0x8004060e lid:43248 storeec:0x8004060e L id:35388 storeec:0x8004060e lid:54336 dwparam:0x3c1a048e lid:35200 dwparam:0x1970 lid:1750--Remote Context End-- lid:1047 storeec:0x8004060e [Server: mbx04.***.com] [Database: DB17, server: mbx02.***.com]

2. View the server log at this time:

The index of the mailbox database DB17 encountered an unexpected exception. Error Details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException:The component operation has failed. ---> Microsoft.Exchange.Search.Core.Abstraction.ComponentFailedPermanentException:Failed to read notifications, Mdb:6fbcc62c-b4ad-45a8-b512-d1daac1090b7. ---> Microsoft.Mapi.MapiExceptionMdbOffline:MapiExceptionMdbOffline:Unable to read events. (hr=0x80004005, ec=1142)

Diagnostic Context:

lid:49384

lid:51176 storeec:0x476

lid:40680 storeec:0x476

lid:43980

lid:16354 storeec:0x476

lid:38985 storeec:0x476

lid:20098

lid:20585 storeec:0x476

In Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning (String message, Int32 HRESULT, Boolean Allowwarnings, Int32 EC, Diagnosticcontext Diagctx, Exception innerexception)

In Microsoft.Mapi.MapiExceptionHelper.ThrowIfError (String message, Int32 HRESULT, Iexinterface IUnknown, Exception innerexception)

In Microsoft.Mapi.MapiEventManager.ReadEvents (Int64 startcounter, Int32 eventcountwanted, Int32 Eventcounttocheck, Restriction filter, Readeventsflags flags, Boolean Includesid, int64& endcounter)

In Microsoft.exchange.search.mdb.notificationseventsource.<>c__displayclass3.<readevents>b__1 ()

In Microsoft.exchange.search.mdb.mapiutil.<>c__displayclass1 ' 1.<translatemapiexceptionswithreturnvalue >b__0 ()

In Microsoft.Exchange.Search.Mdb.MapiUtil.TranslateMapiExceptions (Idiagnosticssession Tracer, LocalizedString ErrorString, Action Mapicall)

---the end of the inner exception stack trace---

In Microsoft.Exchange.Search.Mdb.MapiUtil.TranslateMapiExceptions (Idiagnosticssession Tracer, LocalizedString ErrorString, Action Mapicall)

In Microsoft.exchange.search.mdb.mapiutil.translatemapiexceptionswithreturnvalue[treturnvalue] ( Idiagnosticssession Tracer, LocalizedString errorstring, Func ' 1 mapicall)

In Microsoft.Exchange.Search.Mdb.NotificationsEventSource.ReadEvents (Int64 startcounter, Int32 eventcountwanted, Readeventsflags flags, int64& endcounter)

In Microsoft.Exchange.Search.Mdb.NotificationsEventSource.ReadFirstEventCounter ()

In Microsoft.Exchange.Search.Engine.NotificationsEventSourceInfo. ctor (Iwatermarkstorage watermarkstorage, Inotificationseventsource EventSource, idiagnosticssession Diagnosticssession, Mdbinfo Mdbinfo)

In Microsoft.Exchange.Search.Engine.SearchFeedingController.DetermineFeederStateAndStartFeeders ()

In Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart ()

In Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart (Object state)

---the end of the inner exception stack trace---

In Microsoft.Exchange.Search.Core.Common.Executable.EndExecute (IAsyncResult asyncResult)

In Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete (IAsyncResult asyncResult)

3. According to the error mapiexceptiontoomanymounteddatabases and system log analysis, recall that we did not enter a production key after adding a new mailbox backend, the evaluation version of the mailbox can install 5 databases by default.

Ps. You can view the build number of the version of Exchange 2013 that is running by using the following command:

Get-exchangeserver | FL name,edition,admindisplayversion

4. Enter the Exchange Enterprise license key normally:

5. Restart the Microsoft Exchange Information Store (Microsoft Exchange Information Store) service.

6. Try adding the database again, and you can add it normally. This troubleshooting operation is complete.

Add:

Exchange 2013 License types

Exchange 2013 is licensed in the server/Client Access License (CAL) model, similar to how Exchange 2010 is licensed. The following are the types of licenses:

• Server License : You must assign a license for each instance of the server software that is running. Server licenses are sold in two server versions: Standard Edition and Enterprise Edition.

• Client access Licenses (CALs): Exchange 2013 also includes two Client Access License (CAL) versions, which are known as Standard CALs and Enterprise CALs. You can use the server version in combination with the CAL type. For example, you can use Enterprise CALs for Exchange 2013 Standard Edition. Similarly, you can use standard CALs for Exchange 2013 Enterprise Edition.

Exchange-unable to mount database row fault