Home   •   Support  •  CD Products  •  Technical Support  •  Troubleshooting CA on CD and CI on CD

Troubleshooting CA and the Collective Indexes on CD

The CA family of databases on CD-ROM (CA on CD and Collective Index or CI on CD) can be installed for

• a single user
• for multiple users on a network.

A network or client-server installation with a Windows server is described here as an example.

General Information

• CA on CD and CI on CD are shipped with booklets that contain valuable information about hardware and software requirements, appropriate server choices, and installation instructions.
• There are a minimum of two computers involved in a network installation.
  • The file server holds the database files and shared software folder and makes them available to client computers. 
  • The client computers on the network provide access for searching.
  • In addition, the license server may be the same computer as the file server or a different computer. The most common installation uses a single computer as the file server, license server, and shared software server.
• All of the CA family databases use the same software. Therefore, there must be a single shared software folder on the server.
• CA on CD starting with 1998 and CI on CD starting with 10CI, including 12CI (reissued) but not the original 12CI, employ a hardware key and associated license manager software to control the number of simultaneous users. 1996 CA on CD and 1997 CA on CD do not require the hardware key. However, if later versions of CA on CD or any version of CI on CD are installed, 1996 and 1997 will use the newer software and the hardware key. 1996 and 1997 should be installed before any of the others.
• The license server must have the hardware key attached to its USB Port. The license server runs the NetHASP License Manager software.
  • CD installations beginning with the January 2007 issue require new Hasp License Server software and drive installation on both the license server and on each client computer.
  • Download the Driver Installation Instructions.
• The database files may be copied to hard drives (recommended) or left on the CD-ROM discs. In any case, all database files must be simultaneously available to clients on the network.
• UNC path names are strongly recommended.  The use of the older mapped drive letter paths may lead to database and HASP license errors.

Example Configuration

Consult the Installation Instructions before installing the databases and software.

In this configuration, we have installed 2007 CA on CD and 14th CI on CD with Abstracts. Configuration details:

    File server name:                 cdserver
    File server operating system:     Windows 2000 or newer
    License server name:              cdserver
    License server operating system:  Windows 2000 or newer
    Shared software folder:           \\cdserver\silo\cacdnet
    CA on CD database location:       Copied to hard drive on cdserver
    13CI database location:           Left on discs on the computer named tower
    Client operating system:          Windows 2000 or newer

The shared software folder contains the client application program and some important files.

• cacdpath.ini on the server, describes the installed databases to the client application.
• nethasp.ini on the server, describes and locates the license server to the client. 
• log.txt contains a history of server installations and updates.
• If you contact CAS Software Support, you'll probably be asked to send these files.

The client application is installed by navigating to the CA on CD server from the client and then running netuser.exe. This program is stored in the shared software folder. The client installation completes very quickly and installs some fonts, makes a change to win.ini, and creates the client application folder (c:\cacd by default). The client application folder contains the files

• cacd.ini
• log.txt.
• If you contact CAS Software Support, you'll probably be asked to send these files.

Causes of Common Problems

• Many CA on CD and CI on CD problems are caused by incompatibilities within cacdpath.ini or between cacdpaqth.ini and cacd.ini located on the client computer.
• The paths in cacdpath.ini must be accessible to the client. For example, if the path to a database is s:\ciab13a, then the client must have drive S: mapped to the proper location. Not only that, but each and every client must have drive S: mapped to that location. The use of UNC path names will eliminate this problem.

---

For answers to questions or help with issues not addressed here, contact

• CAS Customer Care for How To Use STN Express
• CAS Software Support Team for Technical Issues