My Progeny cannot connect to the server

Frequently Asked Questions regarding the Progeny membership management software.

My Progeny cannot connect to the server

Postby [TDR] Ross Hammer » November 17th, 2008, 12:19 pm

Keywords: server connection "SQL Server is unavailable or does not exist"
Applies to: All Client Server versions

When using ProgenyES in Client-Server mode with a Microsoft SQL Server, all data is stored on a central server or host computer running the SQL Server software. Progeny communicates with the SQL Server software directly via the TCP protocol (not the same as file sharing). Database authentication access is multi-level: Progeny uses SQL Server Authentication to validate the connection, Microsoft Windows uses a combination of Windows User and Computer access authentication depending whether a workgroup or domain is being used. All of these lends a high degree complexity and makes working through connectivity issues difficult.

The first items to check when a ProgenyES client cannot connect is the server name (and instance, if applicable), the login name, and the password. An example of a connection to a MSDE service would be as follows.
Code: Select all
Server = YourServer\Progeny
User = sa
Password = somepassword

If the settings are correct, the next thing to check is basic TCP connectivity. Open a command console window and issue a Ping command. Note that this is not 100% reliable as some servers may be configured to not respond to a ping to reduce the possible of a Denial of Service (DOS) attack.
Code: Select all
RUN> cmd
C:\> PING YourServer

Even if you have a named instance for the SQL Server service, do not include it when pinging, it should be only the name of the server computer. If the Ping times out or indicates it cannot find the host, then the server may not be connected to the same network as the client (or vice versa). If the Ping succeeds, the next item to check is the port and firewall. Most default installs of SQL Server will automatically use TCP Port 1433. If a firewall is enabled on the server, it may block this port and will need an exception created for either TCP traffic via that port, or a more specific exception for the SQL Server service executables. To examine the port, separate instructions for SQL Server 2000 and 2005 follow.

SQL Server 2000 (and MSDE):
The check what port the SQL Server 2000 service is using, login to your server and run "SvrNetCn". Select the TCP/IP protocol and click the Properties button. The port for the service will be indicated.

SQL Server 2005:
The check what port the SQL Server 2005 service is using, login to your server and run the Microsoft SQL Server 2005 - Configuration Utiltities - SQL Server Configuration Manager. Select the Protocols section (if not already selected) and double-click the TCP/IP protocol, then select the IP Address tab in the resulting properties dialog. The port for the service will be indicated (possibly under "IPAll").

Command line for any version:
To look more directly at what ports are active, the following commands may be run to open a command console window and check the active ports (you'll be looking for the entry for "sqlservr.exe").
Code: Select all
RUN> cmd
C:\> NetStat -p tcp -b -a -n

If the port is configured for other than 1433, the Progeny Server Settings dialog has an Advanced section where you can specify a non-default Port value, however this will often not be necessary as long as the SQL Browser service is enabled and running, permitting Progeny and your SQL Server to automatically negotiate the correct communication ports.

If none of these tips resolve your issue, following is a link to a Microsoft Knowledge Base article with many more links and suggestions on correcting connectivity issues (copy and paste it into your browser address bar).
[TDR] Ross Hammer
Posts: 85
Joined: August 19th, 2008, 9:56 am
Location: Redding, CA

Return to FAQ