Exchange 2010
Anything interesting and related to Microsoft Exchange 2010
-
The InnerException message was ‘Maximum number of items that can be serialized or deserialized in an object graph is ‘2000000’.
This was quite an interesting error for a mailbox I tried to migrate from Exchange 2013 to Exchange Online. The mailbox synced to 95% and I received the below error after I tried completing the batch. Error details: The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://tempuri.org/:ISourceFolder_EnumerateChanges2Result. The InnerException message was ‘Maximum number of items that can be serialized or deserialized in an object graph is ‘2000000’. The key to this error is the object graph limit that is set in the MsExchangeMailboxReplication.exe config file. To resolve the issue do the following: Logon to your on premises Exchange…
-
This operation requires a unique source object, but multiple objects have been found. Please remove any wildcard characters and check the data source for corruption.
You receive an error as per below when trying to restore a user’s mailbox in Exchange from a Recovery Database: This operation requires a unique source object, but multiple objects have been found. Please remove any wildcard characters and check the data source for corruption. I’m currently busy with a hand over at work and the engineer that will be taking over from me ran into this error when trying to restore a user’s mailbox. The Recovery Database has been created and the data has been restored to the database. The database is mounted and he was trying to run the below from the Exchange management Shell: Restore-Mailbox -Identity “UserSurname,…
-
Removing mail with the same subject from the Exchange Queues
Sometimes you need to remove thousands of e-mails in your Hub Transport server queues. We see this every now and then with mail storms from an application that went off the rails or maybe with 2 mailboxes sending each other auto replies causing a mail loop. There’s a few ways to stop the mail storm before removing the mail items in your Exchange queues but that is not the scope for this article. If you are ever in the situation of thousands of mails queued on all your Hub Transport servers then the below cmdlet should help you to quickly remove those mails from the queue. (Obviously do this with…
-
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: 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: To rectify this, open AD Attribute Editor and browse to the msExchRecipientTypeDetails attribute. You should see the below: Change the Value of 2 to 1 for msExchRecipientTypeDetails as you need the mailbox to show as a user mailbox on premises before…
-
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…
-
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…
- Active Directory, Exchange 2007, Exchange 2010, Exchange Management Shell, Exchange Online, Exchange Tools, Microsoft Exchange, Office 365
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: Logon to Exchange Online using Powershell. Run: get-mailbox user | fl *archiveguid* Make a note of the GUID Open Exchange Management Shell on premises Run: Get-RemoteMailbox User | fl *archiveguid* You should see that the GUID on prem is different to the GUID from Exchange Online To resolve, in Exchange Management Shell on prem run: Set-RemoteMailbox User -ArchiveGuid “GUID you got from Exchange Online” The above should work without…
-
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: Make note of the distribution group in the recipient information tab. Search for the Distribution Group in Exchange Management Console Right click on the group and choose properties Go to the Advanced tab 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…
-
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…
-
Exchange 2010 Queue Build up with Event ID 1035
We had an interesting issue with queues building up to remote sites. In queue viewer we noted errors sending mail to different remote sites as per below: 451 4.4.0 Primary Target IP Address responded with: “235 00000xxxxxxxxx” And in the Event Viewer we noticed event ID 1035 , MSExchangeTransport At first we thought the issue has to be on the specific Exchange 2010 server trying to send the mail as it was the only server in the DAG that could not send mail to the remote servers. However, the problem was still present after restarting the Hub Transport Service on the server experiencing the above issues. As a shot in…