Troubleshooting error log messages in Microsoft Outlook Mobile Manager (294558)


The information in this article applies to:

  • Microsoft Outlook Mobile Manager
This article was previously published under Q294558
Microsoft Outlook Mobile Manager has been discontinued and is no longer available for download. If you have already installed Outlook Mobile Manager, continue to check the Microsoft Knowledge Base for any documented issues. To obtain additional information about Microsoft Mobile Information Server, visit the following Microsoft Web site:

http://www.microsoft.com/miserver/default.asp

SUMMARY

This article describes the error messages that you may receive when you connect to your server or forward messages to your wireless device.

MORE INFORMATION

When you use Microsoft Outlook Mobile Manager, error messages are logged in a troubleshooting log that may be saved in a text format (Outlook Mobile Managerlog.txt) that you can review at later. You can also click Support, and then click Troubleshooting to review the troubleshooting log entries. When you click the error message, a description of the message is displayed in the left pane.

Error Messages

  • Outlook has lost connection to your e-mail server. Contact your administrator.
    This error message occurs if there is a loss of network connectivity or your mail server is unavailable. To resolve this issue, check basic network functionality to make sure that you can connect to network resources. If other network resources are available, check with your Exchange Server administrator to ensure that your server is available.
  • Error 400: There was an unexpected fault in the connector while trying to send a message. The message was not sent.
    This error message is not common, but may occur if the message that you are sending contains unusual formatting or content that prevents it from being forwarded.
  • Error 401: Microsoft Outlook Mobile Manager could not initialize because of an unexpected fault in the connector. Please make sure that the connector configuration data is valid.
    Error 402, 403, 1906, 1907, 2906, 2907: There was an unexpected fault in the connector while trying to retrieve or set the configuration settings.
    These error messages occur if your connector configuration contains incorrect information. Typically, the first error message occurs if there is a typographical error in the server name, user name, or device ID. To resolve this issue, check the information in the connector configuration to make sure that you entered it correctly. Make sure that you entered the correct connector type (Mobile Information Server or Simple Mail Transfer Protocol [SMTP]).
  • Error 404, 408: There was an unexpected fault in Microsoft Outlook Mobile Manager while exiting the program. The fault has been handled and there should not be any adverse effects.
    This error message occurs if Outlook Mobile Manager was able to handle the error it found, and because no other faults or problems occurred, shut down continued normally. This is an informative error message. This error message may occur if another program is running. To resolve this issue, check for other programs that may be running when this error message occurs.
  • Error 405: There was an unexpected fault in the connector while trying to retrieve current update information from your provider. The fault has been handled, but no update information could be retrieved. If this fault persists please check your provider's website manually for any available updates, and report this to PSS.

    This error message may occur if there is a problem contacting your wireless carrier's Web site or if there are network connectivity problems. To resolve this issue, manually check your carrier's Web site to ensure that it is available.
  • Error 406: Microsoft Outlook Mobile Manager could not initialize because there was an unexpected fault in the msg formatter. Try reinstalling the product to make sure there are no missing files.
    This error message may occur if there is a problem with the Outlook Mobile Manager installation. Another program such as a messaging program or anti-virus program may have prevented files for Outlook Mobile Manager from being installed correctly. To resolve this issue, shut down any extra programs, and then reinstall Outlook Mobile Manager.
  • Error 407, 1816: There was an unexpected error in Microsoft Outlook Mobile Manager while processing a message, because of which this message could not be sent. The problem may have been specific to the data content of that message. If this problem persists across different messages, please report it to PSS.
    This error message is similar to error message 400; it may occur if the message contains unusual or malformed formatting. When this error message occurs, it is usually an isolated incident.
  • Error 410: Microsoft Outlook Mobile Manager was shutdown by the user in order to change the active connector.
    This error message is informational and may also be logged as "Outlook Mobile Manager is shutting down to allow you to change connectors."
  • Error 411: Microsoft Outlook Mobile Manager could not initialize because no valid connector was chosen. Please restart the program and choose a valid connector by following the instructions in the UI.
    This error message may occur if you have specified either a non-existent server or one that cannot be contacted. In addition, this message may occur if there is a typographical error in the server name. To resolve this issue, check the configuration information in the connector.
  • Error 413: Microsoft Outlook Mobile Manager could not initialize due to an internal error in the active connector.
    This error message is also similar to Error 400 or Error 405; it may occur if there is a problem either making a connection or confirming the connection. To resolve this issue, check network connectivity, and then confirm that your server is available.
  • Error 700: Microsoft Outlook Mobile Manager ran out of internal memory while trying to process a message.
    This error message does not indicate that there are low memory conditions; this message generally implies that the message was too complex and the memory required by Intellishrink to process the message was too large. You can turn Intellishrink off or set it to no compression to work around this error message. If this error message persists for a large number of messages, report this issue to Microsoft Product Support Services (PSS). To contact PSS, refer to the following Microsoft Web site:

    http://support.microsoft.com/contactus/?ws=support

  • Error 701: Microsoft Outlook Mobile Manager could not initialize because it could not load some internal strings. Please make sure your system is not running low on memory and restart the program. If the problem persists, it may indicate a bad binary - try reinstalling the program.
    This error message may occur if there is a memory deficiency on the computer, or if there is a problem with the installation. To resolve this issue, check that there are not excessive programs that are running that are exhausting memory resources. You may have to reinstall Outlook Mobile Manager.
  • Error 702: Microsoft Outlook Mobile Manager could not initialize because the natural language parser could not be loaded. Please make sure you have a valid install with all the files.
    This error message indicates that natural language support for Outlook Mobile Manager cannot be loaded successfully. This error message may occur if there is a problem with the localized version that you have installed, or if you have configured an incorrect locale setting for the localized version you have installed.
  • Error 703, 1000, 1001, 1817: Microsoft Outlook Mobile Manager could not process a message because a memory allocation failed. This is probably because your system is running low on memory.
    These error messages occur if the computer resources are limited because there is a large number of programs that are running simultaneously. To resolve this issue, quit some programs or restart your computer to increase the amount of available memory.
  • Error 1700, 1706: Microsoft Outlook Mobile Manager could not initialize because of an unexpected internal error. Try reinstalling to make sure you do not have a corrupt installation.
    If these error messages occur, remove and then reinstall Outlook Mobile Manager to resolve the problem.
  • Error 1701, 1702, 1703, 1704, 1705, 1822, 1823: Microsoft Outlook Mobile Manager could not initialize because it could not allocate required system structures. This is probably because your system is running too low on resources. Try shutting down some programs and then restarting Microsoft Outlook Mobile Manager.
    These error messages may occur if computer resources have been depleted by a large number of programs that are running on the computer, or if the resources are not released as they are closed. To resolve this issue, quit any programs that are running that may not be necessary.
  • Error 1808, 1809, 1810, 1811, 1812, 1814, 1815, 1818, 1820: An unexpected fault occurred while running. This fault has been handled, but Microsoft Outlook Mobile Manager cannot continue running because some internal structures may be corrupt. Please restart the program.
    These error messages may occur if there is an internal program error and Outlook Mobile Manager cannot continue running. To resolve this issue, restart Outlook Mobile Manager. If the issue is not resolved, you may have to reinstall Outlook Mobile Manager.
  • Error 1813: Microsoft Outlook Mobile Manager had to discard some messages from its outbound queue because the queue became too long, or some messages were too old.
    This error message may occur if the connector is getting transient errors and is unable to send any messages out. The oldest messages are always discarded first. The error log indicates the number of messages that had to be discarded. To resolve this issue, check the error log for warning error messages that are logged by the connector. If a large number of transient errors are occurring, there may be a connectivity problem with the server. Confirm your network connectivity and server availability.
  • Error 1821: Microsoft Outlook Mobile Manager could not initialize the idle timer subsystem. Please make sure your system is fully compatible with Microsoft Outlook Mobile Manager in terms of IE and Office requirements.
    This error message may occur if you are not running the correct version of Microsoft Internet Explorer. To resolve this issue, check the version of Internet Explorer that is installed on the computer and the e-mail client (Internet Explorer 5.0 or later versions are required, Internet Explorer 5.5 is recommended). Microsoft Outlook 97 or later versions are required; Exchange Server client and Outlook Express do not work if these programs are installed as your only mail client. Confirm that your computer meets the other requirements to run Microsoft Outlook Mobile Manager successfully.
  • Error 1819: Microsoft Outlook Mobile Manager could not drain the outbound message queue before exiting. The error message in the log indicates how many messages could not be sent.
    This error message may occur if the connector is experiencing transient errors (similar to error 1813), and could not successfully talk to the server when the program was trying to exit. To resolve this issue, check the error log for warning errors that are logged by the connector, and then confirm your network connectivity and server availability.
  • Error 2802: Microsoft Outlook Mobile Manager was unable to retrieve information about possible updates from the server.
    This error message may occur if you are using the Options window that is displayed when you click About on the Help menu. When you click the Check Now button, the Web site is queried for updates to Outlook Mobile Manager. If no updates are available, or if there are other problems, an extended error code is logged that indicates where the problem may be occurring. The following list describes the extended error codes that may be displayed:
    • 1: Outlook Mobile Manager could not contact the server. This error code can occur if the server is down, or if the computer does not have enough memory for Outlook Mobile Manager to create the connection.
    • 2, 3, 6: The version information that is returned from the server is invalid and could not be parsed correctly. Report this problem to the administrator for your server. This error code may indicate a communication or connectivity problem, or another problem on the server.
    • 4: There is no information available for your product. This error code can occur if there is version that is not available for the language that is installed on your computer. Contact the administrator of the server for help. Outlook Mobile Manager is currently available for English, Spanish, and German language versions. If you use other languages, you may receive this error message. This error message may also be logged if an update is not available.
    • 5: The Extensible Markup Language (XML) for the upgrade URL returned in the version information was ill-formed and could not be parsed. Report this issue to the administrator of the server. This error code may also indicate a communication or connectivity problem, or another problem with the server.

      Note Outlook Mobile Manager continues to try to get update information, but it does not log any more error messages so that the error log is not filled with the same message. After Outlook Mobile Manager manages to retrieve update information, it puts the entry in the log. If this state persists, you may want to try checking your server manually for any upgrades.
  • Error 2803: Microsoft Outlook Mobile Manager was successfully able to retrieve update information after being in a failure state.
    This error message may occur after retries have been able to retrieve the information requested for an update.
  • Error 2801, 2804: There was an unexpected fault while resolving an upgrade request. The fault has been handled, but the request to do or to postpone an upgrade might be lost. Please retry the upgrade procedure.
    These error messages may occur if there is a connectivity issue or some other condition that prevents Outlook Mobile Manager from completing an update download. To resolve this issue, retry the update to ensure that you have downloaded the latest version successfully.
  • Error 2800: Microsoft Outlook Mobile Manager is shutting down to allow an upgrade to be completed. Please follow instructions in the browser to complete the upgrade and then relaunch Microsoft Outlook Mobile Manager.
    This error message may occur if there is an upgrade instead of a minor update for Outlook Mobile Manager. You must quit Outlook Mobile Manager while the upgrade takes place. After the upgrade has completed, restart Outlook Mobile Manager to continue.
  • Error 1900, 1901: The Mobile Information Server connector was unable to setup the structures to contact the server. The message could not be sent.
    This error message may occur if there is a problem with memory resource availability on the computer. To resolve this issue, shut down some programs, and then restart Outlook Mobile Manager. These error messages occur if computer resources have been depleted by a large number of programs that are running or if the computer does not release resources as they are closed. Shut down other unnecessary programs to free resources.
  • Error 1902: The Mobile Information Server Connector timed out while trying to connect to the server. The server may be down or your system may be low on resources. The message will be retried automatically.
    This error message may occur if the computer resources are low. This error message more likely occurs if there is a problem with server connectivity. To resolve this issue, verify that you have network connectivity and that your server is available.
  • Error 1903, 1904: The Mobile Information Server connector could not successfully connect to the server. The message was not sent. If these errors persist, report the problem to the administrator for your Mobile Information Server server along with the Win32 error code listed in the log entry.
    These error messages may occur if there is a problem connecting to the Mobile Information Server computer and messages cannot be sent. The problem may occur because of network conditions or connectivity problems. These messages can also occur if the Mobile Information Server computer is down or unavailable, or if there is a problem connecting to your mailbox. The troubleshooting log contains an error message that lists a Win32 error code as well. The following list describes the Win32 error codes that may be logged:
    • Win32 error 0x8004010f: Outlook Mobile Manager could not initialize the session with the Exchange Server computer. Verify that the Outlook (Messaging Application Programming Interface [MAPI]) profile that you have selected is valid. There may be a network problem or your Exchange Server computer may be offline.
    • Win32 error 0x80040115: The connection to the Exchange Server computer was lost. This message may indicate that there is a network problem or your Exchange Server computer is offline.
    • Win32 error 0x2ee7: The connector to the Mobile Information Server computer could not contact the server and a message could not be sent. The message is retried automatically.
  • Error 1905: The server returned a failure response to the HTTP request. The actual HTTP error code received is listed in the log. The message will automatically be retried. Please check your connector configuration to make sure all the information in there is entered correctly.
    This error message may occur if there is a problem connecting to the Mobile Information Server computer. There may be no response from the server or it may not be found. To resolve this issue, check the connector configuration to verify the information that you have entered for the server. The HTTP error code that is logged indicates of the root of the problem. The following list contains the common HTTP error codes that may be logged:
    • 400 Bad request
    • 401.1 Logon failed
    • 401.2 Logon failed due to server configuration
    • 401.3 Unauthorized due to ACL on resource
    • 401.4 Authorization failed by filter
    • 401.5 Authorization failed by ISAPI/CGI program
    • 403.1 Execute access forbidden
    • 403.2 Read access forbidden
    • 403.3 Write access forbidden
    • 403.4 SSL required
    • 403.5 SSL 128 required
    • 403.6 IP address rejected
    • 403.7 Client certificate required
    • 403.8 Site access denied
    • 403.9 Too many users
    • 403.10 Invalid configuration
    • 403.11 Password change
    • 403.12 Mapper denied access
    • 403.13 Client certificate revoked
    • 403.14 Directory listing denied
    • 403.15 Client Access Licenses exceeded
    • 403.16 Client certificate untrusted or invalid
    • 403.17 Client certificate has expired or is not yet valid
    • 404 Not found
    • 404.1 Site not found
    • 405 Method not allowed
    • 406 Not acceptable
    • 407 Proxy authentication required
    • 412 Precondition Failed
    • 414 Request-URI too long
    • 500 Internal server error
    • 500.12 program restarting
    • 500.13 Server too busy
    • 500.15 Requests for Global.asa not allowed
    • 500-100.asp ASP error
    • 501 Not implemented
    • 502 Bad gateway
  • Error 1908: Microsoft Outlook Mobile Manager could not initialize because the Mobile Information Server connector is not configured correctly. Please restart the program and you will be able to change the configuration settings for this connector. Contact your Mobile Information Server server administrator if you do not know what settings to use.
    This error message may occur if you entered incorrect information for the Mobile Information Server computer. In this case, Outlook Mobile Manager does not initialize correctly. If this error message occurs, restart Outlook Mobile Manager from the system tray, or use the menu option, and then verify that the configuration information for the Mobile Information Server computer is correct.
  • Error 2909: The SMTP connector could not connect to the server. The server may be down, or the system may be too low on resources to allow the connection to be made. The message will automatically be retried.
    This error message may occur if computer resources are low. This message more likely indicates that there is a problem with server connectivity. To resolve this issue, verify that you have network connectivity and that your server is available.
  • Error 2900, 2902: The SMTP connector got "an error response" from the SMTP server. The message was not sent and will not be retried.
    These error messages occur if there is a problem at the SMTP server that you are using to forward messages to your device. This error message does not indicate a problem with network connectivity, but it may indicate that the server is down or unreachable. The "error response" message is a 500 level error message. The actual HTTP 500 level error message that is received is included in the log entry with an extended error response string from the service. The extended error response is a delivery status notification error code, which is described in Request for Comments (RFC) 1893. The 500 level error and the delivery status notification error code in the log indicate where the problem occurs. The following list describes the common 500 level error messages and the delivery status notification extended error responses that are included with the error message:
    • 500, 501, 502, 503, 504, 552, 553, 554: These error codes should never occur because they indicate that either an improperly formed request is being sent to the server, the server does not exist, the server cannot process the request that is being made, or the server is returning an invalid response. If these error messages occur, check your connector configuration and check for network connectivity. If the connector configuration is correct, and you have network connectivity, you may need to remove and reinstall Outlook Mobile Manager and your browser.
    • 550, 551: Typically, these error codes indicate that your server is not set up to relay to another SMTP server that knows the destination address. You must point to a server that can send SMTP messages outside any firewall. If these error messages continue, contact your administrator to ensure that SMTP-relaying is not prohibited at your server.

    Delivery Status Notification Error Codes

    • 4.X.X Persistent Transient Failure
    • 5.X.X Permanent Failure

    Second and Third Digits

    • X.1.0 Other address status
    • X.1.1 Bad destination mailbox address
    • X.1.2 Bad destination system address
    • X.1.3 Bad destination mailbox address syntax
    • X.1.4 Destination mailbox address ambiguous
    • X.1.5 Destination mailbox address valid
    • X.1.6 Mailbox has moved
    • X.1.7 Bad sender's mailbox address syntax
    • X.1.8 Bad sender's system address
    • X.2.0 Other or undefined mailbox status
    • X.2.1 Mailbox disabled, not accepting messages
    • X.2.2 Mailbox full
    • X.2.3 Message length exceeds administrative limit
    • X.2.4 Mailing list expansion problem
    • X.3.0 Other or undefined mail system status
    • X.3.1 Mail system full
    • X.3.2 System not accepting network messages
    • X.3.3 System not capable of selected features
    • X.3.4 Message too big for system
    • X.4.0 Other or undefined network or routing status
    • X.4.1 No answer from host
    • X.4.2 Bad connection
    • X.4.3 Routing server failure
    • X.4.4 Unable to route
    • X.4.5 Network congestion
    • X.4.6 Routing loop detected
    • X.4.7 Delivery time expired
    • X.5.0 Other or undefined protocol status
    • X.5.1 Invalid command
    • X.5.2 Syntax error
    • X.5.3 Too many recipients
    • X.5.4 Invalid command arguments
    • X.5.5 Wrong protocol version
    • X.6.0 Other or undefined media error
    • X.6.1 Media not supported
    • X.6.2 Conversion required and prohibited
    • X.6.3 Conversion required but not supported
    • X.6.4 Conversion with loss performed
    • X.6.5 Conversion failed
    • X.7.0 Other or undefined security status
    • X.7.1 Delivery not authorized, message refused
    • X.7.2 Mailing list expansion prohibited
    • X.7.3 Security conversion required but not possible
    • X.7.4 Security features not supported
    • X.7.5 Cryptographic failure
    • X.7.6 Cryptographic algorithm not supported
    • X.7.7 Message integrity failure
    For more information about delivery status notification error messages, click the following article number to view the article in the Microsoft Knowledge Base:

    256321 Enhanced status codes for delivery - RFC 1893

    For more information about delivery status notification error codes, review RFC 1893.

  • Error 2901, 2903: The SMTP connector got a transient error response from the SMTP server. The message will automatically be retried.
    These error messages may occur if there is a problem at the SMTP server that you are using to forward messages to your device. The 2901 and 2903 error codes differ from error codes 2900 and 2902 in that they are transient error codes rather than permanent failures. When these codes occur, message forwarding is retried. These error messages may indicate a problem with network connectivity, but they may indicate that the server is down or unreachable temporarily. The error response code is a 400 level error code. The actual HTTP 400 level error message that was received with an extended error response string from the service is included in the log entry. The extended error response is a delivery status notification error code as described in RFC 1893. The combination of the 400 level error messages and the delivery status notification error code in the log should give an indication of where the problem is occurring. The following list describes the HTTP 400 level error messages that may occur.

    Note The delivery status notification error codes in the preceding section apply to these error logs as well.
    • HTTP 421: The server is shutting the SMTP service down. This issue may occur for various reasons that indicate problems at the server. There may also be problems with the DNS server. Contact an administrator for the SMTP server to verify the stability of the SMTP service.
    • 450, 451, 452: The server had some local problems that should clear up. These may be maintenance problems that caused the SMTP service to stop and start, or the server may have been restarted. The error message occurs when the first the message is forwarded; subsequent retries should succeed.
    • 454: The client did not have authorization to connect to the server. This issue may occur because your SMTP server may not be set up to allow anonymous access. You must point to a server that allows you to log on anonymously. SMTP servers that require authentication do not allow Outlook Mobile Manager to work successfully, and these errors continue to be logged.
  • Error 2904, 2905: The SMTP connector could not be initialized because it failed a memory allocation. Please shut down some programs to increase system resources and then restart the program.
    This error message can occur if there is a memory or resource deficiency on the computer. To resolve this issue, quit any extra programs are running that may be exhausting memory resources.
  • Error 2908: Microsoft Outlook Mobile Manager could not initialize because the SMTP connector is not configured correctly. Please restart the program and you will be able to change the configuration settings for this connector. Contact your administrator if you do not know what settings to use.
    This error message can occur if you have entered incorrect information for the SMTP server. In this case, Outlook Mobile Manager cannot be initialized correctly. If this error message occurs, restart Outlook Mobile Manager by using the system tray icon or menu option, and then verify that the configuration information for the SMTP server is correct.
Modification Type:MajorLast Reviewed:11/17/2005
Keywords:kbinfo KB294558
©2004 Microsoft Corporation. All rights reserved.