John Yassa's Blog

Home » Posts tagged 'hr=0x80004005'

Tag Archives: hr=0x80004005

MapiExceptionShutoffQuotaExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1245)

When importing PST into mailbox using the command New-MailboxImportRequest an error appears in the event log and the import operation failed

The error appeared as below in the event log

Log Name: Application
Source: MSExchange Mailbox Replication
Date: 2/16/2013 3:29:03 AM
Event ID: 1100
Task Category: Request
Level: Error
Keywords: Classic
User: N/A
Computer: Exchnage.domain.local
Description:
Request ‘RequestGuid (269c6164-b533-4a67-baa6-c3cbd91c2998), RequestQueue: (0d4dbbbc-cf43-4dce-844d-e8b9133e6402)’ (269c6164-b533-4a67-baa6-c3cbd91c2998) failed.
Error code: -2147467259
MapiExceptionShutoffQuotaExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1245)
Diagnostic context:
……
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=14479]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=31727]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=31727]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=28618]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=28874]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=31727]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=31727]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=31727]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=797]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 17082 ROP Error: 0x4DD
Lid: 31329
Lid: 21921 StoreEc: 0x4DD
Lid: 31418 — ROP Parse Done —
Lid: 22753
Lid: 21817 ROP Failure: 0x4DD
Lid: 22630
Context:
——–
Operation: IMapiFxProxy.ProcessRequest
OpCode: TransferBuffer
DataLength: 31680
——–
Operation: IMapiFxProxy.ProcessRequest
OperationSide: Target
Primary (d284246a-b522-4356-8893-240806f05e4d)
OpCode: TransferBuffer
DataLength: 31680
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
<System>
<Provider Name=”MSExchange Mailbox Replication” />
<EventID Qualifiers=”49156″>1100</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=”2013-02-16T01:29:03.000000000Z” />
<EventRecordID>15856</EventRecordID>
<Channel>Application</Channel>
<Computer>Exchnage.domain.local</Computer>
<Security />
</System>
<EventData>
<Data>RequestGuid (269c6164-b533-4a67-baa6-c3cbd91c2998), RequestQueue: (0d4dbbbc-cf43-4dce-844d-e8b9133e6402)</Data>
<Data>269c6164-b533-4a67-baa6-c3cbd91c2998</Data>
<Data>-2147467259</Data>
<Data>MapiExceptionShutoffQuotaExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1245)
Diagnostic context:
……
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=14479]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=31727]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=31727]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=28618]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=28874]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=31727]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=31727]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=0]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 31418 — ROP Parse Done —
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=31727]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=61][latency=797]
Lid: 23226 — ROP Parse Start —
Lid: 27962 ROP: ropFXDstPutBufferEx [157]
Lid: 17082 ROP Error: 0x4DD
Lid: 31329
Lid: 21921 StoreEc: 0x4DD
Lid: 31418 — ROP Parse Done —
Lid: 22753
Lid: 21817 ROP Failure: 0x4DD
Lid: 22630 </Data>
<Data>——–
Operation: IMapiFxProxy.ProcessRequest
OpCode: TransferBuffer
DataLength: 31680
——–
Operation: IMapiFxProxy.ProcessRequest
OperationSide: Target
Primary (d284246a-b522-4356-8893-240806f05e4d)
OpCode: TransferBuffer
DataLength: 31680</Data>
</EventData>
</Event>

 

The solution was to remove the Mailbox quota on the mailbox you are trying to move to or remove the quota on the mailbox database you are trying to move to

OR you can at least increase the quota for both mailbox and mailbox DB

Can’t mount Database with error ,Unable to mount database. (hr=0x80004005, ec=-550)

Couldn’t mount the database that you specified. Specified database: DB2; Errorcode: An Active Manager operation failed. Error: The database action failed. Error: An error occurred while trying to select a database copy for possible activation. Error: The database ‘DB2’ was not mounted because errors occurred either while validating database copies for possible activation, or while attempting to activate another copy. Detailed error(s):

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

Before you can mount a database restored from a backup, it needs to be in a clean shutdown state. You can use the Eseutil tool to check whether a database is in a clean shutdown state – if it is not in a clean shutdown state you can perform a repair to get the database into consistency.

Soft Recovery using Eseutil

The first thing you want to do is verify that the database is in a dirty shutdown state. We can do this using the eseutil /mh command. For example:

the output should be as below:

as long as you can it shows that the DB is closed dirty shut down
also you can see the logs that is missing
we can replay the log files into the DB (if they only exist) using the command eseutil /r /l /d

For example, my log file prefix is E03, and my database and logs are stored in G:\E_\Program Files\Microsoft\Exchange Server\V14\Mailbox\DAGDB1

after it finsihed you can the first command eseutil /mh to confirm that the DB is now in clean shut down state

if after these steps , you try to mount the DB  if it fails to mount then you will have to do a hard repair using the command  eseutil /p

after it finsihed you can the first command eseutil /mh to confirm that the DB is now in clean shut down state , then try to mount the DB , it should mount with you with no problem

%d bloggers like this: