pombreda / google-calendar-connectors

Automatically exported from code.google.com/p/google-calendar-connectors
0 stars 0 forks source link

Uable to view free busy info using Google Calendar Connector #13

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
When running the Diagnostics.aspx page I get the following response while
trying to verify free / busy information can be found in Exchange:

Error occured while retrieving free busy ranges

    Google.GCalExchangeSync.Library.GCalExchangeException: Error occured
while retrieving free busy ranges ---> System.Net.WebException: The
underlying connection was closed: Could not establish trust relationship
for the SSL/TLS secure channel. --->
System.Security.Authentication.AuthenticationException: The remote
certificate is invalid according to the validation procedure. at
System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken
message, AsyncProtocolRequest asyncRequest, Exception exception) at
System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken
message, AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count,
AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32
count, AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes,
AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken
message, AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count,
AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32
count, AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes,
AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken
message, AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count,
AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32
count, AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes,
AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken
message, AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count,
AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst,
Byte[] buffer, AsyncProtocolRequest asyncRequest) at
System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult
lazyResult) at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData) at
System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(
TryCode
code, CleanupCode backoutCode, Object userData) at
System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state) at
System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
ContextCallback callback, Object state) at
System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) at
System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) at
System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) at
System.Net.ConnectStream.WriteHeaders(Boolean async) --- End of inner
exception stack trace --- at System.Net.HttpWebRequest.GetResponse() at
Google.GCalExchangeSync.Library.WebDav.XmlRequestImpl.IssueRequest(String
url, Method method, String body, HttpHeader[] headers) at
Google.GCalExchangeSync.Library.WebDav.WebDavQuery.LoadFreeBusy(String
exchangeServerUrl, ExchangeUserDict users, DateTimeRange window) at
Google.GCalExchangeSync.Library.FreeBusyService.LookupFreeBusyTimes(ExchangeUser
Dict
users, DateTimeRange window) --- End of inner exception stack trace --- at
Google.GCalExchangeSync.Library.FreeBusyService.LookupFreeBusyTimes(ExchangeUser
Dict
users, DateTimeRange window) at 
Google.GCalExchangeSync.Library.ExchangeService.GetCalendarInfoForUsers(Exchange
UserDict
users, DateTimeRange window) at
Google.GCalExchangeSync.Library.ExchangeService.Search(String
ldapAttribute, DateTimeRange utcRange, String[] searchTerms) at
Google.GCalExchangeSync.Library.ExchangeService.SearchByEmail(DateTimeRange
utcRange, String[] searchTerms) at
Google.GCalExchangeSync.Tests.Diagnostics.ExchangeTester.QueryFreeBusy(String
email) at GCalExchangeLookup.Diagnostics.ButtonQueryExchFB_Click(Object
sender, EventArgs e)

Using:
Google Calendar Connector Web Service, 1.2
Exchange 2k3 with sp2
Self Signed Cert
SSL enabled for OWA

Thanks
JohnL

Original issue reported on code.google.com by jlyerly%...@gtempaccount.com on 30 Dec 2009 at 6:43

GoogleCodeExporter commented 9 years ago
Is the SSL certificate being used by the IIS server issued by a Trusted 
Internet Root 
Certificate Authority or and Internal Authority? Based on the errors it appears 
the 
SSL cert is not consider trusted.

If it is based on an Internal Authority you will need to import the Cert Chain 
of 
your Internal Authority into the Computer Cert Store as this is used by the 
"SYSTEM" 
account which IIS is running under. Use MMC and load the Certificate snap-in. 
Select 
service account and load the World Wide Web Publishing Service.

You can disabled SSL for testing purposed until you fix your SSL Certificate 
Trust 
issue in IIS.

Based on the error: : Could not establish trust relationship for the SSL/TLS 
secure 
channel. --->
System.Security.Authentication.AuthenticationException: The remote
certificate is invalid according to the validation procedure.

Original comment by dk...@google.com on 30 Dec 2009 at 6:55