Announcement Module

Emergency Hours

Due to the increase in call volume during our normal business hours because of the Covid-19 Pandemic, Saturday and Sunday support was temporarily closed. Technicians were re-allocated to assist with the calls coming in during normal hours.

We are re-opening Saturday Emergency Support on August 8th, 2020, with Sunday Emergency Support to follow on a later date.

Please check back on for any changes in this announcement.
See more
See less

Troubleshooting Survival Guide - Connection Issues!

Page Title Module
Move Remove Collapse
This topic is closed.
This is a sticky topic.
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Troubleshooting Survival Guide - Connection Issues!

    You must first know that in order for a client machine to connect to a server, both computers should be on the same network. A quick way to find this out is by right-clicking on the My Computer or Computer icon and then clicking on the Properties option from the menu that appears.

    On Windows XP the following screen will appear.

    On Windows 7 the following screen will appear.

    You basically want to make sure that both your server and client computers are assigned to the same WORKGROUP name. If you are unsure on how to change the WORKGROUP name, simply perform a Google Search for "How to change workgroup name on Windows (your version)"

    On the client machine, you will then want to navigate to C:\RWD and open the utility titled RWDBUTIL.EXE. The following window will appear.

    Note: With older versions of Liberty4 and Liberty2002, the installation would include an older version of MSDE which may not require an instance name. In such cases, you will only need the server name without the instance name specified in the server name field. In the example above you would simply type "server" without the qoutes.

    If the client will not connect:

    If the client refuses to connect, you will typically see the following error prompt on the screen.

    Where to begin:

    Note: The following suggestions do not need to be performed in the exact order listed below.

    Make sure to test a connection after you perform each step!

    1. Make sure the Windows Firewall is disabled on the server computer (Click here for instructions).

    2. Check for other security programs. We have seen in many cases where security programs such as AVG, McAfee, Norton 360, PC-Cilian, Trend Micro, Avast, E-Set32, Avira and many others will come with additional layers of security that can prevent database connections. Please check with your third party security vendor for more information on how to properly configure or disable built-in smart firewalls or auto-protection options that could be interfering with SQL database connections or the Liberty4 program. I recommend turning off all protection that your security program offers then see if you are able to connect using the RWDBUtil.exe. If you ARE able to connect then proceed to contact the security vendor for instructions on how to apply exclusions or exceptions that will allow Liberty4 to properly connect. Simply explain to your vendor that you need all executable files contained within the C:\RWD folder to be excluded from being scanned by your security program.

    3. Check to make sure that the SQL service is enabled and running properly. If you are still running an older version of Liberty4 or Liberty 2002, you may still be running MSDE which is an older version of SQL. If you are running MSDE, you will generally find a small icon in your system tray on the bottom right corner.

    Double click on the icon and the following screen will appear. This screen will allow you to click the Start button if the service does not appear to be running.

    If you are running a newer version of SQL 2008 then you will need to click on your Windows Start menu > All Programs OR Programs > Microsoft SQL Server 2008 Configuration Tools > SQL Server Configuration Manager.

    Click on the SQL Server Services option on the left then SQL Server (Liberty) on the right. You will need to double click to see the section where you can choose to start the service.

    4. Make sure that SQL browser is running. You may also stop the service then restart the service the same as you would the SQL Server.

    5. Check what protocols are being used to connect to SQL by running CLICONFG.exe. You can launch this by going to Start > Run > CliConfg.exe

    For best results, on the SERVER computer you will want to make sure that you ONLY have shared memory selected. There should be no protocols enabled. It should appear like the example below.

    On the CLIENT computer, you should have TCP/IP and NAMED PIPES enabled. We recommend copying all options as shown in the sample below.

    6. You will sometimes have no choice but to connect using the server's IP address. The IP address is basically how the server computer is identified on your network. The IP address is kind of like a phone number or mailing address that allows the other computers (clients) on your network transmit data back and forth from your server. There can sometimes be Windows related issues that can cause the computer's name i.e "server" to not properly resolve to the IP address. In such cases, you can bypass the name from needing to be resolved by simply using the IP address rather then the server's name. In order to retrieve the IP address from your server's computer, please click here for detailed instructions.

    Once you have obtained your IP address, you will need to run the RWDBUtil.exe utility to see if you can now connect. The example below shows how I replaced the server's name with my IP address.

    7. On Windows 7, there are some additional levels of security that can also prevent a connection. These extra options can be found in Network and Sharing Center. Click Start > Control Panel > Network and Sharing Center.

    On the following screen, click on "Change advanced sharing settings".

    I recommend expanding both Home and Public to select the proceeding options specified.

    • Turn on Network Discovery
    • Turn on File and Printer Sharing
    • Turn off password protected sharing

    8. If your server or client that refuses to connect is running Windows XP then you can also try to repair MDAC. Follow the instructions in the following article and perform the steps on your server or client or both if all are running Windows XP. Click here for instructions on how to repair MDAC.

    9. In some instances, it is possible to receive a SA Login Failed error message appear when you attempt to connect using the RWDBUtil.exe utility. This basically means that the database password being used on the client machine does NOT match the one applied to the server you are attempting to connect to.

    The encrypted database password should read one of the following - Feel free to try both if necessary:

    In Windows XP, you can apply the database password by going to Start > Run > Type Regedit. This will open the Windows registry where you will then need locate the following:


    If you double click on the name DBPassword, you will be able to paste the correct database password that was copied from your server.

    On Windows 7 - Click Start > Type Regedit in the search field. You will then need to search for until you locate all binary strings where you can enter the correct database password. In Windows 7, you may need to apply this to multiple keys. The registry keys will look very similar to how they appear in the Windows XP example above. Make the same change to the DBPassword key when you find it in all instances.

    If you plan to proceed with a customer install of SQL, please click here for more information on installing your own version of SQL to work with Liberty4.

    Hope this helps!
    Angel Vazquez
    Web Developer