Link to home
Start Free TrialLog in
Avatar of undy30
undy30

asked on

No free/busy information could be retrieved

Hello. I just upgraded from Exchange 2003 to Exchange 2010. Everything went well. We still have Exchange 2003 up, but not much is on it.

With Exchange 2003 everyone had Free/Busy info, on Exchange 2010 no one does. It just gives the "No free/busy information could be retrieved" message in Outlook.

Per Microsoft KB I run:
Get-PublicFolder "\non_ipm_subtree\schedule+ free busy" -recurse |fl name,*rep*

I get:
Name                           : SCHEDULE+ FREE BUSY
LocalReplicaAgeLimit           :
Replicas                       : {}
ReplicationSchedule            : {}
UseDatabaseReplicationSchedule : True

Name                           : EX:/o=Company/ou=Company
LocalReplicaAgeLimit           :
Replicas                       : {Public Folder Database, EX2003\First Storage Group\Public Folder Store (EX2003)}
ReplicationSchedule            : {}
UseDatabaseReplicationSchedule : True

Name                           : EX:/o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)
LocalReplicaAgeLimit           :
Replicas                       : {Public Folder Database, EX2003\First Storage Group\Public Folder Store (EX2003)}
ReplicationSchedule            : {}
UseDatabaseReplicationSchedule : True



To me that shows both Free/Busy public folders have each other as Replicas, which looks good. Not sure what the first one is, just a folder containing the 2? I run the following:
Set-PublicFolder -Identity "\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY" -Replicas "Company\First Storage Group\Public Folder Store (EX2003)"''

Now the 2003 server is a replica of that entry. I can't add the 2010 server for some reason.

In 2003 ESM I see both Free/Busy Info entries and both servers are replicas of each. In 2010 EMC I see both public folders and both are also replicas. I run Update Content on both and it goes through.


We're all running Outlook 2007 local, no Outlook Anywhere.

Thanks!
Avatar of undy30
undy30

ASKER

An Update. in Eventvwr of 2010 I get

Couldn't find an Exchange 2010 or later public folder server with a replica for the free/busy folder: EX:/O=Ameripay/OU=Company.
Avatar of Malli Boppe
Is autodicovery setup for exchange 2010 and working properly.
Avatar of undy30

ASKER

Autodiscover itself seems fine. We have a SVR record created, no A record though. So I can't ping Autodiscover but it should work because of the SVR record.
I do the Autodiscover test in Outlook and it is successful.

I do Test-OutlookWebServices -identityblah@company.com | fl
and Autodiscover is successful but EWS fails:

Creating a new session for implicit remoting of "Test-OutlookWebServices" command...

RunspaceId : 09dcf130-e4af-4f02-985a-3d7bc767c4d4
Id         : 1019
Type       : Information
Message    : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://Ex2010.company.com/Autodiscover/Autodiscover.xml.

RunspaceId : 09dcf130-e4af-4f02-985a-3d7bc767c4d4
Id         : 1006
Type       : Information
Message    : Contacted the Autodiscover service at https://Ex2010.company.com/Autodiscover/Autodiscover.xml.

RunspaceId : 09dcf130-e4af-4f02-985a-3d7bc767c4d4
Id         : 1016
Type       : Information
Message    : [EXCH] The AS is configured for this user in the AutoDiscover response received from https://Ex2010.company.com/Autodiscover/Autodiscover.xml.

RunspaceId : 09dcf130-e4af-4f02-985a-3d7bc767c4d4
Id         : 1015
Type       : Information
Message    : [EXCH] The OAB is configured for this user in the AutoDiscover response received from https://Ex2010.company.com/Autodiscover/Autodiscover.xml.

RunspaceId : 09dcf130-e4af-4f02-985a-3d7bc767c4d4
Id         : 1014
Type       : Information
Message    : [EXCH] The UM is configured for this user in the AutoDiscover response received from https://Ex2010.company.com/Autodiscover/Autodiscover.xml.

RunspaceId : 09dcf130-e4af-4f02-985a-3d7bc767c4d4
Id         : 1022
Type       : Success
Message    : Autodiscover was tested successfully.

RunspaceId : 09dcf130-e4af-4f02-985a-3d7bc767c4d4
Id         : 1013
Type       : Error
Message    : When contacting https://Ex2010.company.com/EWS/Exchange.asmx received the error The request failed with
              the error message:
             --
             <html><head><title>Object moved</title></head><body>
             <h2>Object moved to <a href="%2fEWS%2flogin.aspx%3fReturnUrl%3d%252fEWS%252fExchange.asmx">here</a>.</h2>
             </body></html>

             --.

RunspaceId : 09dcf130-e4af-4f02-985a-3d7bc767c4d4
Id         : 1025
Type       : Error
Message    : [EXCH] Error contacting the AS service at https://Ex2010.company.com/EWS/Exchange.asmx. Elapsed time wa
             s 958 milliseconds.

RunspaceId : 09dcf130-e4af-4f02-985a-3d7bc767c4d4
Id         : 1013
Type       : Error
Message    : When contacting https://Ex2010.company.com/EWS/Exchange.asmx received the error The remote server retur
             ned an error: (404) Not Found.

RunspaceId : 09dcf130-e4af-4f02-985a-3d7bc767c4d4
Id         : 1027
Type       : Error
Message    : [EXCH] Error contacting the UM service at https://Ex2010.company.com/EWS/Exchange.asmx. Elapsed time wa
             s 49 milliseconds.


I ran Remove-WebServicesVirtualDirectory and then New-WebServicesVirtualDirectory successfully and then restarted IIS and I get the same errors when I test OutlookWebServices.

This is a new install of Ex2010, no modifications.
Avatar of undy30

ASKER

OOF is also broken on Outlook clients, probably also due to the EWS not working. I hear it controls OOF and F/B
ASKER CERTIFIED SOLUTION
Avatar of undy30
undy30

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This question has been classified as abandoned and is being closed as part of the Cleanup Program.  See my comment at the end of the question for more details.
We are having this exact same issue. FYI:  When we upgraded a few users to Outlook 2010, the Free/Busy info appeared.

We do not want to have to upgrade the entire company to Outlook 2010 just to address this issue, so we are still hoping for a solution to this problem.

Thanks,
Gabe