Troubleshooting Contributions and Check In Applications
KBA-01611-Z4X1Q6
Purpose & Scope
Troubleshooting Contributions and Check In Applications
Procedure

There are several important configuration steps are helpful to know when installing and using Fellowship One Check-in and Contributions.  These issues include slow performance and Check-in or Contributions not being able to get past "Checking for Updates".


The following steps are the most common issues that churches encounter:

  1. Ensure that previous versions of Fellowship One Check-in®  has been properly uninstalled and latest version has been installed.
  • Go here to install the latest version of Check-in
  1. If using v2.5, ensure that Check-in is installed in the correct directory (C:\FT\Fellowship One Check-In)
  2. Ensure that the Window’s User account used to sign in to the computer has been assigned full Administrative rights to the installation directories and sub-directories either by assigning Administrator rights directly to the User or to a Group of which the User is a member
  3. Ensure that the proper .NET Framework is installed.

Check-in: Check-in requires the installation of .NET version 2.0. 

  • For Windows Vista and Windows 7 the installation of .NET 2.0 and 3.51 are performed by enabling them in Window’s features area using the Programs and Features Application on the Windows Control Panel.
  1. Ensure that the computer date, time and time zone are correct.
  2. For Check-in, ensure that you have the latest printer driver for the Label printer.  This can be found on the manufacturer’s website. Do not use the one that is on the manufacture’s CD since those are normally out of date.If you are using the USB connection instead of the parallel port for connection of the Check-In tag printer, you will need to install the proper USB printer driver for your printer. If you are using the LPT port you do not need to install a printer driver.
  3. Ensure that the Background Intelligent Transfer Service (BITS) is set to Automatic and is started. Some anti-virus/firewall packages disable it. It is the same service that Windows uses to install Windows updates. It can be Stopped and Started from the Windows Management Console and under Services. It should always be set to Automatic Start and should be started.
  4. For Windows Vista and Windows 7 and 8, ensure that the Windows User Access Control (UAC) is turned off.  This is located on the Control Panel under User Accounts. In Windows Vista turn it off by unchecking the box. In Windows 7 slide the slider to the bottom to "Never Notify".
  5. Ensure that your Network Firewall, Internet Content Filter, and any routers (wireless and wired) have the correct IP address exceptions for SSL (Port 443) and HTTP (Port 80).

Add the following SSL and HTTP exceptions on your network firewalls and content filters:

Here is the IP range in various forms since some devices accept IP ranges in various ways:
136.179.1.0/24
136.179.1.1 - 255.255.255.0
136.179.1.1 - 136.179.1.254

If you are using a true Proxy Server it is also advisable to add an exception for the Proxy for *.fellowshipone.com or at a minimum checkin.fellowshipone.com

  1. Ensure that the Ethernet ports between the primary router and primary switch have matching duplex configurations. Do not set the ports to Auto Duplex. It is also advisable to do this between the primary (core) switch and its downstream switches. Duplex settings between switch to switch and router to switch should be hard set to Full Duplex.
  2. Ensure that all Windows Updates have been installed.
  3. Ensure that your anti-virus software, the Windows firewall or some other application is not blocking the applications. Many firewall products will require that exclusions be made for directories or application that need to be allowed to pass data. This can happen often with non-Windows firewalls.



Downloads:

Contributions App Install Troubleshoot guide.pdf
Check-In App Troubleshooting Guide.pdf






 

Additional Comments