locked
Error while publishing topology while migrating on SFB standard server. RRS feed

  • Question

  • hi ,

    we have a situation in which we have a Skype for business server 2015 on premise server (front end server ,web app server and an edge server). we have to reinstall the Skype server completely . we have created another SFB server and installed front end server in that. while publishing the topology we are getting following error 

    we tried to remove the existing central management but still getting same error .

    how can i get it freshly installed at the new server.?

    thanks in advance.

    Thursday, March 31, 2016 12:06 PM

Answers

  • In that case maybe the following blog can help you:
    https://lyncdude.com/2013/02/06/remove-lync-server-configuration-from-active-directory/

    Maybe you should also first delete everything in the Topology Builder and publish the "empty" topology.

    • Marked as answer by Mayank P Monday, April 4, 2016 10:55 AM
    Thursday, March 31, 2016 1:13 PM
  • Did you start the Topology Builder as administrator (run as administrator)?

    Please check the following blog by Thomas:
    http://lyncuc.blogspot.de/2015/08/skype-for-business-file-share-failed-to.html

    He described exactly the same error you currently have. Maybe this helps.

    • Marked as answer by Mayank P Monday, April 4, 2016 10:55 AM
    Friday, April 1, 2016 8:05 AM

All replies

  • Hi,

    a possible solution would be to add the new server to the existing topology, migrate the users and the CMS to the new server and afterwards delete the old server from the topology.

    Regards
    Dirk

    Thursday, March 31, 2016 12:27 PM
  • actually in our case we want to use different binaries of Skype for business Provided by clients.so we need to create a new Skype server ans a new central management store . as our previously deployed server was with different binaries(MSDN) and we can't use this for production.
    Thursday, March 31, 2016 12:32 PM
  • In that case maybe the following blog can help you:
    https://lyncdude.com/2013/02/06/remove-lync-server-configuration-from-active-directory/

    Maybe you should also first delete everything in the Topology Builder and publish the "empty" topology.

    • Marked as answer by Mayank P Monday, April 4, 2016 10:55 AM
    Thursday, March 31, 2016 1:13 PM
  • Thanks for the above link. i used this and i was able to successfully publish topology with warning.i have attached the log  screen shot below.

      i continued installation as it was a warning while installing local configuration store and was not able to configure local replica . below is the screen shot . 

    Please help.

    Friday, April 1, 2016 5:24 AM
  • that's not a Warning but an error. It basically says that it can't find the CMS location pointer in AD. Also that explains why it cannot retrieve the configuration automatically. 

    Try downloading the topology now?. I recon it would not be able to find the deployed topology as well. If that's the case, you might need to configure the topology once again and publish.


    http://thamaraw.com

    Friday, April 1, 2016 5:38 AM
  • while publishing the topology i am getting rights issue .i have share the folder with local administrator with full read and write rights but will having this error then i shared it to everyone with full read and write but still its failing.

    Please help




    • Edited by Mayank P Friday, April 1, 2016 6:58 AM
    Friday, April 1, 2016 6:52 AM
  • What about the NTFS permission?. Do you configure to allow local admin to have full read and write permission to the share?.

    http://thamaraw.com

    Friday, April 1, 2016 7:15 AM
  • I have shared the directory with local administrator with Full Control.but still getting the error while publishing the topology.is any other configuration required other than sharing the folder with  local administrator???
    Friday, April 1, 2016 7:27 AM
  • Did you start the Topology Builder as administrator (run as administrator)?

    Please check the following blog by Thomas:
    http://lyncuc.blogspot.de/2015/08/skype-for-business-file-share-failed-to.html

    He described exactly the same error you currently have. Maybe this helps.

    • Marked as answer by Mayank P Monday, April 4, 2016 10:55 AM
    Friday, April 1, 2016 8:05 AM
  • Hi,

    For the permission of the shared folder, make sure it is the member of

    RTCHS Universal Services

    RTC Component Universal Services

    RTC Universal Server Admins

    RTC Universal Config Replicator

    Also, for the issue when publishing the topology, please try to delete the topology information on AD using ADSI and then test again.

    Best Regards


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

    Eason Huang
    TechNet Community Support

    Monday, April 4, 2016 7:01 AM
  • You get it if you haven't launched topology builder as administrator (right click, run as admin). is that the case?

    www.rtcpedia.com - A real time communications blog

    Monday, April 4, 2016 10:42 AM