Nov 14 2016

Unable to access or move a mailbox receiving error the mailbox is disabled when it’s not

If you ever try to move a mailbox and you receive an error that the mailbox is disabled but you have checked and the mailbox is not disabled then try the following:
(other errors we received was trying to access the mailbox using Outlook Web App and stating it’s disabled or from Outlook stating you need to connect to Exchange)

  • Verify that the mailbox is indeed not disabled. If not proceed to the next steps
  • Open Exchange Management Shell and run: Set-CASMailbox -Identity mailboxSMTPAddress@domain.com -MAPIEnabled $False
  • Wait for replication
  • Run: Get-CASMailbox mailboxSMTPAddress@domain.com (check that it shows MAPI Enabled is false)
  • If MAPI Enabled is false run: Set-CASMailbox -Identity mailboxSMTPAddress@domain.com -MAPIEnabled $True
  • Wait for replication
  • Run: Get-CASMailbox mailboxSMTPAddress@domain.com (check that it shows MAPI Enabled is true)
  • Try an connect to the mailbox using Outlook, Outlook Web App or moving the mailbox.
  • If you still get an error try running: Clean-MailboxDatabase DatabaseNameWhereTheMailboxIsHomed (we actually had to run this for one of the mailboxes giving us issues)

This should sort out the issue for you.


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.


Oct 21 2016

Logging in to a shared mailbox using IMAP on Exchange 2010 using Outlook or a 3rd party application

I keep forgetting the correct way in which the username needs to be used when using IMAP to logon with your account to a shared mailbox.

To logon to a shared mailbox you need to provide the domain first then / and then the account you want to authenticate with and another / then the shared mailbox you are trying to access. Below is an example.

domain/accountThatNeedsToauthenticate/AliasOfTheSharedMailboxYouAreTryingToAccess


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

There is currently no route to the distribution group expansion server

You see the error “There is currently no route to the distribution group expansion server” in a stuck message from your Exchange Hub Transport server submission queue.

To resolve this:

  1. Make note of the distribution group in the recipient information tab.
  2. Search for the Distribution Group in Exchange Management Console
  3. Right click on the group and choose properties
  4. Go to the Advanced tab
  5. Untick the box next to “Set expansion server”

You might have to restart the Hub Transport or SMTP service depending on your Exchange version.

We found this happened because the Expansion server was removed from the environment and not accessible. Another cause could also be the deletion of a routing group in Exchange 2003.

 


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 9 2016

Newly migrated mailbox to Office 365 does not receive new e-mail

We had an interesting issue where  user’s mailbox was migrated to Office 365 but he could not see any new mail in the mailbox. Even sending himself mail did not show the new e-mail items.

We sent a few test mails and tracked the mail from on premises Exchange to Office 365 which showed that the mail delivered to the cloud.
We then traced the mail items from within the Office 365 admin portal and confirmed that the mails delivered to the mailbox but we could still not see the items.
Thinking that it might be desktop related we asked the user to logon to Outlook Web App and we could still not find the mail items that showed as being delivered to the mailbox.

I then ran the Get-InboxRule cmdlet against the mailbox to see if a rule might be interfering. Suddenly the new test mails sent after I ran the cmdlet delivered to the mailbox and we were able to see them. Testing all new mail to and from the mailbox seemed to have worked after I ran the Get-InboxRule cmdlet as if it reset the rules somehow.

This still boggles my mind but it’s worth a try if you have the same issue.


Mar 9 2016

Moving an on premise mailbox to Office 365 gives the error “Transient error StoragePermanentException has occurred. The system will retry (6/640).”

One of my colleagues battled to migrate an on premise Exchange 2010 mailbox to Office 365. After trying to repair the mailbox and numerous other things he still received the below error:

Transient error StoragePermanentException has occurred.

                                           The system will retry (6/640).

Eventually he appended the -SkipMoving:FolderRestrictions to the New-MoveRequest cmdlet and managed to migrate the user’s mailbox to Office 365.


Feb 24 2016

Messages awaiting directory lookup – Queue Build up on Exchange

We had an Exchange 2003 server that had a queue build up. The messages were building up in the “Messages awaiting directory lookup” queue.

After investigation we found that the server had old DNS entries which were removed and new entries were added. The queue cleared almost immediately.

If you see build up in the Messages awaiting directory lookup queue then be sure to check DNS is working as expected.