Category: Exchange 2013

something went wrong UserHasNoMailboxException

Issue: Customer couldn’t access office 365 mailbox using the unified URL and kept getting “something went wrong, user has nomailboxexception” errors.
Notes: Customer was running hybrid configuration with Office 365 and Exchange 2013. Also the mailbox is a remote mailbox
Resolution: TargetOWAURL for the organization relationship at customer site was
outlook.com/owa/servicedomain.edu
Issue was resolved when customer modified remote routing address of the remote mailbox to user@servicedomain.edu
The service domain in the target OWA url needs to match the remote routing address of the remote mailbox

Exporting Mailbox to a PST File

​Exporting mailbox to a PST File
Note: Must have the “Mailbox Import Export” role assigned
 
From powershell, type New-MailboxExportRequest -mailbox testmbox -name -filepathservernamepstfilestestmbox.pst
This will export all folders and data in each and export it into the specified PST file. Also note that the dumpster will also be exported by default.
If you want to get additional details about the mailbox export request, you can use the Get-MailboxExportRequest or Get-MailboxExportRequestStatistics cmdlet.
 
if the export fails to complete, you can add -baditemlimit for eg
 
New-MailboxExportRequest -mailbox testmbox -name -filepathservernamepstfilestestmbox.pst -baditemlimit 50

Delivery status notifications in Exchange Server

Non-delivery reports (NDRs) are system messages that report the delivery status of a message to the sender. The messages are a subclass of a general message information structure that is known as delivery status notifications. Delivery status notifications describe three kinds of situations:

  • Success (2.X.X numeric codes)
  • Persistent transient failure (4.X.X numeric codes)
  • Permanent failures (5.X.X numeric codes)

NDRs are generated when a message cannot be delivered. If the computer can detect the reason for the failed delivery, it maps the reason onto a status code, and a corresponding error message is printed. For NDRs, most numeric error codes are reported in the form of “5.X.X” and are described as permanent failures. However, certain transient conditions cause “4.X.X” codes. 

Reference:

Check the Event Viewer from PowerShell

Below are examples of checking the event viewer via PowerShell.
Running local with event id and date range
Get-WinEvent -FilterHashtable @{logname=’application’;id=4107;StartTime=”1/15/11″;EndTime=”1/17/11″}
 
Running on remote computer with event ID
Get-WinEvent -computername <remote computer> -FilterHashtable @{logname=’application’;id=15006}

Allow Exchange 2013 to accept remote powershell from Orchestrator

Scenario: Orchestrator was not able to connect and run Exchange powershell commands. The error received is:

Error opening remote PowerShell runspace to endpointhttp://exchangeservername/powershell: Connecting to remote server failed with the following error message : The WinRM client cannot process the request.
 
Resolution:
1. Make sure the Execution Policy on the Exchange Shell is set to RemoteSigned.
a. Use Get-ExecutionPolicy to see what it is.
b. Use Set-ExecutionPolicy RemoteSigned to set it.
2. Enable Basic and Windows Authentication on the Powershell IIS Site.
a. Expand: Default Web siteàPowershell.
b. Click on Authentication
c. Enable Basic and Windows Authentication.
  
The above steps did the trick for me, but the site below offers a few more steps.

Permission issues Ex2013 shared calendar with Ex2010 mailbox

​​Scenario: A user with a mailbox in Exchange 2010 is getting permission errors in Outlook when trying to access and edit a shared calendar of a mailbox in Exchange 2013 even though the correct permissions are set for that Exchange 2010 mailbox. The error is:
“You do not have permission to veiw this calendar. Do you want to ask user to share his or her Calendar with you?”
Resolution: Enable Outlook to connect to Exchange using HTTP for the Exchange 2010 mailbox in the Outlook Profile
1. Start Outlook if not started already.

2. Navigate to your Outlook Account Settings:

a. Outlook 2013/2010: Click on File –> Account Settings–> Account Settings.
b. Outlook 2007: Click on Tools –> Account Settings.
3. Select your Exchange account, and then click Change.

4. Click More Settings, and then click the Connection tab.

5. Under Outlook Anywhere (Exchange over the Internet for 2007), select the Connect to Microsoft Exchange using HTTP check box.

6. Click Exchange Proxy Settings.

7. Make sure the following settings are set:
a. Enter the URL to connect to  proxy server for Exchange: https://mail.domain.com
b. On fast networks, connect using HTTP first,… is checked.
c. On slow networks, connect using HTTP First,… is checked
d. Proxy Authentication Settings is set to Basic Authentication.

8. Click OK to close each Outlook window.

9. Restart Outlook

10. If your are prompted for authentication, use the following:
a. username: domainusername
b. password: your password.

IMAP4 backend service not authenticating to any mailbox on that server.

Scenario: The IMAP4 Backend Service cannot connect to local mailboxes in Exchange 2013 after confirming there was a certificate on the Exchange 2013 server with the IMAP and POP services assigned. The symptom on the client end is failed authentication prompts when connecting to their mailbox via imap using valid credentials and IMAP being enabled on their mailbox.

The IMAP log displays the following: 
NO AUTHENTICATE failed.””;Msg=””AuthFailed:LogonDenied
 
The application log in the event viewer displays the following:
EventID 1102: The IMAP4 service failed to connect using SSL or TLS encryption. No valid certificate is configured to respond to SSL/TLS connections. Check the configured host name as well as which certificates are installed in the Personal Certificates store of the computer.
Resolution: 
1. Remove the certificate and re-add the certificate again on that Exhange 2013 server.
2. In Exchange Management Shell run the following: Enable-ExchangeCertificate -Thumbprint XXXXXXXXXX -Services POP,IMAP
3. Restart the Imap and Pop frontend and backend services.

Connecting to Exchange 2013 EWS with Exchange 2010 Folder Permissions

Scenario: When making Exchange 2013 EWS calls that proxies down to a Exchange 2010 mailbox connecting via shared folder permissions of another Exchange 2010 mailbox, the EWS connection may be unstable. Programs such as Starfish, SoapUI, or other programs making EWS calls, may or may not connect consistently and some errors encountered are 400 Bad Request errors.

Resolution: We created a new mailbox in Exchange 2013 and gave this mailbox the folder share permissions to the Exchange 2010 mailboxes. Making EWS calls to Exchange 2013 by using the 2013 mailbox to connect to the mailbox folders of the 2010 mailbox, EWS had become stable and successful.

Exchange 2013 IMAP and POP Backend Services

Microsoft has made changes in Exchange 2013 for how IMAP and POP communicate between the Exchange servers holding the Client Access and Mailbox role. The roles below need the following services started for the Exchange servers to communicate properly with IMAP and POP.
Client Access Role: The following services need to be started for each server holding the CAS role to accept the connection from clients.
  1. MSExchangeIMAP4
  2. MSExchangePOP3
Mailbox Role: The following services need to be started for each server holding the Mailbox role to accept the connection from the CAS.
  1. MSExchangeIMAP4BE
  2. MASExchangePOP3BE
On servers where the Client Access and Mailbox roles are running on the same server, you manage both services on the same computer.