There are more than a couple of situations when you may receive the error code, 0×80040005. Here are some of those situations:

1. when you cannot move, synchronize, or autoarchive messages
2. if active mail session with Exchange server was broken
3. when emailing a report using the tree email from within FRx Report Designer
4. when you use Distributed Authoring and Versioning (DAV) to query for message properties on the information store in Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003

If you are in a situation where you (1) cannot move, synchronize or autoarchive messages then you may receive the error code 0×80040005. When you try to AutoArchive messages, move messages, or synchronize items while Microsoft Outlook is connected to a Microsoft Exchange Server mailbox, you may receive the following error message:

Error while archiving folder <folder name – Inbox> in store “Archive Folders”. The source and destination folders for this operation cannot be the same.

Continue reading Troubleshooting Error Code 0×80040005

There are several reasons why you may have received the 0x8004011C error code. Sometimes an Extended MAPI function will return a numeric result codes that is the equivalent of the MAPI_E_UNCONFIGURED error code.

Other times you will receive this error in conjunction with using the MAPI component of ASP. The Mail Application Programming Interface (MAPI) is a component used in Active Server Page (ASP) code. It was formerly called Active Messaging, but is now called Collaboration Data Objects (CDO). To allow for greater functionality from the object library than was available in Active Messaging 1.1, the objects were replaced by CDOs. CDOs are objects that support capabilities beyond simple messaging into the areas of calendaring, collaboration, and workflow.

ASP technology is used very widely in Exchange 2000 conferencing and as a result, you may encounter a variety of MAPI warnings and error messages one of which will be the 0x8004011C error code.

Continue reading Troubleshooting Error Code 0x8004011C

I am sure that at some point your users have come to you and complained that they can’t send email. You can take a look at the logs and also at a particular user’s setting to see if there if anything different about their profile.

Sometimes they will try to send an email but get back a message similar to the following: This message could not be sent. Try sending the message again later, or contact your network administrator. The Microsoft Exchange server is currently busy. If this message is still displayed in 30 minutes, contact your Exchange server administrator. Error is
[0x80040111-0x80040111-0x000520].

There are other situations when you may get the error code 0×80040111 such as:

• PRB: Error “ClassFactory Cannot Supply Requested Class” (80040111 …  (279129).
• Attempting to install Microsoft Windows Live OneCare.
• If you have two instances of Microsoft SQL Server 2000 on the same computer, and SQL Mail is configured with separate mail profiles on each instance.
• Move Mailbox operation is unsuccessful.
• Logons to the Microsoft Exchange server computer fail and you get “The information store could not be opened” error message.
• If the MSSQLServer Service startup account is set to the local system account and xp_startmail fails.
• Exchange 2000 Management Pack MAPI Logon Check Reports Logon Failures.

Continue reading Troubleshooting Error Code 0×80040111

Many people have reported problems when they try to sync their cell phones with their Exchange servers.

When they try to sync with MS Exchange Server 2003 using Windows Mobile 5.0 they might get the following error code: 0x80072f17. Some users have also reported problems when trying to sync with MS Exchange Server 2007.

This problem is usually associated with using Secure Socket Layer (SSL) certificates.

Remember that you use SSL for Internet protocols such as Network News Transfer Protocol (NNTP), Simple Mail Transfer Protocol (SMTP), Post Office Protocol version 3 (POP3), and Internet Message Access Protocol (IMAP).

Continue reading Troubleshooting Error Code 0x80072f17

There are more than a couple of situations under which you will see the error code 0x8004011b.

Some of these situations include:
- when Outlook performs send/receive operation
- when a user performs send/receive operation
- when there is a MAPI_E_CORRUPT_DATA message from the Exchange Calendar Update Tool

Here are some ways to resolve these problems.

In the first situation, The error message:  “Task ‘Microsoft Exchange Server’ reported error (0x8004011B) : ‘Unknown error 0x8004011B” can appear when outlook does a send/receive operation.

There are several causes for this problem:

1. Antivirus software blocks a connection from Outlook to the Exchange server.
2. Firewall blocks a connection from Outlook to the Exchange server.
3. Outlook 2003 has been installed on Exchange 2003 Server/domain controller.
4. Outlook profile has been corrupted.
5. Exchange database has been corrupted (usually this will occur if some third party software – like antivirus – scans Exchange database directly).

Continue reading Troubleshooting Error Code 0x8004011b

Trying to view Public Folders in the Exchange System Manager can sometimes cause the error message “The SSL certificate name is incorrect – ID Number  c103b404” to occur. This happens when a SSL certificate on the default web server contains a different Fully Qualified Domain name (FQDN) than the internal server’s FQDN – externally the server had a different FQDN than what is used internally. If the Exchange System Manager thinks that the folder name is incorrect then it will not allow you to view the public folders.

One solution is to remove the SSL requirement from both the public virtual directory and the Exadmin in IIS. You should also read and review Microsoft Article ID : 324345. http://support.microsoft.com/kb/324345/en-us

Another solution is to use the ADSIEdit utility to manually stop the Exchange System Manager from using SSL. You can do so by doing the following:

1. Install the ADSIEdit Utility (a Windows Server Support tool) from your SBS CD using suptools.msi
2. Run a Microsoft Management console (Start->Run->MMC)
3. Open the ADSIedit.msc (browse to the Support Tools folder)
4. Drill down to: Configuration > Services >  Microsoft Exchange > Domain Name > Administrative Groups >     First Administrative Group > Servers > Servername > Protocols > HTTP > 1 > Exadmin
5. Right click msExchSecureBindings, and click Properties
6. Highlight :443: and click Remove
7. Click OK
8. Restart the Exchange System Attendant and the IIS Admin service

Continue reading Troubleshooting Error Code c103b404

Troubleshooting error codes in Microsoft Windows can be an arduous task. Oftentimes the error code can occur under different conditions and will take multiple diagnostic paths until you discover the reason for the error. Sometimes the error can seem random and other times the error is consistent and can be reproduced.

For instance, error code 0×80040119 is most often produced to indicate synchronization problems. Sometimes the error will occur after you’ve performed an Exchange upgrade. But diagnosing what code or application produced the error will take some time.  If you’re like most system administrators your highest priority is to keep the systems up and running. And this implies that you need to keep your end users up and running. So with that pretext in mind I will focus this blog post on how to correct your problem so that you can keep your users online and as productive as possible.

Sometimes you will have a small number of email users, out of hundreds of users, who are the only ones receiving email error messages. Everyone else will be receiving emails with no problems.  The email error messages will reference error code 0×80040119 and say something about client operation failures or synchronization errors. One such system administrator running Microsoft Outlook had the situation where only a couple email users out of many were receiving emails indicating synchronization issues. Here’s a sample of those email error messages:

Synchronizer Version 11.0.6352
Synchronizing Mailbox ‘John, Doe’
Synchronizing Hierarchy
Error synchronizing folder
       [80040119-501-0-5C0]
       The client operation failed.
       Microsoft Exchange Server Information Store
       For more information on this failure, click the URL below:
       http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80040119-501-0-5c0
Done
Microsoft Exchange offline address book
Download successful

A possible solution is to recreate the outlook profile for each user who is having the error messages. This has been known to fix the problem in the past.

Continue reading Troubleshooting Error Code 0×80040119