Forum Discussion
glenhenderson
Aug 08, 2023Copper Contributor
Upgrading to Exchange 2019 from 2010 through 2013 and 2016
Hi All,
We have been facing issues with our exchange server deployment, it is based in an entirely online mode other than assigning remote mailboxes to users. To continue assigning mailboxes we were going to try upgrade through the versions to 2019, install exchange remote management tools and shut it down. In this upgrade process we got this error on our exchange 2013 hop server:
Error:
The following error was generated when "$error.Clear();
$arbMbxname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
$arbMbxLastName = "MsExchDiscoveryMailbox D919BA05-46A6-415f-80AD-7E09334BB852";
$arbUser = @(Get-User -Filter {LastName -eq $arbMbxLastName} -IgnoreDefaultScope -ResultSize 1);
if ($arbUser.Length -eq 0)
{
Install-UserAccount -Name $arbMbxname -LastName $arbMbxLastName;
}
" was run: "Microsoft.Exchange.Data.Directory.ADConstraintViolationException: An Active Directory Constraint Violation error occurred on (our domain controller). Additional information: The operation failed because UPN value provided for addition/modification is not unique forest-wide.
Active directory response: 000021C8: AtrErr: DSID-03200BE8, #1:
0: 000021C8: DSID-03200BE8, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 90290 (userPrincipalName)
---> System.DirectoryServices.Protocols.DirectoryOperationException: A value in the request is invalid.
at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
at Microsoft.Exchange.Management.Deployment.InstallUserAccount.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Please help i have googled parts of this error and it comes back with minimal results,
Thank you,
Glen H
- Try running the following command in Exchange Server 2013 Management Shell!
Get-MailBox -arbitation- glenhendersonCopper ContributorHi Tae,
Thank you for the help, the error i get is when installing the 2013 management tools, as such i cant enter commands in unless they're for the 2010 management tools,
Thank youIdentify the specific UPN value that is causing the conflict.
Check the existing user accounts in your Active Directory forest to see if any other user already has that UPN value.
If you find a duplicate UPN, you will need to modify one of the accounts to have a different UPN that is unique.