MTA log contains errors: CMessage::CopyFromPST Error -2147467259 The client operation failed. (4285405)

MTA log contains errors: CMessage::CopyFromPST Error -2147467259 The client operation failed.

The Mail Target Agent log contains errors of the following form whilst PRV files are being processed:

CFolder::UpdateFoldersChanges Informational 5502 Updating folders hierarchy.( Folder: '', SourceKey: '6B3FAFBEBB50ED4DAE0BBCEBC9BF055800000006108B') (Folder: '', SourceKey: '6B3FAFBEBB50ED4DAE0BBCEBC9BF055800000006108B')

MailKernel::ImportTarget Informational 2049 Current '\Deferred Action' (Server: 'Virginia', SourceKey: '6B3FAFBEBB50ED4DAE0BBCEBC9BF055800000006108D').
MailImport::ImportMessage TraceMsg 1411 Restoring message '0553D41530B98E4CB4741CD75AE1258C00002F8049CA' from the PST File.
CMessage::CopyFromPST Error -2147467259 The client operation failed. - MAPI_E_CALL_FAILED (Microsoft Exchange Server Information Store) File: 'aeCopyMsg.cpp' Line: '449' (Subject: '0553D41530B98E4CB4741CD75AE1258C00002F8049CA', SourceKey: '0553D41530B98E4CB4741CD75AE1258C00002F8049CA')

These errors are reported when processing a particular server side hidden system folder: '\Deferred Action'

The server side hidden system folder '\Deferred Action' is for holding deferred action messages (DAM). This folder should not be migrated, so the errors can be safely ignored.

The message class IPC.Microsoft Exchange 4.0.Deferred Action can be excluded from migration by adding this class to the MessageToSkipTypes parameter. Please see Solution SOL51743 - Excluding specific message classes upon migration - https://support.quest.com/kb/SOL51743 for additional information on the use of the MessagesToSkipTypes= parameter.

An Enhancement Request has also been created so that future versions of the software will skip the IPC.Microsoft Exchange 4.0.Deferred Action message class by default.  (CR 352565)

When you create a rule, the Rules Wizard stores the rule settings (conditions, actions, and exceptions) in a .rwz file with the same name as the user's profile. For rules for incoming messages, it also stores that information in the Inbox folder itself, with an indicator of what profile created the rule. This means that the details of the rule are available to the server. When a message arrives, the server compares it with the list of rules. If the server can execute the rule, it does so. If not, it places a deferred action message (DAM) in a hidden Deferred Action folder in the mailbox. When the user runs Outlook, the client checks the Deferred Action folder and examines each DAM. If the rule was created with the current profile, Outlook carries out the actions indicated in the DAM. This helps explain why rules may fire in an order different from that listed in the Rules Wizard: If the user is not logged in, rules that run on the server execute first, while client-only rules don't fire until the next time the user runs Outlook with the appropriate profile.