The upcoming release of Microsoft Exchange Server 2010 includes new email archiving features.  Previously the domain of third party add-on products from various software vendors, this marks the first time it has been built in to the Exchange Server product itself.

Given the long and proven history of some of the third party solutions one wonders whether Microsoft’s first attempt at a built in archiving feature will compare favorably.  Let’s take a look at what we know so far about archiving in Exchange Server 2010.

Exchange Server 2010 Archiving

There are a few pre-requisites for Exchange Server 2010 archiving to function.  Firstly, it requires Enterprise CALs for the users that will be archive enabled.  In addition, the archive mailbox is only viewable using Outlook 2010 (due for release sometime after Exchange 2010), which means Outlook 2007 and prior versions will not be able to see it, although it is visible using the Exchange 2010 Outlook Web App.

The archiving feature can be enabled on a per-mailbox basis.  Once enabled it creates a second mailbox for the user, the archive mailbox.  Mailbox items can be moved to the archive mailbox either manually or via the use of Retention Policies set by the administrator.

Unlike the primary mailbox, the archive mailbox cannot be cached by Outlook for offline access.  This reduces the file size of the cached OST file on the end user’s computer; however, this benefit is somewhat redundant because the OST file format in Outlook 2007 SP2 and Outlook 2010 has been greatly optimized and will now run quite efficiently at large sizes such as 10 gigabytes. Continue reading Is Exchange Server 2010 Archiving a Hit or Miss?

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

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

As always, getting an error message can have different causes. And when administering the “fix” you might not solve your problem. So I will offer a couple of different solutions to problems that produce the 0×8004011D error message.

Sometimes you have cancelled the Exchange Server logon for synchronization and you then receive the 0×8004011D error message from Outlook. This situation can occur when you synchronize and then work offline or restart offline. You’ll get the following error message after you press F9 to reconnect for another synchronization and then click Cancel in the network logon dialog box:

Task “Microsoft Exchange Server” reported error (0×8004011D): “The server is not available. Contact your administrator if this condition persists.”

Microsoft has confirmed that this is a problem in Microsoft Office Outlook 2007, Microsoft Office Outlook 2003 and Microsoft Outlook 2002 Standard Edition.

You can also get the same error message – Task “Microsoft Exchange Server” reported error (0×8004011D): The server is not available. Contact your administrator if this condition persists – whenever your machine tries to connect to the Exchange Server.

Continue reading Troubleshooting Error Code 0×8004011D

There are many situations when you may receive the error code 0×80040115.

Such situations may include:
- An attempt to save an activity in the Microsoft Dynamics CRM client.
- The xp_sendmail extended stored procedure does not run.
- The Information Store service crashes on an Exchange Server 2003.
- RPC data may be blocked and Outlook may not start in Windows Server.
- Event ID 8207 repeatedly appears in the application log.
- Event IDs When Starting the Information Store with Blank Databases.
- Multiple Exchange Server 2007 services do not start when you upgrade.
- Microsoft Exchange Server – Sending” reported error.
- The connection to the Exchange Server computer was lost.

Here are some ways to resolve some of these errors.

Continue reading Troubleshooting Error Code 0×80040115

Have your users ever complained about not being able to send email that had large attachments?

Sometimes your end users will try to send emails that contain large files that are maybe ten (10) to twenty (20) megabytes or larger. After they hit the submit button they’ll get an error message that goes something like: “The message being sent exceeds the message size established for this user.” You can check the user’s outbox and the message is still there.

This can happen with Exchange using Outlook. Outlook may or may not be setup in Exchange server cached mode. One thing you can do is to have the Exchange system administrator check the global send size limits. Then compare those limits to the size of the outbound email attachment. If the email attachment exceeds that size limit then you can have your user try zipping the file(s) so as to reduce the total size of the attachment(s). Then try re-sending the email.

The user may also have to consider splitting the attachment into smaller pieces and then resend those smaller chunks in separate emails. Sometimes users are sending PowerPoint attachments which can be very large when graphics and images especially are added to the presentation. The user could break the presentation into a sequence of three or four sections and then resend those sections separately.

Every once in a while you have the situation where you’ve attempted to preempt a potential problem by cleaning up a folder such as the Sent Items folder. One admin had reported that they removed a large message from the Sent Items folder after they surmised that the large message was not going to get past the recipient’s firewall and that the message was too large. After doing so they then started getting the 0×80040610 error code. They then tried to cancel all (pending transactions) but received another error indicating that the task was cancelled before it was completed. Continue reading Troubleshooting Error Code 0×80040610