You don’t have permission to book this resource error [QUICK FIX]

A number of users have reported seeing the error message You don’t have permission to book this resource whenever they try to book a room (or other assets), by using the Outlook Exchange.

This issue is caused by migrating the room mailbox from an on-premises location to the Outlook Exchange Online service. When the move is performed, the permissions of the server need to be assigned again to avoid this issue.

This error message can cause a lot of confusion, as the initial settings of the local room mailbox seem to be in order at first glance. Even though that is the case, these features become inactive for security reasons. This protects the information stored on the servers from any third-party that wants to extract that information.

For these reasons in this article, we will explore several troubleshooting methods to deal with this issue. Please follow the steps described in this guide closely to avoid any other issues.

How to fix You don’t have permission to book this resource error?

1. Assign corresponding permissions of the room mailbox to your Exchange Online account

  1. Log into the Exchange Admin Center with your administrator account.Microsoft Office 365 admin - You don't have permission to book this resourceMicrosoft Office 365 admin - You don't have permission to book this resource
  2. Navigate to Recipient -> Resources.Microsoft Office 365 admin - You don't have permission to book this resourceMicrosoft Office 365 admin - You don't have permission to book this resource
  3. Double-click the room mailbox.
  4. Inside the pop-up window that appears, select Mailbox Delegations.
  5. Add your administrator account inside the Full Access blank space.
  6. Click on the Save button.
  7. Open Room Mailbox again and check to see if the issue persists.

Note: It is recommended that when performing these above steps, you use a private browsing session. Press CTRL+SHIFT+P for Mozilla Firefox, Microsoft Edge, and Internet Explorer. For Google Chrome press CTRL+SHIFT+N.

Send emails like a pro with these great email clients!

2. Add your account to Open Room MailboxExchangeOnline - You don't have permission to book this resourceExchangeOnline - You don't have permission to book this resource

  1. Log into your Open Room mailbox account.
  2. Select Options -> Resource Schedule page -> Add your account to the list.
  3. Inside your Outlook (with admin access) -> right-click Calendar -> select Data Properties.
  4. Inside the Permissions tab -> add the users with the appropriate access level -> click Save.Microsoft Office permissions - you don't have permission to book this resourceMicrosoft Office permissions - you don't have permission to book this resource
  5. Try to see if the issue persists.

Another possible reason for this error message could be caused by users trying to book rooms with 1 year before the preset time limit. This information can be checked by going to Portal ->Exchance -> Recipients -> Calendar -> Edit booking options.

In this article we explored a quick fix for the error You don’t have permission to book this resource when trying to reserve a room or other assets on Exchange Online.

Because this issue is caused by porting the data storage from local to cloud, the problem can be fixed by re-allowing the access for each of the users inside your Microsoft Exchange Admin Center.

Please feel free to let us know if this guide helped you solved your problem, by using the comment section found below.



I need a solution

Dear Sir/Madam

I can’t seem to get emails out due to error …..I manage to clear out other blockage but get this error on the mailbox….

lost connection with[] while sending end of data — message may be sent more than once

my IP Address is




Recovering ‘Deleted Mailbox’ with NMM

Recovering ‘Deleted Mailbox’ with NMM

This article covers the scenario of recovering a ‘deleted’ mailbox from NMM. The procedure documented in this article applies both to NMM 8 and NMM 9. Exchange server 2010 is used in this demo.

Before I cover this procedure in NMM, below is background on how the need for this restore may arise.

In Exchange 2010 a user mailbox can either be ‘Removed’ or ‘Disabled’.


Difference between ‘Remove’ and Disable’ mailbox choice in EMC:

Disable: Will remove the Exchange attributes from the user account but will leave the user account in Active Directory. The mailbox for the user will still exists on the mailbox database and it gets purged when the retention time elapses (default of 30 days)

Remove: Remove will remove both the user mailbox and user account from Active directory. The mailbox will still be there on the mailbox database till the retention time has elapses.

If the mailbox was either ‘deleted’ or ‘removed’ (for some reason, like employee leaving a company), there may be a need to restore this mailbox in future. If the deleted mailbox retention time has not expired, it could be recovered as below:

  1. If the mailbox was ‘Disabled’. This mailbox will show in the ‘Exchange Management Console’ under ‘Disconnected Mailbox’ as shown below:



b. To recover this mailbox, Right click the mailbox and select ‘Connect…’


c. Select ‘User Mailbox’ , then ‘Next’


d. Click ‘Browse’ Under ‘matching user’ and then select the user to connect this mailbox to


e. Provide the ‘Alias’, then select ‘next’


f. Review Summary and select ‘Connect’


g. Review and select ‘Finish’. This will ‘reconnect’ the disconnected mailbox to the user in Active directory.

2. If the mailbox was ‘removed’ and is still within the retention period, create a new ‘user’ in Active Directory with the same name as the original user and then follow the above steps to ‘connect’ the user to the mailbox on the database.

The following exchange shell command is useful to get a list of ‘Disabled’ or ‘Removed’ mailbox users that are still within the retention period:

Get-MailboxDatabase | Get-MailboxStatistics | where {$_.DisconnectReason -ne $null} | ft displayname,database,disconnectreason,*guid*,*server* -auto

DisplayName Database DisconnectReason MailboxGuid ServerName OriginatingServer

———– ——– —————- ———– ———- —————–

charlu carydb3 Disabled 3f91bda9-453c-4752-8b88-423d2f4ccc53 APPHOST1 apphost1.spring.local

Once the retention period expires and the mailbox is purged from the database, it will not show up in the above output.

Once the mailbox data is purged from the mailbox database, if a restore is required after the retention period, then you would need to depend on your backups for restore.

Restoring a deleted mailbox using NMM:

I have used NMM 8.2.4 to demo this procedure. It likely will work as is, with NMM 8.2.3 or NMM 8.2.2. Also the same procedure applies to NMM 9. The first step in performing mailbox restore of mailbox (deleted or otherwise) is to perform GLR or restore to RDB. Refer to the post

  1. Once the initial phase of GLR or RDB restore is complete, the mailboxes can be browsed from NMM GUI:


2. When you click the ‘deleted’ mailbox it generates this error message (shown below). Note, because there is no user associated with this mailbox or the associated user has its mailbox properties removed, MAPI is not able to show the contents of this mailbox. You can only recover the ‘Entire’ mailbox and not individual folders or mail items within it.


3. Acknowledge the message window by click ‘ok’. When you switch to the ‘Monitor’ tab, you will notice the same message there:

Selecting Exchange RDB view

Mailbox SystemMailbox{18d1f726-3cd7-48cd-8983-12ec40779e8b} is a ArbitrationMailbox and is not browsable nor can it be recovered.

Error getting item list: Error browsing folders — Failed to fetch mailbox items. Please see libmapibrowse.raw for more information. [exch_get_mbx_list].

Error browsing folders — Failed to fetch mailbox items. Please see libmapibrowse.raw for more information. [exch_get_mbx_list].

4. Select the mailbox for ‘restore’. Once you select the mailbox for restore, there are 2 types of restores that can be done:

  1. Restore the mailbox to itself

If you want to restore the mailbox to itself, create the mailbox with the same name (you would do this before you do the restore with NMM. You can do this with Exchange Management Console or Exchange powershell and then come back to the NMM GUI and select ‘Recover..’ as shown below:

(Note: If you have disabled the mailbox, connect the mailbox shown under ‘Disconnected Mailbox in EMC to the original user. If the mailbox was removed, then connect, under ‘Disconnected mailbox’ to a new mailbox and a new AD user with the same name. If the mailbox was deleted from the database, due expiry of retention time or the mailbox was manually deleted from the database, using the ‘remove-storemailbox’, then create a new user and new mailbox with the same name and proceed with the restore. In all variations of deletions, the mailbox can be restored to the original mailbox name)


b. Restore the mailbox to another mailbox. (Alternate mailbox)

To restore this mailbox to another mailbox, you would choose ‘Advance Recover..’. Then in the ‘Select Alternate Mailbox User’ box, specify the user to which you want to restore to and click ‘Search’ to locate the user. Then select this user and click ‘Next’


Here we are performing the restore to an alternate mailbox ‘Andy’ and ‘Start Restore’


5. When the restore is complete, switch to the ‘Monitor’ tab to check on the progress.


6. Verify the restore by logging into the mailbox of the target user, in our case ‘Andy’ :


Restore using Exchange PowerShell:

This mailbox restore can also be done using Exchange Powershell:

  1. First get the GLR database name:



b. Issue the new-mailboxrestorerequest command:

new-mailboxrestorerequest -sourcedatabase GLR20180516163434 -sourcestoremailbox “charlu” -targetmailbox “Andy” -TargetRootFolder Restore201805161717 –AllowLegacyDNMismatch



This article covered the procedure involved in restoring a deleted mailbox from NMM 8.2.4 backups. The procedure also applies to NMM 9. Key point to remember is that the deleted mailbox cannot be browsed for individual mail items recovery from the NMM GUI. The entire mailbox can be recovered from NMM GUI or using powershell. Powershell command can be further refined to recover individual folders within the mailbox if desired.


7022961: Forward Copy Rule Using NGW-Variable

This document (7022961) is provided subject to the disclaimer at the end of this document.


GroupWise Mailbox Management


A rule needs to be created that will contain the from address for every user in the system, and forward to a specific folder or address. How can this be done in bulk using GroupWise Mailbox Management?


GroupWise Mailbox Management (GWMM) utilizes the NGW Variable in order to populate fields in the rules, as well as the signatures, so that the administrators do not have to create a rule for every user. Using the variables, and the copy feature in GWMM can save a lot of time and effort. The steps are outlined below to copy a rule and forward it to a different e-mail address, or other action.

1) Create a Forward Rule for a user. In the condition set it to From | Contains | and then input the NGW Variable Email Address: [[NGW-EmailAddress]]
2) Define the action and save the Rule.
3) Launch GroupWise Mailbox Management and select the user that the rule was created, and click on rules
4) Copy the rule to the users.
Note: There is a known issue where the display name will be incorrect, showing the rule creator. The NGW-EmailAddress, however, will have changed to the correct user in the from field. The rule itself will work in GroupWise, and display properly for the users


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.


Processed Count is less than the number of items in a PST or mailbox

Article Number: 496727Article Version: 4 Article Type: Break Fix

SourceOne Email Management 7.2

The ‘Processed’ number of items reported in a mailbox or PST activity is less than the number of items in the PST or mailbox

If no errors are reported for the activity and the job did not fail, the ‘Processed’ count will be lower than the number of items in the PST or mailbox if the PST or mailbox contains items that were processed previously by a SourceOne Email Management activity. When an item is processed by a SourceOne archiving activity, the item is stamped with some unique properties used by SourceOne to indicate that the item has been processed previously. If previously processed items are encountered during subsequent activities, these items are silently skipped over. For mailboxes or PSTs where all items have been processed previously, subsequent activities would report zero ‘Processed’ items

This behavior is expected and allows activities to run faster because items can be skipped if SourceOne properties are present, indicating that the item or items were already archived


SecureMail: Unable to send emails “You cannot send the mail”

Issues with user account unable to send mails

From the logs we see the following warning repeatedly which indicates that the exchange mail submission service is not running. Basically this service submits message from the mailbox server to exchange hub transport servers.

SecureMail,WARNING (3),-[SendMailService(AutoRetry) retryPendingOutboxItemsForAccount:operationQueue:]_block_invoke,”Not retrying outboxItem=0xd00000000004002a <x-coredata://B2AA20B6-9117-4C2E-8DAE-303352E95B07/OutboxItem/p1> due to mailbox submission errors”,-,NSManagedObjectContext 0x10d101ab0,15937,Secure Mail,/jenkins/workspace/iOS_WorxMail/Release_10.7.30/Release_10.7.30/ExchangeMail/activesync/outboxservice/SendMailService/SendMailService+AutoRetry.m,64


Email Encryption Working

I need a solution

We need to know when a user(outside) replies to an encrypted email, does it come back to Outlook mailbox as normal mail, or does the user requires opening the portal to get to the emails?

I will appreciate if you can share details on how the process works.

Thank you



7022496: Can’t see Shared Mailboxes

This document (7022496) is provided subject to the disclaimer at the end of this document.


Directory & Resource Administrator 9.1.x


After installing Directory and Resource Administrator (DRA) 9.1.x, the ability to search for Shared Mailboxes seems to be lost. The previous version of DRA was able to search for the Shared Mailbox, and searching for users seems to return fewer objects in either the 32bit client or Web Console. Checking outside of DRA, in AD for users may show a different number again. By searching for all objects in the Web Console, the result may be different than the one from the 32bit client. Checking in the environment shows that the Web Console is able to view the Shared Mailbox.
The Shared Mailbox is a mailbox that is accessed and used by multiple users, it is a special mailbox type in Microsoft Exchange. Users do not directly access the Shared Mailbox. DRA is able to manage these mailboxes in addition to other types such as the Exchange Enabled AD Users, Equipment Mailboxes, Linked Mailboxes, and Room Mailboxes.


In order to view the Shared Mailboxes, open the Web Console and login as a user who has the proper powers to view the object. From here, click the “More” drop box to the right of the search field, and by “Search for” make sure that the Shared Mailbox is checked. Within the drop down box for “Search for” there will be numerous object types to search for. The search for all objects is simple, just open up the “Search for” box and click ‘”Select All”. Now every object type will show up in the search, in addition now that the Shared Mailbox is selected in the search, any shared mailbox in the environment will show up.


On DRA 9.0.x or older, the Shared Mailbox object also managed the User Account that is associated with it. This can explain why searching in the 32bit client returns fewer objects when searching. With DRA 9.1 or newer, the Shared Mailbox ignores the User Account associated with it and only manages the mailbox itself. This is the reason why Shared Mailboxes are only visible when searching on the Shared Mailboxes and searching all objects from within the Web Console.

Additional Information

This applies to the REST Web Console installed via the DRA REST Installer from DRA 9.1.x.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.