Matt,

First, something went wrong with your post. The "Response" link takes me to www.greyhound.com. Somehow your URL got mixed in with Revelation's HTML. Therefore I created a new post to respond.

When we've seen dodgy GFEs in the way you have described them then we suspect bad clusters or bad RAM in the server. You seemed to have ruled out he former.

To confirm the validity of the GFEs we move the files to a local machine and run our tests. If they are clean on a local machine but not clean on the server then you have a bonafide phantom or semi-pseudo GFE problem. Remember, these can become real GFEs if the source of the problem isn't fixed, which seems to be happening to you.

[email protected]

SRP Computer Solutions, Inc.

Don,

First, something went wrong with your post. The "Response" link takes me to www.greyhound.com. Somehow your URL got mixed in with Revelation's HTML. Therefore I created a new post to respond.

Well, that's just my nefarious attempt to drive up traffic to our website and maybe increase ticket sales. *grin* Seriously, I left off one of the closing tags, my apologies.

When we've seen dodgy GFEs in the way you have described them then we suspect bad clusters or bad RAM in the server. You seemed to have ruled out he former.

I don't think I've ruled out the former completely. It's still in the mix. I'm going to have our server gurus run a plethora of diagnostics on the box to see if any subsystems are failing.

Also, I think the other post about the virus engine might be dead on target. With the big push to update our virus DATs, they might have changed the config or some-such. Or it's possible they were just doing a very aggresive scan on the server to make sure it was clean. Either way, I'm going to have a serious talk with our McAfee EPO administrator.

Thanks for all of the ideas guys, it's greatly appreciated. BTW, the system seems stable today. No GFEs, phantom or otherwise.

[email protected]

Greyhound Lines, Inc.

I've had an ongoing phantom GFE problem with a client, and every time, it has turned out to be either a network card or a cable run too close to a florescent light. They had their network guy come out and put a sniffer on. The bad packets were causing trouble with AREV, but not anything else. The problems also caused an index on a trans file (4 part key) to fail fairly often, and it was a long rebuild. Every great now and then, another index would fail or they would get a Link-List error.

They are in Chicago, and get quite a few lightening storms, which I think accounts for the high failure rate of the cards (1 every 6-9 months or so).

Larry Wilson

[email protected]

I had cust with 1-2 phantom GFEs/day.

After several months of messing about I logically determined (guessed) that it was memory in server. I suggested upgrade.

Client upgraded to IBM server with 1 GB and phantom and real GFEs went away.

(more detail in postings about 1-2 years ago)

View this thread on the forum...