"Error 80070057" Occurs When You Try to Browse a Mailbox Using Outlook Mobile Access (297282)



The information in this article applies to:

  • Microsoft Mobile Information 2001 Server

This article was previously published under Q297282

SYMPTOMS

When you try to browse your mailbox by using Outlook Mobile Access, the operation may fail, and you may receive the following error message on the wireless device:
An Unknown error occurred. OMA Control Module, 0x80070057; The parameter is incorrect.
In addition, the following event may be logged in the Application event log:

Event Type: Error
Event Source: Outlook Mobile Access
Event Category: None
Event ID: 1
Date: 2/25/2001
Time: 3:07:49 PM
User: N/A
Computer: MISSERVER
Description:
Internal Error in Module: MIS OMA: WML Rendering Module
Error Code: 80070057
Description: The parameter is incorrect.
User: USERNAME
Host:
Path:
Query String:

CAUSE

This issue can occur in either of the following scenarios:
  • The mailbox does not exist; this behavior can occur if the mailbox has not been initialized when you log on to it by using Microsoft Outlook or Microsoft Outlook Web Access (OWA).

    -or-
  • Outlook Mobile Access cannot access the mailbox; this behavior can occur if the Exchange 2000 information store or database are inaccessible.

WORKAROUND

To work around this issue if you are an administrator, ensure that the Exchange 2000 mailbox is functioning properly. Verify that the user has an Exchange 2000 mailbox and that the mailbox can be accessed by using OWA when you use the user's wireless account credentials (if you are using a topology other than "Integrated") or the Message Processor account credentials (if you are using the "Access User" topology).

If the mailbox has not been initialized, log on to the mailbox by using OWA. When you do so, the mailbox is initialized correctly, and an object is created in the Exchange 2000 information store. Outlook Mobile Access can now to retrieve the data successfully.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:4/25/2005
Keywords:kbbug KB297282