I am about ready to pull my hair out, and while the bald look is in, I'm not quite ready for it yet.

The system is ARev 3.02 (Ceridian's HR-1), Novell 5.1 with the appropriate NLM, and mostly Win95 (a few 98 and 1 XP) clients.

This morning at approximatley 0800, it was noticed that the indexes on the EMP table were not working correctly. One index had gone completely missing, and another was returning GFEs when you tried to access it. I completely removed and rebuilt the indexes, and this corrected the problem.

Two hours later I began receiving GFEs for the main data table. I ran a verifylh, and over 30 groups were listed as bad. I tried accessing some of the records from those groups, from several machines, and received Fatal Errors on each. First, I renamed the REV files for the table and then copied them back to their "correct" names. This was to "freeze" a file on any bad clusters on the disc in case this was causing the problem. I then ran fixlh on the first 15 groups, and one record from each was written to systemp. After the first 15 groups, the next three did not delete any records. I then re-ran the verify, and the table was "clean." I identified the 15 records that were deleted and was able to restore last night's backup to DEV and move those records back in.

I then re-ran the verify. It showed three groups as having errors. I ran the verify again, and no errors were found. I ran the verify yet a third time, from a different machine (to eliminate NIC, etc. issues), and no errors were found.

Since I have worked here (almost 4 years), we have occasionally had indexes become corrupted, but this is the first time I have seen a GFE. We have used the NLM that entire time. To my knowledge, nothing has been changed on the server or the client configurations. I have verified repeatedly that the NLM is operational on the server and the appropriate REVPARAM files are in all directories with REVMEDIA files.

If anyone has any ideas, thoughts, suggestions, prayers, jokes, cases of fine liquor, or anything else to share, I would greatly appreciate it.

TIA,

msorrel@greyhound.com

<a href=http://www.greyhound.com"

Hard to response:)

Just one tought … the one XP station and the virus active few days ago? … may be the situation in the network is not the same?

How DID you respond? When I tried, I got directed to greyhound's website.

Anyway, I would suggest to Matt to down the NLM and possibly the server and restart. There may be a cache issue.

Hi Victor,

it was chalange:)

Using notepad and clipboard … copy message URL to notepad, check how to response (on another thread) … copy to notepad, replace the ParentUNID. … than use the edited URL:).

There was missing quote in URL http://www.greyhound.com" .

Easier way was to go to document source, correct the bug, and response from corrected copy.

View this thread on the forum...