During a cross-forest test migration from Exchange 2003 to Exchange 2010 I got the following error:

Warning: Unable to update AD information for the source mailbox at the end of the move.  Error details: An error occurred while updating a user object after the move operation. –> Failed to find the address type object in Active Directory for address type “SMTP:AMD64″.
Failed to cleanup the source mailbox after the move.
Error details: MapiExceptionNotFound: Unable to delete mailbox. (hr=0x8004010f, ec=-2147221233)

When I looked in the old and new environment I found out that the mailbox both existed in the old and new environment. In this  case you might have a big issue even when the mail is delivered in the Exchange 2003 environment  and the homeMDB attribute is not updated. Updating the attribute may take a while due to AD replication, in this case mail is not delivered in the new mailbox and so mails will not be placed in the new mailbox.

To prevent this issue Microsoft has released a hotfix for Exchange 2003 which can be found on the website below.

open

Gepost in Exchange 2003, Exchange 2010 ~ Geen Reactie

During one of my forum visits I found a really interesting issue. Someone tried to remove his old Exchange 2003 cluster but received the following error when trying to dit it:

Found no Disk resource for the disk that contains the folder ‘W:\EXCHSRVR’

When looking in the Cluster Administrator the resource was not visible, very strange. So we needed to remove the pointer to the w:\ disk by using ADSIEDIT.

Before performing such an action you will first need to create a backup of your AD.

Next execute the following steps:

- open adsiedit
- choose connect to
- change the domain to configuration
- expand CN=Configuration …
- expand CN=services
- expand CN=Microsoft Exchange
- expand CN=First organization (or your organization if different)
- expand CN=servers
- expand CN=servername
- expand CN=Information Store

There you will find the First Storage group and other storage group. Get the properties of them both the storage group and the databases in it it and check if none of them points to the w:\disk
But in this case it was something else where we need to have a look at, perform the same steps as above but stop after expand CN=servers and continue with the steps below:

- get the properties of theservername
- search for the value MsExchDataPath
- check if the pointer is not listed

After this try to remove the Exchange cluster again.

Gepost in Exchange 2003 ~ Geen Reactie

Today I had a nice issue with Exchange. For some kind of strange reason Exchange 2003 kept sending the same mails.  Even when deleting the mails from the queue in the Exchange System Manager. A result of this was that the bandwidth was almost used 100% so I adjusted the simultaneous connections etc, without any effect.

So I decided to search for a solution for this issue. I found a post on expert-exchange which described almost the same issue. It adviced to use MFCMAPI to cleanup the temp table. The specific messages may get stuck in that table

After applying the solution the issue was solved indeed, below you will find the steps to solve the issue:

• download and install MFCMAPI
• choose session and select logon and display store tables
• if there are multiple profiles found you will be asked to select a profile, in this case select the administrator profile
• an overview of the mailbox and public folders will be displayed. Select MDB  and choose the option get mailbox table
• an overview of all mailboxes found in the store will be displayed. Search for the mailbox of SMTP
• search in the left pane for Temp Tables
• delete all sub folders below the Temp Tables, when asked if the messages need to be hard deleted choose to do this
• restart the SMTP service

Gepost in Exchange 2003 ~ Geen Reactie