locked
Cannot Move CMS or replicate RRS feed

  • Question

  • We were running an in place upgrade in our production environment from lync 2013 to SFB2015( performed the same in LAB on VM and it worked) published the topology and installed Skype on front end servers but now after moving users from Lync 2013 to SFB 2015 i was trying to move the CMS from Lync2013 to Skype and it wont move, it kept giving errors turned out the  FTA service was not started, after some digging and modifying the DB was able to start the FTA but the CMS and the  replication still failed.

    Invoke-CsManagementServerFailover -Restore -Verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: ([0] 2-BackupService-11:SourceCollection) [Invoke-CsManagementServerFailove
       r], Exception
        + FullyQualifiedErrorId : FutureServiceVersion,Microsoft.Rtc.Management.Deployment.MoveCms.FailoverCmsCmdlet
    Invoke-CsManagementServerFailover : ServiceId "CentralManagement:fepool02c.fad.com" is of RoleId "7",  where RoleId
    "7" is not defined.
    At line:1 char:1
    + Invoke-CsManagementServerFailover -Restore -Verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: ([0] 2-CentralMgmt-11:SourceCollection) [Invoke-CsManagementServerFailover]
       , Exception
        + FullyQualifiedErrorId : FutureServiceVersion,Microsoft.Rtc.Management.Deployment.MoveCms.FailoverCmsCmdlet
    Invoke-CsManagementServerFailover : ServiceId "CentralManagementDatabase:m3-lyncsql03.board.win.fad.com" is of RoleId
    "7",  where RoleId "7"

    Another log that indicated missing parameters

    C:\Users\\AppData\Local\Temp\2\Test-CsDatabase-76d6947e-041a-4f68-b742-3b2c2d9e9cb6.xml".
    WARNING: Skipping service "2-UserStore-6" version "7", expected version "6".
    WARNING: Skipping service "2-ApplicationStore-6" version "7", expected version "6".
    WARNING: Skipping service "2-MonitoringStore-6" version "7", expected version "6".
    WARNING: Skipping service "2-CentralMgmtStore-11" version "7", expected version "6".
    VERBOSE: No changes were made to the Central Management Store.

    Is there any way to salvage the CMS and fail it over to Lync2013 or SFB2015 and to start the replication? Or the only way out is to upgrade the Lync 2013 Front ends to SFB2015 and then attempt the replication again?


    • Edited by Solitude99 Sunday, July 31, 2016 1:51 PM
    Sunday, July 31, 2016 1:51 PM

All replies

  • I'm not sure, what you have done.

    The normal migration path is to install the new SFB server. Install a fresh CMS database on the SFB server and run move-csmanagementserver.


    regards Holger Technical Specialist UC

    Sunday, July 31, 2016 3:13 PM
  • Hi,

    Version 7 here means Skype for Business 2015. Make sure you run the commands on the target Skype for Business 2015 other than Lync 2013 server.  Then try again.

    For your reference:https://ucsteps.com/2015/05/18/step-by-step-migration-from-lync-2013-to-skype-for-business-server-2015-step-3/

    Note:
    Microsoft is providing this information as a convenience to you. The sites are
    not controlled by Microsoft. Microsoft cannot make any representations
    regarding the quality, safety, or suitability of any software or information
    found there. Please make sure that you completely understand the risk before
    retrieving any suggestions from the above link.

    Best Regards,

    Jessie Yuan


    Please remember to <b>mark the replies as an answers</b> if they help and <b>unmark</b> them if they provide no help.<br/> If you have feedback for TechNet Subscriber Support, contact <a href="mailto:tnmff@microsoft.com"> tnmff@microsoft.com</a>.

    Monday, August 1, 2016 6:06 AM
  • Do you have Pool pairing enabled before your CMS move to new Pool ?  can you bit overview of your setup to understand the scenario to provde right solution.


    Regards, Rajukb | MCSE (Communication ), MCSA (o365) ,Certified "Lync server 2013 depth support engineer"| This posting is providedwith no warranties and confers no rights. If my reply answers your question please mark as answer/helpful if its helpful.

    Monday, August 1, 2016 2:32 PM
  • Yes we have pool pairing and we cannot break the pairing , we performed the same test in our LAB with identical setup and was successful but on VM's upgraded DR pool to SFB2015 from Lync2013, move CMS from PrimaryLync2013 to SFB2015 , move users from LYNC2013 to SFB2015, Upgrade primary Lync2013 to SFB2015 move users back to Primary Pool ran the same steps on Production but the CMS wont failover from LYNC2013 to SFB2015. The File transfer agent would start and stop which was one of the reason for the CMS and replication to fail but we got that reslved by modifying the XDSconfigIssue DB value but when we run the Get-CsManagementstorereplicationstatus the Active Master FQDN is blank while the rest of the information is correct. To me it looks like it doesn't know where the CMS is even though it is still on the Lync2013 Server. 
    Monday, August 1, 2016 3:01 PM
  • That is not entirely true, we have done this migration in our test environment twice and it worked its just ran into issues while doing this in production.
    Monday, August 1, 2016 3:03 PM
  • Hi Ankur,

    Just want to confirm if you ran the commands on Lync 2013 or on the SFB 2015. Feel free to let us know if you encounter the same problems when running them on SFB 2015. We will try to help you further.

    Best Regards,
    Jessie Yuan

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 9, 2016 9:18 AM
  • Yes we ran on SFB2015 and also on Lync2013 and also i was poking around in topology builder (even though we cant publish it) and found that on the properties for both Lync 2013 and Skype 2015 Front End Pools they showed " Note: You cannot move the user store for this pool because this pool also host the Central Management Server. To move the user store to another SQL instance, you must assign the Central Management Server to another pool. To do this see the product documentation." This looks like Lync and Skype thinks they have CMS on themselves where as CMS is only on Skype for Business server and this was confirmed via Lync 2013 runing the cs-management failover-whatif
    Thursday, August 11, 2016 4:37 PM