For our customers using CardConnect for credit card processing, CardConnect is currently experiencing issues with processing payments. They are aware of the issue and are working to rectify the problem. For up to date information on the outage you can go to Status.CardConnect.com

On Monday, September 2nd, our offices will be closed for the Labor Day holiday. Our regular business hours will resume on Tuesday, September 3rd at 9 A.M. Eastern Daylight Time.

>System Maintenance is scheduled Sunday night, April 22nd, between 10:00 PM and 5:00 AM EST Monday, April 23rd. While these database upgrades and maintenance is necessary, it will mean that our online services will not be available during this maintenance window. These services include: online booking, messaging, remote access, memberships or any account management. We apologize for any inconvenience this work may cause and thank you for your service and patience.

We recently experienced a service outage related to some Amazon Web Services, which affected key functionality of our Remote Access Service. This interruption happened on Thursday, June 22nd, between the hours of 9:00pm and 2:00am EST. The Remote Access Service is now fully restored. If you continue to experience issues with your Remote Access Service, please follow the directions on this Support Article to restart the Remote Access Service and try reconnecting again. You can also restart your computer to restart your service. If you are still experiencing issues afterwards please contact our support team at 1 (800) 604-2040.

All of our services have been restored after a brief interruption that impacted our Cloud online services. This interruption occurred between 9:45 a.m. and 10:55 a.m. EST on September 18th. We apologize for the inconvenience and thank you for your patience!

Network Troubleshooting Guide

These instructions will help you connect your client computer(s) when the connection to the server computer is lost. These instructions assume that the software on your server computer is currently installed and functioning properly.

Check Server Connection
  1. Obtain the correct server name by opening the program on a computer that is working (either another client or the server itself). While Inside the program go to the File drop-down menu at the top-left, and then select Database Settings > Connection Settings. This window will display the correct Server Name. Record this information so that you may use it to configure your client computer(s). (NOTE: You will encounter problems if your client computer(s) and your server computer share the same computer name(s), i.e. DESKTOP-WORK and DESKTOP-WORK. If this is the case, one or more of the computer names will have to be changed through your computer’s properties before a connection between the client and server computers can be established.) 
  2. Go to the client computer that is not working and try opening the program. ​
    • If you get a message stating that the SQL Server could not be found, click on the Continue without Connecting button. This should bring you to a screen that says No Database Open. Go to the File drop-down menu at the top-left and select Database Settings. Then click the Connection Settings button.
    • If you get a window indicating that the program is attempting to establish a connection with the database that stays on your screen for more than a few moments, click the Close button once it becomes available. This will bring you to the Connection Settings screen.
    • If the program opens but appears to be using a different database than the server computer, go to the File drop-down menu at the top-left and select Database Settings > Connection settings. Then click on the Edit Connection Settings button.
  3. On this screen, select the This is an additional computer (client) option and press Continue. Select Manual Setup and type in the name of the server computer you found from Step 1 in the text box labeled Connect to: Click the Continue button).​​At this point if everything is configured correctly, then you will be prompted to enter your database password if you originally created one. If you don’t have a database password, the client computer will be reconnected with the server computer and your database will be opened. If you instead receive an error message saying SQL Server was not found or is not functioning properly, then this would most likely be caused by one of two reasons:​​ You can click OK on this message, but do not close out of the Select Server screen for now.
    1. There is a firewall enabled on the server computer that is blocking the client computer from connecting.
    2. Your business’s network is not functioning properly.
Firewall Troubleshooting
On the server computer, verify that all firewalls are turned off. This includes, but is not limited to, the Windows Firewall that comes installed on Windows XP, Vista, 7, and 8 computers.  You should also check to see if there is a firewall built into your antivirus software on the server computer, such as Norton AntiVirus or McAfee AntiVirus. Disable the firewall in these programs also.  Since there are many different antivirus programs, we cannot provide instructions for every program. 

To disable the Windows Firewall, perform the following steps:
  1. On your server computer, if using Windows Vista or Windows 7, go to the Windows Start button (bottom, left corner of your Desktop) and click on Control Panel. If using Windows 8, push the Windows key on your keyboard and type Firewall. Click Settings and then Windows Firewall.  
  2. Open Windows Firewall.
  3. If you are running Windows Vista, Windows 7, or Windows 8 click on Turn Windows Firewall on or off.
  4. Toggle the Windows Firewall​ to off.
With the Firewall turned off, try connecting again from the client computer by clicking the Connect button from the Select Server screen. If it is still unsuccessful, or if Windows Firewall was already turned off, browse through the programs on the server computer to see if another antivirus program installed on your computer has a firewall.

If you don’t want disable a firewall entirely for safety purposes, then you can set up firewall exceptions for Microsoft SQL Server instead of turning the firewall completely off by following the knowledge base article here.
You should, however, first consider turning the firewall off entirely to verify that it’s actually the problem. If you disable the firewall and find your client connects, then you can always go back to the server and enable the firewall again to create firewall exceptions.

Network Troubleshooting
Aside from a firewall issue, the other most likely reason that the client cannot connect to the server is that the client cannot see the server computer over the network. The most common symptom of this is that the client or the server computer no longer has access to the Internet. However, if the Internet is working on both computers then there may be another problem with the network configuration that prevents the two computers from communicating directly. To be certain that there is a network configuration problem, following these steps:
  1. Perform a ping test from the client computer to the server computer. A ping test will let you know if one computer can contact another in a network.
  2. On your client computer, go to Windows Start > All Programs > Accessories > Command Prompt.
  3. Type in ping [server computer’s name], where [server computer’s name] is replaced by the server’s actual name. The server name is the name from Step 1 in the Check Server Connection​ section of this document. For example, if you found the server name from Step 1 on Page 1 to be THOMAS\CMJ, then the server computer’s name is THOMAS. In this case you would type ping THOMAS, and then hit the Enter key on your keyboard.

A successful ping will give you a response similar to this:
An unsuccessful ping will give you a response similar to this:

Or this:

If you were able to successfully ping the server computer from the client, then it is most likely not a network issue. You may want to go back to searching your system for a firewall or continue on to the next section, Other Suspects.

If you were not able to ping the server, then you are experiencing a network problem. Below are a few basic troubleshooting measures to try out if you cannot ping the server:
  1. Restart both the client and server computers.
  2. Verify that both the server computer and the client computer are connected to the network router. You should verify that all cables are connected snugly on the back of the computer(s) and the router.
  3. If one (or both) of the computers is connected to the router wirelessly, be sure that the computer has a strong signal.
  4. Reset your router (use the reset button or by unplug it for several seconds and plug it back in) and reconnect the computers in the network.
If you’ve performed the above steps and still cannot connect your client computer to the server computer and are certain that both computers are connected to the router, i.e. they both have Internet access, then you can try to configure the settings in the software to connect using the server computer’s IP address instead of the server name. (NOTE: Connecting to your server computer using the IP address is NOT recommended if your computer is assigned an IP address dynamically.)

Connecting Your Server Using an IP Address
When a computer is assigned an IP address dynamically, the computer is assigned a new IP address each time it connects to a network. In other words, your client computer(s) will lose connection to the server computer again every time they connect to the network. If you are not sure whether your IP address is assigned dynamically or statically, do not use this method. A dynamic IP address is the most common method for assigning an IP address on a PC computer, especially if you are using a wireless router or your network was set up automatically. Perform the following steps if your server has a static IP address, or if you would like to connect to the server by the IP address as a temporary solution:
  1. Go to the server computer and bring up the command prompt by going to Windows Start > All Programs > Accessories > Command Prompt. In the Command Prompt type ipconfig. You will see some information about your computer’s network.Note: If you have Windows XP then look for the number labeled IP Address. In Windows Vista, 7, and 8 this number is named IPv4 Address (much of the information shown can be ignored).
  2. Go back to the client computer and navigate to the Select Server screen in your software.
  3. Replace the server name with the IP Address you obtained in Step 1 on this page. Click the Connect button (or OK depending on the version you are running).
If this is unsuccessful, try to ping the IP address from the client the same way you pinged the server name.
  • If it cannot ping the IP address, then your two computers are likely not in the same network. Check all connections and verify that both are connected to the same router or contact your business’s network administrator to have them set the network up properly.
  • If the client can ping the server’s IP address but still not connect through the Select Server screen, check for firewalls on the client computer and try to establish a connection.
Again, connecting by the IP address should only be done as a temporary solution unless your server has a static IP address. If you can connect by the IP address but not the computer’s name, this is a DNS issue within Windows. If this is the case you can either configure your server to have a static IP address or set up a new Local Area Network (LAN) in your Windows operating system. The steps to do either of these should be provided by the documentation that came with your router.

Other Suspects
Roughly 99% of all client connectivity issues result from server-side firewalls or network problems. You should not attempt any of the below until you have exhausted all of the possibilities described above, including contacting your network administrator if you have one available.
If there are no server-side firewalls and you are able to ping the server computer using the server’s name or IP address, then here are a few other potential problems that could cause a client computer to be unable to connect to the server computer.
  1. Client-side outbound firewalls: Certain antivirus packages have built-in outbound firewalls.  The Windows Firewall discussed earlier is exclusively an inbound firewall, so this does not need to be disabled on the clients. If your antivirus software does have an outbound firewall, you can disable it entirely or set up the firewall exceptions the same way you would for an inbound firewall.
  2. SQL Server Browser is disabled: SQL Server Browser is a component of SQL Server 2008 Express R2 that is installed on your server computer. To check if it is disabled on your server computer go to Windows Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Server Configuration Manager. Click on SQL Server 2008 Services. In this screen you will see SQL Server Browser. Make sure that its state is Running and its start mode is Automatic.
  3. TCP/IP is disabled for the SQL Server instance: To check if it is disabled on your server computer go to Windows Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager. Expand SQL Server Network Configuration and select the Protocol for [instance name], i.e. CMJ. Make sure TCP/IP says Enabled. If it does not, right-click on it and select Start. Then go back to SQL Server Services and right-click on the SQL instance and select Restart.
  4. Miscellaneous SQL Server 2008 problems: Certain errors with SQL Server 2008 R2 will cause clients to be unable to connect. If this is the case, all client computers will be unable to connect. As a last resort and if you are absolutely sure that you have a backup of your database, then you can uninstall and reinstall SQL Server 2008 R2 on your server computer. If you do this you will need to restore your backup onto the server computer once the new SQL installation is complete to retrieve all of your data. An article with instructions to reinstall SQL Server 2008 R2 can be found here.
  5. SQL Server Browser cannot start: Very rarely SQL Server Browser cannot start after reinstalling, or a computer cannot accept inbound connections. If this happens you can make a different computer in your network the server computer and reconfigure each of your clients and your previous server to connect to the new server. Click here for instructions.

Did you find this article helpful?