I have been working on this issue for quite some time and I am unable to find a solution that works. I will try and explain everything as clearly as I can.We have two exchange servers at two different sites. The sites are connected through a VPN, and all DCs and Exchnange Servers contained in both sites are part of the same domain. Both sites are running Exchange Server 2007 on Server 2003 Enterprise 64-bit. Both are member servers and both have transport and CAS server roles installed.At one site (site #2), OOF works fine and when turned on, responds with the out of office message specified by the user.At the other site (site #1), OOF turns on but won't respond when someone emails. When "test email auto configuration" is run - all the tests pass, however, when I type Test-OutlookWebServices in EMS on the server in site #2 I get the following information. Id Type Message -- ---- ------- 1003 Information About to test AutoDiscover with the e-mail address user@domain.com1006 Information The Autodiscover service was contacted at https://autodiscover .domain.com/autodiscover/autodiscover.xml. 1013 Error When contacting https://domain.com/ews/exchange.asmx re ceived the error The request failed with HTTP status 401: Unau thorized. 1016 Error [EXCH]-Error when contacting the AS service at https://domain.com/ews/exchange.asmx. The elapsed time was 31 millisec onds. 1015 Success [EXCH]-Successfully contacted the OAB service at https://domain.com/ews/exchange.asmx. The elapsed time was 0 millise conds. 1014 Success [EXCH]-Successfully contacted the UM service at https://domain.com/unifiedmessaging/service.asmx. The elapsed time wa s 46 milliseconds. 1016 Information [EXPR]-The AS is not configured for this user. 1015 Information [EXPR]-The OAB is not configured for this user. 1014 Information [EXPR]-The UM is not configured for this user. 1017 Success [EXPR]-Successfully contacted the RPC/HTTP service at https:// mi.equitysrvs.com/Rpc. The elapsed time was 0 milliseconds. 1006 Success The Autodiscover service was tested successfully. 1021 Information The following web services generated errors. As in EXCH Please use the prior output to diagnose and correct the errorsI do want to point out that in Site #2, users who use Outlook 2003 are able to turn on Out of Office and it works fine - this problem pertains to users of Outlook 2007. I am unable to find any helpfulinformation on the 10XX error codes. Any help would be greatly appreciated.

The problem is usually caused by one of the following reasons: Reason 1: Wrong Autodiscover Service settings Reason 2: Wrong certificate Reason 3: Wrong permission settings on the EWS virtual directory. Reason 4: Logged on with another user account (user logged into pc with a different domain than email account ie logged into to PC as MICHAEL\Rich and logged into email server as Richard\Mike) See the link below for detailed screen prints and documentation that will resolve your issue. Usually is the reason 3 or reason 4, even though everyone points to the autodiscovery issues. http://www.proexchange.be/modules.ph...rticle&sid=686Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

Couple of things that I would like to check over here.1. From site 1, try to browse https://domain.com/ews/exchange.asmx on the IE, and check if you get a XML page and without any certificate error.2. Then browse the same URL from other Site3. When you run Test Email Autoconfiguration on the OL 2007 clients, do you get the correct URLs4. Check the authentication on EWS v-dir in IIS Manager, it should be Windows Integrated5. Do you have a BES in your environment, if yes then check if its updated to the latest SP.6. Which is the SP for OL 2007, make sure its SP2 with the hotfix 970944Harpreet Singh Khandiyal (http://support.microsoft.com/kb/555375)

Hi,Did you meanthe OOF could be configured without any issue but not function when receiving the email? Is this issue occurring in OWA? Please understand that in Exchange 2007, the Availability service is a Web service running on the Client Access Server that exposes Web methods that enable Outlook 2007 clients to set and retrieve their Out of Office settings. To make OOF function, that is the OOF rule. Outlook and OWA utilize hidden messages inthe Inbox to store the OOF rule used to trigger the OOF reply and the OOF message template used in the response.ThanksAllen

Couple of things that I would like to check over here. 1. From site 1, try to browse https://domain.com/ews/exchange.asmx on the IE, and check if you get a XML page and without any certificate error. 2. Then browse the same URL from other Site 3. When you run Test Email Autoconfiguration on the OL 2007 clients, do you get the correct URLs 4. Check the authentication on EWS v-dir in IIS Manager, it should be Windows Integrated 5. Do you have a BES in your environment, if yes then check if its updated to the latest SP. 6. Which is the SP for OL 2007, make sure its SP2 with the hotfix 970944 Harpreet Singh Khandiyal (http://support.microsoft.com/kb/555375) Harpreet, Thanks for the reply and sorry mine took so long, i was going back to my notes to remember everything we did. (1) I went to https://domain.com/ews/exchange.asmx and I DID get a certificate error on (2) both servers. I forgot to mention that we are not using a unified communications certificate so we had to modify the internal URLS. We followed this KB article http://support.microsoft.com/?kbid=940726. Also, the server in site 2 (the site where OOF works) has two autodiscover virtual directories. One is set up to accept connections from external users, it is then set to forward to the default exchange autodiscover virtual directory. (3) Yes I am returned with our common name that we used on our SSL cert, NOT the FQDN of the server as expected. (4) EWS is set for Integrated Windows Authentication and Basic Authentication (5) No we do not have BES (6) Outlook 2007 is running SP2 Thanks,

We just went through a similar situation this week. Here's what we eventualy did to resolve it.#1 - if you are performing the test-outlookwebservices from the CAS server, you have to turn off loopback using method #2 (you should turn this back on after your problem gets resolved) from the following article http://support.microsoft.com/?id=896861 also make sure you can do the test-outlookwebservices with and without an identity. #2 - we had recently installed .net framework 3.5 sp1 on the server, there is a known problem with 3.5 SP1 and Exchange 2007 SP1 (see this article http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=363175), which we then applied the 3 fixes in KB959209 (http://support.microsoft.com/kb/959209 )#3 - finally, we determined on top of all this we were having a DNS issue with a new domain controller we had installed, which it would not resolve external names. We discovered this by running nslookup on the exchange CAS server and perfming a variety of lookups on both internal & external servers for all 3 DNS servers in the exchange CAS server's DNS list. 1 of the DNS servers was having issues. We fixed this.after ALL 3 of these things, our issue was solved.

#2 - we had recently installed .net framework 3.5 sp1 on the server, there is a known problem with 3.5 SP1 and Exchange 2007 SP1 (see this article http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=363175 ), which we then applied the 3 fixes in KB959209 (http://support.microsoft.com/kb/959209 ) #3 - finally, we determined on top of all this we were having a DNS issue with a new domain controller we had installed, which it would not resolve external names. We discovered this by running nslookup on the exchange CAS server and perfming a variety of lookups on both internal & external servers for all 3 DNS servers in the exchange CAS server's DNS list. 1 of the DNS servers was having issues. We fixed this. after ALL 3 of these things, our issue was solved. #2 - It didn't prompt me to restart - did you have to restart your server for the changes to take effect? #3 - Did you see any problems after you ran netdiag? I think our DNS server is fine but I will double check.

Update: I wanted to let everyone know that a corrupt exchange database was the reason that the out of office assistant wasn't working. I moved 4 mailboxes into a new database and it worked for all 4 (i had to restart the exchange topology service after each move). I am now in the process of moving all mailboxes to the new database. Thanks for all the help.