SharePoint 2013 connection to a Non-default port SQL Server

SharePoint 2013 farms are not allowed to appear in connection addresses that contain port numbers, otherwise the farm configuration will error, and cannot be completed when executing to the configuration farm database.

If SQL Server is not using the default port 1433, then you need to hang the top number. The workaround is to configure the alias, but the server-side alias does not take effect in 64-bit SQL Server, so you can install the native Client to resolve the problem. You can also resolve this by using a Non-default port for replication.

First you need to install native Client on the farm Web server. Then execute Cliconfg.exe on the farm server and configure the port as shown in Figure 1.

Figure 1. Native Client

Therefore, we can make the connection string no longer contain the port number.

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/web/sharepoint/