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.

It is possible that you receive the following message in the synchronization log:
12:51:31 Error synchronizing folder   
12:51:31 [80004005-501-0-550]   
12:51:31 The client operation failed.   
12:51:31 Microsoft Exchange Server Information Store
     
You might also receive the following error message when you attempt to copy/move:
“Can’t move the items. The item could not be moved. It was either already moved or deleted or access was denied.”

To resolve this behavior, verify that all items with attachments are either opened or deleted when you receive them.

You can use the Preview pane in Outlook to view the messages. This opens the messages and allows the scan to take place. There may be minor delays in the process while the scans occur.

In the case where (2) active mail session with Exchange server becomes broken - this may happen if xp_sendmail fails with the mail error code 0×80004005.

When you use xp_sendmail extended stored procedure to send e-mail from SQL Mail with SQL Server 2000, you might receive the following error message:
 
Server: Msg 18025, Level 16, State 1, Line 0
xp_sendmail:failedwithmailerror 0×80040005
 
You receive the same error message if you use SQL Server Agent to send email messages. However, when you use the Microsoft Outlook client on a computer that is running SQL Server (and Outlook is configured with the same MAPI profile as SQL Mail), the delivery of messages is not affected and you can successfully send e-mail.

You can experience problems described in the “Symptoms” section of this article if connection to the Microsoft Exchange server was broken during active SQL Mail session. The connection could be broken due to a sudden loss of network connectivity with an Exchange server or because of other network problems. As a result, an invalid SQL Mail session is left on an SQL Server, and SQL Server attempts to utilize it for xp_sendmail calls. Since the mail session is invalid, an error is returned.

To fix the problem without restarting the SQL Server service, you may manually stop the invalid mail session. To do so, connect to the SQL server with Microsoft SQL Server Query Analyzer or similar utility using an account with sysadmin privileges, and run the following command:
 
exec master.dbo.xp_stopmail
 
This will force the broken mail session to quit and allow new sessions to be successfully created during xp_sendmail calls.

Another situation can occur where you receive the 0×80040005 error message, “Send Message Error: -2147467259 – (Collaboration Data Objects) – e_fail (80004005)”

This error occurs when (3) emailing a report using the tree email from within FRx Report Designer.

One of the following should resolve the error:

1. Confirm that the pathing for the Output path in the Company – Information screen and pathing that has been entered in the Catalog – Output tab Filename field is a valid path.
2. When sending an attachment and using the email in the tree, a Mailbox file size limit may be reached. Remove some users from the tree or increase the size limit of the Microsoft Outlook mailbox.

Another possible circumstance when you might receive the error code 0×80040005 is (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. Then the DAV query of the information store for message properties returns the 0×80004005 error code.

A 0×80004005 (ecCallFailed) error is returned if the urn:schemas:mailheader:to property is requested. Additionally, an error is returned if there are messages in the result set that have recipients where the value of PR_EMAIL_ADDRESS is an empty string (”").

To resolve this problem, obtain the latest service pack for Exchange Server 2003. For more information you can review article number, 836993, in the Microsoft Knowledge Base to learn more about how to the latest service packs for Exchange Server 2003.

In addition, a supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem concerning when the DAV query of the information store for message properties returns the 0×80004005 error code.