no free busy information could be retrieved Exchange 2007 Where do I start?
I have this error "no free busy information could be retrieved" once a have added a user to the scheduling Assistant
We have a exchange 2007 server and the emails work fine. We do have a problem with the autodiscovery service that still needs to be resolved. But I hope that this might help me get closer to the real problem, Any one able to point me in a direction where
to start with this?
June 1st, 2010 5:22pm
Ok Here we go with some initial questions:
1-What is the client access method (owa, outlook) on which u have the issue? In case Outlook, is it 2007?
2-What is exactly the problem with your autodiscover service? What is the output from test-OutlookWebServices?
3-All Exchange Roles into a single server?
4-Problem always happened? What is your service pack/Update Rollup?
5-Any events (errors or warnings) on your CAS server(s) on application log, with source "MSexchange Availability"?
Best regards,
Sam
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2010 2:09am
Hi Sam
Thanks for your intrest in my problem.
Here are the info you requested.
1. We have one emp using MSoutlook 2007 and the rest all use MS Entourage.
2. Can you please advise how to test-OutlookWevServices? Since I am no expert in this.
3. Our Exchange server roles are DNS AD Domain Services + Web Server (IIS)
4. Windows Server 2008 R2 Standard with Exchange Server 2007 Microsoft Version: 08.01.0311.002
I dont know if this might help:
get-clientaccessserver |fl info
Name : EXCH52
OutlookAnywhereEnabled : False
AutoDiscoverServiceCN : exch52
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://mail.mydomain.com/Autodiscover/Autodis
cover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {Default-First-Site-Name}
IsValid : True
OriginatingServer : exch52.domain.com
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=EXCH02,CN=Servers,CN=Exchange Administrativ
e Group (FYDIBOHF23SPDLT),CN=Administrative Gr
oups,CN=Domain Organization,CN=Microsoft Exc
hange,CN=Services,CN=Configuration,DC=Domain
,DC=com
Identity : EXCH52
Guid : 04b9fa83-b945-47bb-8064-b29d891b4fdf
ObjectCategory : domain.com/Configuration/Schema/ms-Exch-Exch
ange-Server
ObjectClass : {top, server, msExchExchangeServer}
WhenChanged : 4/8/2010 12:08:55 AM
WhenCreated : 10/24/2009 8:46:07 AM
Thanks A million for Helping me with this.
June 2nd, 2010 11:30am
Hi,
Its realy important to know on what client the issue is.
Is it on MSOutlook or Entourage.
If it is MSOutlook 2007 try to disable the cache-mode and check if you see the Free/Busy information in online mode.
That's a start to see if it is client or server based.
Oh yeah and server roles are HUB, CAS & MBX
So do you have "1 server with hub, cas and 1 mbx server" or "1 server with all the roles"?
Greetzz,
Timmy
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2010 1:46pm
Ok, here we go:
1-open Exchange Management Shell
2-run the following command:
test-outlookwebservices | fl
3-post the results here
4-this will do a series of tests regarding the current functionality of autodiscover, and will let us know if your Outlook clients are having issue on locating the needed URL for availability services.
5-Check the application log on your CAS server, and check for any error/warning events with source "MSExchange availability".
I will see your answers and we can head on with more steps.
June 2nd, 2010 5:09pm
Hi,
Whether all the users or just one user has this issue?
For Free/Busy issue, we first need to ensure Autodiscover service to be working well since the client uses AS URL to access user's calendar to get the free/busy information. And the AS URL is retrieved from Autodiscover response.
Please try to do the test based on the VeilSlidebr's suggestions.
Thanks
Allen
Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2010 12:10pm
Hi Sam
Again thanks a million.
Here are the results:
Id : 1003
Type : Information
Message : About to test AutoDiscover with the e-mail address Administrator@mydomain.com.
Id : 1007
Type : Information
Message : Testing server exch52.mydomain.com with the published name https://ma
il.mydomain.com/EWS/Exchange.asmx & .
Id : 1019
Type : Information
Message : Found a valid AutoDiscover service connection point. The AutoDiscover
URL on this object is https://mail.mydomain.com/Autodiscover/Autodis
cover.xml.
Id : 1013
Type : Error
Message : When contacting https://mail.mydomain.com/Autodiscover/Autodiscover.x
ml received the error The remote server returned an error: (400) Bad
Request.
Id : 1006
Type : Error
Message : The Autodiscover service could not be contacted.
Autodiscovery does not work in Outlook 2007 or in MS Entourage (Mac) The mail works intrenaly and externaly for MS Entourage. (Note if Manually configured) but not in Outlook 2007. Outlook 2007 only works internally with manual config.
Using Entourage All I did was change the settings to the following under advance:
Exchange server: https://mail.mydomain.com/EWS/Exchange.asmx
and LDAP: https://mail.mydomain.com/EWS/Exchange.asmx
with the following ticked "This server requires to logon" "this server requires secure ssl" This LDAP server requires a secure connection (ssl)"
Mail in Entourage is not the problem works great.
Since my boss does not want to buy a secure ssl all I did was setup a self signed ssl in iis mail.mydomain.com a ssl to the hostname of the mail server.
So in Mac and Outlook evertime a popup comes up with a secure connection error but the mail still works.
The DNS IS created like this:
autodiscovery.mydomain.com Alias pointing to record mail.mydomain.com
mail.mydomain.com points to exchange server IP
The SRV is created like this:
_autodiscover srv port nr 443
https://mail.mydomain.com/Autodiscover/Autodiscover.xml
When doing I "Test E-mail AutoConfiguration"
its logs like this:
Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml strarting
Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml FAILED (0X800C8203)
Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml starting
Autodiscover request completed with http status code 403
Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml FAILED (0X8004005)
Local autodiscover for mydomain.com starting
Local autodiscover for mydomain.com FAILD (0X8004010F)
Redirect check to http:/autodiscover.mydomain.com/autodiscover/autodiscover.xml starting
Redirect check to http:/autodiscover.mydomain.com/autodiscover/autodiscover.xml FAILED (0X80004005)
Srv Record lookup for mydomain.com starting
Autodiscover URL redirection to https://mail.mydomain.com/autodiscover/autodiscover.xml starting
Autodiscover request completed with http status code 301
Autodiscover to https://mail.addynamo.com/autodiscover.xml FAILED (0X80004005)
Srv Record lookup for mydomain.com FAILED (0X80004005)
June 3rd, 2010 6:13pm
Hi,
Thanks for your information.
From the testing result, we know that the autodiscover service could not be contacted. Now please try to access
https://localhost/autodiscover/autodiscover.xml on the CAS, then post the information here.
Thanks
Allen
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2010 12:13pm
Hi,
To addition of the troubleshooting by Allen...
1. Did you publish the self-signed certificate that you created to the clients?
2. Also check the internal and external URL's and "AutodiscoverServiceInternalURI" <- maybe this one is important cause of the self-signed certificate you created and I presume its all about internal traffic to the cas server.
Standard the AutodiscoverServiceInternalURI points to the https://servername.mydomain.com/autodiscover/autodiscover.xml and you changed the certificate to point
to CN=mail.mydomain.com and if you didn't add the ServerName to the SAN part of the certificate....
So probably if you point your AutodiscoverServiceInternalURI to
https://mail.mydomain.com/autodiscover/autodiscover.xml
Its worth the try...
How to check internalautodiscoveruri:
Get-clientaccessserver * | select *uri*
How to change it:
get-clientaccessserver * | set-clientaccessserver -AutodiscoverServiceInternalURI
https://mail.mydomain.com/autodiscover/autodiscover.xml
Greetzz,
Timmy
June 4th, 2010 2:04pm
Hi Tim
Thanks for the help Here are the results
[PS] C:\Windows\system32>Get-clientaccessserver * | select *uri*
AutoDiscoverServiceInternalUri
------------------------------
https://mail.mydomain.com/Autodiscover/Autodiscover.xml
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2010 4:48pm
Hi Allen
When going to https://localhost/autodiscover/autodiscover.xml on the CAS
I first get the cert notification once confirmed I get a Authentication required popup. Loging with my user details then the page show me the Outlook Web Access login screen
https://mail.mydomain.com/owa/auth/logon.aspx?url=https://mail.mydomain.com/owa/&reason=0
Should this even happen?
My IIS config is setup like this:
(Sites)
autodiscover.mydomain.com (http Permanent (301)redirect https://mail.mydomain.com/autodiscover/autodiscover.xml
(Default Web Site)
Autodiscover (http Permanent (301)redirect to: https://mail.mydomain.com/owa)
June 4th, 2010 5:50pm
H Ultra,
Thanks for your update.
Yes, that is expected behaviour. Please go on inputting username and password, check what happen.
Thanks
Allen
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2010 5:24am
Hi Allen
When I login with my username and password it logs into my mailbox. scheduling Assistant seems to work fine from inside OWA. Any Idea on the autodiscovery error and what the cause might be for this happening?
Thanks
Colbert
June 7th, 2010 10:18am
Hi,
First please forgive my careless about your previous response.
For the OWA, it doesn't use the Web Service to get the free/busy but access the API directly. We can ingore it.
That's not right behaviour for the testing. When accessing
https://localhost/autodiscover/autodiscover.xml on the CAS server, the credential UI should be represented. Then the error code 600 must be received after inputting the user's credential.
This indicates the autodiscover virtual directory has some issue. Now please try to delete it and recreate it based on the below command:
First run the below command to remove Autodiscover VD:
Remove-AutodiscoverVirtualDirectory –Identity "cas-servername\Autodiscover (Default Web Site)"
Then recreate it:
New-AutodiscoverVirtualDirectory -WebsiteName "Default Web Site" -WindowsAuthentication $true -BasicAuthentication $true
Please ensure the authentication method is identical as previous configuration and restart IIS.
Thanks
Allen
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2010 10:34am
Hi Allen
This solved my problem with autodiscovery or well when I do the test it works but Email still does not work in outlook from outside the network :-( Dont know how to see what the cause might be coz all test goes trough and then when outlook start its unable
to connect. weird..
But still thanks a million for the help you really know your stuff!!!
Best regards
CB
June 9th, 2010 12:39pm
Hi,
If the free/busy issue was resolved, you can create a new thread for other issues. This can help use handle the issue in order.
Thanks
Allen
Free Windows Admin Tool Kit Click here and download it now
June 10th, 2010 5:22am
All sorted thanks :-)
July 15th, 2010 11:59pm