Unable to Add in Secondary Delivery Controller if Mirror Database is Configured with Custom Port

Unable to Add in Secondary Delivery Controller if Mirror Database is Configured with Custom Port

book

Article ID: CTX218189

calendar_today

Updated On:

Description

XenApp 7.9 incident – unable to add in the secondary delivery controller if mirror database is configured with a custom port.

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Resolution

Resolution for the two causes:

  1. On 2nd DDC, make sure the db connection strings are null and delete the studio cache file.
  2. Break the mirror.
  3. Add the controller and check.
  4. Recreate the mirror.

Or

Use the workaround in the cause section (has not been tested in this case):

Changed the way we are creating the keys under: 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo] 
and [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo]

Example: It needs to have an entry like:

"mirror.domain.com\\InstanceName"="DBMSSOCN,mirror.domain.com,11850"

Problem Cause

Cause of the first issue:

The database connection strings were set to the old deleted environment.

Second cause:

From CDF traces, Error Id: XDDS:C030812D and The mirror database cannot be contacted.
There were 2 possible causes (either permission issue or using a custom port for db).

Powered by Wolken Software