Unable to book resource through OWA
Our environment consists of an Exchange 2007 server, Outlook 2003, Outlook 2007 and OWA clients. We are beginning to use calendaring to schedule meetings and reserve resources. Until now, we have been able to reserve resources either via Outlook or via OWA. Recently, we have been unable to book SOME (not all) of the resources via OWA. When we attempt to do so, we receive the message: Your meeting request was declined. You do not have permission to book this resource. Sent by Microsoft Exchange Server 2007. The same user can book the same resource for the same time period if they do it through Outlook. Please help. We are trying to get our users to adopt calendaring and frustrations like this are hindering adoption. I have seen indication that the server could use some clean up of free/busy and the like. I know there is a command line you can run and have done so on clients, but am not sure about running it on the server. Any suggestions would be appreciated. Thanks, Andi
November 23rd, 2010 1:51pm

Hi Andi, Form the message “You meeting request was declined. You do not have permission to book the resource”. We know that you may do not have permission to book the resource. But you said that the same user can book the same resource for the same time period if they do it through Outlook. Let’s take the following steps to troubleshoot the problem: 1. Does this issue occur to all the users or only one user? 2. Please let me know whether the resource Mailboxes which cannot book are created on Exchange 2007 Server directly or migrating from Exchange 2003. Based on my experience, this problem often occurs to pervious Exchange Servers: Cannot book resources in Outlook Web Access http://support.microsoft.com/kb/329036 3. Which method you use to book the resource room, by sending email or logon to its calendar? 4. Please create a new resource mailbox to have a try. 5. If your Exchange Server have not installed the latest updates, please install the latest updates to have a try. Thanks, EvanPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
November 27th, 2010 10:50am

Hi Evan, I am told that our Exchange 2007 server was a clean install (not an update). The problem has occurred for several users (2 "regular" exchange clients and myself as an admin). We are trying to book by creating an appointment within our own calendar and then adding a room using the scheduling assistant. As I indicated, this was working both via Outlook and via OWA but now works only via Outlook. The resources are set up to AutoAccept and Autodecline conflicting. I have read several posts (most old) that say this is a problem for OWA but I was hoping this might have been resolved by now (especially since, as I say, it was working at one point). We need to have the requests auto-processed as we do not want to have someone have to monitor the resource. Per your request, I created a new resource. I set it up as above granting default and anonymous the rights to view details, create items, edit own, delete own and folder visible. When I created an appointment via OWA from a "generic user mail account", the "invitation" was delivered to the resource but was not processed. It remains in the Inbox. This is slightly different than the behavior we are seeing with the previous resources where they were automatically processed but declined because "you do not have permission.....". I have set the resource scheudling permissions and options by logging into the outlook client as the resource. Perhaps I would have better luck if I set the properties using the dreaded Shell? If so, could/would you be able to provide correct syntax for each of the things I need to set to make this work with OWA. The other thing that I have read has something to do with an auto-accept agent to be installed on the server? Is this something I need to do? Re: the exchange server, it is running 08.01.0340.000 on Windows Server 2003 SP2 64 bit. I believe it is due for an update but we have been hesitant as we got singed by a SEP update this last summer. Any thoughts/suggestions?
November 29th, 2010 1:15pm

Hi Andi, From you description, I understand that the appointment which you send via OWA can see in the new resource box, but cannot process. It is different from the problem you got before. So I suggest you follow this steps to troubleshoot the problem: 1. I suggest you use this command “Get-MailboxCalendarSetting” to check the setting , and post all the setting in your next post. Here are some related articles: Set-MailboxCalendarSettings http://technet.microsoft.com/en-us/library/aa996340.aspx Resource scheduling in Exchange Server 2007 http://msexchangeteam.com/archive/2007/05/14/438944.aspx 2. Please use Outlook to do a test for the new resource( make sure use the same account to do the test), whether the same error will occur or not? You can know more about auto accept agent from this link. Besides that, I suggest you upgrade to sp3 and test the issue. Best Regards, Evan Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2010 3:40am

Morning Evan, I think I am going to go ahead and work out a schedule to update our exchange server. This morning's test yielded the following: 1- The "new" resource that did not process the requiest from OWA yesterday, sent confirmation of today's request. 2- However, one of the original resources is still misbehaving - same user can book through Outlook but receives a denial due to "permissions" when using OWA. 3- The shell results for the "origional" resource are: Identity AutomateProcessing -------- ------------------ domain.local/Resources/*Resource-Conference Room 2 AutoAccept 4- The shell results for the "new/test" resource created yesterday: Identity AutomateProcessing -------- ------------------domain.local/Resources/*Resource-TestRoom AutoUpdate I see the difference between the two but am confused. Despite saying AutoUpdate, the "new" resource does accept and send confirmation. I just tried set-mailboxcalendarsettings identity Confrm2 -AutomateProcessing AutoUpdate. The user was then able to book the resource via OWA. I see that AutoUpdate invokes the Calendar Attendent as opposed to Resource booking and while I have seen the terms, I am totally not clear on the difference. If I go ahead and change all of the existing resources to Calendar attendent, will the work for both my Outlook clients and my OWA users? When I originally set up the resource scheduling, I used the client to log-in to the resource mailbox and set the autoaccept parameters and permissions. Does it make a difference? Do I have to log in to the resource via OWA also? Also, I did all setup via the gui and there, the settings for all resources are exactly the same, yet, when viewed through the shell you see that the system did not actually set them up identically. Would you know why this occurred? Thanks much for any enlightenment you can provide. My previous experience with Exchange was 2003 which in retrospect I remember as being a lot simpler. Best, Andi
November 30th, 2010 12:04pm

PS What are the potential negetive consequences of setting all resources to Calendar attendant vs Resource booking? Thanks, Andi
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2010 12:16pm

I just realized that this will not work for us. The calendar attendant appearantly requires someone to open the resource mailbox before the requests are actually processed. Since the goal is to relieve folks from having to monitor and approve resource requests,,,,,, Can anyone help? Please............. Thanks, Andi
December 2nd, 2010 4:22pm

Hello all, We have updated the Exchange server to SP3 and unfortunately, the same resource booking problem continues. Can anyone shed some light please? Also, if I were to set the resource mailboxes to <Auto Update> (as opposed to auto accept), would someone with full permissions having the calendar open in their mailbox (as an open shared calendar) force the processing or would the mailbox have to actually be opened as the "resource/user" signing directly into the account in order for the reservation to be confirmed (as opposed to tentative)? Thanks, Andi
Free Windows Admin Tool Kit Click here and download it now
December 9th, 2010 8:40am

Thanks to Evan for supplying the links to the information that finally helped me to get this configured. Initially, I created the the resource mailboxes. Then, within the Exchange Management Counsole, I granted full access permissions to the resource mailboxes as required. After than, I logged into each of the mailboxes using the Outlook client and from <Tools> in <Calendar> settings, I chose the options to <Auto Accept> and granted the necessary permissions to the default and anonymous users to allow each to view free/busy, create items, and modify and delete their own items. When I viewed the autoprocessing parameters on the mailboxes using the shell, I got the above results (some AutoAccept, some AutoUpdate). At this point, some worked in OWA, others did not. All worked via the Outlook client. My bad I guess as I did not think that logging into the mailbox using a different interface (OWA as opposed to the full blown client) and setting options the same options there would produce different results. However, that is exactly what happened. I guess I always thought that the mailbox was the mailbox on the Exchange server and Outlook/OWA where simply different ways to view the same information. Given the above, I would say that is not quite true. So, the moral of the story is, if you have users that use Outlook as well as those that use OWA, you will probably be wanting to set the parameters via both clients. Thanks again for your help Evan.
December 9th, 2010 1:31pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics