Article ID: 2632201 - View products that this article applies to.
When a MAPI application registers at the root level of a store to receive notifications in a Microsoft Exchange Server 2010 environment, the MAPI application may encounter MAPI_E_INVALID_PARAMETER errors. Additionally, the following error message is logged in the remote procedure call (RPC) Client Access log on the Exchange Server 2010 Client Access server:
RopHandler: OpenFolder: [StoragePermanentException] The process failed to get the correct properties. -> [MapiExceptionInvalidParameter] MapiExceptionInvalidParameter: Unable to get properties on object. (hr=0x80070057, ec=-2147024809)
Note By default, the RPC Client Access log is located in the following folder:
C:\Program Files\Microsoft\Exchange Server\V14\Logging\RPC Client Access
Note The 0x80070057 error number corresponds to the MAPI_E_INVALID_PARAMETER error code.
When this issue occurs, the following error message is logged in the Application log on the Exchange Server 2010 Mailbox server:
Log Name: Application
Source: MSExchangeIS Mailbox Store
Event ID: 10022
Task Category: General
Computer: Mailbox Server
A client direct access to an internal view folder has been rejected for mailbox Mailbox.
MsgHeader ID: Message Header ID
Folder ID: Folder ID
App ID: Client=MSExchangeRPC
This issue occurs because the notifications are sent incorrectly to the MAPI application when internal store objects are created on the server. Then, the MAPI application tries to retrieve more information about the internal objects. This causes the MAPI_E_INVALID_PARAMETER errors to occur.
To resolve this issue, install the following update rollup:
(http://support.microsoft.com/kb/2661854/ )Description of Update Rollup 2 for Exchange Server 2010 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the MAPI_E_INVALID_PARAMETER value, visit the following Microsoft website:
General information about the MAPI_E_INVALID_PARAMETER valueFor more information about how to handle message store notifications, visit the following Microsoft website:
How to handle message store notifications
Article ID: 2632201 - Last Review: April 16, 2012 - Revision: 1.0