Nov 14 2016

Error: MigrationRecipientNotFoundException: A recipient was not found for “mailboxName”

If you received the error “Error: MigrationRecipientNotFoundException: A recipient was not found for “mailboxName”” when migrating a mailbox to Exchange Online (Office 365) then check for the below AD attributes.

The error from the Exchange Admin Portal on Office 365:

0365migrationrecipientnotfound

Open the on premises Exchange Management Console and search for the user. You should see the mailbox shows it’s a Linked Mailbox instead of a Remote Mailbox as expected:

linkedmailbox

To rectify this, open AD Attribute Editor and browse to the msExchRecipientTypeDetails attribute. You should see the below:

msexchrecipienttypeforlinkedmailboxes

Change the Value of 2 to 1 for msExchRecipientTypeDetails as you need the mailbox to show as a user mailbox on premises before trying to migrate it to Exchange Online.

1

Wait for replication, remove the move request in Exchange Online via Shell and then migrate the mailbox to Exchange Online


Nov 14 2016

VB.Net application unable to connect to some Exchange 2010 mailboxes

We had an interesting issue last week where a Visual Basic .Net application could connect to some mailboxes but could not connect to other mailboxes on Exchange 2010. The application uses MAPI to connect to the mailboxes.

We were however able to access the affected mailboxes using Outlook and with the MFCMAPI tool from the application server. We moved the affected mailboxes to other servers and databases but the application could still not connect to the affected mailboxes. We then added our CAS Array name and IP in the application server’s host file and checked the Exchange RCA logs.

We could not see any connections from the application server to the affected mailboxes but could see connections to the working mailboxes in the RCA logs.

The error from the application were as below but note that it was misleading as it stated it authenticated, connected but could not expand the mailbox store.

ProcessMails() LogonExchangeMailbox Success
———————————————————————————
Date Time : 2016-11-07 06:30:17
Error : Error in IMAPISession::OpenMsgStore: MAPI_E_FAILONEPROVIDER
ulVersion: 0
Error: The information store could not be opened.
Component: MAPI 1.0
ulLowLevelError: 0
ulContext: 649
Source : at Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack)
at MailReader.Form1.ProcessMails(String sToDoFolder, String sDuplicateToDoFolder, String sTiffFolder, String sDuplicateTiffFolder, String sExchangeServer, String sInboxUser, String sInboxName, Int32 maxItems, Int32 branchRef)

We then resolved the issue by doing the following:

  • Opened Exchange Management Shell
  • Ran this cmdlet against a working mailbox: get-mailbox mailboxSMTPaddress@domain.com |fl *legacy*
  • Made a note of the output
  • Ran the above cmdlet against a non working mailbox and compared the outputs.

The output of the working mailbox:

ServerLegacyDN : /o=yourdomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MailboxServerName
LegacyExchangeDN : /o=yourdomain/ou=exchange administrative group (fydibohf23spdlt)/cn=recipients/cn=MailboxAlias

The output of the non working mailboxes:

ServerLegacyDN : /o=yourdomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MialboxServerName
LegacyExchangeDN : /o=yourdomain/ou=SomeOU/cn=recipients/cn=MailboxAlias

The fix:

We then used AD Attribute Editor to change the LegacyExchangeDN on non working mailboxes (LegacyExchangeDN : /o=yourdomain/ou=SomeOU/cn=recipients/cn=MailboxAlias) to reflect the working mailboxes’ LegacyExchangeDN (LegacyExchangeDN : /o=yourdomain/ou=SomeOU/cn=recipients/cn=MailboxAlias)

Waited for replication and the application could once again access all the required mailboxes.


Sep 13 2016

Error due to mismatch of GUID: Recipient “NameOfRecipient” has mismatched Archive GUID

You receive the error “Recipient “NameOfRecipient” has mismatched Archive GUID” when you try and off board a mailbox from Exchange Online to on premises Exchange.

Follow the below steps o resolve the issue and migrate the mailbox back to the on premises Exchange environment:

  1. Logon to Exchange Online using Powershell.
  2. Run: get-mailbox user | fl *archiveguid*
  3. Make a note of the GUID
  4. Open Exchange Management Shell on premises
  5. Run: Get-RemoteMailbox User | fl *archiveguid*
  6. You should see that the GUID on prem is different to the GUID from Exchange Online
  7. To resolve, in Exchange Management Shell on prem run: Set-RemoteMailbox User -ArchiveGuid “GUID you got from Exchange Online”

The above should work without any issues but we had an issue where the mailbox in question was migrated from Exchange 2007, we want to migrate it back to an Exchange 2010 DAG and received the below error when trying to set the GUID as per step 7 above:

Property Archive GUID can’t be set on on this object because it requires the object to have version 0.10 (14.0.100.0) or later. The object’s current version is 0.1 (8.0.535.0)

To resolve the above error follow the below steps:

  1. Open Active Directory Users and Computers
  2. Make sure you choose view -> Advanced Features
  3. Browse to the User, right click on the user and choose Properties
  4. Click on the Attribute Editor Tab
  5. Look for MSExchVersion and open it
  6. We had to change the version to Exchange 2010 from 2007. Thus change the data to 44220983382016
  7. Click OK
  8. Wait for replication and run the Set-RemoteMailbox User -ArchiveGuid “GUID you got from Exchange Online” again from Exchange Management Shell on prem.
  9. Wait for replication
  10. Run get-mailbox User | fl *archiveguid* and make sure the GUID has now been changed to the GUID you found in Exchange Online
  11. Proceed to migrate the mailbox to on prem after the GUID has been set

The Exchange Version AD Attributes are:

Exchange 2010: 44220983382016

Exchange 2007: 4535486012416

We used the below 2 web articles / blogs which assisted us greatly. Please check out these articles as well as they were the sources used to resolve the above mentioned issues:

Paul Cunningham’s ExchangeServerPro.com website:

The Article which describes how to get the Archive GUID and set it on prem.

Technotip blog.

Here we found the attribute values for the Exchange versions.

 

 


Sep 7 2016

Find a duplicate e-mail address in Active Directory

We recently started seeing a lot of mails stuck in the submission queues and found that there were a few duplicate e-mail addresses in the environment. Most of the time we could not find the duplicate addresses in Exchange and had to search for the duplicates in Active Directory as some addresses were bound to AD objects.

To search for a duplicate address do the following:

  1. Open Active Directory Users and Computers
  2. Right click on your domain name and click on find
  3. Next to find choose custom search (see below screen shot)
  4. Then click on the Advanced tab (see below screen shot)
  5. Under “Enter LDAP query:” type the next search query (see below screen shot)
  6. proxyaddresses=smtp:useremail@domain.com
  7. Click find you you should find all objects with the duplicate address.

Screen Shot of the LDAP query in when looking for a duplicate address


Aug 12 2016

Unable to see remote mailbox on the on premises Exchange servers but can see it in Exchange Online

We’ve had a few instances where a user could not receive mail into their Exchange Online mailbox. Upon investigation we noted the onmicrosoft.com address is the primary SMTP address for the user and that the remote mailbox object is not available in Exchange on premises.

To resolve this do the following:

  • Open Active Directory Users and Computers (dsa,msc from start -> run)
  • Click on View -> Advanced Features
  • Do a search for the user who has the issue as per above
  • Right click on the user and choose properties
  • Click on Object and make a note of the path
  • Close the search you made.
  • Now navigate in Active Directory Users and Computers to the user by dropping down through the OU’s etc.
  • Right click on the user and choose properties
  • Click on Attribute Editor (Note that changes made here could break something so make sure you compare it to a working user just in case)

Now you need to look for the below entries and change them or ensure they are set correctly as per below:

  • homeMDB – <not set>
  • homeMTA – <not set>
  • msExchHomeServerName  – <not set>
  • msExchRemoteRecipientType – 6
  • msExchRecipientDisplayType – (-2147483642)
  • msExchRecipientTypeDetails – (2147483648)
  • proxyAddress – check SMTP addresses are all there and correct
  • targetAddress – smtp:alias@yourdomain.mail.onmicrosoft.com (check this against a working user in your environment)


Mar 6 2015

Unable to expand a distribution list in Outlook – Exchange 2003 Environment

Have you ever receive an error stating that “There was an error while expanding the list. The list was not fully expanded.” when you try and expand a distribution list in Outlook? The error looks like the one below:

list

To solve this change the list to a Universal Distribution Group. Wait for replication if need be and you will then be able to expand the list and view the members within Outlook.


Oct 29 2014

Exchange 2003 Services won’t start – Event ID’s 9175, 2114 and 1005

Exchange Server 2003 services does not want to start or takes a long time to start for all the Exchange servers in the same site.

We had this issue and found that the Exchange servers tried to authenticate with a domain controller in another site. I found that the Exchange servers had the local Domain Controllers configured in Exchange and could contact the servers using ping and telnet.

The application log showed 3 errors that were related to the Exchange Servers not being able to authenticate to the local Domain Controllers. The event ID’s were 9175, 2114 and 1005.

Solution:

Add the “Manage auditing and security log” permission under “local policy – User Rights assignment on the local Domain Controllers.

For more on this please see this Microsoft Article.


Aug 13 2014

E-mail address strikethrough in Exchange 2007

We had a problem when our provisioning system would not update the “managed by” property for a distribution list.

Further investigation showed that the distribution list’s e-mail address had a strike through like this: (Seen in the DL’s properties using EMC)

email@company.com

We could not add a new smtp address to the group nor delete the current address.

We then opened ADSIedit to have a more in depth look. We then noticed that the SMTP address in proxyAddresses had a space before the @ in the SMTP address. We rectified that and the strikethrough disapeared.

We made the changes and managed to provision the DL without any problems.


Aug 5 2014

Adam Database not syncing with Active Directory

I have a multi tenant messaging system that needs to sync user information to Mimecast. We have setup an ADAM database to sync with Active Directory. In turn Mimecast syncs with the ADAM database to have up to date user details of which SMTP addresses are the most important as Mimecast has been setup to not allow mail from an e-mail sent from our system for an email address that it is not aware of.

Problem:

ADAM stopped syncing with Active directory because of the below errors found.

1. The error in the ADAM sync log

Error

 

2. The problem shown in the ADAM database

orphaned object

Resolution:

Delete the containers as shown in 2 above and re-run the sync.