Exchange 2016 CU 23 Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '2147950639' and message

Question

Exchange 2016 CU 23 Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '2147950639' and message

Rafael Carvalho 61

Dear friends, I am going through an unusual situation. I'm trying to perform a migration from Exchange Server 2010 SP3 CU32 to Exchange Server 2016 CU 23, but when installing Mailbox role: Transport service the same error is always displayed.

"The following error was generated when "$error.Clear();
install-ExsetdataAtom -AtomName SMTP -DomainController
$RoleDomainController

" was run: "Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with
error code '2147950639' and message 'A constraint violation occurred.'.
at
Microsoft.Exchange.Configuration.Tasks.Task.ThrowTerminatingError(Exception exception, ErrorCategory category, Object
target)
at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.HandleExsetdataReturnCode(UInt32 scErr)
at
Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.InstallAtom(AtomID atomID)
at
Microsoft.Exchange.Management.Deployment.InstallExsetdataAtom.InternalProcessRecord()
at
Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at
Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean
terminatePipelineIfFailed)"."

Has anyone gone through this?
I've already checked in several forums about this error (1002) but the answer is always the same, excluding the server through ADSI, but unfortunately not even excluding it does not solve it.

Thanks!

Jame Xu-MSFT 4,191 Reputation points

2022-06-16T05:54:26.27+00:00

Hi @Rafael Carvalho ,
I searched the documents migrated from exchange2010 to exchange2016. You can check whether there is a problem with the steps :
https://www.kerneldatarecovery.com/blog/step-by-step-guide-for-migrating-exchange-server-2010-to-2016-part-1/
Microsoft provides third-party contact information to help you find additional information about this topic. This contact information may change without notice. Microsoft does not guarantee the accuracy of third-party contact information.

You can check if you are using a supported Server operating system :
https://learn.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019

You can check the error information in the exchange installation log and provide it to us for subsequent analysis.
( The Exchange Setup log is available at <system drive>:\ExchangeSetupLogs\ExchangeSetup.log )
Michel de Rooij 1,546 Reputation points MVP

2022-06-16T09:37:05.097+00:00

Did you actually read the question, JameXu?
To me, "constraint violation occurred" could indicate Active Directory blocking some operation. The account used has proper permissions and is able to write
in the cn=configuration,dc=contoso,dc=com namespace (that is, no ACLs configured)
You are not installing Exchange on a domain controller or something?
Any pointers in the operations shortly before this message in the Exchange Setup log?
Rafael Carvalho 61 Reputation points

2022-06-16T10:47:26.113+00:00

Hi @Michel de Rooij ,

Thank you for your help.
Well that's my suspicion as we had a problem adding a new W2k16 domain controller and the security folks struggled a lot. However, when checking the registry in ADSI it is possible to see the entry referring to the server in configuration. In fact, it's a problem that I've been facing for a few days now and pulling my hair out (laughs). The user is a Domain Admins, Enterprise and Schema Admins, but as I know that they changed the AD permissions structure or even a GPO, I don't have an exact direction to "point the finger" where the problem actually occurs. Even so, my suspicion is linked to some non-inherited permission in AD.
Rafael Carvalho 61 Reputation points

2022-06-16T10:48:31.62+00:00

Hi @Jame Xu-MSFT ,

Thank you for your help. I'm going to read this article
again and see what I might have gotten, but I double-checked it. But you will know, right? I don't have access to the log at the moment, because here in Brazil it's a holiday, but tomorrow I'll send it to you. Thank you so much again.
Jame Xu-MSFT 4,191 Reputation points

2022-06-24T06:35:29.727+00:00

Hello, let me ask if your question has progressed, has there been a reply from the AD side?
Rafael Carvalho 61 Reputation points

2022-06-28T18:41:54.723+00:00

Sorry @Jame Xu-MSFT , I didn't quite understand your question. If so, what else do I need to check to get more help?
Jame Xu-MSFT 4,191 Reputation points

2022-06-29T09:12:57.937+00:00

Hi @Rafael Carvalho ,
Did you say to have your customers check for AD issues first? I wonder if the problem with AD is now resolved, or if the problem is still the error message you mentioned earlier “An error occurred with error code '2147950639' and message ” ? If you have solved the problem of Exchange, you can share it here to help more people, if your issue with Exchange has not been solved, you can also continue to leave a message here, I will do my best to help you solve the problem.
Rafael Carvalho 61 Reputation points

2022-06-29T11:10:45.223+00:00

Unfortunately no, I'm trying to support MS as no method actually causes the installation to continue. As I'm not sure what it is in AD, it was complicated to pass this to the client.
Jame Xu-MSFT 4,191 Reputation points

2022-07-04T09:17:16.317+00:00

Hi @Rafael Carvalho ,
You said before that there is a problem with AD that causes problems with exchange migration, since we are Exchange's forum, only focus on solving Exchange problems, so it is recommended that you check AD first to see if it is normal. Wait until you've determined that there's no problem with AD, then deal with the issue of Exchange migration. you can refer to this link:
http://woshub.com/check-active-directory-health-and-replication/#:~:text=Dcdiag%20is%20a%20basic%20built-in%
Microsoft provides third-party contact information to help you find additional information about this topic. This contact information may change without notice. Microsoft does not guarantee the accuracy of third-party contact information.
Rafael Carvalho 61 Reputation points

2022-07-04T12:17:22.113+00:00

Hi @Jame Xu-MSFT ,
I'm dealing with this issue with support and as soon as I get it resolved I'll report here. Thanks.
Rafael Carvalho 61 Reputation points

2022-07-27T18:31:43.037+00:00

@Jame Xu-MSFT

Well, I got it with the help of Microsoft advanced support and the attribute that was generating the installation error was found, follow the excerpt below.
"msExchAuthenticationFlags" that did not have the correct value to finish the Exchange Server installation, the value was set to "6" and the default setting should be left without value.
Thank you.

2 answers

Your answer

Jame Xu-MSFT 4,191 Reputation points

2022-06-16T05:54:26.27+00:00

Hi @Rafael Carvalho ,
I searched the documents migrated from exchange2010 to exchange2016. You can check whether there is a problem with the steps :
https://www.kerneldatarecovery.com/blog/step-by-step-guide-for-migrating-exchange-server-2010-to-2016-part-1/
Microsoft provides third-party contact information to help you find additional information about this topic. This contact information may change without notice. Microsoft does not guarantee the accuracy of third-party contact information.

You can check if you are using a supported Server operating system :
https://learn.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019

You can check the error information in the exchange installation log and provide it to us for subsequent analysis.
( The Exchange Setup log is available at <system drive>:\ExchangeSetupLogs\ExchangeSetup.log )
Michel de Rooij 1,546 Reputation points MVP

2022-06-16T09:37:05.097+00:00

Did you actually read the question, JameXu?
To me, "constraint violation occurred" could indicate Active Directory blocking some operation. The account used has proper permissions and is able to write
in the cn=configuration,dc=contoso,dc=com namespace (that is, no ACLs configured)
You are not installing Exchange on a domain controller or something?
Any pointers in the operations shortly before this message in the Exchange Setup log?
Rafael Carvalho 61 Reputation points

2022-06-16T10:47:26.113+00:00

Hi @Michel de Rooij ,

Thank you for your help.
Well that's my suspicion as we had a problem adding a new W2k16 domain controller and the security folks struggled a lot. However, when checking the registry in ADSI it is possible to see the entry referring to the server in configuration. In fact, it's a problem that I've been facing for a few days now and pulling my hair out (laughs). The user is a Domain Admins, Enterprise and Schema Admins, but as I know that they changed the AD permissions structure or even a GPO, I don't have an exact direction to "point the finger" where the problem actually occurs. Even so, my suspicion is linked to some non-inherited permission in AD.
Rafael Carvalho 61 Reputation points

2022-06-16T10:48:31.62+00:00

Hi @Jame Xu-MSFT ,

Thank you for your help. I'm going to read this article
again and see what I might have gotten, but I double-checked it. But you will know, right? I don't have access to the log at the moment, because here in Brazil it's a holiday, but tomorrow I'll send it to you. Thank you so much again.
Jame Xu-MSFT 4,191 Reputation points

2022-06-24T06:35:29.727+00:00

Hello, let me ask if your question has progressed, has there been a reply from the AD side?
Rafael Carvalho 61 Reputation points

2022-06-28T18:41:54.723+00:00

Sorry @Jame Xu-MSFT , I didn't quite understand your question. If so, what else do I need to check to get more help?
Jame Xu-MSFT 4,191 Reputation points

2022-06-29T09:12:57.937+00:00

Hi @Rafael Carvalho ,
Did you say to have your customers check for AD issues first? I wonder if the problem with AD is now resolved, or if the problem is still the error message you mentioned earlier “An error occurred with error code '2147950639' and message ” ? If you have solved the problem of Exchange, you can share it here to help more people, if your issue with Exchange has not been solved, you can also continue to leave a message here, I will do my best to help you solve the problem.
Rafael Carvalho 61 Reputation points

2022-06-29T11:10:45.223+00:00

Unfortunately no, I'm trying to support MS as no method actually causes the installation to continue. As I'm not sure what it is in AD, it was complicated to pass this to the client.
Jame Xu-MSFT 4,191 Reputation points

2022-07-04T09:17:16.317+00:00

Hi @Rafael Carvalho ,
You said before that there is a problem with AD that causes problems with exchange migration, since we are Exchange's forum, only focus on solving Exchange problems, so it is recommended that you check AD first to see if it is normal. Wait until you've determined that there's no problem with AD, then deal with the issue of Exchange migration. you can refer to this link:
http://woshub.com/check-active-directory-health-and-replication/#:~:text=Dcdiag%20is%20a%20basic%20built-in%
Microsoft provides third-party contact information to help you find additional information about this topic. This contact information may change without notice. Microsoft does not guarantee the accuracy of third-party contact information.
Rafael Carvalho 61 Reputation points

2022-07-04T12:17:22.113+00:00

Hi @Jame Xu-MSFT ,
I'm dealing with this issue with support and as soon as I get it resolved I'll report here. Thanks.
Rafael Carvalho 61 Reputation points

2022-07-27T18:31:43.037+00:00

@Jame Xu-MSFT

Well, I got it with the help of Microsoft advanced support and the attribute that was generating the installation error was found, follow the excerpt below.
"msExchAuthenticationFlags" that did not have the correct value to finish the Exchange Server installation, the value was set to "6" and the default setting should be left without value.
Thank you.

Answer 1

Hi @Rafael Carvalho ,
I searched the documents migrated from exchange2010 to exchange2016. You can check whether there is a problem with the steps :
https://www.kerneldatarecovery.com/blog/step-by-step-guide-for-migrating-exchange-server-2010-to-2016-part-1/
Microsoft provides third-party contact information to help you find additional information about this topic. This contact information may change without notice. Microsoft does not guarantee the accuracy of third-party contact information.

You can check if you are using a supported Server operating system :
https://learn.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019

You can check the error information in the exchange installation log and provide it to us for subsequent analysis.
( The Exchange Setup log is available at <system drive>:\ExchangeSetupLogs\ExchangeSetup.log )

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in [our documentation][11] to enable e-mail notifications if you want to receive the related email notification for this thread.

[11]: https://learn.microsoft.com/en-us/answers/articles/67444/email-notifications.html

Email notifications on Microsoft Q&A
How to setup and utilize email notifications on Microsoft Q&A.

Rafael Carvalho 61 Reputation points

2022-06-17T12:53:16.387+00:00

Hi @Jame Xu-MSFT ,

Follow the logs as requested. I also added the Exchange evtx where it points out the error in the attempt to execute the PowerShell script, the log with _old is the log since the beginning of the installation (very extensive by the way) and the .log which is a new one that only contains this new attempt of today.
I want to thank you in advance for your help.

EQGqptQVT5RLmHLWtCE_pDsBhQltkL9sMgQLD1FBbVlfLg

Answer 2

I found these logs in the event viewer.

Install-BridgeheadRole
-DomainController "AGUASCLARAS.sefaz.net" -UpdatesDir $null -LanguagePacksPath "F:\" -StartTransportService "True" -DisableAMFiltering "False"
sefaz.net/Users/AdmExch
Local-Exchange Management Console-Unknown
2504 ExSetupUI.exe
72
00:00:00.8437536
View Entire Forest: 'True', Configuration Domain Controller: 'AGUASCLARAS.sefaz.net', Preferred Global Catalog: 'AGUASCLARAS.sefaz.net', Preferred Domain Controllers: '{ AGUASCLARAS.sefaz.net }'
Microsoft.Exchange.Management.Deployment.ScriptExecutionException: The following error was generated when "$error.Clear();
install-ExsetdataAtom -AtomName SMTP -DomainController $RoleDomainController

" was run: "Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '2147950639' and message 'A constraint violation occurred.'.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowTerminatingError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.HandleExsetdataReturnCode(UInt32 scErr)
at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.InstallAtom(AtomID atomID)
at Microsoft.Exchange.Management.Deployment.InstallExsetdataAtom.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)". ---> Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '2147950639' and message 'A constraint violation occurred.'.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowTerminatingError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.HandleExsetdataReturnCode(UInt32 scErr)
at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.InstallAtom(AtomID atomID)
at Microsoft.Exchange.Management.Deployment.InstallExsetdataAtom.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
--- End of inner exception stack trace ---
0
Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '2147950639' and message 'A constraint violation occurred.'.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowTerminatingError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.HandleExsetdataReturnCode(UInt32 scErr)
at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.InstallAtom(AtomID atomID)
at Microsoft.Exchange.Management.Deployment.InstallExsetdataAtom.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
Ex88D115
False
0 objects execution has been proxied to remote server.
0
ActivityId: 3aef2807-1357-482e-97f4-812c5d7b21d4
en-US

Install-ExsetdataAtom
-AtomName "SMTP" -DomainController "AGUASCLARAS.sefaz.net"
sefaz.net/Users/AdmExch
Local-Exchange Management Console-Unknown
2504 ExSetupUI.exe
66
00:00:00
View Entire Forest: 'True', Configuration Domain Controller: 'AGUASCLARAS.sefaz.net', Preferred Global Catalog: 'AGUASCLARAS.sefaz.net', Preferred Domain Controllers: '{ AGUASCLARAS.sefaz.net }'
Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '2147950639' and message 'A constraint violation occurred.'.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowTerminatingError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.HandleExsetdataReturnCode(UInt32 scErr)
at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.InstallAtom(AtomID atomID)
at Microsoft.Exchange.Management.Deployment.InstallExsetdataAtom.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
0
Ex5BE347
False
0 objects execution has been proxied to remote server.
0
ActivityId: 3aef2807-1357-482e-97f4-812c5d7b21d4
en-US

Jame Xu-MSFT 4,191 Reputation points

2022-06-21T09:48:35.923+00:00

Hi @Rafael Carvalho ,
From the information you provided, has the problem you encountered during AD installation been solved? Because the installation of Exchange is based on AD, the problems in the installation of Exchange may also be caused by problems in AD, and the relevant information I found points to AD. This is a forum for exchange that focuses on solving exchange related problems. You can post a new thread with AD related tag ( windows-active directory ) to check if there is a problem with AD. If there is no problem with AD, then solve the exchange related problems.
Rafael Carvalho 61 Reputation points

2022-06-21T10:05:09.127+00:00

It is precisely at this point that I want to get to, have a reference or base turned to AD and pass it on to the customer, today he insisted that there are no more problems, but I know that Exchange is 100% dependent and if something is not right in AD the installation do not pass.
He hired me to install Exchange and he already wants me to solve the problems with AD which is not part of my scope, I already have a clear reference, I already pass the ball to him again hahah

Share via

Exchange 2016 CU 23 Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '2147950639' and message

2 answers

Your answer