This article helps you troubleshoot the Windows DS-System (or Windows DS-Client) installation, if you encounter problems with connection to a remote MS SQL Server database instance. These solutions apply if the following (or a similar) popup message occurs during installation:
Here are several possible causes are the corresponding solutions (this list is not exhaustive):
|
The network protocols are not enabled. |
This can be fixed by making the appropriate changes using the SQL Server Configuration Manager. |
|
There is a firewall between the computer where you install the DS-System (or DS-Client) software and the remote SQL Server instance. |
You can turn off the firewall or set up the appropriate exceptions to allow the communication. |
|
The protocol to be used is TCP and the port that the remote SQL instance listens to is not the default one (TCP 1433). There are several ways to ensure that the software connects to the desired port: |
If possible, configure the remote MS SQL Server instance to listen to the default port (TCP port 1433). |
If the instance uses a dynamic port, ensure that SQL Server Browser service is running on the remote SQL server. (Note: This may not work if the remote SQL is clustered.) |
On the client machine (where the DS-System or DS-Client software is to be installed) create a server alias configuration where to specify the required port. The SQL Server Instance should be configured to use a static port, otherwise the alias may become invalid. - The alias should be specified as <computer_name_or_IP> for the default instance, or as <computer_name_or_IP>\<SQL_instance_name> for named SQL instances.
- One note for 64-bit installations: the installation package itself is a 32-bit process, while the service is 64-bit; therefore you should make sure that the alias is properly configured in both 64-bit and 32-bit views.
- You can use the SQL Client Configuration Utility (filename: cliconfg.exe) that comes with the Windows installation.
- The native 32-bit or 64-bit version can be found under: C:\Windows\system32 - If using a 64-bit system, you can find the 32-bit version under: C:\Windows\SysWow64 |
Using the same cliconfg.exe tool as specified above (Solution 3), someone can change the default port that clients try to use for SQL Server connections. Be careful when using this option, since it may cause failures if any other application requires connections to other SQL instances on the default port. |
|
The user running the DS-System or DS-Client software installation cannot connect to the SQL Server instance using a trusted connection. |
- If both computers are members of the same domain or they are members of different domains but there is a trust relationship between the 2 domains, you can run the installation under a Windows account that can connect to the SQL server instance (as long as it also has rights to create databases and extended stored procedures).
- If the previous configuration is not possible, you must create a local account with the same name and password on the 2 computers. Make sure that the user (or a group to which this user belongs) has login rights to the SQL Server (you may need to add the BUILTIN\<group_or_user_name> in the Logins section of the SQL Server Management Studio or SQL Server Enterprise Manager for SQL 2000). Run the DS-System or DS-Client software installation under that same user.
|
The information provided in this document is provided "AS IS", without warranty of any kind. ASIGRA Inc. (ASIGRA) disclaims all warranties, either express or implied. In no event shall ASIGRA or its business partners be liable for any damages whatsoever, including direct, indirect, incidental, consequential, loss of business profits or special damages, even if ASIGRA or its business partners have been advised of the possibility of such damages. © Asigra Inc. All Rights Reserved. Confidential.