Exchange Server Forums

Out of Office not working

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Installation >> Out of Office not working

Page: [1]

Message

<< Older Topic Newer Topic >>

Out of Office not working - 22.Feb.2012 2:45:23 PM

bvilleneuve

Posts: 12
Joined: 4.Jan.2012
Status: offline

Hi guys,

i've been searching for a miracle post all day and found nothing regarding my problem. Let me explain what is going on. User with Microsoft Outlook 2007 are trying to open up the OOF Agent and they get an error message saying "The server is unavailable. Try again late."

I started my journey with this and got pretty good documentation on how to setup Autodiscover in EMC and adding Records in DNS, etc. I went through all of these. But none of them helped me very much.

Interesting fact is that it's working from OWA. It is not working internally with a standard client. My personnal setup is 2010 and I can manage the OOF wizard. Looks like 2007 is the only situation.

Since a couple of weeks, i issued a certificate (SAN) with StarField and I went through the configuration to make it work for the OWA website: fine.
For some reason, the OOF stopped working even if in my certificate, i added autodiscover.external-domain.com.

In this cert I got:
DNS Name: owa.external-domain.com
DNS Name: www.owa.external-domain.com
DNS Name: autodiscover.external-domain.com
DNS Name: external-domain.com
DNS Name: EX-Server
DNS Name: EX-Server.internaldomain.local

In my DNS, the actions I've taken are:
Creating a new forward lookup zone - external-domain.com
In this zone, add: A Record for (parent folder), autodiscover (pointing to my EX-Server), owa (to EX-Server again) and www (external website's hosting manager).

In the domain.local zone, i added an A Record for autodiscover (pointing to EX-Server).

I heard about CNAME, does that make a difference? Do i need to create a CNAME instead?

This done, i went in EMC to Set-WebServicesVirtualDirectory ... to https://owa.external-domain.com/EWS/Exchange.asmx (Am I right here?)

If I go on my client PC and run the autodiscover test, it is successful (Like others having the same issue). My OOF address looks like: https://owa.external-domain.com/EWS/Exchange.asmx By the way, it's the same for Availability Service URL.

In my ISP's DNS, i told them to add a Record for owa.external-domain.com to my Firewall's address. For the outside, everything is working fine. How come internally, my users can't open the OOF feature? I'm missing something...

Also, i thought it'd be good to provide some output of Test-OutlookWebServices which is talking about the NTFS permissions and web.config file. (I did some tests on redirecting HTTP/HTTPS with Error Codes and it seems to be stuck there. Even if i removed it, in the web.config there is still a HTTPError section that i can't remove).

Thanks for helping me out!

[PS] C:\Windows\system32>Test-OutlookWebServices

...

<body>
<div id="header"><h1>Server Error in Application "DEFAULT WEB
SITE/EWS"</h1></div>
<div id="server_version"><p>Internet Information Services 7.5</p></div>
<div id="content">
<div class="content-container">
<fieldset><legend>Error Summary</legend>
<h2>HTTP Error 500.19 - Internal Server Error</h2>
<h3>Absolute physical path "C:\inetpub\custerr\en-US" is not allowed in
system.webServer/httpErrors section in web.config file. Use relative path
instead.</h3>
</fieldset>
</div>
<div class="content-container">
<fieldset><legend>Detailed Error Information</legend>
<div id="details-left">
<table border="0" cellpadding="0" cellspacing="0">
<tr class="alt"><th>Module</th><td>CustomErrorModule</td></tr>
<tr><th>Notification</th><td>SendResponse</td></tr>
<tr
class="alt"><th>Handler</th><td>WebServiceHandlerFactory-ISAPI-2.0-64</td></tr>

<tr><th>Error Code</th><td>0x8007000d</td></tr>

</table>
</div>
<div id="details-right">
<table border="0" cellpadding="0" cellspacing="0">
<tr class="alt"><th>Requested
URL</th><td>https://owa.external-domain.com:443/EWS/Exchange.asmx</td></tr>
<tr><th>Physical Path</th><td>D:\Program Files\Exchange
Server\ClientAccess\exchweb\EWS\Exchange.asmx</td></tr>
<tr class="alt"><th>Logon Method</th><td>Not yet determined</td></tr>
<tr><th>Logon User</th><td>Not yet determined</td></tr>

</table>
<div class="clear"></div>
</div>
</fieldset>
</div>
<div class="content-container">
<fieldset><legend>Most likely causes:</legend>
<ul> <li>The worker process is unable to read the applicationhost.config or
web.config file.</li> <li>There is malformed XML in the applicationhost.config
or web.config file.</li> <li>The server cannot access the
applicationhost.config or web.config file because of incorrect NTFS
permissions.</li> </ul>
</fieldset>
</div>
<div class="content-container">
<fieldset><legend>Things you can try:</legend>
<ul> <li>Look in the event logs for information about why the configuration
files are not readable.</li> <li>Make sure the user identity specified for the
application pool, or the authenticated user, has the required permissions to
access the web.config file.</li> </ul>
</fieldset>
</div>

<div class="content-container">
<fieldset><legend>Links and More Information</legend>
This error occurs when there is a problem reading the configuration file for
the Web server or Web application. In some cases, the event logs may contain
more information about what caused this error.
<p><a
href="http://go.microsoft.com/fwlink/?LinkID=62293&IIS70Error=500,19,0x8007000d
,7600">View more information �</a></p>

</fieldset>
</div>
</div>
</body>

...

--.
At line:1 char:24
+ Test-OutlookWebServices <<<<
+ CategoryInfo : NotSpecified: (:) [Test-OutlookWebServices], Inv
alidOperationException
+ FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Excha
nge.Management.SystemConfigurationTasks.TestOutlookWebServicesTask