-
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,…
-
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
- 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…
-
Provisioning Layer initialization failed error when running a cmdlet in Exchange Management Shell
I’ve had the below error a few times this year when trying to open the Exchange Management Shell or running a cmdlet. To get this working browse to another Exchange 2010 server and copy the ScriptingAgentConfig.xml file from the working server and paste it in the same directory (as per below) on the non-working server. The file can be found under your Exchange Installation by default c:\Program Files\Microsoft\Exchange Server\V14\Bin\CmdletExtensionAgents\
-
Unable to connect a disconnected mailbox – User not found error when trying to connect a mailbox to a user in Exchange
We’ve had a few instances where we need to disconnect a mailbox and reconnect it to a new user account for a user. This should be easy right? Well not always. It’s happened more than once where we try to use the Exchange Management Console to connect the mailbox to the user account but Exchange can’t find the user account. Have a look in Active Directory and the account shows up. You then try to connect the mailbox to the user account using the Exchange Management Shell with the same results. user not found. See below on how to get this issue resolved: 1. Open adsiedit.msc (start, run and type…
-
E-Mail delivers to Deleted Items folder
We had a shared mailbox where all the mail sent to the mailbox delivered to the deleted items folder. To resolve this do the following: 1. Open Exchange Management Shell 2. Type Get-CalendarProcessing “mailboxname” | fl and press enter 3. If AutomateProcessing shows AutoAccept in the returned results then run the next cmdlet 4. Set-CalendarProcessing “mailboxname” -automateprocessing none 5. Wait for replication and check that Get-CalendarProcessing “mailboxname” | fl shows that it’s set to :none We verified after running the above that mail delivered to the mailbox deliveres to the Inbox as expected.
-
Meeting requests sent to a room mailbox, replaces the Subject, with the Senders name
We received a call today where a meeting request sent to a Room mailbox shows the meeting organiser’s name in the subject line. This can be rectified by running the following: Exchange 2010/2013: Set-CalendarProcessing -identity “meeting room name” -DeleteComments $true -AddOrganizerToSubject $true -DeleteAttachments $true -DeleteSubject $true Exchange 2007: set-mailboxcalendarsettings -identity “meeting room name” -deletesubject $false -addorganizertosubject $false Hope this makes your life a bit easier.
-
When installing Exchange 2010 you receive “The start mode for the Net. TCP Port Sharing service must be set to Automatic before Setup can continue”
During my lab testing and installing Exchange Server 2010 on Windows Server 2008 R2 I keep receiving this pre-requisite that fails. The start mode for the Net. TCP Port Sharing service must be set to Automatic before Setup can continue. As far as I know (I might be wrong) this pre-requisite only fails the readiness check on Windows Server 2008 R2. In order to set the Net.TCP Port Sharing Service to Automatic at start-up do the following: Open Power Shell on the Windows 2008 R2 Server that you are trying to install Exchange 2010. Type: Set-Service NetTcpPortSharing -StartupType Automatic Hit enter. Run the Exchange installation wizard again and you should be…
