Microsoft Exchange
Anything interesting and related to Microsoft Exchange
-
The Active Directory schema isn’t up-to-date, and this user account isn’t a member of the ‘Schema Admins’ and/or ‘Enterprise Admins’ groups.
I am busy installing Exchange 2016 in a test environment and received the below error when running Setup.exe /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /PrepareSchema when trying to extend the domain schema. “The Active Directory schema isn’t up-to-date, and this user account isn’t a member of the ‘Schema Admins’ and/or ‘Enterprise Admins’ groups.” Thing is, my account is part of the Schema Admins and Enterprise Admins group. I then found the solution from this post (thanks Andy!) In short, open the group membership tab on your account in Active Directory Users and Computers and then check which group is set to default, then click on Schema Admins and click on Set Primary Group to make…
-
Unable to send mail through specific Send Connector
I’m finding it difficult to give this post a proper heading but hopefully the tags in the post would have led you to the solution of this problem I experienced. We have a specific Send Connector in Exchange 2016 that sends mail to one of our other companies in a different forest. I noticed that only on one server the queue for mail destined to this domain was queueing. The error in the queue destined to the other domain was stating that it failed to connect. I tested with telnet to the VIP IP and could not connect to the VIP on port 25. After restarting the Transport service and…
-
Maximum number of items that can be serialized or deserialized in an object graph is ‘2000000’
You receive the below error when moving a mailbox to another database in Exchange 2013: The default limit for the maxItemsInObjectGraph is set to 20000000. The work around that resolved this for me is as per below: Open Notepad and browse to: C:\Program Files\Microsoft\Exchange Server\V15\Bin (or where you installed Exchange). Look for the config file (MsExchangeMailboxReplication.exe.config) and open it. Hit ctrl + f and search for graph. You will see the below entries. Change the “2” to “3” in order to increase the limit. Restart the Microsoft Exchange Mailbox Replication service on the server you are migrating the mailbox to. Resume the move-request. Change the above back to the previous…
-
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…
-
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