unable to add additional delivery controller in existing site

[shrikant padole]

Unable to add 2nd controller to the site with error "Error Id: XDDS:1FA8BEDF" failed to update database.

[Benjamin Bartels]

This has many possible causes.  This may not be easy to troubleshoot via this thread, but we can run some basic checks.

Follow the steps here to troubleshoot and verify the site is properly prepared for the addition of the second controller. 

 

1. Backup all site databases. (hopefully you also have a backup of the database from a time prior to the addition of DDC2)
2. Verify all the normal SQL Windows services are running on the SQL server. These will typically all be set to a start-up type of automatic.
3. Use SQL mgmt studio to check for logon or permissions errors in the SQL maintenance Logs. The user who's is logged into windows during controller addition workflow must be able to perform some admin level actions on the SQL server. See: https://support.citrix.com/article/CTX127998.
4. If that is not possible in your environment, you must use the generate scripts option and provide the scripts to your SQL DB admin to run against the database in SQL CMD mode. https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/manage-deployment/delivery-controllers.html
5. If there are no errors and you have verified the admin has the proper permissions go to next step .
6. Log into the good controller as the admin with SQL database admin rights. Usually the admin account that created the CVAD site initially will work. 
7. Launch PowerShell as admin from the good controller and run the following commands: 

asnp citrix*

get-broker controller

1. Verify that only one controller is listed and it has a status of Active.
2. If the second controller is listed, then you will have to evict the 2nd controller.
3. If Studio is working, go to the Controllers node and remove the bad controller. 
4. If this fails then we have a bigger problem and you may have to evict using the script here:
   1. https://support.citrix.com/article/CTX139505
5. Once the controller is evicted you can run the site health checks from Studio on the good controller. 
6. Studio has built in site tests that will identify any major issues with the site health. 
7. Also, run thru the commands here and see if any errors occur. https://support.citrix.com/article/CTX238581
8. Take note of the results of these commands. 

 

You should now have a good idea of the overall health of the environment and maybe some more clues as to the cause of the failure. 

 

There are some mitigation options as well.

 

You can revert to a database backup prior to the controller add workflow.

Armed with the evidence you have uncovered, you may be able to re-add the controller after the site heath is restored.

You may have to generate the scripts for the SQL DB admin to add the controller. 

 

Hope this helps.

 

 

 

 

 

[shrikant padole]

On 19/8/2019 at 8:49 PM, Benjamin Bartels said:

This has many possible causes.  This may not be easy to troubleshoot via this thread, but we can run some basic checks.

Follow the steps here to troubleshoot and verify the site is properly prepared for the addition of the second controller. 

 

1. Backup all site databases. (hopefully you also have a backup of the database from a time prior to the addition of DDC2)
2. Verify all the normal SQL Windows services are running on the SQL server. These will typically all be set to a start-up type of automatic.
3. Use SQL mgmt studio to check for logon or permissions errors in the SQL maintenance Logs. The user who's is logged into windows during controller addition workflow must be able to perform some admin level actions on the SQL server. See: https://support.citrix.com/article/CTX127998.
4. If that is not possible in your environment, you must use the generate scripts option and provide the scripts to your SQL DB admin to run against the database in SQL CMD mode. https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/manage-deployment/delivery-controllers.html
5. If there are no errors and you have verified the admin has the proper permissions go to next step .
6. Log into the good controller as the admin with SQL database admin rights. Usually the admin account that created the CVAD site initially will work. 
7. Launch PowerShell as admin from the good controller and run the following commands: 

asnp citrix*

get-broker controller

1. Verify that only one controller is listed and it has a status of Active.
2. If the second controller is listed, then you will have to evict the 2nd controller.
3. If Studio is working, go to the Controllers node and remove the bad controller. 
4. If this fails then we have a bigger problem and you may have to evict using the script here:
   1. https://support.citrix.com/article/CTX139505
5. Once the controller is evicted you can run the site health checks from Studio on the good controller. 
6. Studio has built in site tests that will identify any major issues with the site health. 
7. Also, run thru the commands here and see if any errors occur. https://support.citrix.com/article/CTX238581
8. Take note of the results of these commands. 

 

You should now have a good idea of the overall health of the environment and maybe some more clues as to the cause of the failure. 

 

There are some mitigation options as well.

 

You can revert to a database backup prior to the controller add workflow.

Armed with the evidence you have uncovered, you may be able to re-add the controller after the site heath is restored.

You may have to generate the scripts for the SQL DB admin to add the controller. 

 

Hope this helps.

 

 

 

 

 

I have removed the orphaned DC from site successfully.

But same error occurs again while adding second DC. I observed that this DC is my active node of SQL cluster and hence it was added hostname account entry in SQL security login.

 

Now I have prepared DC server on separate new server and added this into existing site successfully..

 

Thanks to all for you valuable supports.