Hi,

I have a GFE in the OS file RevMedia.OV in one of my volumes that is stopping me from adding further tables to the volume. (I get a GFE error screen saying "…Invalid frame type value.")

Any ideas on how I can fix this? The error screen says that the corrupted table is called "???", so I can't run FixLh on it.

Many thanks,

Andrew.

Easiest way is to create a new blank file (TEMP) in the volume with the problem and note the REVnnnnn.* details. SETALIAS LOCATION SYSPROG REVMEDIA REVMEDIA then COPYROW REVMEDIA * TO:(TEMP then delete the REVMEDIA and rename the REVnnnnn.* as REVMEDIA.*.

Back up first IMG height=12 src=http://64.4.18.24/emwink.gif" width=12]. One word of warning - that can occur when backup operations (normally ArcServe) run with AREV running.

The Sprezzatura Group

World Leaders in all things RevSoft

Andrew ..

Your best bet is to restore REVMEDIA from a backup. Unless you add a lot of tables all the time, it should probably be pretty close. You can then Add / Remove or resolve any discrepancies. The easiest thing to do is to print the REVMEDIA contents and then do a DOS DIR on the volume. Match up the REVnnnnn.LK / OV entries witht he map. Anything present in DOS needs to ba added to the map. Anything in the map that is not in DOS needs to be removed from the media. To do this, use an editor to create empty files with the correct dos names and then delete the entry from the TCL. Adding existing files to the map is a little more difficult. There are several utilities that will let you do this. If you need one, let me know.

Don C. Miller

C3 Inc.

Thank you both (or should it be "all"),

I managed to "SetAlias" the table and then "FixLh"'ed it.

Cheers,

Andrew.

I suggest you create an online backup of the pair of files that are REVMEDIA in each directory. Don't just call them BAKMEDIA.* since you would have the same name in each directory. I name them after the sequence established in respective directory, e.g. BAK73000.*.

Not only have I had GFE in REVMEDIA, I must admit I've copied REV*.* from one directory to another and whoops, wrong destination!

Dave

Can you list the exact instructions for creating a new REVMEDIA temp file, and renaming/replacing the old bad REVMEDIA with that new temp file?

We've got GFEs in two different AREV accounts and when we create the new temp file with the same properties and replace them on the server, AREV won't startup. It kraps out at launch with "Unable to read boot media map."

Replace the new REVMEDIA.* files with the old one we know contains a GFE, and AREV launches fine again. It seems like such a simple process but we're obviously missing a step somewhere. Detailed steps might pinpoint what step we're missing.

thanks,

dEVoN

If you're sure it's a GFE, then fixing them is the same as in any other file. The devil is in the details, as they say, and the detail in this case is gaining access to the file.

There are two ways to gain access to a REVMEDIA file. The first method only works from the SYSPROG account. You simply attach the file as a file in it's volume. For example, if your REVMEDIA file is in the MARKET volume, then you would just enter

ATTACH MARKET REVMEDIA

and the file is attached. Once attached, the REVMEDIA file is an LH file, just like any other.

The second method works from any account. To use this method, you set an ALIAS or QPOINTER to the file. Using the example from above, enter

SETFILE MARKET SYSPROG REVMEDIA REVMEDIA

Remember to use the password option if SYSPROG is password protected.

Now that the file is attached, you can DUMP and fix the file as required.

The Sprezzatura Group

World Leaders in all things RevSoft

The GFEs we have are in REVBOOT REVMEDIA. I've already tried fixing it with typical methods to not success.

]ATTACH REVBOOT REVMEDIA

]FIXLH REVMEDIA

Or fixing it from the DUMP display with ctrl+f.

The problem is DUMP doesn't show any GFE in the 5 primary groups this REVMEDIA file has. The problem stemmed from trying to REMAKETABLE on SYSTEMP to make it bigger and that failed because of a GFE in REVMEDIA in group 2. Dumping REVMEDIA shows no GFE in group 2. VerifyLH displays the following error:

"Group: 0; Code: 5; Description: Initial setup failed!! Overflow frame header type is incorrect"

Respectfully, this is why I was requesting the exact steps you have used successfully to create a new temp file and replace the REVMEDIA.* files with that newly created temp file.

thanks,

dEVoN

If DUMP does not show a GFE, you can probably do the following:

[list]

[*]Create a new file in REVBOOT

[*]Dump the new file to identify the file name

[*]Attach REVBOOT REVMEDIA (or setfile to it if not logged onto SYSPROG

[*]Copy all rows from REVMEDIA to the new file. If you get an error as you did before, perhaps you can continue on past the error.

[*]Make sure no users are logged in. You may need to down the NLM if you use the NLM, but I'm not sure about this. The reason for this would be to get it to reload any cached REVMEDIA information.

[*]Rename REVMEDIA.* to something else

[*]Rename REV#####.* to REVMEDIA.* (where ##### was identified above)

[*]Restart NLM if it was shut down.

Perhaps a simpler solution to your problem, though, would be to restore your REVMEDIA.* files from backup. They should not have changed unless you have made changes to file definitions (recreate, create, delete).

Alternatively, you could sleuth out the problem with the overflow frame and fix it with the DUMP editor.

Those exact steps (including shutting down the NLM and restarting it) were attempted a couple of time with the same failed results. That is, trying to launch AREV results in the error…

"Unable to read boot media map."

We've tried replacing the 'REVMEDIA' file with new files of exactly the same parameters and nothing seems to work. We always end up with the above error.

A really interesting data point, although we're not sure how to replicate it, is there is a size difference in the old and new files even though they were created with the same parameters and contain the same data. The current REVMEDIA with the GFE in it has the following file sizes:

 REVMEDIA.LK    262,144 bytes

 REVMEDIA.OV    262,144 bytes

The new REVXXX file we created with the same parameters and containing the same copied rows is:

 REVXXXXX.LK    262,144 bytes

 REVXXXXX.OV    0 bytes

Dumping the bad REVMEDIA with the GFE shows no overflow frames in use. So why is there exactly the same number of bytes in the .OV as in the LK? The answer could easily be related to the fact that VERIFYLH results show the GFE error as 'Code 5; Initial Setup Failed! Overflow frame header type is incorrect.' Which brings us back to the original posted question of how this can be fixed.

If any one has any steps that might work to replace the REVBOOT REVMEDIA.* files, we would greatly appreciate it.

thanks,

dEVoN Hubbard

BenComp National Corp.

Are you sure you did a:

REN REVxxxxx.lk REVMEDIA.LK

REN REVxxxxx.ov REVMEDIA.OV

and not a:

copy REVxxxxx.lk REVMEDIA.LK

copy REVxxxxx.lk REVMEDIA.OV

or something similar???

What happens if you copy the saved version of the presumably broken REVMEDIA file back? Do you still get the error message when trying to start ARev?

Also:

Are you loading the LHIPXTSR prior to starting ARev?

Was LHIPXTSR loaded into memory on any of the workstations when you restarted the NLM? I found that LHIPXTSR is loaded somewhere and communicating with the network before the NLM was loaded I'd get the error message you mentioned. It's best to make sure all the LHIPXTSR stations are at least logged out from Netware before restarting thr NLM.

The error message in question is usually caused by the LHIPXTSR not communicating with the NLM for whatever reason, typically due to frame typing in the Ethernet bindings.

Finally, as suggested before, why not just restore the REVBOOT REVMEDIA.* files from a backup? Unless you've renamed, recreated files or added or deleted an application/account the REVMEDIA file should not have changed.

Here is exactly what we have tried with no success…

1. Disable logins (this is a netware server).

2. Create a new table in REVBOOT with the same '1 1 1 1028' parameters as REVMEDIA. Specifically, '1 1 1 1024 80'. For example, REV42111.LK & .OV are created.

3. Logout of AREV. Logoff any other AREV sessions that are running.

4. Shut down LHIPXSER.NLM and LH.NLM

5. Rename REVMEDIA.LK and .OV as REVMEDIA_bad.LK & .OV, respectively.

6. Rename REV42111.LK & .OV as REVMEDIA.LK & .OV, respectively.

7. Restart the LH.NLM and LHIPXSER.NLM

8. Launch AREV application to try and log back in.

Results is the 'Unable to read boot media map'.

To get logins working again…

1. Delete the 'REVMEDIA.LK and .OV file.

2. Rename 'REVMEDIA_bad.LK' and .OV as REVMEDIA.LK and .OV, respectively.

Again, the REVBOOT REVMEDIA file has that shows up by VERIFYLH but does not in a DUMP.

Also, every REVMEDIA file we have tried from backup tapes has this GFE in it. It's had to have been on our system for at least 6 months or more. We don't have backup tapes further back than that, that haven't been cycled over.

Why is it so difficult to repair and/or replace REVMEDIA?

thanks,

dEVoN

REVMEDIA is no different than any other file. It's just attached differently. REVMEDIA is attached directly, whereas other files are attached using REVMEDIA to look up what name to use. Other than that, they are the same.

As far as that goes, you should be able to attach REVMEDIA and then EDIT REVMEDIA REVMEDIA_STUNTDOUBLE*SYSPROG enter REVMEDIA on the top line. Then you can attach REVMEDIA_STUNTDOUBLE and use it like any other Arev file.

As to why VERIFYLH finds an error and DUMP doesn't, I can't say because I don't know how VERIFYLH works. A possible explanation might be that DUMP accesses the files directly using something akin to OSBREAD/OSBWRITE, whereas VERIFYLH uses some combination of that and going through the NLM. If communications are a problem, you would then get an error in VERIFYLH but not DUMP because the file is actually good but the data does not get to VERIFYLH as expected.

Note that this is speculation on how VERIFYLH works. Confirmation/rebuttal by someone who knows better is appreciated.

Try this:

Create a folder say F:\fixit

From ARev SYSPROG at TCL:

NAMEMEDIA F:\FIXIT

MAKETABLE - parameters:

- Tables possible you're loosing file descriptors. Hopefully these will turn up in SYSTEMP and can be edited back into . Once you've cleaned up any missing descriptors, copy the REVxxxxx files corresponding to over the REVMEDIA.* files in REVBOOT.

Why is it so difficult to repair/replace?

1) As I recall, DUMP Fix on SYSALIAS files doesn't work to begin with since it involves creating a temp file and renaming it when done and gets lost in the reattach process. Although this may have changed in later versions of ARev

2) Obviously the REVMEDIA file is vital for the functioning of ARev so ARev will be overly 'sensitive' to anomolies in this file.

Here's a list of the contents of my REVBOOT REVMEDIA for 3.12. I removed the most obvious 'mine only' files but a few may still remain or some that are left overs from upgrades or add-ons with optional features.

Typically you should have one REVxxxxx pair (.LK & .OV) for each entry in the REVMEDIA file. Exceptions - a .OV may be missing - this is sort of okay because the ARev filing system will create the .OV as needed. Synonym file descriptors - same REVxxxxx, different file/application name.

Note: the REVxxxxx numbers here in all likelihood will not correspond to what is on your system. I left them in as I'm too lazy to edit it out.

CUSTOMER_COMMENTS         GLOBAL          REV46033                    
DICT.CUSTOMER_COMMENTS    GLOBAL          REV46004                   
DICT.FILTERS              GLOBAL          REV46006                    
DICT.IMPORTEXPORT         GLOBAL          REV46352                    
DICT.LABELS               GLOBAL          REV46008                    
DICT.LOG                  GLOBAL          REV46326                    
DICT.MERGES               GLOBAL          REV46011                    
DICT.MESSAGES_OLD_1X      GLOBAL          REV46232                    
DICT.MRG_PRINTER_CONFIG   GLOBAL          REV46013                    
DICT.QUERIES              GLOBAL          REV46015                    
DICT.REVMEDIA             GLOBAL          REV46016                    
DICT.SYSCOLUMNS           GLOBAL          REV46243                    
DICT.SYSKNOWLEDGE         GLOBAL          REV46359                    
DICT.SYSLHGROUP           GLOBAL          REV46311                    
DICT.SYSLHVERIFY          GLOBAL          REV46312                    
DICT.SYSMENUS             GLOBAL          REV46031                    
DICT.SYSMESSAGES          GLOBAL          REV46234                    
DICT.SYSPOPUPS            GLOBAL          REV46017                    
DICT.SYSPRINTERS          GLOBAL          REV46313                    
DICT.SYSRELATIONS         GLOBAL          REV46356                    
DICT.SYSTABLES            GLOBAL          REV46005                    
DICT.SYSTYPEMAPS          GLOBAL          REV46242                    
DICT.SYSTYPES             GLOBAL          REV46240                    
DICT.SYSVOLUMES           GLOBAL          REV46021                    
DICT.SYSWINDOWS           GLOBAL          REV46003                    
LOG                       GLOBAL          REV46328                    
MESSAGES_OLD_1X           GLOBAL          REV46231        QUICKDEX.MFS 
MRG_PRINTER_CONFIG        GLOBAL          REV46024                    
SYSALIASES                GLOBAL          REV46042                    
SYSEMBEDDED               GLOBAL          REV46236                    
SYSHELP                   GLOBAL          REV46025                    
SYSINCLUDE                GLOBAL          REV46235                    
SYSKNOWLEDGE              GLOBAL          REV46357        SI.MFS      
SYSLHGROUP                GLOBAL          REV46315                    
SYSLHVERIFY               GLOBAL          REV46316                    
SYSMENUS                  GLOBAL          REV46026        QUICKDEX.MFS 
SYSMESSAGES               GLOBAL          REV46233                    
SYSNETWORKS               GLOBAL          REV46030                    
SYSOBJ                    GLOBAL          REV46001                    
SYSPOPUPS                 GLOBAL          REV46027        QUICKDEX.MFS 
SYSPRINTERS               GLOBAL          REV46317                    
SYSTEMP                   GLOBAL          REV46329                    
SYSTEXT                   GLOBAL          REV46318                    
SYSTYPEMAPS               GLOBAL          REV46241                    
SYSTYPES                  GLOBAL          REV46239                    
SYSVIEWS                  GLOBAL          REV46237                    
SYSWINDOWS                GLOBAL          REV46002        QUICKDEX.MFS 
SYS_DBASE_BOND            GLOBAL          REV46248                    
SYS_QUERY_COLUMNS         GLOBAL          REV46320                    
DICT.VOC_OLD              REVBOOT         REV46087                    
VOC_OLD                   REVBOOT         REV46086                    
BATCHUPDATE               SYSPROG         REV46046        QUICKDEX.MFS 
CAPTURED                  SYSPROG         REV46032                    
DCERRORS_ERR              SYSPROG         REV46090                    
DICT.DCERRORS_ERR         SYSPROG         REV46091                    
DICT.IMPORTEXPORT         SYSPROG         REV46353                    
DICT.TRADEUP_BP           SYSPROG         REV46049                    
DICT.VOC                  SYSPROG         REV46020                    
FILTERS                   SYSPROG         REV46035                    
HELP                      SYSPROG         REV46034                    
IMPORTEXPORT              SYSPROG         REV46036        QUICKDEX.MFS 
LABELS                    SYSPROG         REV46037                    
LISTS                     SYSPROG         REV46038                    
MACROS                    SYSPROG         REV46039                    
MENUS                     SYSPROG         REV46040                    
MERGES                    SYSPROG         REV46022                    
POPUPS                    SYSPROG         REV46041                    
QUERIES                   SYSPROG         REV46043                    
REPORTS                   SYSPROG         REV46044                    
SQL_QUERIES               SYSPROG         REV46319                    
SYSENV                    SYSPROG         REV46028                    
SYSRELATIONS              SYSPROG         REV46355                    
VOC                       SYSPROG         REV46029                    
WINDOWS                   SYSPROG         REV46045        QUICKDEX.MFS 

At one time, Mike Pope published a utility to help rebuild REMEDIA.MAP. It required a certain intimacy with the data files (It would show a few frames of the REVxxxxx file and ask you what it should be named and what account to link it to). Rather tedious with dozens of files. REBUILD.MAP I believe it was called. It maybe in the ALLFILES.ZIP in the download section.

Additionally I have a CLEAN_ACCOUNT utility which compares the contents of each attached volumes REVMEDIA map with the corresponding folder and notes mismatches. However it is up to the user how to resolve these mismatches (either create/delete REVMEDIA entry, or delete/create the REVxxxxx files). I can email it to you if you feel a need for it.

View this thread on the forum...