When using LDAP filters to manage user membership within mailbox collections, after updating the intended Active Directory attribute to move a user or users into their new collection, they are never displayed within the statistics section of the new collection.
However when previewing the user membership of the source and destination collections, they appear correctly. As well, when reviewing the Migration Agent for Exchange logs it will appear that the users are still being processed by the agent handling the collection they were intended to be moved from.
The following error will also be present within the Migration Agent for Exchange log for the collection the users were being moved from:
Error System.Data.SqlClient.SqlException: Cannot insert the value NULL into column 'ALIAS', table 'DATABASENAME.dbo.MAILBOX'; column does not allow nulls. INSERT fails.
This issue is actually encountered when the problematic user or users are added to the initial collection, but the symptoms described are not observed until attempting to move users out of the collection.
The cause of this is when a user is added to a collection but is missing the "mailNickname" attribute, which is known to the agent and stored in the SQL database as the "ALIAS" value. When the Migration Agent for Exchange retrieves these specific attributes from Active Directory and this attribute does not contain any value, the action to store this data with SQL fails due to the dbo.MAILBOX table not allowing NULL values.
This subsequently causes the process to mark the user as "to be removed" from this collection to fail, and will also prevent the process from moving any users from the impacted collection.
To resolve this issue, the user that is causing the failure will need to be identified firstly. This can be done by reviewing the Migration Agent for Exchange log that corresponds to the collection the users were attempted to be moved from.
Once the SQL Exception error log line (identified in the description section of this article) is found, just above this error you will see the following actions taking place:
LdapHelper::FindOne. LDAP query: searchBase (The LDAP filter appearing to the left will contain environment specific information, as well as user specific information)
Exec SQL: ADD_MAILBOX2 @NAME = 'user displayName'
Once the user is successfully identified there are two actions that can be taken to resolve the issue:
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center