More Free/Busy Issues (Full Version)

All Forums >> [Microsoft Exchange 2007] >> General



Message

rparsons1000 -> More Free/Busy Issues (28.Mar.2007 2:14:18 PM)

We are experiencing similar free/busy issues that I've read about from various posts here but we run into stumbling blocks at each remediation.

Tried to update the public folder hierarchy but get an error:
Multiple Mapi Public Trees Found

Tried to test autodiscover but get a failure when it runs the autodiscover.xml. Tried to go to the URL and get:
  <?xml version="1.0" encoding="utf-8" ?>
- <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">

- <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">

- <Error Time="10:54:10.4505428" Id="1484156002">

  <ErrorCode>600</ErrorCode>
  <Message>Invalid Request</Message>
  <DebugData />   </Error>  </Response>  </Autodiscover>  Any ideas on this one?



ewall -> RE: More Free/Busy Issues (28.Mar.2007 7:19:38 PM)

Sounds like you're browing directly to https://servername/autodiscover/autodiscover.xml? If so, that's why you're getting the "Invalid Request": it won't respond with data unless you 'post' a properly-formatted XML query to it. (Microsoft actually documented this, but who would bother to do that by hand?) That's what Outlook 2007's Autodiscover test will do for you.

More useful would be the error message the OL07 said when it did the Autodiscover test--there are a number of error codes it returns which can help determine what the problem with the Autodiscover web directory is.

(Um, that is, if you're using Outlook 2007 clients... if not, you don't need Autodiscover.)

Also, can you be more specific about what command you did when you "tried to update the public folder hierarchy"?



rparsons1000 -> RE: More Free/Busy Issues (28.Mar.2007 7:38:07 PM)

Before I go further let me explain the situation. My mailbox is on Exchange 2003 and I am using Outlook 2007. When I view a user on Exchange 2007 I can't see any free/busy info but viewing users free/busy on Exchange 2003 is not a problem. When a user on Exchange 2007 using Outlook 2003 tries, they can't see anyone's free/busy. I haven't tried any other configurations.

As far as the actual autodiscover log, I will type out the failures:

Autodiscover to https://casserver.domain/autodiscover/autodiscover.xml FAILED (0x800C8203)
Autodiscover to https://emaildomain.com/autodiscover/autodiscover.xml FAILED (0x800C8203)
Autodiscover to https://autodiscover.emaildomain.com/autodiscover/autodiscover.xml FAILED (0x800C8203)
Local autodiscover for "emaildomain.com" FAILED (0x8004010F)
Redirect check to http://autodiscover.emaildomain.com/autodiscover/autodiscover.xml FAILED (0x80072EE7)

The specific for updating the public folder hierarchy is that I used the Management Shell to run the "Update PublicFolderHiearchy" per a post from Henrik found at
http://forums.msexchange.org/m_1800412268/mpage_1/key_Autodiscover/tm.htm#1800434101

BTW, we are running 2 Exchange 2003 servers and 1 Exchange 2007. I am using Outlook 2007.



ewall -> RE: More Free/Busy Issues (29.Mar.2007 10:16:05 AM)

Ah... I don't have a ton of time to reply at the moment, but I found the bookmark that will probably help you a lot:
http://www.exchangeninjas.com/AvailabilityServiceFAQ

Clearly, the results of your Autodiscover test demonstrate that the Outlook 2007 clients are not able to get their info that way, which will prevent them from getting the Offline Address Book, Out-of-Office Agent, and the Availability Service--a/k/a Free/Busy schedules--when all of these things may work fine in other methods with the Outlook 2003 clients, which do not use Autodiscover.

The error 0x800C8203 and 0x80072EE7 suggest "networking or DNS errors"... meaning the DNS name did not resolve or it didn't find a web server at that address. Have you registered a DNS alias named "autodiscover" pointing to your Exchange 2007 server? See http://www.informit.com/guides/content.asp?g=windowsserver&seqNum=249&rl=1

Hope that helps!



Helinium -> RE: More Free/Busy Issues (12.Apr.2007 5:56:55 PM)

I have the solution for autodiscover problem. I will post it very soon.



rparsons1000 -> RE: More Free/Busy Issues (4.Dec.2007 9:17:52 AM)

You might find this helpfull

http://www.exchangeninjas.com/AvailabilityServiceFAQ

Our problem had to do with Public Folders and I ended calling Microsoft as we had some old 5.5 garbage creating problems. There is also some articles on your specific event log error on the net.....



t0ta11ed -> RE: More Free/Busy Issues (4.Dec.2007 11:13:44 AM)

quote:

ORIGINAL: rparsons1000

Before I go further let me explain the situation. My mailbox is on Exchange 2003 and I am using Outlook 2007. When I view a user on Exchange 2007 I can't see any free/busy info but viewing users free/busy on Exchange 2003 is not a problem. When a user on Exchange 2007 using Outlook 2003 tries, they can't see anyone's free/busy. I haven't tried any other configurations.

As far as the actual autodiscover log, I will type out the failures:

Autodiscover to https://casserver.domain/autodiscover/autodiscover.xml FAILED (0x800C8203)
Autodiscover to https://emaildomain.com/autodiscover/autodiscover.xml FAILED (0x800C8203)
Autodiscover to https://autodiscover.emaildomain.com/autodiscover/autodiscover.xml FAILED (0x800C8203)
Local autodiscover for "emaildomain.com" FAILED (0x8004010F)
Redirect check to http://autodiscover.emaildomain.com/autodiscover/autodiscover.xml FAILED (0x80072EE7)

The specific for updating the public folder hierarchy is that I used the Management Shell to run the "Update PublicFolderHiearchy" per a post from Henrik found at
http://forums.msexchange.org/m_1800412268/mpage_1/key_Autodiscover/tm.htm#1800434101

BTW, we are running 2 Exchange 2003 servers and 1 Exchange 2007. I am using Outlook 2007.


This is because the Autodiscover service is not finding what it needs at the URLs it's trying. A CNAME for the URL to the FQDN of the mail server or changing the URL used will fix it.



Page: [1]