Good morning!

I'm having an issue at a client of mine  regarding a shared calendar.  The client is a small clinical practic and the calendar in question is the doctors calendar on which all appointments are scheduled.  This calendar has been shared out with three users who all have publishing editor permissions on the calendar.  However, when one of the users, lets call her User A, makes changes on the calendar, nobody else can see it.  All other users (including the doctor whose calendar it is) see appointments made by everyone EXCEPT User A.  User A also does not see any appointments made by anyone but herself.  This is all in Outlook 2013.

Now if I log into OWA and create an appointment on the shared calendar as her all other users can see it and she can see the appointments made by all other users?  All of the account settings w/ regards to cached mode are the same in Outlook for her as compared with other users so I'm at a bit of a loss to explain this.

Make sure that the calendar isn't being used in cached mode.

Ed,

The issue seems to have cleared itself up.  Not really sure what happened.  I was going to take off cached mode but since it started working properly I figured "If it's not broken..."

Let us not leave it like this. 

If you are able to see the calendar entries after it has been created in OWA then it is surely an issue with outlook client and not the server end.

Also it is possible that only one of the 3 users have issue replicating the calendar entry to server from where it is distributed to other 2. Please narrow down the issue so that if it reappears we can fix it.

Prem,

It was only one user that was having issues with replication.  User1 would make a change in her Outlook and users 2 and 3 would not see those changes.  User 2 or user 3 could make a change and they would both see it but user 1 would not.

However, as I said, suddenly user 1 is able to see other updates made to the calendar and all other users are able to see the updates user 1 makes as well.  The issue is pretty narrow, its just no longer occurring so there is nothing to test/fix at the moment.

Hi,

Thank you for your update. If this issue reappear, please post here for further troubleshooting.

ok...