If an error message is given, stating “Data Invalid. One or more data files are missing or damaged. Do you wish to open another database?”, then press Cancel.

In this case, the database is corrupted, so zip all the database files (about 65 dbf and cdx files) and e-mail it to info@iccs-ltd.co.uk for fixing.

[Back to Index]

1.2 Software Not Registering Weights From Balance

When an operator puts a product on the balance, the weight is not accepted by the software.

1.2.1 Solution:

Make sure that the balance is configured to “Send Continuously.”

Make sure that the balance is configured correctly in
Data Entry Configuration Balance.

Make sure that settings are sensible in Data Entry Options Workstation Options:

i.e. Minimum Weight (default 20 g)

Maximum Difference (default 0.001 g)

No. Readings for Stable (default 2)

Make sure that the product being sampled is defined correctly:

i.e. Correct spec / plausibility limits, correct Tare Type.

If the balance in connected via a serial-to-USB cable, and a message similar to “Bad ID : Comm port not recognised” is displayed, then unplug and replug the balance from the workstation, or reboot the workstation.

[Back to Index]

1.3 Cannot Connect To Database In A Client-Server System

When the system cannot find the data, in the case of adding a new workstation, or installing new software.

1.3.1 Solution:

On the server, start CodeBase Administrator by pressing the Start button then selecting:

Programs CodeBase 6.5 CodeBase Administrator.

Press Connect.

Select Server Settings… and make sure that the Default Directory shows the path on the server to the database.

Press OK, then File Exit.

Start the ICCS software – in the Configuration window, make sure that the Data Path is blank, the Server ID displays the name of the server PC that holds the database, and the DBUsername and DBPassword fields are blank.

[Back to Index]

1.4 Missing Data

When the system seems to be working fine, but data is missing from the MIS.

1.4.1 Solution:

Press the refresh button to see new data.

Make sure that the Filter is configured correctly.

Make sure that View Exceptions Only is not selected (QCpro v5).

Make sure that Show Setup Data is selected.

Re-index the database.

[Back to Index]

1.5 Database File Locked When It Shouldn’t

When attempting to perform sampling of a test plan, the system reports that the test plan is already running, or a file is locked, even though no other user is using that test plan.

1.5.1 Solution:

This usually occurs because a workstation PC that was using the test plan either crashed, or was shut down without exiting the ICCS software.

Either restart the CodeBase Database Server service, or wait about 2 to 8 hours for the locks to disappear automatically.

[Back to Index]

1.6 Dongle Missing For Hundred’s of Days

When attempting to start ICCS software, the message “Dongle has been missing for (very many) days” is displayed, and the user cannot get past the database configuration screen.

1.6.1 Solution:

This occurs when the dongle is either “dead”, or removed from the system, or the wrong dongle is present. If there never was a dongle, the system would be a “Demonstration System”.

Check that the dongle is a Sentinel Super Pro dongle for PharmAssist v5, QCpro v5 and InLine QCpro. DOS software uses a Sentinel Pro dongle.

Check that the dongle’s 5-digit code number on the label is the expected one.

Check that the dongle is attached to the correct PC.

Check that there are no other unnecessary dongles attached.

Check that the network is OK.

Check the date and regional settings of the PC’s are correct (British date format).

Check that parallel port is working.

Delete the 7 wa*.* files from the database and start the software – if “Demonstration System” appears, then the dongle is not being read – check that the dongle has been programmed correctly for the software being run.

Check that the correct dongle code has been entered for support, users, etc.

Check that the dongle drivers are present, i.e. the ICCS software was installed correctly and not using a “wrap” that missed these drivers.

[Back to Index]

1.7 Thin Client’s Freezing

In a thin client system, workstations may freeze.

1.7.1 Solution:

On the server, access Terminal Services Configuration and select Sessions. Make sure that “End a disconnected session” is “Never”, and “Allow reconnection” is “from previous client”.

Attempt to reconnect – should be able to normally if disconnection due to busy or interrupted network.

This may also be due to the way thin client works (“constantly cycling themselves”) – a solution is to “turn off and back on” the thin client PC’s. It is enough to reboot these PC’s once a day.

[Back to Index]

1.8 CodeBase Administrator Will Not Start After Installation

After installing CodeBase, the Administrator will not start and displays a message “Runtime error 429 – ActiveX component can’t create object”. This will stop the user configuring CodeBase Administrator.

1.8.1 Solution:

In order to configure CodeBase Administrator, a Command Prompt can be used.

Go to the CodeBase Server installation directory, e.g. C:\CodeBase\Server.

Type s4edit s4server systempath c:\codebase\server

then s4edit s4server defpath c:\iccs\qcpro\data (path of the database).

Also: CodeBase error (-2110).

Data folder (and path) needs full (read/write/etc.) permissions enabled for System User.

Is the data path too long?

Does the data path have spaces in it?

[Back to Index]

1.9 Check Flush Error / CodeBase Error (-1)

ICCS software crashes stating the error code above.

1.9.1 Solution:

Stop all workstations running the ICCS software and stop the CodeBase Database Server service. Re-index the database using Database Update Utility. Start the CodeBase service again.

[Back to Index]

1.10 Corrupt Data / CodeBase Error (-200)

Database Update Utility crashes during a re-index, stating the error code above.

1.10.1 Solution:

Database must be repaired by ICCS.

[Back to Index]

2 Interbase Systems

2.1 Largepack Not Capturing Data From Filler

Data is not collected by Largepack from the KHS-Till filler.

2.1.1 Solution:

Customer needs to run the IntfCheck script to see whether Largepack has processed all data supplied by the KHS-Till application.

[Back to Index]

2.2 ICCS Software Unusually Slow Or Not Launching

ICCS software appears to be ridiculously slow or doesn’t even launch; it just hangs.

2.2.1 Solution:

Press CTRL+ALT+DEL on the server to start Task Manager. An antivirus update may be using nearly 100% of the processor.

[Back to Index]

2.3 Interbase Products – PlantSTATS, LargePack Running Slowly

2.3.1 Solution:

One reported fix was to backup and then restore the database using the Interbase backup and restore utilities.

[Back to Index]