locked
SFB 2015 deploy SQL mirroring with SQL 2016 SP1: install-csmirrordatabase "no such interface supported" RRS feed

  • Question

  • FE Pool is deployed and trying to add mirroring.  SQL servers (SQl1 and SQL2) are SQL 2016 SP1, witness (SQL3) is SQL Express 2016, file share is on DFS share with Everyone having Change.

    Install-CsMirrorDatabase -ConfiguredDatabases -FileShare "\\<share>\<folder>" -SqlServerFqdn "<sql1>.company.com" -DropExisitingDatabasesOnMirror

    Tried Publishing with Topology and same result.

    Windows fire wall on all the SQL servers have ports TCP: 80, 443,1433, 1434, 5022, 7022 UDP:1434 opened.

    Any ideas what to look for?  firewall, File share, etc?  Searching web gave very few\ No results.


    • Edited by BiggJake Thursday, January 24, 2019 10:26 PM
    Thursday, January 24, 2019 10:14 PM

All replies

  • Hi,

    Its nothing to do with the SFB ... We had this issue ...please install cumulative update and you would be good.

    Resolution


    This fix is included in the following updates:

    Hope this helps!

    ---------------------------------------------------------------------------------------------------------

    Please don't forget to “mark the replies as answers” if they helped, also set "like" it’s a boost for us to keep blogging J

    Click here to learn more. Visit the dedicated Community forum to shareexplore and talk to experts about Microsoft Kaizala.

    Thursday, January 24, 2019 10:27 PM
  • Thanks.

    I applied that CU2 to both SQL servers and the Witness.  Still get the same:

    <?xml version="1.0" encoding="UTF-8"?>
    -<CsMgmtLog Name="Install-CsMirrorDatabase">
    <Info Time="2019-01-25 00:24:24Z" Title="Connection">Data Source=SQL01.<company>.COM\SFB;Failover Partner=SQL02.<company>.com\SFB;Initial Catalog=xds;Integrated Security=True;Application Name=Microsoft.Rtc.Management</Info>

    -<Action Name="InstallMirrorDatabaseCmdlet.StartMirroring" Time="2019-01-25 00:24:24Z">

    -<Exception Time="2019-01-25 00:25:06Z" Message="No such interface supported " Type="COMException">
    <StackTrace Time="2019-01-25 00:25:06Z"> at System.Management.ThreadDispatch.Start() at System.Management.ManagementScope.Initialize() at Microsoft.Rtc.Management.Deployment.MirrorUtils.GetSqlServerAccount(String server, String instanceName) at Microsoft.Rtc.Management.Deployment.TopologyParser.PopulateDatabasesForSqlInstance(ISqlInstance sqlInstance) at Microsoft.Rtc.Management.Deployment.TopologyParser.FindDatabasesForMachine(IMachine machine) at Microsoft.Rtc.Management.Deployment.TopologyParser.FindDatabasesForFqdn() at Microsoft.Rtc.Management.Deployment.TopologyParser.GetDbListToMirror() at Microsoft.Rtc.Management.Deployment.InstallMirrorDatabaseCmdlet.StartMirroring() at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog(Action action)</StackTrace>
    </Exception>
    <Complete Time="2019-01-25 00:25:06Z"/>
    </Action>
    <Error Time="2019-01-25 00:25:06Z" Title="Error">An error occurred: "System.Runtime.InteropServices.COMException" "No such interface supported "</Error>

    -<Exception Time="2019-01-25 00:25:06Z" Message="No such interface supported " Type="COMException">
    <StackTrace Time="2019-01-25 00:25:06Z"> at System.Management.ThreadDispatch.Start() at System.Management.ManagementScope.Initialize() at Microsoft.Rtc.Management.Deployment.MirrorUtils.GetSqlServerAccount(String server, String instanceName) at Microsoft.Rtc.Management.Deployment.TopologyParser.PopulateDatabasesForSqlInstance(ISqlInstance sqlInstance) at Microsoft.Rtc.Management.Deployment.TopologyParser.FindDatabasesForMachine(IMachine machine) at Microsoft.Rtc.Management.Deployment.TopologyParser.FindDatabasesForFqdn() at Microsoft.Rtc.Management.Deployment.TopologyParser.GetDbListToMirror() at Microsoft.Rtc.Management.Deployment.InstallMirrorDatabaseCmdlet.StartMirroring() at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog(Action action) at Microsoft.Rtc.Management.Deployment.DeploymentCmdlet.CmdletProcessRecord()</StackTrace>
    </Exception>
    </CsMgmtLog>

    The share is a DFS and I put in \\<name>\sfb\sqlmirror for file share during publish.

    Friday, January 25, 2019 12:42 AM
  • Hi,

    Please check the patch you installed in SFB server and make sure you have updated the latest one for SFB just in case the issue is caused by any bug that fixed in the newer CU.

    https://support.microsoft.com/en-in/help/4340904/july-2018-cumulative-update-6-0-9319-534-for-skype-for-business-server

    Kind regards,

    Calvin Liu


    Please remember to mark the reply as an answer if you find it is helpful. It will assist others who has similar issue. 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.

    Friday, January 25, 2019 9:06 AM
  • We are actually on CU8 for SFB 6.0.9319.537 (https://support.microsoft.com/en-in/help/4464355/january-2019-cumulative-update-6-0-9319-537-for-skype-for-business-ser).

    SQL version:

    Microsoft SQL Server 2016 (SP1-CU13) (KB4475775) - 13.0.4550.1 (X64)   Jan 10 2019 19:31:11   Copyright (c) Microsoft Corporation  Standard Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)

    Friday, January 25, 2019 4:03 PM
  • I ran the post CU backend Install-CSDatabse -update command again just to see if that helped.

    I got the following Warnign on the Lis and xds databases:

    WARNING: The database lis being updated has data file path at
    \\SQL01.<company>.COM\e$\SFBSQL\Databases\CentralMgmtStore\SFB\DbPath\lis.mdf and supplied data file path
     is \\SQL01.<company>.COM\E$\CsData\CentralMgmtStore\SFB\DbPath\lis.mdf. Supplied path will be ignored.
    WARNING: The database lis being updated has log file path at
    \\SQL01.<company>.COM\e$\SFBSQL\Logs\CentralMgmtStore\SFB\LogPath\lis.ldf and supplied data file path is
    \\SQL01.<company>.COM\E$\CsData\CentralMgmtStore\SFB\LogPath\lis.ldf. Supplied path will be ignored.

    WARNING: The database lis being updated has data file path at
    \\SQL01.<company>.COM\e$\SFBSQL\Databases\CentralMgmtStore\SFB\DbPath\lis.mdf and supplied data file path
     is \\SQL01.<company>.COM\E$\CsData\CentralMgmtStore\SFB\DbPath\lis.mdf. Supplied path will be ignored.
    WARNING: The database lis being updated has log file path at
    \\SQL01.<company>.COM\e$\SFBSQL\Logs\CentralMgmtStore\SFB\LogPath\lis.ldf and supplied data file path is
    \\SQL01.<company>.COM\E$\CsData\CentralMgmtStore\SFB\LogPath\lis.ldf. Supplied path will be ignored.

    WARNING: The database xds being updated has data file path at
    \\SQL01.<company>.COM\e$\SFBSQL\Databases\CentralMgmtStore\SFB\DbPath\xds.mdf and supplied data file path
     is \\SQL01.<company>.COM\E$\CsData\CentralMgmtStore\SFB\DbPath\xds.mdf. Supplied path will be ignored.
    WARNING: The database xds being updated has log file path at
    \\SQL01.<company>.COM\e$\SFBSQL\Logs\CentralMgmtStore\SFB\LogPath\xds.ldf and supplied data file path is
    \\SQL01.<company>.COM\E$\CsData\CentralMgmtStore\SFB\LogPath\xds.ldf. Supplied path will be ignored.

    Not sure if that is causing an issue.

    NOTE:  The Instance being used is NOT the default.

    Friday, January 25, 2019 10:44 PM
  • Hi,

    Would you please try running the following cmdlet to have a try?

    Install-CsDatabase -DatabaseType User -SqlServerFqdn {ServerName} -DatabasePaths {UNC Path to the erroring database} -SQLInstanceName {Instance name if required}

    Also, based on my research if you want to go with custom ports for SQL server, please try to go with named instances. If you want to use the default instance, you will need to use the default tcp port of 1433.


    Kind regards,

    Calvin Liu


    Please remember to mark the reply as an answer if you find it is helpful. It will assist others who has similar issue. 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.

    Wednesday, January 30, 2019 10:48 AM
  • I have the mirror in place and can manually do failovers of all the databases.

    I cannot get the witness server to show on the databases.

    Is there a guide for preparing the sql witness before adding it?

    Can the witness be added manually to each database?

    Monday, February 4, 2019 3:53 PM
  • Hi,

    For the SQL path issue, let’s see if these would help:

    http://howdouc.blogspot.com/2012/11/exploring-default-installation-and-sql.html

    And for the witness role configuration, please refer to this article:

    https://docs.microsoft.com/en-us/sql/database-engine/database-mirroring/database-mirroring-witness?view=sql-server-2017

    https://docs.microsoft.com/en-us/skypeforbusiness/deploy/deploy-high-availability-and-disaster-recovery/sql-mirroring-for-high-availability

    Kind regards,

    Calvin Liu


    Please remember to mark the reply as an answer if you find it is helpful. It will assist others who has similar issue. 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, February 12, 2019 9:59 AM