Question: What are the common reasons for encountering "Error: Hosted Organization does not exist"? OR we are receiving the error "Error: Hosted Organization does not exist." while trying to add a mail domain/mailbox to an existing organization; or while importing the Exchange Organization in HC Panel. What could be the reason for it? OR After decommissioning old DC and moving to the new DC, while trying to create a mailbox on a few different clients in our HC we receive this error: "Error: Hosted Organization does not exist.".
Answer : Exchange and Active Directory are tightly coupled as most of the objects related to Exchange are also created at the back-end in Active Directory therefore if any manual change is performed on the Active Directory which is related to any Exchange Organization then such change can result in this error Error: Hosted Organization does not exist inside HC panel. However, there could be other issues too for this error which can be diagnosed and corrected by following the instructions as mentioned in this kb article. Most common reasons for this error are given below along-with the resolution to each problem :
Reason # 1 ( Exchange is not connecting in HC panel ) : If HC panel is not connecting to Exchange server from : Configuration >> Server Manager >> Server >> Edit >> Save & Edit Roles at Global/Global-sub admin level then this error may be encountered.
Resolution : To resolve it, follow the instructions as mentioned in the kb article given below:
Note: If Exchange Connectivity in HC panel started to fail after applying Exchange Cumulative Update, then only follow step # 2 of the aforementioned kb article link to resolve the issue.
Reason # 2 ( HC Generated Security Group for Exchange Organization does not exist ) : Upon creation/import of Exchange Organization via HC panel, a security group named OrganizationName_DL is added by HC panel. If this security group is somehow deleted from the Organization Unit (OU) in Active Directory then HC throws error "Error: Hosted Organization does not exist.".
Resolution : If the security group OrganizationName_DL does not exist under the concerned Organization Unit in Active Directory then create it manually and this will resolve the issue.
Note: Important points while creating this group must be considered:
- Scope of OrganizationName_DL group must be Universal
- Type of OrganizationName_DL group must be Security
Reason # 3 ( If ABP and its constituents ( GAL,AL,Room Lists, OAB are not according to HC standards ) ) : Upon creation/import of an Exchange Organization in HC panel, the following objects are created in the Active Directory for each organization with the following Common Names :
If Common Name of any of these objects is not found in Active Directory then error "Error: Hosted Organization does not exist." is thrown in HC panel. These names can be seen in adsiedit editor and must not be changed as it could make HC to throw the error as discussed in this kb article.
To create any of the missing objects via Exchange PowerShell commands, please contact Hosting Controller support department by sending an email to email@example.com
Important Note : Do not try to add these objects by yourself via PowerShell commands as HC team will provide you with the standard commands for creation of these objects according to HC standards.
Reason # 4 ( If Root OU path of an Exchange Organization is wrong in HC Panel database) : HC stores all Organizations under Root Organization Unit that is specified while configuring Exchange Server role in HC panel under Configuration >> Server Manager >> Server >> Edit >> Save & Edit Roles at GlobalAdmin/GlobalSubAdmin user. Please see below screenshot for clarity:
If this Root OU path is not correctly mentioned against an Exchange Organization in HC database then error "Error: Hosted Organization does not exist." is thrown in HC panel.
Resolution : Copy Root Organizational Unit OU path from HC panel by navigating to : Configuration >> Server Manager >> Server >> Edit >> Save & Edit Roles under GlobalAdmin/GlobalSubAdmin user and specify it in tblOrganizationRoles against the column "Path" for the concerned Exchange Organization.