FAQ

KATS FAQ'scanine software command canine kats canine management database report

KATS FAQs

Installation FAQs

Common Issues


1. Recommended minimum requirements for SERVER/CLIENT/DESKTOP Installation of KATS Generation 4 include:

  • .NET Frame Work 2.0 installed
  • 256 MB of RAM (Recommended - 512 MB)
  • Processor Speed: 1.5 GHz, any processor
  • Hard Disk : 1 GB of available space

For the Client-Server Installation, Registering the application on server by running the application is mandatory before the Client machines run the application.

Supported Operating Systems: Windows XP, Windows 2000, Windows VISTA

2. Registration Error - This error only happens for one reason.  The information you have entered is incorrect.  The spelling, capitalization, punctuation and spacing must be EXACTLY as it shows on your KATS Generation 4 License.  If in doubt, backspace over each entry and re-type the information into the system.

3. Installer cannot find files - You are using the wrong file to do the install. The proper file is called Setup.exe.  The katssetup.exe file you see in the installation package is one of the numerous file packages the installation file needs to complete the install of the various components of the system.  Some systems were having difficulty with pathing issues on the intial release of KATS. Those issues were resolved with a new install build uploaded to the KATS Website on April 18th, 2007. You can download the new installation packages here.

4. Network Installation - When installing on a network, install KATS™ on the server first.  Select the Server installation button when prompted by the KATS™ Installation procedure. When installing on the clients, select the client button when prompted.  The system will provide you a browser window from which to select the path to the location where the KATS database information is stored.  The path should be similar to: \\ Server\KATS40 directory\configdb\config\kats.config

5. .NET Compatability Issue - There is an issue with v2.0 of .NET that Microsoft released subsequent to
v1.1 in that it was not made to be backwards compatible.  KATS Generation 3 was
developed using v1.1.  If v2.0 is installed, the training side of Generation
3 ceases to function properly.  The .NET issue is not only a problem with
KATS, but with many programs that were created under v1.1 of .NET.

KATS Generation 4 was created using v2.0 of .NET and is installed on your
system by the KATS Generation 4 installation process.  Therefore you need to
export your records from Generation 3 before installing KATS Generation 4 on
your system in order to maintain the integrity of the training side of
Generation 3 so it can do the export properly.

In order to do a full and complete export from Generation 3 and import into
Generation 4 you need to follow these steps in this order:

    1. Export your records from Generation 3 ensuring that the "Export All
    Records" box is checked at the time of export.  Generation will create a .KAD file
    which you need to store safely away.

    2.  Install KATS Generation 4 on your system as per the instructions.

    3.  Go into the KATS Generation 4 Records Maintenance system and import and
    browse to the stored .KAD file.  Check of the boxes for all handlers you
    need to import and import the selected records.

    If you have already installed KATS Generation 4 on your system you can
    remove v2.0 of .NET from the Add and Delete Programs menu in your control panel,
    then reboot your computer. This will drop you back to v1.1 of .NET which will
    still be on your system.  Do step 1 above, then re-install v2.0 of .NET which you
    can download from Microsoft's website  here.

6.  System - Attempts to re-install when desktop icon clicked - Problems with the system trying to re-install itself when the KATS shortcut is clicked on is a user logon issue and usually occurs in the case of Windows VISTA.  It may also occur on some other systems as well. To get the program to execute normally, create a new icon by going to the KATS40 directory and locating the K9ApplicationPrototype.exe file.  It will be 3,820 kb in size.  Right click on that file to create a new shortcut and drag it to your desktop or use the "Send to Desktop" option to create the shortcut.  Make sure you are signed on so that it is applied to all users.  If you wish, you can then change the actual appearance of the icon to the original icon in the KATS40 directory.

You may also want to rename the application to KATS and delete your original desktop icon.  This is an issue with the user settings and we are presently preparing a fix for it in our next release.

7.  Records from Generation 3 are not showing up in Generation 4 - KATS Generation 3 had a feature where the system remembered the last point you exported from and set pointers so that you wouldn’t have to export information you had already exported. This allowed the system to export quickly as it would only export information that had not already been sent. In some cases, officers export the system more than once, which sets these pointers where there are no more files to export.  In order for you to export all your files there is a selection box that says EXPORT ALL FILES that must be checked.  Ensure that box is checked when you export.  You will find that box in the export screen on most KATS Gen 3 systems.  If you are running an older version of KATS Gen 3 that box is hidden.  To bring it up, hold the ALT and the A keys down together when you are in the export screen and it will bring up the export all files box for you.  Place a check in the box and then export your records. Another issue is that the deployment tab was skipped over when the user is filling out the incident record. The deployment tab is a mandatory screen, as the team name in this field determines who all the information in that incident is assigned to. With no team name saved in the deployment field, the information will not come across.

8. Team name is not showing up in the activities drop down box - In every incident it is imperative that the deployment tab be utilized. This deployment tab is where the system identifies which team is related to the activities in this incident.  If you do not open the deployment tab, ensure your team name is in the box and click on the SAVE button, then the information will not carry through to the rest of the system.

 

Copyright 2008 - Eden Consulting Group