Unable to book a resource directly

[Guest]

We have 5 meeting rooms which are setup as resources in Outlook.

We have been booking these resources without a problem until recently.

All meeting rooms except 1 can be booked as a resource. Whenever I try and
include Meeting Room 3 as a resource and select send I get the error message:

"The opreation failed. Unable to directly book a resource for this meeting"

This error appears on Outlook 2000 clients only. All Outlook 2003 clients
book the resource without any errors.

All the resources have identical permissions set, and have worked OK in the
past.

I don't understand why all of a sudden, one resource does not work !!!

 

[Guest]

I'm experiencing a similar issue. We have several meeting rooms and all have
been working fine - some users were granted a combination of editor
access\delegation access thru outlook, mailbox rights thru ad users and
computers. After this, It was then requested that they have regular access
and then those users whose access was reduced got the error "The operation
failed. An object could not be found. Unable to directly book a resource
for this meeting." when trying to book the meeting room or other meeting
rooms.

The users are using outlook 2003 in cached mode. The users also have author
permissions on the mailboxes (the default settings have author, and we
explicitly added the users with author and then editor for testing - still no
luck)

I tried deleting the c:\documents and settings\user profile\local
settings\applpication data\Microsoft\FORMS\frmcache.dat file, then the
booking works a few times, and then we get the same error - and when we check
the then the file has been regenerated.

As a temporary fix, I have reconfigured outlook 2003 to work in non-cached
mode and the error is no longer there (in tools-e-mail accounts, view or
change existing e-mail accounts,select the account, change, uncheck used
cached exchange mode).

Has anyone found the issue and an solution for this?
Kareem

 

[Leom]

Active Directory Problem

Had the same problem
It was a rights issue in active directory. The group that had access was a distribution group only - when changing them to a security group problem solved