asked on

Out of Office Issue

Hi,

I have an issue with all my users not being able to set their OOO. They get an error message saying "your out of office settings cannot be displayed, because the server is currently unavailable. try again later".

This happens for all our users who use Outlook 2007, 2010 & Outlook 2011 for Mac even though all users can set their OOO using the OWA.

I used the testoutlookconnectivity tool which throws up no errors. I've even reset the Virtual Directories for EWS & Autodiscover.

Also after resetting the Virtual Directory for EWS I can no longer configure Outlook 2011 for any new users and also my current MAC users can no longer connect to the Exchange server.

I've also configured the internalurl & externalurl for each of the EWS & Autodiscover Virtual Directories, but still not luck.

Can anyone shed any light on what I am doing wrong or anything that I may have missed?

Your help is much appreciated.

novatek

Simon Butler (Sembee)

Does Autodiscover work?
Internal and External URL on the Autodiscover virtual directory is a waste of time, as it isn't used. You should set those back to "null".

The value that matters is what you see here:

get-clientaccessserver | select identity, autodiscoverserviceinternaluri

The host name on that value must
a. Resolve to Exchange internally.
b. The host name must be on the SSL certificate
c. the SSL certificate must be trusted by the clients.

If any of that fails, then Autodiscover doesn't work, and the clients cannot find availability information, which includes OOTO.

Simon.

novatekitsolutions

ASKER

Hi sembee2,

Thanks for the prompt response.

I have removed the internal/external URL & when I run the Get-ClientAccessServer |fl identity,autodiscoverserviceinternaluri

I get the following results, which is what I expected:

Identity: exchangeservername
AutoDiscoverServiceInternalUri: https://owa.maildomain.co.uk/autodiscover/autodiscover.xml

As for the hostname resolving, and being on the SSL cert, this again is all correct as well as being trusted by all the clients.

Simon Butler (Sembee)

To be clear here, it resolves to the INTERNAL IP address of the server?
Do you have a proxy on your network?

Simon.

novatekitsolutions

ASKER

Hi Simon,

Yes it resolves to the internal IP of the server.

Also we don't have a proxy in our network.

Also, I just tried going to https://mymailserver/ews/exchange.asmx and I got the following error:

Server Error in '/EWS' Application.
--------------------------------------------------------------------------------

Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type 'Microsoft.Exchange.Services.Global'.

Source Error:

Line 1: <%@ Application Language="C#" Inherits="Microsoft.Exchange.Services.Global"%>

Source File: /EWS/global.asax Line: 1

This is really weird. I've checked all the settings in IIS as well and nothing seems a miss there either.

Simon Butler (Sembee)

That is net framework error. Exactly what version of Exchange and Windows are you running?

Simon.

novatekitsolutions

ASKER

We are using Exchange 2010 SP3 on Windows Server 2008 R2 Standard.

All 3 roles are installed on this one server.

novatek

Simon Butler (Sembee)

I would start by resetting the virtual directories using the wizard in EMC.

Simon.

novatekitsolutions

ASKER

That was one of the first things I tried...but still no luck.

Simon Butler (Sembee)

Exactly what virtual directories did you reset?

Simon.