HTTP Resource Conflict Error -18591

[monkeymissile]

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: Exchange

One of my users is getting this error whenever she tries to create a calendar event on a shared calendar and invite people to it. The message gets saved in her Drafts folder and is otherwise useless. This just recently started, previously she had no problems. According to MS, this error code doesn't exist for Entourage. Any ideas? Thanks.

 

[Diane Ross]

One of my users is getting this error whenever she tries to create a calendar
event on a shared calendar and invite people to it. The message gets saved in
her Drafts folder and is otherwise useless. This just recently started,
previously she had no problems. According to MS, this error code doesn't exist
for Entourage. Any ideas? Thanks.

We don't have this error, but often errors close in number have similar
solutions.

Number Errors <http://www.entourage.mvps.org/error/number.html#error-18596>

Does the user have permissions for the calendar?

 

[monkeymissile]

evidently this is now a known bug with the latest Office 2008 update and Entourage. I hope the patch is in the works. Thank you for the reply.

<http://blog.entourage.mvps.org/2008...reaks_sending_exchange_meeting_invitatio.html>

 

[mayall]

I was getting a different error when using 12.1.3. I have updated to 12.1.4 and now get the error described in this message. If I keep tryig to send, eventually it is sent OK.

This gives me the strong impression that the bug introduced in 12.1.3 was not properly fixed.

Will Mayall

 

[Diane Ross]

I was getting a different error when using 12.1.3. I have updated to 12.1.4
and now get the error described in this message. If I keep tryig to send,
eventually it is sent OK.

This gives me the strong impression that the bug introduced in 12.1.3 was not
properly fixed.

Others are reporting the issues are fixed. This error number was not
associated with the update bug.

 

[monkeymissile]

I am experiencing the same symptoms as the bug, but the error code may be different because we aren't using Exchange for mail.
I see that a patch has been issued although the AutoUpdater within Office 2008 isn't detecting it yet. I'll try the patch and report back.
Thanks