The below screenshot shows the error that the install-csdatabase command spits back:Įrror 40 – could not open a connection to SQL Server. The above command installs the Skype for Business Monitoring Database on SQL server Install-CSDatabase -DatabaseType Mirroring -SQLServerFQDN -UseDefaultSqlPaths -Clean -Verbose To test this, I changed the default instance port from 1433 to 6100Īfter restarting the SQL service, I then ran:
Changing this port to any other port will cause the Skype for Business database installation process to fail. This means that the SQL server port must remain as port 1433. If SQL Server has been installed as a Default Instance, you must use the default SQL server ports if you want to use the instance to store Skype for Business backend databases. This is vitally important as if you want to run SQL server on a non-standard port, one will work with Skype for Business, and the other won’t. Generally speaking whenever a new Instance of SQL is installed, an administrator will choose a Named Instance over a Default Instance. Changing the default SQL server port is a Microsoft recommended step too, to harden your SQL server security. Yes – running SQL server on non-default (1433) ports is supported by both Microsoft support, and Skype for Business server (both 20).
Skype for Business Server and SQL Server are no exception, and some administrators immediately go to work changing SQL’s default ports after installing a new instance. Because of this, system administrators are constantly working to ensure their environments are as secure as they can be. Today, security is more important than ever.
0 kommentar(er)
