• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6422
  • Last Modified:

Scheduling Assistant not Available between Exchange 2010 and Exchange 2007

I'm hoping you guys can help with a niggling Exchange problem we're having:

NYC Exchange Server
2007 - Standard (MB/HT/CAS)
Server 2003 R2 x64

PHX Exchange Server
2007 - Standard (MB/HT/CAS)
Server 2003 R2 x64

LA Exchange Server
2007 - Standard (MB/HT/CAS)
Server 2003 R2 x64
Holder of Public Folders

DataCenter Exchange Server1
2010 - Enterprise (MB)
DAG
Server 2008 R2

DataCenter Exchange Server2
2010 - Enterprise (MB)
DAG passive
Server 2008 R2

DataCenter Exchange Server3
2010 - Standard (HT/CAS)
Server 2008 R2

My problem is that all servers can use the Scheduling Assistant in order to see meeting Attendees availability.  

The one exception being:

Any user on the DataCenter Exchange Server 1 can see the availability of users on NYC Exchange, LA Exchange, and DataCenter Exchange.  However, when trying to schedule meetings with any user on the PHX Exchange we are unable to see the availability information.  The diagonal lines appear over their time slots and we get an information bubble saying "No Information.  No free/busy information could be retrieved.  The recipient's server could not be contact.  Contact your administrator."

I would be able to understand if this was the case for all servers, but why just this 2007 box in PHX, and the other two 2007 boxes are viewable?

Additionally, I ran the exchange remove connectivity test website against all servers for the autodiscover service, and all passed the test with the green checkmark.

Desperately hoping someone can provide some insight.

Any further info required, please let me know.
0
trecool
Asked:
trecool
  • 19
  • 17
1 Solution
 
MegaNuk3Commented:
So is the problem between datacenter 1 and PHX? What happens if someone in PHX tries to view availability of someone in datacenter 1?

If you have firewalls between the 2 locations then I would check the logs/rules to see if you can see it blocking port 80/443 between the 2 servers
0
 
trecoolAuthor Commented:
No, not a firewall problem, and phx can see datacenter.
0
 
MegaNuk3Commented:
On datacenter 1 exchange go into EMS and do:
Test-outlookwebservices "<email address of someone on phx server>" | fl

Then do it again from a working location and compare the output
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
trecoolAuthor Commented:
From the PHX server, it found the Autodiscover Server, but failed on everything else.  The other servers all returned success..  I have attached a screen cap of the errors on PHX.

does this help? Screen Cap of errors
0
 
MegaNuk3Commented:
What is vader?

Take the autodiscover URL and put it in IE and see if you get a cert error or prompted for credentials. If it prompts for credentials then enter a valid username and password and give you an error code 600, which means it is working properly.
0
 
trecoolAuthor Commented:
Vader is just what someone called the server...   I do get the 600 invalid message.  I kind of knew this would be the case since the Exchange connectivity tests all passed with the green check mark.  Is there anything else we should be looking at?
0
 
MegaNuk3Commented:
So is vader a PHX CAS server?
Do
Get-GetClientAccessServer vader | fl
And look at the autodiscoverserviceinternaluri and the sitescope

Does vader have a cert installed that contains it's name? Did you get a cert error or warning when doing the IE test? Try Test-outlookwebservices again
0
 
trecoolAuthor Commented:
The autodiscoversrviceinternaluri and site scope all check out, and there are no cert errors when doing the IE test.

Still the same errors when i run the test-outlookwebservices command.
0
 
MegaNuk3Commented:
What is 192.168.20.8 ?
0
 
trecoolAuthor Commented:
Internal IP of PHX server
0
 
MegaNuk3Commented:
Is Vader the PHX CAS server?
0
 
trecoolAuthor Commented:
Yes
0
 
MegaNuk3Commented:
1.) Can all other servers contact Vader? like Datacenter server 2?

2.) Is the problem limited to datacenter server 1 contacting Vader?
3.) Vader has no issues contacting datacenter2? Can it see datacenter1?
0
 
trecoolAuthor Commented:
1.  All other servers can see vader's scheduling assistant / free busy.
2.  Correct
3.  correct
0
 
MegaNuk3Commented:
What versions of Outlook are you running?
0
 
trecoolAuthor Commented:
Tried with outlook 2007 and 2010, same problem on both.
0
 
MegaNuk3Commented:
Have a look on the Datacenter1 CAS and VAder and see if they are logging any scheduling assistant events.
0
 
MegaNuk3Commented:
Does it work from OWA?
0
 
trecoolAuthor Commented:
In OWA I get "the attendees sever couldn't be contacted error code 5016"
0
 
MegaNuk3Commented:
Is vader or the other CAS logging any availability events in the application event log?
0
 
MegaNuk3Commented:
Can you open OWA of the mailbox you are trying to get availability for? Have a look at http://technet.microsoft.com/en-us/library/ff597979(v=exchg.80).aspx
0
 
trecoolAuthor Commented:
2011/04/05 11:06:47.586: Getting ASURL

2011/04/05 11:06:47.586: URL returned from cached autodiscover: https://dc1-exchaccess1.usabal.com/ews/exchange.asmx

2011/04/05 11:06:47.586: Request to URL: https://dc1-exchaccess1.usabal.com/ews/exchange.asmx

2011/04/05 11:06:47.586: Request action: http://schemas.microsoft.com/exchange/services/2006/messages/GetUserAvailability

2011/04/05 11:06:47.586: Request XML: <?xml version="1.0"?>

<q:Envelope xmlns:q="http://schemas.xmlsoap.org/soap/envelope/"><q:Body><ex12m:GetUserAvailabilityRequest xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages"><ex12t:TimeZone xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types"><ex12t:Bias>480</ex12t:Bias><ex12t:StandardTime><ex12t:Bias>0</ex12t:Bias><ex12t:Time>02:00:00</ex12t:Time><ex12t:DayOrder>1</ex12t:DayOrder><ex12t:Month>11</ex12t:Month><ex12t:DayOfWeek>Sunday</ex12t:DayOfWeek></ex12t:StandardTime><ex12t:DaylightTime><ex12t:Bias>-60</ex12t:Bias><ex12t:Time>02:00:00</ex12t:Time><ex12t:DayOrder>2</ex12t:DayOrder><ex12t:Month>3</ex12t:Month><ex12t:DayOfWeek>Sunday</ex12t:DayOfWeek></ex12t:DaylightTime></ex12t:TimeZone><ex12m:MailboxDataArray><ex12t:MailboxData xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types"><ex12t:Email><ex12t:Address>ptaylor@balglobal.com</ex12t:Address><ex12t:RoutingType>SMTP</ex12t:RoutingType></ex12t:Email><ex12t:AttendeeType>Required</ex12t:AttendeeType></ex12t:MailboxData></ex12m:MailboxDataArray><ex12t:FreeBusyViewOptions xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types"><ex12t:TimeWindow><ex12t:StartTime>2011-03-20T16:00:00</ex12t:StartTime><ex12t:EndTime>2011-04-19T16:00:00</ex12t:EndTime></ex12t:TimeWindow><ex12t:MergedFreeBusyIntervalInMinutes>30</ex12t:MergedFreeBusyIntervalInMinutes><ex12t:RequestedView>Detailed</ex12t:RequestedView></ex12t:FreeBusyViewOptions></ex12m:GetUserAvailabilityRequest></q:Body></q:Envelope>

2011/04/05 11:06:47.586: Sending request

2011/04/05 11:07:09.043: Request sent

2011/04/05 11:07:09.043: Response error code: 00000000

2011/04/05 11:07:09.043: HTTP status code: 200

2011/04/05 11:07:09.043: XML response:<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Header><h:ServerVersionInfo MajorVersion="14" MinorVersion="1" MajorBuildNumber="269" MinorBuildNumber="0" xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types" xmlns="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/></s:Header><s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><GetUserAvailabilityResponse xmlns="http://schemas.microsoft.com/exchange/services/2006/messages"><FreeBusyResponseArray><FreeBusyResponse><ResponseMessage ResponseClass="Error"><MessageText>System.Net.WebException: Unable to connect to the remote server ---&gt; System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.20.8:443&#xD;
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)&#xD;
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket&amp; socket, IPAddress&amp; address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception&amp; exception)&#xD;
   --- End of inner exception stack trace ---&#xD;
   at System.Web.Services.Protocols.WebClientAsyncResult.WaitForResponse()&#xD;
   at System.Web.Services.Protocols.WebClientProtocol.EndSend(IAsyncResult asyncResult, Object&amp; internalAsyncState, Stream&amp; responseStream)&#xD;
   at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)&#xD;
   at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)&#xD;
   at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)&#xD;
   at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)&#xD;
   at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling():&lt;No response&gt;. The request information is ProxyWebRequest type = CrossSite, url = https://vader.usabal.com/EWS/Exchange.asmx
Mailbox list = &lt;Paige Taylor&gt;SMTP:ptaylor@balglobal.com, Parameters: windowStart = 3/20/2011 4:00:00 PM, windowEnd = 4/19/2011 4:00:00 PM, MergedFBInterval = 30, RequestedView = Detailed
., inner exception: Unable to connect to the remote server</MessageText><ResponseCode>ErrorProxyRequestProcessingFailed</ResponseCode><DescriptiveLinkKey>0</DescriptiveLinkKey><MessageXml><ExceptionType xmlns="http://schemas.microsoft.com/exchange/services/2006/errors">Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException</ExceptionType><ExceptionCode xmlns="http://schemas.microsoft.com/exchange/services/2006/errors">5016</ExceptionCode><ExceptionServerName xmlns="http://schemas.microsoft.com/exchange/services/2006/errors">DC1-EXCHACCESS1</ExceptionServerName></MessageXml></ResponseMessage><FreeBusyView><FreeBusyViewType xmlns="http://schemas.microsoft.com/exchange/services/2006/types">None</FreeBusyViewType></FreeBusyView></FreeBusyResponse></FreeBusyResponseArray></GetUserAvailabilityResponse></s:Body></s:Envelope>

2011/04/05 11:07:09.043: XML response processed successfully
0
 
trecoolAuthor Commented:
"System.Net.WebException: Unable to connect to the remote server ---&gt; System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.20.8:443"

This appears to me to be the pertinent issue.  The site is timing out when being polled for a response.  So my assumption is that the 2 x 2007 servers are configured to access this server by a specific URL (that correctly responds), but the 2010 server is trying to access from a different URL (which apparently doesn't work).
0
 
MegaNuk3Commented:
Check the HTTP keep Alives in IIS are on and ensure they should be at least 120 seconds, I prefer 600 seconds
0
 
trecoolAuthor Commented:
They were set to 120, I increased to 600.  Still no joy :-(
0
 
MegaNuk3Commented:
Did you do an iisreset after the change?

Is windows auth enabled for the EWS virtual directory?
0
 
trecoolAuthor Commented:
I did an IIS reset and the windows authentication is check on EWS.  Incidentally, I rebuilt a new CAS server role for this server (2007) and the problem still exists which this new CAS role too.
0
 
MegaNuk3Commented:
Can you access https://dc1-exchaccess1.usabal.com/ews/exchange.asmx without getting a cert error?

What is dc1-exchaccess1?
0
 
trecoolAuthor Commented:
I get an prompted for a password
Then I get an XML file.

That is one of the 2010 CAS / HT servers
0
 
MegaNuk3Commented:
Can you verify the auth on that directory is windows auth and not basic?
0
 
trecoolAuthor Commented:
Integrated Windows Auth only.
0
 
MegaNuk3Commented:
Do you get prompted for a password when hitting a EWS URL on an Exchange 2007 CAS?

Feel free to hit "Request Attention" on this question to see if we can get some fresh ideas from other experts on this.

Have you thought about installing a temporary Exchange 2010 CAS in the PHX site to see if that allows the exchange 2010 servers to query PHX availability properly?
0
 
trecoolAuthor Commented:
None of the above worked.  The only way I was able to fix it was by moving all the users to the new environment (2010).  Initially, the concern was that we could not move them at that point due to a modular messaging function with Avaya phones and Exch 2010, but this was resolved with an upgrade.

I really appreciate all the effort that was put into this, and I would recommend the mod award the points to MegaNuk3 anyway, despite no real resolution
0
 
MegaNuk3Commented:
Thanks for the update
0
 
MegaNuk3Commented:
Feel free to close the question as you see fit
0
 
trecoolAuthor Commented:
Great troubleshooting, but ultimately, no result.
0
 
Johannes BrandSystem AdministratorCommented:
Exchange 2010SP2 in forest A  and Exchange 2010SP2 in forest B.
we tried this: http://technet.microsoft.com/en-us/library/bb123546%28d=printer%29.aspx 
Did not work.
Need to get Free/Busy working.
Outlook Error: The recipient's server could not be contacted....
OWA Error: The Attendee's server could not be contacted (Error Code 5016)

Any suggestions
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 19
  • 17
Tackle projects and never again get stuck behind a technical roadblock.
Join Now