locked
Failed to Publish Lync 2013 Topology with Error - ClusterFqdnChange: A pool fully qualified domain name (FQDN) cannot be changed once set. RRS feed

  • Question

  • Hi,

    Previously i successful setup a Lync 2013 standard edition but due to management wants to have HA, so i uninstall all and install Lync 2013 enterprise edition.

    That my headache happen. I've tried to setup in server 01 (same server with standard edition) but facing many issue when i wants to deploy the topology. Then i get another advise to setup at another new server.

    I setup new server named as 02. After everything configured in topology builder, when i want to publish, it failed with message below. Is anyone can help me over come this issue? Million thanks!

    Action Action Information Time Logged Execution Result
    Publish-CsTopology Failed
    Connection: Data Source=lynprddbs01.astro.net;Initial Catalog=xds;Integrated Security=True 7/2/2013 11:18:34 PM
    Backup filename: C:\Users\hpadmin\AppData\Local\Temp\2\Publish-CsTopology-Backup-ddbead10-27ce-4ae7-97f9-0b3a2efe5988.xml 7/2/2013 11:18:34 PM
    PublishTopologyCmdlet.PublishTopologyDocument 7/2/2013 11:18:34 PM Failed
    Publish Topology 7/2/2013 11:18:36 PM Failed
    Validate XML Schema 7/2/2013 11:18:36 PM Success
    Result: Validation was successful. 7/2/2013 11:18:36 PM
    Validate New Topology 7/2/2013 11:18:36 PM Success
    Result: Validation was successful. 7/2/2013 11:18:36 PM
    Validate Central Management Store Location 7/2/2013 11:18:36 PM Success
    ObjectDn: CN=4e64f98c-3715-45db-962c-99b41e1d4d5e,CN=Topology Settings,CN=RTC Service,CN=Services,CN=Configuration,DC=astro,DC=net 7/2/2013 11:18:36 PM
    ExistingObject: Central Management store location object set to back-end database "lynprddbs01.astro.net". 7/2/2013 11:18:36 PM
    ExistingObject: Central Management store located on pool 'lynprddbs01.astro.net', instance ''. 7/2/2013 11:18:36 PM
    Action 7/2/2013 11:18:36 PM Success
    Result: Cluster ID is validated successfully against current deployment. 7/2/2013 11:18:36 PM
    Check Orphaned Users 7/2/2013 11:18:36 PM Success
    Result: No users or application contacts are assigned to the "0" retired service assignment tag IDs. 7/2/2013 11:18:36 PM
    Check Orphaned Analog Devices 7/2/2013 11:18:36 PM Success
    Result: No analog devices are assigned to the "0" retired service assignment tag IDs. 7/2/2013 11:18:36 PM
    Check Trusted Application Pools 7/2/2013 11:18:36 PM Success
    Result: No Registrar dependencies where changed for any application servers or external servers. 7/2/2013 11:18:36 PM
    Check Orphaned Users 7/2/2013 11:18:36 PM Success
    Result: No users or application contacts are assigned to the "0" retired service assignment tag IDs. 7/2/2013 11:18:36 PM
    Check Orphaned Conferences 7/2/2013 11:18:36 PM Success
    Result: No conferences are scheduled on the "0" instances of "UserServices" services removed. 7/2/2013 11:18:36 PM
    Check Edge Settings Inconsistency 7/2/2013 11:18:36 PM Success
    Result: No edge settings inconsistency found. 7/2/2013 11:18:36 PM
    Check Service dependent settings 7/2/2013 11:18:36 PM Success
    Check Site dependent settings 7/2/2013 11:18:36 PM Success
    Result: Network configuration depends on a site that is being removed. 7/2/2013 11:18:36 PM
    Check Machines Not Moved 7/2/2013 11:18:36 PM Success
    Check that Machines Exist 7/2/2013 11:18:36 PM Success
    Service Version Check 7/2/2013 11:18:36 PM Success
    Check Cluster FQDNs Not Changed 7/2/2013 11:18:36 PM Failed
    ClusterFqdnChange: A pool fully qualified domain name (FQDN) cannot be changed once set. 7/2/2013 11:18:36 PM Error
    ClusterFqdnChange: Cluster "1:1" updated FQDN from "lynprdweb01.astro.net" to "pool1.astro.net". 7/2/2013 11:18:36 PM
    ClusterFqdnChangeResolution: Remove the pool and recreate it with a new fully qualified domain name (FQDN). 7/2/2013 11:18:36 PM
    Error: Changing the FQDN of a cluster is not permitted. You must remove and add in separate steps.
    Type: DeploymentException
    Stack Trace
    at Microsoft.Rtc.Management.Deployment.Tasks.CheckClusterFqdnTask.Action()
    at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog(Action action)
    7/2/2013 11:18:36 PM Error
    Error: An error occurred: "Microsoft.Rtc.Management.Deployment.DeploymentException" "Changing the FQDN of a cluster is not permitted. You must remove and add in separate steps." 7/2/2013 11:18:36 PM Error

    Wednesday, July 3, 2013 8:48 AM

Answers

All replies

  • Hi,

    It looks like some remnants from SE install still exists in AD. My advise would be to uninstall Lync 2013 as well - how ever far you have reached. Then to go through ADSIedit and cmdlets to make sure that all references are deleted and then start the Lync 2013 deployment again.

    The following blog might help - http://blog.ucmadeeasy.com/2010/11/09/lync-server-2010-active-directory-references-and-how-to-remove-them/


    Murali Krishnan| My blogs: UnifiedMe | Twitter: @Mkris9

    • Proposed as answer by Kent-Huang Thursday, July 4, 2013 6:04 AM
    • Marked as answer by Kent-Huang Tuesday, July 23, 2013 4:47 AM
    Wednesday, July 3, 2013 2:35 PM
  • Hi,
    You need to remove all references for the old server 01 in AD.

    Kent Huang
    TechNet Community Support

    Thursday, July 4, 2013 6:04 AM
  • Hi Murali,

    I didn't found the RTC in ADSI, so i suspect DB server holding the previous instance? I decide to uninstall the SQL and install a fresh SQL. Wish me good luck and will keep the update here, Thx!

    Friday, July 5, 2013 3:37 AM
  • I found new error as below.

    Lync Server 2013 Deployment Log Collapse All Actions
    Action Action Information Time Logged Execution Result
    Publish-CsTopology Failed
    Connection: Data Source=lynprddbs01.xxx.net;Initial Catalog=xds;Integrated Security=True 7/5/2013 3:52:59 PM
    Backup filename: C:\Users\hpadmin\AppData\Local\Temp\2\Publish-CsTopology-Backup-c6f816d7-3b83-4cb3-82cc-09bbc060ca31.xml 7/5/2013 3:52:59 PM
    PublishTopologyCmdlet.PublishTopologyDocument 7/5/2013 3:52:59 PM Failed
    Publish Topology 7/5/2013 3:53:01 PM Failed
    Validate XML Schema 7/5/2013 3:53:01 PM Success
    Result: Validation was successful. 7/5/2013 3:53:01 PM
    Validate New Topology 7/5/2013 3:53:01 PM Success
    Result: Validation was successful. 7/5/2013 3:53:01 PM
    Validate Central Management Store Location 7/5/2013 3:53:01 PM Success
    ObjectDn: CN=4e64f98c-3715-45db-962c-99b41e1d4d5e,CN=Topology Settings,CN=RTC Service,CN=Services,CN=Configuration,DC=astro,DC=net 7/5/2013 3:53:01 PM
    ExistingObject: Central Management store location object set to back-end database "lynprddbs01.astro.net". 7/5/2013 3:53:01 PM
    ExistingObject: Central Management store located on pool 'lynprddbs01.astro.net', instance ''. 7/5/2013 3:53:01 PM
    Action 7/5/2013 3:53:01 PM Success
    Result: Cluster ID is validated successfully against current deployment. 7/5/2013 3:53:01 PM
    Check Orphaned Users 7/5/2013 3:53:01 PM Success
    Result: No users or application contacts are assigned to the "0" retired service assignment tag IDs. 7/5/2013 3:53:01 PM
    Check Orphaned Analog Devices 7/5/2013 3:53:01 PM Success
    Result: No analog devices are assigned to the "0" retired service assignment tag IDs. 7/5/2013 3:53:01 PM
    Check Trusted Application Pools 7/5/2013 3:53:01 PM Success
    Result: No Registrar dependencies where changed for any application servers or external servers. 7/5/2013 3:53:01 PM
    Check Orphaned Users 7/5/2013 3:53:01 PM Success
    Result: No users or application contacts are assigned to the "0" retired service assignment tag IDs. 7/5/2013 3:53:01 PM
    Check Orphaned Conferences 7/5/2013 3:53:01 PM Success
    Result: No conferences are scheduled on the "0" instances of "UserServices" services removed. 7/5/2013 3:53:01 PM
    Check Edge Settings Inconsistency 7/5/2013 3:53:01 PM Success
    Result: No edge settings inconsistency found. 7/5/2013 3:53:01 PM
    Check Service dependent settings 7/5/2013 3:53:01 PM Success
    Check Site dependent settings 7/5/2013 3:53:01 PM Success
    Result: Network configuration depends on a site that is being removed. 7/5/2013 3:53:01 PM
    Check Machines Not Moved 7/5/2013 3:53:01 PM Success
    Check that Machines Exist 7/5/2013 3:53:01 PM Success
    Service Version Check 7/5/2013 3:53:02 PM Success
    Check Cluster FQDNs Not Changed 7/5/2013 3:53:02 PM Failed
    ClusterFqdnChange: A pool fully qualified domain name (FQDN) cannot be changed once set. 7/5/2013 3:53:02 PM Error
    ClusterFqdnChange: Cluster "1:1" updated FQDN from "lynprdweb01.astro.net" to "pool1.astro.net". 7/5/2013 3:53:02 PM
    ClusterFqdnChangeResolution: Remove the pool and recreate it with a new fully qualified domain name (FQDN). 7/5/2013 3:53:02 PM
    Error: Changing the FQDN of a cluster is not permitted. You must remove and add in separate steps.
    Type: DeploymentException
    Stack Trace
    at Microsoft.Rtc.Management.Deployment.Tasks.CheckClusterFqdnTask.Action()
    at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog(Action action)
    7/5/2013 3:53:02 PM Error
    Error: An error occurred: "Microsoft.Rtc.Management.Deployment.DeploymentException" "Changing the FQDN of a cluster is not permitted. You must remove and add in separate steps." 7/5/2013 3:53:02 PM Error

    Friday, July 5, 2013 7:55 AM
  • hi, is the above error after a fresh SQL back end re-install ?

    It shows that you can't change pool FQDN from  "lynprdweb01.astro.net" to "pool1.astro.net". Hence there are still remnants from the previous installation. The below from TechNet might help.

    You can use ADSIEdit to see the current state of the definition for the Central Management store in Active Directory Domain Services (AD DS). The location of the SCP is in the Configuration container, under the distinguished name (DN) CN=Topology Settings, CN=RTC Service, DC=<your domain>. Under CN=Topology Settings is an object named with a globally unique ID of the class msRTCSIP-GlobalTopologySetting. Right-click the GUID and then click Properties. The Central Management Server is defined in the attribute named msRTCSIP-BackEndServer in the format of fully qualified domain name (FQDN) of the SQL Server, and the instance (for example, sqlbe.contoso.net\rtc).

    If you find any msRTCSIP -please remove it prior to commencing the new installation.


    Murali Krishnan| My blogs: UnifiedMe | Twitter: @Mkris9

    Friday, July 5, 2013 12:37 PM
  • Also you may delete the previous sip pool from configuration store by ADSI edit (ADSI Edit\CN=Configuration,DC=domain,DC=com\CN=Services\CN=RTC Service\CN=Pools), then run Remove-CsConfigurationStoreLocation on Lync server.

    Murali Krishnan| My blogs: UnifiedMe | Twitter: @Mkris9

    Friday, July 5, 2013 12:39 PM
  • Hi Murali,

    I've removed the ADSI entry and run the Remove-CsConfigurationStoreLocation but seems the same error keep on appear.

    the entry in ADSI is been deleted some how the same error keep on appear.

    Check Cluster FQDNs Not Changed 7/8/2013 4:33:40 PM Failed
    ClusterFqdnChange: A pool fully qualified domain name (FQDN) cannot be changed once set. 7/8/2013 4:33:40 PM Error
    ClusterFqdnChange: Cluster "1:1" updated FQDN from "lynprdweb01.xxx.net" to "lynprdweb00.xxx.com.my". 7/8/2013 4:33:40 PM
    ClusterFqdnChangeResolution: Remove the pool and recreate it with a new fully qualified domain name (FQDN). 7/8/2013 4:33:40 PM
    Error: Changing the FQDN of a cluster is not permitted. You must remove and add in separate steps.
    Type: DeploymentException
    Stack Trace
    at Microsoft.Rtc.Management.Deployment.Tasks.CheckClusterFqdnTask.Action()
    at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog(Action action)
    7/8/2013 4:33:40 PM Error
    Error: An error occurred: "Microsoft.Rtc.Management.Deployment.DeploymentException" "Changing the FQDN of a cluster is not permitted. You must remove and add in separate steps." 7/8/2013 4:33:40 PM Error

    Monday, July 8, 2013 8:39 AM
  • Hi, that is strange. quick qn though - I can see that you are changing the server / pool names as well as the domain names (xxx.net to xxx.com.my) .

    Can you tell me what is Lyncprdweb01 and web00 and are the above said domains internal / external ?


    Murali Krishnan| My blogs: UnifiedMe | Twitter: @Mkris9

    Monday, July 8, 2013 11:05 AM
  • Hi Murali, both is internal.

    Monday, July 8, 2013 11:09 AM
  • Hi Kenny,

    Sorry for delayed response. Please try to use the FQDN of front end server as pool name instead of using pool1.astro.net.


    Kent Huang
    TechNet Community Support

    • Marked as answer by Kent-Huang Tuesday, July 23, 2013 4:47 AM
    Thursday, July 18, 2013 2:06 PM