Here is an example of error “MapiExceptionJetErrorLogDiskFull” error
that I received when I tried to bring a database back online in Exchange
2010, this example and the screenshot is on a database store called “8GB
1″. The problem here is that the exchange server log space for this
database is full. It was quite an easy one to fix as the clue is in the
error itself. Remember you can not really delete the exchange log files,
if you have a build up of log files then you will probably find you have
a problem with your backups. In this instance we were able to increase
the volume size for the logs so we could get this mailbox store back
online, then look at the reason why afterwards.

——————————————————–

Microsoft Exchange Error

——————————————————–

Failed to mount database ‘8GB 1’.

8GB 1

Failed

Error:

Couldn’t mount the database that you specified. Specified database: 8GB
1; Error code: An Active Manager operation failed. Error The database
action failed. Error: Operation failed with message:
MapiExceptionJetErrorLogDiskFull: Unable to mount database.
(hr=0x80004005, ec=-529)

. [Database: 8GB 1, Server: here.is.the.server.name].

An Active Manager operation failed. Error The database action failed.
Error: Operation failed with message: MapiExceptionJetErrorLogDiskFull:
Unable to mount database. (hr=0x80004005, ec=-529)

. [Database: 8GB 1, Server: here.is.the.server.name]

An Active Manager operation failed. Error Operation failed with message:
MapiExceptionJetErrorLogDiskFull: Unable to mount database.
(hr=0x80004005, ec=-529)

. [Server: here.is.the.server.name]

MapiExceptionJetErrorLogDiskFull: Unable to mount database.
(hr=0x80004005, ec=-529)

By Duncan

Leave a Reply