Security Compliance

Problem creating users with the Exchange connection in ARM

This article describes how to mitigate a problem with a mailbox creation that fails after the creation of the user in AD with a customized template in ARM.

First published date

8/30/2021 10:31 AM

Last published date

2/26/2025 3:23 AM

Overview

  • It can happen that the user in AD gets created but not the related mailbox in exchange.
  • The following error messages may come up in the logs in pnJob.log and armServer.log respectively.
Referenced Exchange objects not found. Either the object does not exist, the object is of wrong type(i.e. not mail enabled) or the given account can not access the object.
 |libPowerShellConnec….PowerShellDataReady|210823|12:38:45.920|Error      ] PowerShellDataReady.ErrorDataReady(Object sender, DataAddedEventArgs e): Error while executing (MailboxEnableLogic):
Couldn't find database "MDB3". Make sure you have typed it correctly.
CategoryInfo: NotSpecified: (:) [Enable-Mailbox], ManagementObjectNotFoundException

 

Product section

Access Rights Manager

Cause

  • The Exchange database specified in the customized template could not be found in Exchange.
  • Maybe the database is not mounted or the list in the template is not updated.
  • It can be also that different customized settings in the Exchange Module of the template can cause this problem by conflicting with the Exchange configuration.

Resolution

  • Try to use the standard Exchange module in the Create New User template as shown in the article below. If it works fine please check the customized sections. An idea of what the problem can be is listed below.
  • https://documentation.solarwinds.com/en/success_center/arm/content/create-an-exchange-mailbox.htm
  • Remove the related code section from the template as described below, so that Exchange chooses a database automatically, or update the list with the available databases.
image.png