Forum Discussion

JrouziesM's avatar
JrouziesM
Copper Contributor
Sep 15, 2023

The type of the resource mailbox can't be blank. It should be either Room or Equipment.

Hello,

 

We are having errors on some Room Remote Mailboxes, and cannot find any reference on Internet or apply any fix unless Disabling and Re-enabling the Room mailbox.

 

Get-remotemailbox HoChiMinhViettelTower_MeetingRoom01 | set-remotemailbox -Type Room


WARNING: The object [REDACTED]HoChiMinhViettelTower_MeetingRoom01 has been corrupted or isn't compatible with Microsoft support requirements,
and it's in an inconsistent state. The following validation errors happened:
WARNING: The type of the resource mailbox can't be blank. It should be either Room or Equipment.
The type of the resource mailbox can't be blank. It should be either Room or Equipment.


At [REDACTED]\tmp_zu4ztplk.5ht.psm1:83693 char:9
+ $steppablePipeline.End()
+ ~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: ([REDACTED]...r_MeetingRoom01:ADObjectId) [Set-RemoteMailbox], DataValidationException
+ FullyQualifiedErrorId : [Server=[REDACTED],RequestId=b9be74fc-1754-48a4-affe-9ffe9bab2772,TimeStamp=9/15/2023 8:35:59 AM] [FailureCategory=Cmdlet-DataValidationExceptio
n] 2FDDA03D,Microsoft.Exchange.Management.RecipientTasks.SetRemoteMailbox
+ PSComputerName : [REDACTED]

 

No command work on it (as show with the Set-RemoteMailbox), AD Attributes are exactly the same as other meeting rooms, recipient types are correct on Get-Mailbox (cloud) or Get-Remotemailbox:

 

get-remotemailbox HoChiMinhViettelTower_MeetingRoom01 | fl *type*


RemoteRecipientType : Migrated, RoomMailbox
RecipientType : MailUser
RecipientTypeDetails : RemoteRoomMailbox

 

get-mailbox HoChiMinhViettelTower_MeetingRoom01 | fl *type*


ResourceType : Room
RemoteRecipientType : Migrated, RoomMailbox
RecipientType : UserMailbox
RecipientTypeDetails : RoomMailbox

 

Any idea? 

6 Replies

  • LeonPavesic's avatar
    LeonPavesic
    Silver Contributor

    Hi JrouziesM,

    The error message you posted indicates a problem with the mailbox type. To try to resolve this, you can try this:

    1. Check that the mailbox type is set correctly as "Room" in Exchange Online. You can do this using PowerShell with the following command:

     

     

    Set-Mailbox -Identity "HoChiMinhViettelTower_MeetingRoom01" -Type Room

     

     

    2. Verify the mailbox type for the remote mailbox by running:

     

     

    Get-RemoteMailbox "HoChiMinhViettelTower_MeetingRoom01" | Select-Object -Property RemoteRecipientType, RecipientType, RecipientTypeDetails

     

     

    Ensure that `RemoteRecipientType` is "Migrated, RoomMailbox," and `RecipientTypeDetails` is "RemoteRoomMailbox."

    3. Permissions: Ensure that the account running the PowerShell script has the necessary permissions to modify resource mailbox types.

    4. Ensure there are no duplicate mailboxes or conflicting settings that might be causing the issue:

     

     

     

    Get-Mailbox -Filter {DisplayName -like "HoChiMinhViettelTower_MeetingRoom01"} | Select-Object DisplayName, RecipientType

     

     

    5. Review AD Attributes: check the Active Directory attributes for this mailbox, ensuring they match those of other working room mailboxes.

    - look for attributes related to mailbox type and permissions. Common attributes to check include:

    • msExchRecipientTypeDetails: This attribute specifies the recipient type of the mailbox. For a room mailbox, it should be set to a value corresponding to "Room Mailbox."

    • msExchRecipientDisplayType: This attribute indicates the recipient's display type. For a room mailbox, it should be set to "Conference Room."

    • msExchResourceMetaData: This attribute may contain additional information about the resource mailbox.

     

    6. Run Mailbox Repair: detect and repair mailbox issues. Here's an example:

     

     

    New-MailboxRepairRequest -Mailbox HoChiMinhViettelTower_MeetingRoom01 -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview

     

    This command initiates mailbox repair for various types of corruption.

     

    6. Remove and Recreate the Remote Mailbox: if the issue persists, remove and recreate the remote mailbox. You can use these commands:

     

     

    Disable-RemoteMailbox "HoChiMinhViettelTower_MeetingRoom01"
    Enable-RemoteMailbox "HoChiMinhViettelTower_MeetingRoom01" -Room

     



    Please click Mark as Best Response & Like if my post helped you to solve your issue.
    This will help others to find the correct solution easily. It also closes the item.


    If the post was useful in other ways, please consider giving it Like.


    Kindest regards,


    Leon Pavesic

    • JrouziesM's avatar
      JrouziesM
      Copper Contributor

      LeonPavesic 

       

      Thanks for detailled reply, unfortunately all those things were already tried.

       

      The types are already good as said in my post.

       

      Online command:

      Set-Mailbox -Identity "HoChiMinhViettelTower_MeetingRoom01" -Type Room
      WARNING: Couldn't convert the mailbox because the mailbox "HoChiMinhViettelTower_MeetingRoom01" is already of the type "Room".

       

      OnPremises command throw the error as indicated also in my original post.

       

      The mailbox work properly, so repair commands Online are not going to fix an error on the OnPremises command.

       

      Active Directory Attributes are filled properly:

       

      Get-ADUserByUPN -UserPrincipalName email address removed for privacy reasons -Properties * | FL *recip*


      msExchRecipientDisplayType : -2147481850
      msExchRecipientTypeDetails : 8589934592
      msExchRemoteRecipientType : 36

       

      Example of another room that does not have the error:

       

      Get-ADUserByUPN -UserPrincipalName email address removed for privacy reasons -Properties * | FL *recip*


      msExchRecipientDisplayType : -2147481850
      msExchRecipientTypeDetails : 8589934592
      msExchRemoteRecipientType : 36

       

      Again I compared all properties with a room without this error / warning, and everything match.

       

      Yes last time it happened, disabling and re-enabling did the trick, but this is not a satisfying solution. Microsoft should find the source of the error and allow us to run a fix.

       

      How do we report this kind of bug officially so Microsoft finds a fix?

       

Resources