locked
Install Persistent Chat server role on AlwaysOn High Availability group fails RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I have a SfB lab environment with an already installed Front End Pool and running. My databases are on a AlwaysOn High Availability group. the installation of the front end database worked just fine. Now I try to install a Persistent Chat Server. I've added the machine in the Topology Builder and tried to update the database. It always fails when the topology builder tries to create the mgc database from scratch. I get the error:

    "System.IO.IOException" "The network name cannot be found.

    The solution explained here http://www.wavecoreit.com/blog/2015/skype-for-business-sql-error-system-io-ioexception-the-network-name-cannot-be-found/ is not the problem. I've checked the paths. They are correct and the user has write access to it. Any suggestions what else it could be?

    thanks.

    Matthias

    Monday, March 12, 2018 11:54 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I fixed it.

    The SQL store in the topology wasn't proper configured. We are using a AlwaysOn HA group. the SQL Server FQDN was set to the AlwaysOn group listener. That didn't work. So I changed it to the primary SQL server node in our cluster. That fixed the problem.

    • Marked as answer by bilberry79 Tuesday, March 13, 2018 8:48 AM
    Tuesday, March 13, 2018 8:48 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi ,

    When you publish the topology ,did you select “Use SQL Server instance defaults” like the following screen shot.

    if you are in the internal environment,you could disable the fireware on the persistent chat server and backend server ,then make a test.

    Please double check the steps that you deploy the persist chat Persistent Chat pool.you could refer to the following link.

    https://insidemstech.com/2015/09/07/step-by-step-persistent-chat-pool-deployment-skype-for-business-server-2015-part-i/

    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,
    Leon Lu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, March 13, 2018 7:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    That's what I mentioned in the link. Yes I did all that. But still no luck.

    Tuesday, March 13, 2018 7:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I fixed it.

    The SQL store in the topology wasn't proper configured. We are using a AlwaysOn HA group. the SQL Server FQDN was set to the AlwaysOn group listener. That didn't work. So I changed it to the primary SQL server node in our cluster. That fixed the problem.

    • Marked as answer by bilberry79 Tuesday, March 13, 2018 8:48 AM
    Tuesday, March 13, 2018 8:48 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for your share.

    Best Regards,
    Leon Lu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, March 13, 2018 10:22 AM