pombreda / google-calendar-connectors

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

Webservice not working - No free busy pulling through #64

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. log into Google Calendar
2. Add Exchange user username@domain.com under Find a time
3. Click on Refresh
4. Calendar cannot be shown

What is the expected output? What do you see instead?
Get Free/Busy times of Exchange user

What version of the product are you using? On what operating system?
Sync and Webservice 1.3.1.
Windows server 2008
Exchange 2007

Please provide any additional information below.
Diagnostics return success as well as the log files.

Original issue reported on code.google.com by mar...@iron-nest.com on 12 Jun 2012 at 1:46

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by mar...@iron-nest.com on 12 Jun 2012 at 2:01

Attachments:

GoogleCodeExporter commented 9 years ago
Does the diagnostics show the correct free busy times ?
The free busy url which you provided in the cpanel, is that accessible from the 
browser on the machine where you are looking up free busy of the Exchange user ?

Original comment by jaideepg...@google.com on 13 Jun 2012 at 12:37

GoogleCodeExporter commented 9 years ago
Yes Diagnonstics show the correct Free/busy times. And yes it is accessible via 
SSL. What is strange is that it does hit the exchange and as you can see in the 
log it does query the users from Google calendar it is just not sending the 
data back for some reason

Original comment by mar...@iron-nest.com on 13 Jun 2012 at 6:58

GoogleCodeExporter commented 9 years ago
Still not able to get busy free times from exchange.

Original comment by mar...@iron-nest.com on 19 Jun 2012 at 9:13

GoogleCodeExporter commented 9 years ago
Could you please explain your setup ? Is the Exchange and Google domain name 
are same and does the Exchange user exist on Google as well ?

Can you check the IIS logs also ?

Original comment by jaideepg...@google.com on 19 Jun 2012 at 5:14