Overview
This page may be for you if you are in this scenario:
I have successfully installed the Treasury Software SQL Express database on a server, and I have installed the Treasury Software client on a workstation.
However, when I attempt to migrate the client (from the main menu File > Migrate to SQL, SQL Express) the process fails.
This can be caused by one of two issues:
A. The SQL Express database engine is not running
B. There is a connectivity issue between the two computers.
The easiest step is to rule out a problem with the database engine. Simply download and install Treasury Software (client) onto the same machine that is hosting the SQL Express database engine.
Once installed, from the main menu migrate to SQL Express (from the main menu File > Migrate to SQL, SQL Express).
If the process failed, please follow the check list at SQL database engine troubleshooting.
If successful, the engine is running and we know it is a connectivity issue. Please proceed to the next step, which is the focus of this help page.
Note: There are a number of connection protocols associated with SQL Express.
The ability to see a server - does not necessarily mean that you can connect to it to and read/write data.
1. Confirm that you can view the broadcast of the SQL Express engine.
From the client computer select File > Migrate to SQL, SQL Express. If you do not see the [server name]\TREASOFT, make sure that when prompted to install SQL utilities, you have done so. Exit and re-start the wizard to trigger the installation.
If you are unable to view the server name, along with the instance, please confirm that you installed the Treasury Software supplied version of SQL Express.
If you have confirmed all of the information, please type in the name and instance (server name\TREASOFT). If this resolves the issue stop here, otherwise - continue.
As a general rule, the client software and SQL Express database should be on the same network - and there should be no ports blocked between them.
Some network administrators will install PC-based firewalls and block all ports, unless specifically enabled. You will need to confirm that ports 1433, 1434 - and possibly additional ports (see below) are open.
Open a command window and from the prompt type
NETSTAT -a -n
and then hit enter.
Review the results - you should see 1433 and 1434 open at a minimum (TCP and UDP).
If these ports are not open - please review your firewall settings.
In addition, it is possible that your router is blocking this traffic.
As a reminder - by default these ports will be open.
They are only blocked if somebody specifically closed them.
Please contact your network administrator for assistance.
3. We've got ports 1433 and 1434 open on both the client and server, but we're still not able to connect.
By default, the first instance of SQL Server (and Express) uses port 1433 for data, and port 1434 to communicate dynamic port information.
Subsequent/named instances of SQL use dynamic ports.
What port is SQL Express using and how does the client know what port to use?
The SQL Express database can be on either static or dynamic port configuration. Assuming port 1434 is open, the client will initially contact the SQL database engine and inquire as to which port to use. The client will then use that port to read/write data.
a. On the server:
Make sure the SQL Browser service is running on the server.
If a firewall is enabled on the server (or exists between the server and the client), you need to put sqlbrowser.exe and/or UDP port 1433 and 1434 into the exception list.
To verify that the SQL Server Browser service is running, from the Windows Start button > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager.
b. Check Protocols in Configuration Manager (on the server)
While the SQL Server Configuration Manager (above) is still open, click on SQL Server Network Configuration Make sure that TCP/IP is enabled
c. Determine the port number (other than 1433)
Right click on TCP/IP and select properties from the pop-up menu.
Click on IP Addresses and scroll to the bottom.
The section 'IP All' will contain the port number (if it is not 1433).
d. Confirm that this port is open.
Open a command window and from the prompt type
NETSTAT -a -n
and then hit enter.
Please note that port 50830 as listed above - is open, as well as 1433 and 1434.
Please perform this step on both the server and the client.
If these ports are not open, please locate the device or service that is blocking them. You will be unable to connect until this is resolved at your location.
Once these ports are opened, you should be able to connect without issue. If we can help further on this, please do not hesitate to contact us.
Note: If you are using SQL Server (not SQL Express), please refer to additional security settings.
How to open ports on your Windows Firewall
http://treasurysoftware.com/Support/support2-Configure-Windows-Firewall-Ports.aspx
Customer Billing Portal
(866) 226-5732
