Outlook Web App – Unified Messaging 500 Unexpected Error :(

twitterlinkedinmail

Environment:

Exchange Server 2013 – On Premise

Skype for Business Server 2015 – On Premise

User Enabled for both Skype for Business Enterprise Voice and Exchange Unified Messaging for voicemail

Issue:

When logging into Outlook Web App via https://exchange.domain.com/owa clicking Tool -> Options -> Phone You receive the beautiful error message of : 500 Unexpected Error 🙁 – An error occurred and your request couldn’t be completed. Please try again.

Resolution:

So to begin troubleshooting the error we understand that we are in Outlook Web App, so first thing we need to do is gather some information on the Policies: Outlook Web App Policy (OWAMailboxPolicy) UserRoles (RoleAssignmentPolicy) to see what features are enabled and what policy is assigned to the user. For the work we’re going to use powershell and some of the settings I will show in the Exchange Admin Center, lets start by opening exchange management shell to starting gathering Info, run each command one at a time:

Server Policies:

  1. Capture the Outlook Web App Mailbox Policy
    1. Get-OwaMailboxPolicy |Select-Object Name
  2. Capture the Mailbox Policy
    1. Get-RoleAssignmentPolicy Select-Object Name



Client Policies Assigned to a User:

  1. Get-Mailbox Habib Select-Object Name,RoleAssignmentPolicy


  2. Get-CASMailbox Habib Select-Object Name,OwaMailBoxPolicy
  3. (*Note: this may show blank because it’s using the Default Policy)

Ok so now that we’ve got the policies assigned to a user and what policies that have been created, let’s see how the policies are configured. These 2 settings (Text Messaging , Unified Messaging ) control the Phone option in OWA we need to validate if they are turned on or off in the OWA Mailbox and Role Assignment Policies.

  1. Open Exchange Management Shell
  2. Find what options are enabled for the OWA Mailbox Policy
    1. Get-OwaMailboxPolicy Select-Object Name, TextMessagingEnabled, UMIntegrationEnabled

  3. Find what options are enabled for the Default Role Assignment:
    1. Get-ManagementRoleAssignment –RoleAssignee ‘Default Role Assignment Policy’ | fl Name,Role, Enabled

Ok so we notice in the OWAMailboxPolicy that TextMessagingEnabled and UMIntegrationEnabled are enabled, but on the RoleAssignmentPolicy we only have MyVoiceMail enabled and MyTextMessaging is disabled.

The issue here is that we need to have MyVoiceMail and MyTextMessaging enabled on the RoleAssignmentPolicy and if you want to have both 1 or both options enabled in OWA you can turn those on or off in the OWA Mailbox Policy.

Alright now to fix this baby! In our environment we want to enable the Voicemail Option and not the TextMessaging so we are going to turn off TextMessaging in the OWAMailboxPolicy and turn MyTextMessaging in the RoleAssignmentPolicy. I will show how to do this in Exchange Management Shell and Exchange Admin Center.

Exchange Admin Center:

  1. Log into Exchange Admin Center https://exchange.domain.com/ecp
  2. Click Permissions
  3. Click User Roles tab
    1. Double Click Default Role Assignment Policy
    2. Check the Boxes for:
      1. MyTextmessaging
      2. MyVoiceMail
    3. Click Save
  4. Click on Outlook Web App Policies
    1. Double Click Default
    2. Click Features
    3. Uncheck Text Messaging
    4. Click Save

Exchange Management Shell

  1. Open Exchange Management shell
  2. We’re going to modify the OWAMailboxPolicy
  3. Get-OwaMailboxPolicy -Identity Default Set-OwaMailboxPolicy -TextMessagingEnabled:$False
  4. We’re going to modify the RoleAssignmentPolicy (user roles)
    1. New-ManagementRoleAssignment -Name MyTextMessaging -Role MyTextMessaging -Policy ‘Default Role Assignment Policy’

Let’s open Outlook Web App by browsing to https://exchange.domain.com/owa clicking Tool -> Options -> Phone and we should now be able to see the Voicemail tab successfully open.

twitterlinkedinmail

Leave a Reply

Your email address will not be published. Required fields are marked *

*