"Could not synchronize record: [calendar item] to Exchange server: [[email protected]]" Error:

[matermorts]

I've been getting this synchronization error since our Exchange admin
moved all of our company's mailboxes to a new server. Not sure why,
but he had to rebuild Exchange 2003 (on a different physical server)
and subsequently moved all of the mailboxes. It's the same version of
Exchange that was on the old server.

I'm running Entourage 11.2.4 on OSX 10.4.7. Other Mac users, running
various versions of Entourage (11.x), are experiencing the same issue.
Send/Receive mail is fine.

Something interesting... I can delete meeting requests from Entourage
and that change will synch to Exchange just fine. It seems to be just
new calendar items. Although, I accepted a meeting request this
morning, coming from a PC user, and that synched fine, but other
invitations from other PC users do not synch. It seems to be
inexplicably intermittent. Also, I can accept meeting requests on my
PC and that will synch down to Entourage but nothing will synch up
(other than the previously mentioned invitation I accepted this
morning).

Very strange. Any suggestions?!?

Thanks,
nate

 

[random.tard]

We're having the same problem. I think it is related to application of
a hotfix to the Exchange server/cluster:

Security Update for Exchange Server 2003 SP2 (KB912442)
http://www.microsoft.com/downloads/...9f-52b7-4f17-96c7-daf3b9987d70&DisplayLang=en
<http://www.microsoft.com/downloads/...2b7-4f17-96c7-daf3b9987d70&amp;DisplayLang=en>


Anyone know how to contact the MacBU?

 

[random.tard]

Just a followup - the 11.2.5 update released today does not resolve
this issue.

 

[jackie.case]

Recent updates to both Exchange 2003 SP1 and SP2 have changed the way
"Send As" permissions are handled. This apparently has had side effects
for Entourage's ability to write to shared calendars. The workaround
I've found is to assign "Send As" rights for the users who need to
write to the shared Calendar by assigning them delegate rights (Tools -
Accounts - Exchange Account - Delegation tab) instead of regular folder
level permissions. "Send As" rights are granted implictly in both
Outlook and Entourage when adding Delegates (not through permissions on
the folder).

J

 

[matermorts]

Recent updates to both Exchange 2003 SP1 and SP2 have changed the way
"Send As" permissions are handled. This apparently has had side effects
for Entourage's ability to write to shared calendars. The workaround
I've found is to assign "Send As" rights for the users who need to
write to the shared Calendar by assigning them delegate rights (Tools -
Accounts - Exchange Account - Delegation tab) instead of regular folder
level permissions. "Send As" rights are granted implictly in both
Outlook and Entourage when adding Delegates (not through permissions on
the folder).

J

I think I'm missing something (or maybe I'm just tired) but these are
calendar items that I added to my calendar. I don't see how adding a
delegate has anything to do with that.

Could you explain further, Jackie?

Thanks,
nate

 

[matermorts]

I've been getting this synchronization error since our Exchange admin
moved all of our company's mailboxes to a new server. Not sure why,
but he had to rebuild Exchange 2003 (on a different physical server)
and subsequently moved all of the mailboxes. It's the same version of
Exchange that was on the old server.

I'm running Entourage 11.2.4 on OSX 10.4.7. Other Mac users, running
various versions of Entourage (11.x), are experiencing the same issue.
Send/Receive mail is fine.

Something interesting... I can delete meeting requests from Entourage
and that change will synch to Exchange just fine. It seems to be just
new calendar items. Although, I accepted a meeting request this
morning, coming from a PC user, and that synched fine, but other
invitations from other PC users do not synch. It seems to be
inexplicably intermittent. Also, I can accept meeting requests on my
PC and that will synch down to Entourage but nothing will synch up
(other than the previously mentioned invitation I accepted this
morning).

Very strange. Any suggestions?!?

Thanks,
nate

Update, in case anybody is still reading this thread:

Our Exchange admin learned that the previous configuration of Exchange
(before the rebuild) contained a combination of Exchange 5.5, Exchange
2000, and Exchange 2003 settings. It was actually upgraded from
Exchange 5.5 to Exchange 2000 and then finally to Exchange 2003; in
other words, never wiped and then clean install.

Well, when he did the clean build last weekend, that wiped out all of
those settings that carried over from upgrade to upgrade.
Unfortunately, our Entourage clients were dependant upon some of those
settings for calendar and Public Folder synchronization. So, now we're
in the process of learning how to configure a brand new install of
Exchange 2003.

Thanks anyway,
nate

 

[Bill Robertson]

I've been getting this synchronization error since our Exchange admin
moved all of our company's mailboxes to a new server. Not sure why,
but he had to rebuild Exchange 2003 (on a different physical server)
and subsequently moved all of the mailboxes. It's the same version of
Exchange that was on the old server.

I'm running Entourage 11.2.4 on OSX 10.4.7. Other Mac users, running
various versions of Entourage (11.x), are experiencing the same issue.
Send/Receive mail is fine.

Something interesting... I can delete meeting requests from Entourage
and that change will synch to Exchange just fine. It seems to be just
new calendar items. Although, I accepted a meeting request this
morning, coming from a PC user, and that synched fine, but other
invitations from other PC users do not synch. It seems to be
inexplicably intermittent. Also, I can accept meeting requests on my
PC and that will synch down to Entourage but nothing will synch up
(other than the previously mentioned invitation I accepted this
morning).

Very strange. Any suggestions?!?

Thanks,
nate

We had this problem adding events to a calendar by a delegate, and after a
lot of work discovered a couple of things.

One is that we could synchronize a calendar item if it was at least 2 months
in the future. This suggested that there was something about the Free/Busy
status involved, since the default value for publishing Free/Busy status is
two months. Resetting this value had no effect on the problem however.

Finally, we found that you can add an appt to a calendar if you set the
Free/Busy status of the event to Free using the Options menu in the new appt
window. The default is Busy.

MS finally said it had something to do with a security patch we'd applied
earlier in the Summer. I don't recall if it was a server or Exchange patch.