This article was previously published under Q309216
This article has been archived. It is offered "as is" and will no longer be updated.
Note Although this article discusses an error message that may occur on a local computer, the problem actually occurs in Microsoft Exchange 2000 Server. To resolve this issue and prevent error messages on the local computer, an update must be applied to the Exchange server that the Microsoft Outlook application is configured to use or to communicate with.
When you try to use Microsoft Outlook Express to retrieve a message from a Post Office Protocol (POP3) e-mail server, you may receive the following error message:
There was a problem logging onto your mail server. Your Password was rejected. Account: 'storedriver3' Server: 'storedriver3' Protocol: POP3 Server Response: '-ERR Unrecognized internal error: 0x800cce21' Port: 110 Secure(SSL): No Server Error: 0x800CCC90 Error Number: 0x800CCC92
If you try to retrieve the same e-mail message by using Internet Messaging Access Protocol (IMAP), you may receive the following error message:
Header download for the 'Inbox' folder did not complete. Could not download new messages from the IMAP server. Account: 'storedriver3 (2)' Server: 'storedriver3' Protocol: IMAP Server Response: 'Unrecognized internal error: 0x800cce21' Port: 143 Secure(SSL): No Error Number: 0x800CCCD2
The following text may appear in the Event log:
Source: POP3SVC Category: Content Engine Event ID: 1023 Error 0x800cce21 occurred while rendering message 0001-000000003b4d for download for user aissd3u000000@STOREDRIVERDOM.StoreDriverOrg.com.
This problem was first fixed in Exchange 2000 Server Service Pack 2. To resolve this issue, install the latest available service pack for Exchange 2000 Server.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was corrected in Exchange 2000 Server SP2. Contact the Exchange administrator to verify that he or she has applied Exchange 2000 Server SP2 or a later service pack to resolve this problem.