Error Stat % 2--Recurring I/O Errors

Input/Output device errors (Stat 2 on the Platinum error message) usually mean that the indicated file has been damaged. Damage can be caused by a variety of "environmental" factors including hardware, power, static and configuration. File damage often occurs in Platinum and not other programs because of the size of the data files, the number of users accessing them over long periods of time, and the volume of disk write activity occurring during almost every Platinum function. The typical resolution of an I/O error is to use the Btrieve Recovery program provided on Platinum's Utility Menu. In almost every case, the file is "saved" with all records intact. If not, the most recent backup must be restored.

Sometimes, I/O errors seem to recur, often on the same file over and over again, even after it has been recovered. These are very frustrating to resolve. The tendency is to blame Platinum software since the error messages are being reported there. However Platinum software does not contain any code that will cause damage to a data file.

Some factors which must be considered when I/O errors recur are listed below. Each of them has been found to cause I/O errors.

1. If the user has operated Platinum for any length of time without I/O errors, we often find that the incidence of I/O errors begin after a hardware/software change of some sort.

a)Was any hardware service performed?

b)Was any new software installed?

c)Were any workstations added to the network?

d)Were any workstations moved?

e)Was the network or any existing hardware of software upgraded?

f)Has anyone accessed Platinum from a remote location via modem? Have the data file been electronically transferred via modem?

g)Has there been any renovation in the office or building?

h)Have there been power fluctuations in the office caused by weather, new equipment in the building or construction in the area?

i)Does any user exit the programs illegally, i.e. by using function keys or turning off their system without escaping through the menus?

j)When was hardware preventative maintenance last performed?

k)Is the network cable adequately shielded? Does it meet the operating system

specifications?

l)Does any cable run close to a fluorescent ballast?

m) Are they running Virus software?

2. Verify that the FILES parameter in CONFIG.SYS on every station is 60 with Btrieve dated 10/15/91, or 100 with Btrieve dated prior to 10/15/91. BUFFERS should be 50. Remove ALL TSR's.

3. Verify that the F: parameter in NETSTART.BAT is high enough; 55 with Btrieve dated 10/15/91 or 120 with Btrieve dated prior to 10/15/91. Place a /O at the end of the Btrieve line (letter O not #0).

4. Check maximum number of file handles/directories on the network operating system. Raise them by 25%.

5. Check all hardware technical bulletins for upgrade devices or other information about defects that could damage data.

6. Begin methodical process of elimination on the hardware.

a)First try installing Platinum on a local drive and log out of network to test if same

errors occur on a local drive.

b)Replace the network adapter card in the server.

c)Replace the network interface board on the workstations.

d)Check the integrity of all cables and connectors.

e)Perform all disk utilities and other hardware diagnostics.

f)On a rotating basis, exclude one workstation at a time from accessing Platinum.

See if I/O errors occur only when a certain station/user is being used.

NOTE: Be sure that if I/O errors occur that they are recovered and/or files are restored BEFORE the next workstation accesses the data. The test will only be valid if each workstation starts off with "clean Files". On ARCNET topologies, do the same type of process of elimination on each hub.