Hi-

A few weeks ago my sysprog login became corrupted for no apparent reason - I can login OK, but get the following errors as soon as I try to use the 3 main menu options:

1. B161 - The object code for (filename). cannot be found in the SYSOBJ table. (Filename). is also not catalogued. Please enter the name of the table containing the object code for (filename)..

2. W175 - "Filename." cannot be executed. "" is not available.

3. W559 - Cannot continue. An attempt was made to execute a null ("") program.

These errors come up only under the sysprog login - all other logins/users are unaffected. We have Arev 3.12 under Novell and NLM. I have another copy of our application in another office within which the sysprog login works fine - could it be possible to copy the sysobj or revmedia or whatever the relevant files may be to my version here to resurrect this one?

I am very much a beginner with Arev, so would appreciate advice in very basic terms - I have spent many hours looking at this site and quite often come away feeling completely bamboozled and with no idea how to execute the advice given to others!!

My most pressing problem is that i need to add some new users and do not know how to do this other than by accessing the menu within my sysprog account. Could someone please help me to add users via the TCL if this is possible, as a stopgap fix until I can resurrect my sysprog account?

Any advice would be greatly appreciated - and I apologise for my limited knowledge in the prescence of you masters out there in Arev land!

Thanks,

Bridget

Sounds like the VOC file for SYSPROG has been corrupted. Do a DUMP VOC DUMP DICT VOC or a LISTMEDIA to determine the REVxxxx.LK and .OV files for VOC and DICT VOC and restore these from backup.

I would not copy them over from a different copy of ARev as there maybe customizations you'll lose or other differences depending on how the copies of ARev were brought up to v3.12 (i.e. upgraded from earlier versions, trade-up, or 3.12 from the box)

Thanks very much for your help Warren - I did as you suggested and got the dos names for dict voc and voc from within sysprog. As my development version is a fairly recent copy from the runtime version, and it too is corrupted, I am using this as a testing ground.

I do not have a backup that is old enough to go back to, as I'm not sure when this problem occurred. Instead, I then deleted the 4 relevant lk and ov files from my development version and tried copying from an older development copy (no upgrades have been made since the newer copy was made). Sysprog works fine within this version, so I figured the 4 files here would be sound to copy over to where the corrupted files were. Unfortunately this had no effect whatsoever - the same errors come up.

Am I missing something vital - any other possibilities/suggestions?

I would make a subdirectory called BAK under your current directory.

copy all rev0000*.* files to it.

copy all the rev0000*.* files off of your instal diskettes.

If this works slowly move the files back from the BAK directory

until you find the offending file.

Once found, attach the offending file to your system and salvage

what you can. It sounds as if SYSOBJ may be corrupted.

I know this is a little cryptic, but e-mail me or call 330-945-5725

and I will walk you through it.

Good luck, Happy New Year

Do the same with the SYSOBJ file.

Thanks Warren. I've just tried this too - but still no joy…!?

If you have a good backup, try restoring the DOS files that correspond with SYSENV.

View this thread on the forum...