GFE'S After Installing Revelation NT Service (AREV Specific)
At 07 NOV 1997 09:34:19PM Ed Bell wrote:
In August I installed a new NT server with 20 Win 95 workstations. My server is a backup domain server in a WAN for a local municipality.
My server is running CRIS by Megg Associates and is used for law enforcement records management. I immediately started getting GFE'S. On Sept 24 I installed the Revelation Service and the GFE's stopped for 35 days. The day before the GFE's started again we moved our server and 15 of the workstations into a new building. As a part of this move my server is connected to a 3Com switch on it's own segment on the WAN. My workstations are on a different segment. It is my understanding that the switch should only forward the TCPIP address from one of the segments to the appropriate segment that my server is on. Does anyone know of any problems with running AREV on two different segments of the network through a switch? The GFE's appeared one day after the move and this is the one major difference I can see in the network topology. I put the revparam file in each folder with Linear Hash files and set it to serveronly=true. How about FlushFileSizeUpdates and FlushAllUpdates? Should these settings be added to the Revpa
ram file set to True while using Win95?
At 10 NOV 1997 11:15AM Victor Engel wrote:
We had a similar problem here resulting from SAP filtering causing packets not being routed between the workstation and the NLM. Although we were able to see the files we needed, no communication with the NLM was established. Network services adjusted the filtering appropriately so that the packets went through completely. Setting the serveronly variable in the revparam file enables Arev to detect when this occasion occurs again (which it has). Since getting all the kinks involving this filtering worked out, we have not had a single GFE since installing the NLM, that I am aware of.
Of course, using an NT server, an NLM would not apply, but I think the filtering would still be an issue for you.
At 12 NOV 1997 06:02PM Tracy Graves wrote:
hi Ed-
I just read this AFTER reading your other post…
Still though, SAP filtering is definitely not the issue.
Also, everything that you are trying to do shouldn't have a problem (as
far as network topology, etc.
Make sure all copies of AREV are using the NPP.
You might want to try disabling any cacing in the REVPARAM file…
Other than that, I don't know.
Tracy
At 02 JUN 1999 04:41PM Kathy Parrow wrote:
Excuse me for asking but what does GFE stand for?
At 02 JUN 1999 05:24PM Warren wrote:
GFE=Group Format Error
or according to one wag on CompuServe (I forgot who): Gone ForEver
Files in Revelation and Advanced Revelation are divided into groups or frames of a fixed size. Records are "hashed" or placed into groups determined by a "hashing algorithm" based on the key and modulo (number of groups) of the file. If the group is filled or the record is larger than the remaining space in the frame any number of overflow frames are appended to the file. Each frame contains header information that points to and where applicable the next or previous frame in the group chain. Records are also stored with record length information and a end-of-record marker. There is also a end-of-frame marker.
Group Format Errors occur if the forward/backward frame pointers are n incorrect or the record length does not match the actual data or the frame header has been corrupted.