Web Service not updating with new Calendar Entries
sherpadave
issue; any new Exchange initiated Calendar entries are not showing up
in Google Apps. There are entries listed, but any new Calendar events
(meetings and such) I create within Outlook (no cached mode, all live)
are not showing up in Google Apps, as well as not showing up in the /
diagnostics.aspx tool. The /diagnostics.aspx tool shows a number of
Busy Times, just not the new ones I've created since I installed the
WebService app.
It did actually update once; I created a new event, and about 20
minutes later is showed up after a number of refreshes (/
diagnostics.aspx). But I've created a few new ones since, and...
nothing... no new data. It all shows up in Outlook, and shows up when
I share the Calendars with other Exchange users, just the WebService
app is not seeing them.
I've tried unmounting and mounting the Public Store, restarting the
Information Store, restarting the IIS server, clearing any local
caches within IE, Firefox, and Chrome, restarting the Exchange server
(which all of this resides; E2K3, IIS, WebService). It's a rather
virgin environment, non production, created from scratch to test the
Free/Busy Connector, with two different user sets... no duplicate
users between Exchange and Google Apps.
It's like the WebService is no longer syncing with the Calendar, stuck
in a cached mode, so to speak.
How can I manually initiate a new sync between the WebService lookup
function and the Public Store, or Calendar, however it does it.
Thanks all,
Dave
dkuhn
The problem you report sounds like an issue with your Exchange
environment. By default Outlook does not publish free/busy data right
away. It only updates the Exchange free/busy store every 15 mins. We
read the Exchage Free/Busy store so if its not there we won't see the
Exchange free/busy data either. I think this explains why after 20
minutes you saw some update. If you then take into account the time it
could take to replicate this free/busy data to other Exchange servers
hosting a copy of the Free/Busy store it can be longer.
Here is a good atrucle that talks about Free/Busy data and Outlook
http://technet.microsoft.com/en-us/library/aa996946(EXCHG.65).aspx
Publishing Free/Busy Data with Outlook
By default, Outlook publishes the free/busy data for a user one time
every 15 minutes, and again when Outlook shuts down. When publishing,
Outlook updates the entire free/busy message instead of just adding
changes to the existing message. The message includes free/busy data
that ranges from the current month to two months in the future.
With that said it sounds like you are still having problems with even
newer events you have created and even after waiting 20 mins you still
don't see it correct?
A couple of things you might want to check.
1) Make sure free/busy replication is working to the server in which
the Google Calendar WebService is configured to talk too? If there is
a problem with replication of free/busy data to this Exchange server
we might never see updates.
2) Verify other users outside of your local Exchange server are able
to view the free/busy data. Again this can be related to free/busy
replication. If you have a single server this should not be an issue.
3) Keep in mind Outlook will keep a cache of your free/busy store as
well (regardless of cache mode or online). Again this is around 15
minutes so it is hard to check free/busy data via Outlook. You can use
the diagnostics.aspx as we don't cache any data.
Lastly I just want to clarify one thing, we don't sync any data for
Exchange Free/Busy data. We always perform a real-time request to the
Exchange Free/Busy store for data. We do sync into Exchange Free/Busy
data for Google Apps users. I just want to make sure in this case you
are only having a problem getting free/busy data for an Exchange user
correct?
We would be happy to review any logs you might have. I would suggest
editing the .config and changing the logging from INFO to DEBUG so
that we get verbose data. We can review that data to see if there is
anything out of the ordinary.
Darrell Kuhn
Google Inc.
sherpadave
environment. No production users. With that said, is replication
even needed? I suspect my Free/Busy process on the Exchange side
isn't working or setup properly. Is there a sure-fire way to test or
make sure it's all working as expected?
Thanks,
Dave
On Jul 23, 4:10 pm, dkuhn <dk...@google.com> wrote:
> Dave,
>
> The problem you report sounds like an issue with your Exchange
> environment. By default Outlook does not publish free/busy data right
> away. It only updates the Exchange free/busy store every 15 mins. We
> read the Exchage Free/Busy store so if its not there we won't see the
> Exchange free/busy data either. I think this explains why after 20
> minutes you saw some update. If you then take into account the time it
> could take to replicate this free/busy data to other Exchange servers
> hosting a copy of the Free/Busy store it can be longer.
>
sherpadave
I've been using the Outlook client when creating the Calendar events
for this particular test user. I would see them in the Outlook
client, as well as from other test user mail Profiles, I could see the
events scheduled when I would view their Calendars. BUT, not via the
diasnostics.aspx script, nor through Google Apps.
Then, when I used OWA and deleted an event... all of a sudden, I could
see the correct information in the diagnostics.aspx script, as well as
within Google Apps. Something in the OWA process pushed the update to
the Public Folder (Free/Busy) where the Outlook client wasn't.
And I restarted the Information Store Service somewhere in the middle
there.
It seems to be working as long as I use OWA... why would the Client be
the flaw in this scenario? Prior to today, I've created (via the
Outlook client) several new events that have not shown up in Free/Busy
(diagnostics.aspx nor Google Apps), even after restarting the server a
few times, dismounting and mounting stores, just about everything...
but OWA (which I understand has a direct tie to the databases, as
opposed to Outlook), OWA kicked it all in the arse and pushed the
updates... why?
Dave