Problem
When running PeopleSync Frontend setup, you encounter the following error message:
...
This can happen if there is a firewall between PeopleSync Frontend and SQL Server, the SQL Browser service is stopped or there is a TLS problem.
Solution
With the following advice you can find out which ports your SQL Server instance uses and consequently determine if they can be reached through the firewall. You can also check for other causes with the script provided.
Determine SQL Server Ports used
Open SQL Server Management Studio and connect to the SQL Server instance where the PeopleSync database is located.
- Open a new query window
Run the following command:
Code Block sql sql EXEC xp_ReadErrorLog 0, 1, N'Server is listening on', N'any', NULL, NULL, 'DESC'
On our server, for example, this gives the following output "Server is listening on [ 'any' <ipv4> 1433]."
Verify Connection
Now that you know which port SQL Server uses, you can check if you can connect from the server where you are installing PeopleSync Frontend by running the following command from a PowerShell window:
...
| Code Block |
|---|
ComputerName : srv-2 RemoteAddress : 10.0.18.96 RemotePort : 1433 InterfaceAlias : Ethernet SourceAddress : 10.0.18.54 PingSucceeded : True PingReplyDetails (RTT) : 1 ms TcpTestSucceeded : False |
If "PingSucceeded" or "TcpTestSucceeded" is false, then probably the firewall hasn't been opened.
...
If the SQL Server port is not 1433, you also have to specify the port in the database connection dialog of PeopleSync server setup. The syntax is
<servername>,<port>. For example, in the setup, the connection to instance "srv-2\instance1" running on port 1456 would be specified as "srv-2,1456". In this case, there is no need to specify the instance name.Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...