500 Unexpected Error when accessing Voice Mail rules

I have an Exchange 2013 environment with Lync2013 and UM. 

Having an issue when users (including Exchange admin) try to access shared mailbox OWA (having the appropriate permissions to do so) to setup Voice Mail rules, they get "500 Unexpected Error. An error occurred and your request couldn't be completed. Please try again"

It works fine if they access their own Voice mail rules. Everything else in OWA works fine.

MyVoiceMail option (in the Default Role Assignment Policy) is checked. Executing Get-UMCallAnsweringRule shell command outputs fine without any errors.  Have also tried creating another Role Assignment policy and assigning to the mailboxes but still does not work.

  

Any suggestions?

thanks in advance.



February 26th, 2015 12:21am

Hi,

According to your description, I understand that open a shared mailbox and modify the setting of Outlook Voice Access by OWA, then return an error 500 unexpected error.
If I misunderstand your concern, please do not hesitate to let me know.

Basis on my testing, run Enable-UMMailbox to enable UM feature for shared mailbox, and enable shared mailbox account in AD. Then login OWA to double check the setting of Voice mail, everything is OK.
However, I get the same error as your mentioned when login another account in OWA and open shared mailbox to modify the setting of voice mail. Also, I get same error when doing this way to access another mailbox.

I find an similar thread about your question, it may be caused by the license of shared mailbox. For your reference:
http://community.office365.com/en-us/f/148/t/160652.aspx
 
Best Regards,
Allen Wang

Free Windows Admin Tool Kit Click here and download it now
February 27th, 2015 8:22am

Logged a premium Exchange server support case with Microsoft.

Tech support said that the issue is a Bug and do not have a solution at this stage :(

I will provide an update as soon as I hear something from Microsoft.


March 25th, 2015 8:59pm

Logged a premium Exchange server support case with Microsoft.

Tech support said that the issue is a Bug and do not have a solution at this stage :(

I will provide an update as soon as I hear something from Microsoft.


Free Windows Admin Tool Kit Click here and download it now
March 26th, 2015 12:55am

Did you get a resolution yet from MS support?

We came across this issue today same as you described above . None of our Exchange 2013

clients work. However it does work for Exchange 2010  mailboxes.

Regards,

John

April 27th, 2015 7:37pm

Hi John,

Nothing yet. I will update this thread when I get an update.

Microsoft support said they cannot confirm when this problem will be fixed. Possibly in future service pack or CU.

Cheers

Free Windows Admin Tool Kit Click here and download it now
April 27th, 2015 8:10pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics