2. Go to the Services app on the machine hosting the SQL database and verify the SQL Express (TREASOFT) or SQL Server is running along with SQL Server Browser. SQL Server Browser enables the Treasury Software to detect the database in the wizard dropdown seen below.

3. Try installing the latest version of SQL Server Native Client - very common.
https://www.treasurysoftware.com/setup/SQLNativeClient1147/sqlncli.msi

4. If you are still not able to connect try typing in the IP\database instance of the server.

5. You can also try installing a local copy of Treasury Software on the server itself and connecting the Treasury Software to the database by using (local)\TREASOFT or IP\TREASOFT. If you are able to connect when the Treasury Software is on the same machine as the database then it is probably a firewall issue (see next step).

5. Need to create rules to get around the firewall? If possible, try turning off the Windows Firewall on the server and computer trying to connect to the database (Control Panel > View by Large Icons > Windows Firewall).

If you need to create a firewall rule please see the following link. Note, you would need to create a rule for the SQL Browser and SQL engine. This link will walk you through that process.

https://www.treasurysoftware.com/hc/en-us/articles/360063390713-SQL-Unable-to-Connect-to-SQL-Server-2-Firewall

6. Try installing SQL Server Management Studio on the client machine and see if you can connect to the SQL database. If so, try connecting the Treasury Software to the SQL database after you have successfully connected with SQL Server Management Studio. In the past this has resolved the connection issue as it installs additional components.

7. Verify you can connect to the database through SQL Server Management Studio on the server using the same authentication as the client will be using.

Note. If they are using the Treasury Software SQL Express database try using SQL Authentication using the Treasury Software sa user name and password. If you do not have this password ask John or Glenn (cannot post passwords). In the past clients have changed this sa password. You will need to manually type this in for them as we do not give this password out.

If they did change the Treasury Software sa password make sure you do not check the following box when making the connection. Note, all users will need to have the 'BankRecPosPay' user role.

http://www.treasurysoftware.com/Support/support2-Troubleshooting-SQL-Server.aspx

8. If possible, try rebooting the computer that is trying to connect to the database first and the server. After it has been rebooted, try reconnecting.

9. Confirm that ports 1433, 1434 - and possibly additional ports (see below) are open.

Open a Command window

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).

10. Stop/restart the database through the Services panel. Then restart software and try to reconnect. Some companies will not open port 1433 or 1434. If they are using a specific port you can specify this port by using a comma followed by the port number.

11. Need to get around the Sample account? Click on File > New Account from the Welcome New Users screen.

Existing installations:

1. Ask if any computer can connect. I would suggest confirming this by entering into the software from another machine and running any report and verify the server and database name by going into the Treasury Software > Settings tab > Maintenance > SQL tab.

2. For SQL Server installations check permissions see the following link. http://www.treasurysoftware.com/Support/support2-Troubleshooting-SQL-Server.aspx

3. Go to the Services panel and verify the SQL Express (TREASOFT) or SQL Server is running along with SQL Server Browser. SQL Server Browser enables the Treasury Software to detect the database running in the wizard.

4. Try installing the latest version of SQL Server Native Client.
https://www.treasurysoftware.com/setup/SQLNativeClient1147/sqlncli.msi

5. If you are still unable to connect, try using the IP address instead of the machine name when making the connection (Settings tab > Migrate to SQL Express, SQL Server).

6. Stop/restart database. Then restart software and try to reconnect.

7. If no computers can connect, install a local copy of the software on the server hosting the database to see if you can connect. If you can connect locally and not from another computer then it’s a connectivity issue, probably a firewall issue.

8. If possible check to see if it’s a firewall issue by turning off Windows Firewall on the server.

9. Need to create rules to get around the firewall? This will need to be done on the server hosting the SQL database. After creating a rule for the SQL Browser and SQL database using the following link, try connecting Treasury Software to the SQL database.

https://www.treasurysoftware.com/hc/en-us/articles/360063390713-SQL-Unable-to-Connect-to-SQL-Server-2-Firewall

10. 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).

Still not connecting?

1. Select Start, and in your list of programs, select SQL Server Configuration Manager. If you are unable to find it try the following:
Control Panel>Administrative Tools>Computer Management

2. Navigate to SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for <machine instance>. If using the Treasury Software SQL Express database select the database with ‘TREASOFT’. You will want to enable Named Pipes and IP4.

Note, if you make a change you will need to restart the database in the Services panel for it to take affect.

Continue by following the instructions in the article: Enabling TCP/IP – Named Pipes

Note, if you make a change you will need to restart the database in the Services panel for it to take affect.

In addition, while you are in SQL Server Configuration manager check to see what port they are using.

SQL Server Configuration Manager 2.jpg

SQL Server Configuration Manager 3.jpg

3. Check to see how the SQL database is set for authentication.

4. Check if the sa user is enabled. If they are using SQL authentication with the sa credentials, you will need to enable the sa login.

5. If you are unable to get the Treasury Software SQL Express database to install or run, please try the 2017 version.
https://www.treasurysoftware.com/setup/Setup_SQL_Express_Host_SQL2017.exe