Exchange 2016 Out Of Office not working

Article
2017-01-04

Question

_{Wednesday, January 4, 2017 2:08 PM}

Hi everbody,

First of all I wish you best for the year 2017!

Recently we migrated from Office 365 to Exchange Server 2016 on-premis. Since the migration Out Of Office no longer workin from Outlook 2013/2016. We have about 120 users running on Outlook 2013 in a RDS-environment.

When a user clicks on OOF in Outlook 2013, they have to wait for a couple of seconds(10sec - 30sec) and then they receive the following message:

The automatic reply settings can not be saved. The server may be unavailable, or your auto-reply message is larger than allowed by the server.

Enable OOF through OWA works perfectly..

I have tried the following:

1. Upgrade Exchange Server 2016 from CU1 to CU3.
2. Install all Windows Updates for Outlook and Windows on the client/server.
3. Tested with Outlook 2013 and Outlook 2016 (in order to exclude Outlook).
4. With or without cache enabled, it makes no difference.
5. Tested from multiple systems, inside and outside the network.
6. Disabled Windows Firewall both sides (client/server).
7. Tested from OWA **--> from OWA OOF works!
**8. Install Outlook on the Exchange Server and tested, same problem.
9. All of de VirtualDirs(internal/external) pointing to the externalhostname. changed the internal to FQDN, and we receive a cert warnign in Outlook. problem still persists.

Tested with E-mail AutoConfiguration from Outlook (Right Click Outlook-icon in the taskbar), searched for the OOF record. It showes: https://remote.hostname.nl/EWS/Exchange.asmx. When i go to this webpage, i receive a credential dialog. I am able to authenticate and see a webpage with:

'You have created a service.'

Sometimes the dialog of OOF in Outlook is visible and the user can type the message. When they click OK, it takes a long time and they again get the same error ...

**Network environment:
**Users connect to a RDS(W2K12r2) server, this server send the user to TS1(W2K12r2) or TS2(W2K12r2). It's a user session RDS environment. All of the users using Microsoft Office 2013 Professional Plus (15.0.4885.1000) 32-bits in their TS session without cache.

I am troubleshooting this probleem for a while and need now some help to troubleshoot it furhter.

Thanks in Advance!

Sincerely, Martien van Dijk Please remember to mark the replies as answers if they help and unmark them if they provide no help. Check out My Blog!

All replies (14)

_{Tuesday, December 19, 2017 9:07 AM ✅Answered | 2 votes}

Hi all,

Thanks to you all for contributing to this challenge!

It seems that de problem is fixed for now.

The Fix:
On the Exchange Server I found out that de software Microsoft Exchange Web Services Managed API 2.2 was installed.

We also noticed a lot of warnings in the eventvwr in the 'System' log on the Exchange Server:

Detail Information about EventID 5011 WAS:

Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          **-**-2017 14:17:03
Event ID:      5011
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      FQDN of Exchange Server
Description:
A process serving application pool 'MSExchangeServicesAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '36384'. The data field contains the error number.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />
    <EventID Qualifiers="32768">5011</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-**-**T13:17:03.000000000Z" />
    <EventRecordID>675820</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>FQDN of Exchange Server</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="AppPoolID">MSExchangeServicesAppPool</Data>
    <Data Name="ProcessID">36384</Data>
    <Binary>6D000780</Binary>
  </EventData>
</Event>

After the removal of **Microsoft Exchange Web Services Managed API 2.2 ** the problem with Out of Office was fixed an the EventID 5011 warnings in the eventvwr are gone.

Problem Solved!

Sincerely, Martien van Dijk. Please remember to mark the replies as answers if they help and unmark them if they provide no help. Check out My Blog!

_{Wednesday, January 4, 2017 4:21 PM}

Hi everbody,

First of all I wish you best for the year 2017!

Recently we migrated from Office 365 to Exchange Server 2016 on-premis. Since the migration Out Of Office no longer workin from Outlook 2013/2016. We have about 120 users running on Outlook 2013 in a RDS-environment.

When a user clicks on OOF in Outlook 2013, they have to wait for a couple of seconds(10sec - 30sec) and then they receive the following message:

The automatic reply settings can not be saved. The server may be unavailable, or your auto-reply message is larger than allowed by the server.

Enable OOF through OWA works perfectly..

I have tried the following:

1. Upgrade Exchange Server 2016 from CU1 to CU3.
2. Install all Windows Updates for Outlook and Windows on the client/server.
3. Tested with Outlook 2013 and Outlook 2016 (in order to exclude Outlook).
4. With or without cache enabled, it makes no difference.
5. Tested from multiple systems, inside and outside the network.
6. Disabled Windows Firewall both sides (client/server).
7. Tested from OWA **--> from OWA OOF works!
**8. Install Outlook on the Exchange Server and tested, same problem.
9. All of de VirtualDirs(internal/external) pointing to the externalhostname. changed the internal to FQDN, and we receive a cert warnign in Outlook. problem still persists.

Tested with E-mail AutoConfiguration from Outlook (Right Click Outlook-icon in the taskbar), searched for the OOF record. It showes: https://remote.hostname.nl/EWS/Exchange.asmx. When i go to this webpage, i receive a credential dialog. I am able to authenticate and see a webpage with:

'You have created a service.'

Sometimes the dialog of OOF in Outlook is visible and the user can type the message. When they click OK, it takes a long time and they again get the same error ...

**Network environment:
**Users connect to a RDS(W2K12r2) server, this server send the user to TS1(W2K12r2) or TS2(W2K12r2). It's a user session RDS environment. All of the users using Microsoft Office 2013 Professional Plus (15.0.4885.1000) 32-bits in their TS session without cache.

I am troubleshooting this probleem for a while and need now some help to troubleshoot it furhter.

Thanks in Advance!

Sincerely, Martien van Dijk Please remember to mark the replies as answers if they help and unmark them if they provide no help. Check out My Blog!

Some more information regarding your Exchange environment woudl be helpful.

1.) How many servers make up your exchange environment?

2.) Are there any load balancers between the Outlook Clients and your Exchange server(s).

3.) Whats the output of Get-WebServicesVirtualDirectory | fl Servername, *url*

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

_{Thursday, January 5, 2017 8:27 AM}

Thanks for your reply!

1) We use one single Exchange Server running on Hyper-V. On this server we have the Mailbox Role installed an the Management Tools.

2) There are no network load balancers between Outlook and the Exchange Server

3) Output below:

[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | fl Servername, *url*


InternalNLBBypassUrl :
InternalUrl          : https://mail.domainname.nl/EWS/Exchange.asmx
ExternalUrl          : https://mail.domainname.nl/EWS/Exchange.asmx

a Ping to mail.domainname.nl result in a reply from the internal networkcard from the Exchange Server.

Sincerely, Martien van Dijk Please remember to mark the replies as answers if they help and unmark them if they provide no help. Check out My Blog!

_{Thursday, January 5, 2017 8:52 AM}

Did you checked by creating a new profile in Outlook?

Thanks,
PK

Please remember to mark the replies as answers if they help.

_{Thursday, January 5, 2017 9:04 AM}

Hello Martien,

To narrow down your issue, I also want to confirm:

Does this issue occurs on all On-premise mailboxes, Exchange Online mailboxes or mailboxes which migrate to Online?
How about recycle MSExchangeServicesAppPool in all Exchange servers?

Since OOF feature is based on EWS, we need EWS service works in Exchange server.
So, run below command to check the server component (check it in all Exchange servers), expecial EWSProxy:
Get-ServerComponentState <Exchange Server Name>

If it's Inactive, run below command to active for testing:

Set-ServerComponentState <Identity> -Component “component name” -Requester HealthAPI -State Active

Besides, we can use Test-WebServicesConnectivity to verify Web Services functionality.

Best Regards,

Allen Wang

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, January 5, 2017 3:21 PM}

What are the auth settings on your EWS Virtual directory?

Can you also get the output of:

Get-ClientAccessServer | fl name, *auto*

_{Friday, January 6, 2017 10:31 AM}

Thanks for your reply!

Yes, i have also created a new Outlook profile, but the problem still persists.

Sincerely, Martien van Dijk Please remember to mark the replies as answers if they help and unmark them if they provide no help. Check out My Blog!

_{Friday, January 6, 2017 10:45 AM}

1) Yes, these problems have migrated mailboxes and mailboxes that are created later on the new on-premis server.

2) I have done a recycle an a iisreset.

Output below from Get-ServerComponentState <Exchange Server Name>

[PS] C:\Windows\system32>Get-ServerComponentState servername

Server                                  Component                               State
                                                                 
servername.mail.domainname.nl... ServerWideOffline                       Active
servername.mail.domainname.nl... HubTransport                            Active
servername.mail.domainname.nl... FrontendTransport                       Active
servername.mail.domainname.nl... Monitoring                              Active
servername.mail.domainname.nl... RecoveryActionsEnabled                  Active
servername.mail.domainname.nl... AutoDiscoverProxy                       Active
servername.mail.domainname.nl... ActiveSyncProxy                         Active
servername.mail.domainname.nl... EcpProxy                                Active
servername.mail.domainname.nl... EwsProxy                                Active
servername.mail.domainname.nl... ImapProxy                               Active
servername.mail.domainname.nl... OabProxy                                Active
servername.mail.domainname.nl... OwaProxy                                Active
servername.mail.domainname.nl... PopProxy                                Active
servername.mail.domainname.nl... PushNotificationsProxy                  Active
servername.mail.domainname.nl... RpsProxy                                Active
servername.mail.domainname.nl... RwsProxy                                Active
servername.mail.domainname.nl... RpcProxy                                Active
servername.mail.domainname.nl... UMCallRouter                            Active
servername.mail.domainname.nl... XropProxy                               Active
servername.mail.domainname.nl... HttpProxyAvailabilityGroup              Active
servername.mail.domainname.nl... ForwardSyncDaemon                       Inactiv
servername.mail.domainname.nl... ProvisioningRps                         Inactiv
servername.mail.domainname.nl... MapiProxy                               Active
servername.mail.domainname.nl... EdgeTransport                           Active
servername.mail.domainname.nl... HighAvailability                        Active
servername.mail.domainname.nl... SharedCache                             Active
servername.mail.domainname.nl... MailboxDeliveryProxy                    Active
servername.mail.domainname.nl... RoutingUpdates                          Active
servername.mail.domainname.nl... RestProxy                               Active
servername.mail.domainname.nl... DefaultProxy                            Active
servername.mail.domainname.nl... Lsass                                   Active
servername.mail.domainname.nl... RoutingService                          Active

Sincerely, Martien van Dijk Please remember to mark the replies as answers if they help and unmark them if they provide no help. Check out My Blog!

_{Friday, January 6, 2017 10:56 AM}

1) see output below:

[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | fl Server, *Auth*, *url*


Server                        : servername
CertificateAuthentication     :
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
LiveIdNegotiateAuthentication :
WSSecurityAuthentication      : True
LiveIdBasicAuthentication     : False
BasicAuthentication           : False
DigestAuthentication          : False
WindowsAuthentication         : True
OAuthAuthentication           : True
AdfsAuthentication            : False
InternalNLBBypassUrl          :
InternalUrl                   : https://mail.domainname.nl/EWS/Exchange.asmx
ExternalUrl                   : https://mail.domainname.nl/EWS/Exchange.asmx

2) Output of Get-ClientAccessServer | fl name, *auto*:

[PS] C:\Windows\system32>Get-ClientAccessServer | fl name, *auto*
WARNING:  The Get-ClientAccessServer cmdlet will be removed in a future version of Exchange. Use the
Get-ClientAccessService cmdlet instead. If you have any scripts that use the Get-ClientAccessServer cmdlet, update them
 to use the Get-ClientAccessService cmdlet.  For more information, see http://go.microsoft.com/fwlink/p/?LinkId=254711.


Name                           : servername
AutoDiscoverServiceCN          : servername
AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://mail.domainname.nl/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope          : {Default-First-Site-Name}

Sincerely, Martien van Dijk Please remember to mark the replies as answers if they help and unmark them if they provide no help. Check out My Blog!

_{Saturday, January 7, 2017 5:37 PM}

we have same problem OOF not working and disable MAPIoverHTTP on Exchange Server 2016

Chris

_{Saturday, January 7, 2017 6:34 PM}

Thanks voor your reply!

Is the problem solved after you have disabled 'MAPIoverHTTP' ?! In my case it is still enabled. It's the preferred connectivity method for Outlook for Exchange 2013 SP1 and later.

[PS] C:\Windows\system32>Get-OrganizationConfig | fl *mapi*


MapiHttpEnabled : True

Sincerely, Martien van Dijk Please remember to mark the replies as answers if they help and unmark them if they provide no help. Check out My Blog!

_{Monday, January 9, 2017 8:58 PM}

1) see output below:

[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | fl Server, *Auth*, *url*


Server                        : servername
CertificateAuthentication     :
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
LiveIdNegotiateAuthentication :
WSSecurityAuthentication      : True
LiveIdBasicAuthentication     : False
BasicAuthentication           : False
DigestAuthentication          : False
WindowsAuthentication         : True
OAuthAuthentication           : True
AdfsAuthentication            : False
InternalNLBBypassUrl          :
InternalUrl                   : https://mail.domainname.nl/EWS/Exchange.asmx
ExternalUrl                   : https://mail.domainname.nl/EWS/Exchange.asmx

2) Output of Get-ClientAccessServer | fl name, *auto*:

[PS] C:\Windows\system32>Get-ClientAccessServer | fl name, *auto*
WARNING:  The Get-ClientAccessServer cmdlet will be removed in a future version of Exchange. Use the
Get-ClientAccessService cmdlet instead. If you have any scripts that use the Get-ClientAccessServer cmdlet, update them
 to use the Get-ClientAccessService cmdlet.  For more information, see http://go.microsoft.com/fwlink/p/?LinkId=254711.


Name                           : servername
AutoDiscoverServiceCN          : servername
AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://mail.domainname.nl/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope          : {Default-First-Site-Name}

Sincerely, Martien van Dijk Please remember to mark the replies as answers if they help and unmark them if they provide no help. Check out My Blog!

Try setting the Autodiscover site scope to have all of your AD sites.

_{Saturday, January 21, 2017 10:38 AM}

Thanks vor your reply,

I will test it and then come back to you.

Sincerely, Martien van Dijk Please remember to mark the replies as answers if they help and unmark them if they provide no help. Check out My Blog!

_{Tuesday, January 24, 2017 3:45 AM}

Hello,

Would you please provide us with an update on the status of your issue?
If there is anything else we can do for you, please feel free to post in the forum.

Best Regards,

Allen Wang

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Share via

Exchange 2016 Out Of Office not working

Question

All replies (14)

Additional resources