When configuring Site Mailboxes in SharePoint 2013 on-premises, you may be presented with a few errors such as:
‘Your SharePoint Server configuration is not supported’
Your Organization’ SharePoint Server configuration is not supported. Please contact your system administrator for more information.
Site Mailboxes finally work:
Another error that is displayed is:
Sorry, something went wrong
An unexpected error has occurred.
To troubleshoot these errors, open your favourite ULS Log viewer and look up the Correlation ID.
With Site Mailboxes, there are specific ‘error codes’ or ‘error keywords’ that will be found in the ULS logs.
Here is a table that I found useful when troubleshooting SiteMailbox configuration issues:
Please review the following table if you encounter issues.
Table of error codes for reference when you run a configuration checklist script
||EWS client was not found on the SharePoint WFE. Run the Check script and ensure the entries are properly in the GAC; you may need to reinstall the EWS client.
||EWS client version is incompatible with SharePoint. Run the Check script to ensure the version meets minimum requirements. Alternatively, the Exchange server may be 2010 or earlier.
||The TeamMailboxDomain parameter is not a valid FQDN or SMTP address.
||The script received a 401 from the Exchange Server, review the Exchange setup steps.
||Exchange timed out during AutoDiscovery. It should be intermittent, please retry, but if it is persistent, follow-up with the Exchange Administrator.
||AutoDiscovery failed to return a URL for ECP/OWA, which means typically that the EWS client version is incompatible with SharePoint. It may also mean Site Mailboxes are not enabled on Exchange, which would require follow-up with the Exchange Administrator.
||Unsuccessful in generating an OAuth token on behalf of SharePoint. This is typically caused by claims-based authentication being disabled on the SharePoint web application.
||An error occurred during the OAuth handshake between SharePoint and Exchange. This is typically caused by server to server configuration issues, such as a realm value mismatch on either side, certificate issues for Exchange or SharePoint, etc. Review certificates and attempt to establish or reestablish trust.
||The AutoDiscover domain property is not set to a valid FQDN.
||An unknown error condition has occurred. Run the Check script and confirm that a valid, trusted instance of SharePoint is available, review prerequisites, confirm AutoDiscover has been set-up properly with the Exchange Administrator.
||If this error is thrown, your web application’s default zone is not set to SSL, and AllowOauthoverHttp is also set to false. Run the Check script to ensure that any web application you intend to host site mailboxes are set with SSL in the default zone, as outlined in the prerequisites.
||One or both of the default Owners and Members groups for the site have been deleted. Each of these two default groups are required to exist on any site where users install site mailboxes. A site administrator should be able to direct a site owner to recreated these required groups.
||The ExchangeTeamMailboxDomain property has not been set.
||No Exchange app principals were found to be trusted. Typically, this means the New-SPTrustedSecureTokenService step was missed. Run the Check script and ensure that the app principal URL(s) outputted are the correct one(s).
||The Exchange app principal being connected to doesn’t have the right permissions on the SharePoint farm. Run the Check script and ensure that the Exchange app principal has the required permissions on the farm.
In my case, I had an Error 104 – ExchangeAppPrincipalNotFound.
No Exchange app principals were found to be trusted. Typically, this means the New-SPTrustedSecureTokenService step was missed. Run the Check script and ensure that the app principal URL(s) outputted are the correct one(s).
I rechecked my OAuth trust settings with Exchange 2013 and I had an issue with the Enterprise partner configuration.