Exchange on Remko's Blog

Exchange Move Mailbox Experiences Part 5

Tue, 04 Oct 2011 15:21:42 +0000

Another interesting Move Mailbox error and in this case I am really unsure how this would be possible!

Let's look at the Move Mailbox log:

powershell Download

1-10-2011 11:49:18 [The Exchange Server] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox.
<baditem id="0000000088B41EB2A774E14BA3B29759527EBBD007007A08E4E185746A45BF5C6EF2A17E8D5500000590285800007A08E4E185746A45BF5C6EF2A17E8D550000059028720000" flags="0x00000000" errorcode="0x80004005" errortype="MapiExceptionMaxSubmissionExceeded">
 <folder id="0000000088B41EB2A774E14BA3B29759527EBBD001007A08E4E185746A45BF5C6EF2A17E8D550000059028580000">Top of Information Store</folder>
 <sender>John Doe</sender>
 <recipient></recipient>
 <subject>archive.pst</subject>
 <messageclass>IPM.Document.PSTFile</messageclass>
 <size>38621879</size>
 <datesent>01/19/2006 14:30:57</datesent>
 <datereceived>01/19/2006 14:30:19</datereceived>
 <errormessage>Message (size 36.83 MB (38,621,879 bytes)) exceeds the maximum allowed size for submission to the target mailbox. You can increase this limit by using the Set-Mailbox cmdlet in the Exchange Management Shell.
Error details: MapiExceptionMaxSubmissionExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1242)

This error occurs because of a size constraint just like the one in the previous part.

But the strange part is that it seems to be a PST file (type IPM.Document.PSTFile) located in the Root folder of the Exchange mailbox (which is not possible AFAIK).

Exchange Move Mailbox Experiences Part 4

Tue, 04 Oct 2011 13:43:23 +0000

The previous part (part 3) addressed Mailbox Size but did you know that even Message Size (or rather Item size) can prevent a successful move as well?

Here's an example move mailbox log:

powershell Download

2-10-2011 3:18:58 [The Exchange Server] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox.
<baditem id="00000000469F68BB3AD7E745B2B8A041FC1B688C07007A08E4E185746A45BF5C6EF2A17E8D55000001537A9D00007A08E4E185746A45BF5C6EF2A17E8D55000001540FF30000" flags="0x00000000" errortype="MapiExceptionMaxSubmissionExceeded" errorcode="0x80004005">
 <folder id="00000000469F68BB3AD7E745B2B8A041FC1B688C01007A08E4E185746A45BF5C6EF2A17E8D55000001537A9D0000">verzonden nov 2004-aug 2005</folder>
 <sender>Jane Doe
 <recipient></recipient>
 <subject>Foto's afscheid John Doe 10 februari jl.</subject>
 <messageclass>IPM.Note</messageclass>
 <size>76121694</size>
 <datesent>02/15/2005 15:28:06</datesent>
 <datereceived>02/15/2005 15:28:06</datereceived>
 <errormessage>Message (size 72.6 MB (76,121,694 bytes)) exceeds the maximum allowed size for submission to the target mailbox. You can increase this limit by using the Set-Mailbox cmdlet in the Exchange Management Shell.
Error details: MapiExceptionMaxSubmissionExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1242)
Diagnostic context:

As you can see in the log this mailbox there is one item with a size of 72 MegaBytes.

Exchange Move Mailbox Experiences Part 3

Wed, 28 Sep 2011 11:08:21 +0000

In Part 2 I showed some details about Mailbox Rule corruptions that can disturb Mailbox Moves.

For this part the topic is Mailbox size, which can be an important factor in deciding which mailboxes you want to move first.

In my case the mailbox size was important because we agreed to move smaller mailboxes during the day but larger mailboxes only outside working hours.

For Exchange 2010 mailboxes it's very easy to obtain the size using PowerShell.

Example:

powershell Download

Get-Mailbox "rweijnen" | Get-MailboxStatistics | select DisplayName, ItemCount, TotalItemSize

 <td valign="top" width="70" align="right">ItemCount</td>

 <td valign="top" width="230" align="right">TotalItemSize</td>
</tr>

<tr>
 <td valign="top" width="130">Remko Weijnen</td>

 <td valign="top" width="70" align="right">313</td>

 <td valign="top" width="230" align="right">34.87 MB (36,564,183 bytes</td>
</tr>

DisplayName

But how can we get the Mailbox Size for Exchange 2003 mailboxes?

Exchange Move Mailbox Experiences Part 2

Tue, 27 Sep 2011 15:07:15 +0000

In part 1 we saw that a corrupted rule made the Mailbox Move fail.

I wanted to know if I had really a corrupted mailbox or maybe even corruption in the store or another problem.

So in this part I will describe how to break down the Mailbox Move Log.

First go to the Failed Move Request and select Properties:

Exchange Move Mailbox Experiences Part 1

Wed, 21 Sep 2011 16:38:23 +0000

I am currently working on a migration project from Exchange 2003 to Exchange 2010.

Most Exchange migration projects use Mailbox Moves to move the mailbox data to the new Exchange environment.

But there are some things I observed during Mailbox Moves (from Exchange 2003 to 2010) that are worth mentioning.

Cannot achieve Exchange Server authentication

Wed, 17 Aug 2011 16:49:53 +0000

I was testing outgoing mail flow in my new Exchange 2010 setup, which should go from the CAS Servers to the Edge server in the DMZ.

After configuring the Edge subscription I noticed that outgoing mails got stuck in the queue with the following error:

"451 4.4.0 Primary target IP address responded with: "451 5.7.3 Cannot achieve Exchange Server authentication." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts."

I verified that name resolution back and forth was ok and that I could communicate on port 25, 50389 and 50636.

Get smallest Exchange Database in PowerShell

Tue, 16 Aug 2011 14:16:33 +0000

I needed to adapt some scripts that create a user with mailbox for Exchange 2010. The existing scripts had a hardcoded database for new mailboxes.

I wanted the mailbox to be created in the smallest database, but how do we determine this?

Set Exchange Product Key with PowerShell

Mon, 15 Aug 2011 09:17:14 +0000

By default Exchange 2007 and 2010 are installed in Trial mode so before going into production you need to enter the Product Key.

The Exchange Management Console will warn you if one or more servers are still in trial mode:

PowerShell script to set Exchange Static RPC Ports

Wed, 10 Aug 2011 16:49:01 +0000

I am currently working on an Exchange migration from 2003 to 2010. For the implementation of a load balancing solution for the CAS/HUB servers I needed to set Static RPC Ports for the RPC Client Access Service and the Exchange Address Book Service.

The procedure of changing these ports is described on the Technet Wiki: Configure Static RPC Ports on an Exchange 2010 Client Access Server

Since I am lazy I decided to do this with a PowerShell script that would automatically do this for all CAS/HUB servers in my 2010 environment.

The case of the duplicate SID’s

Mon, 27 Jun 2011 10:04:01 +0000

I encountered another interesting error during Exchange 2010 installation today. During the Organization Preparation I got the following error:

The setup.log doesn’t give us much more detailed info:

text Download

[06-22-2011 11:16:29.0614] [2] [ERROR] Active Directory operation failed on dc001.zorg.local. This error is not retriable. Additional information: The requested object has a non-unique identifier and cannot be retrieved.
Active directory response: 0000219D: SvcErr: DSID-031A0FC0, problem 5003 (WILL_NOT_PERFORM), data 0

[06-22-2011 11:16:29.0630] [2] [ERROR] The server cannot handle directory requests.
[06-22-2011 11:16:29.0630] [2] Ending processing initialize-ExchangeUniversalGroups
[06-22-2011 11:16:29.0630] [1] The following 1 error(s) occurred during task execution:
[06-22-2011 11:16:29.0630] [1] 0. ErrorRecord: Active Directory operation failed on dc001.zorg.local. This error is not retriable. Additional information: The requested object has a non-unique identifier and cannot be retrieved.
Active directory response: 0000219D: SvcErr: DSID-031A0FC0, problem 5003 (WILL_NOT_PERFORM), data 0

[06-22-2011 11:16:29.0630] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on dc001.zorg.local. This error is not retriable. Additional information: The requested object has a non-unique identifier and cannot be retrieved.
Active directory response: 0000219D: SvcErr: DSID-031A0FC0, problem 5003 (WILL_NOT_PERFORM), data 0

I remembered from a Tweet by Helge Klein recently that the Active Directory schema has no mechanism for enforcing uniqueness of an attribute.

Exchange 2010 well-known object entry install error

Fri, 24 Jun 2011 12:52:30 +0000

Today I was testing the installation of Exchange 2010 in a VMWare sandbox environment. We created the sandbox to test migration from a 2003 AD and Exchange environment to 2008 R2 with Exchange 2010.

We used a P2V to get real copies of the Active Directory and the AD upgrade to 2008 R2 was already tested.

But during the Exchange installation in the sandbox I got the following error:

How Outlook and Exchange handle Timezones

Wed, 18 May 2011 19:53:27 +0000

Again an old war story, this time about timezone handling in Outlook/Exchange.

I am not sure which year it was but I had just started to work for a new company and inherited an Exchange 5.5 Server.

The mail had been migrated from an earlier version and calendar data was migrated from Schedule+.

On the first change to Daylight Savings (DTS) all recurring appointments where shown one hour later (or earlier can't remember) in Outlook. A manual change was not an option: there were over 2000 mailboxes each with a lot of appointments.

We first tried a workaround by disabling DTS on the the workstations and then manually change the time when changing from and to DTS.

But this influenced the timestamps on externals mails and of course appointments with external parties.

After a lot of (and I really mean a lot) of researching I found that Outlook stores all times in an appointment as relative (UTC) time.

Upon display it uses an undocumented TimeZone descriptor field to convert to Local Time.

Adding a hidden Exchange mailbox to Outlook

Tue, 25 Jan 2011 13:11:42 +0000

In Exchange it’s possible to hide a Mailbox from the (Global) Address List. You can do that in the Exchange System Manager:

But after you have hidden a Mailbox you cannot create an Outlook profile for it (or add it as an extra mailbox).

When you click Check Name in the wizard you’ll get an error:

The common workaround is to remove the “Hide from Exchange address lists” setting, create the profile (or add the Mailbox) and afterwards set it again.

Once the profile is created it all keeps working.

There is an easier solution though!

Scripted creation of Server Manager Answer Files

Thu, 25 Nov 2010 16:14:42 +0000

A while ago I created a script that I can run as embedded script in Altiris that creates a Server Manager Answer File (for Server 2008).

I could have simply done an echo >answer.xml but I wanted a well formed XML that could be read and displayed in an XML editor or Internet Explorer when needed.

I use the Microsoft.XMLDom object in the script the create the XML and I think the code is easy to understand so I will just show it here:

The case of the failing Exchange 2007 Install

Mon, 08 Nov 2010 20:56:24 +0000

I was creating an unattended Exchange 2007 install job today and while testing it, it failed with the following error:

text Download

Active Directory operation failed on nl-dc001.MYDOMAIN.LAN. The object 'CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=My Organisation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MYDOMAIN,DC=LOCAL' already exists

I opened the Exchange System Manager and expanded the Tree (Recipient | All Address Lists | All Global Address Lists) and I found 2 Global Address Lists but not the Default Global Address List:

Removing Public Folder Replicas in Exchange 2007

Wed, 11 Nov 2009 15:47:35 +0000

When you uninstall Exchange 2007 you need to remove all Mailbox- and Public Folder databases. If you try to remove the Public Folder Database this will fail because there are replicas of the system folders in the Public Folder database. I didn’t find a way to remove these replicas from the Exchange Management GUI but it can be done with the following Powershell Code: