Some Calendars/Contacts will only share "Read-Only"
 

We have installed MS SBS2003 and Outlook 2007. We have 3 attorneys in the
office that have thier calendars shared to one (the same person) assitant
with rights as "Publishing Editor". The assistant can only add items to one
calendar/contacts and not the other two. The permissions are the same for
all three. When trying to add an item to one of the two we are having
problems with we recieve the following error message: Microsoft Office
Outlook - Cannot open the free/busy information. You do not have sufficient
permission to perform this operation on this object. See the folder contact
or your system administrator.

We have tried to share the two attorney's calendars/contacts with others in
the office and we recieve the same message.

We have also tried sharing the "top level" of the users mailbox with
"Publishing Editor" rights and this has not solved the problem either.

Where else can we look? Or what else can we do?

Thanks in advance for your time,

Scot

Some Calendars/Contacts will only share "Read-Only"
 

I have found some other notes that state to open Outlook with the command
/FreeBusyClean and I have done this on both systems where the calendar is
shared and the recipients system as well and this has not solved the problem.

"BSLGroup" wrote:

We have installed MS SBS2003 and Outlook 2007. We have 3 attorneys in the
office that have thier calendars shared to one (the same person) assitant
with rights as "Publishing Editor". The assistant can only add items to one
calendar/contacts and not the other two. The permissions are the same for
all three. When trying to add an item to one of the two we are having
problems with we recieve the following error message: Microsoft Office
Outlook - Cannot open the free/busy information. You do not have sufficient
permission to perform this operation on this object. See the folder contact
or your system administrator.

We have tried to share the two attorney's calendars/contacts with others in
the office and we recieve the same message.

We have also tried sharing the "top level" of the users mailbox with
"Publishing Editor" rights and this has not solved the problem either.

Where else can we look? Or what else can we do?

Thanks in advance for your time,

Scot