FS1003, RTP57, Confusion (AREV Specific)
At 12 OCT 1999 07:20:12PM Kristina Ruiz wrote:
Someone here was working in an AREV application, and accidentally started to delete a record she didn't want to. Her solution was to unplug her computer while it was deleting the record, hoping it would stop. As soon as she tried to go in again GFEs popped up (FS127). Rather then try to fix the error I just restored the entire directory form a backup, which I've done may times before with success.
After restoring this time, when someone goes into the AREV application, the screen reads:
FS1003RTP57SYSMESSAGES
FS1003RTP57SYSMESSAGES
FS1003RTP57SYSMESSAGES
FS1003RTP57SYSMESSAGES
IN.MEMORY
]
Pressing Enter five times gets youinto the application, where nobody has had any problem entering information.
When exiting the AREV application the same messages come up, and pressing return a number of times gets you past them. The final message is:
FS1003RTP57SYSMESSAGES
W170]
So OK, I decided to try to fix the GFE. When I run VERIFYLH on one or all tables I get the same numerous FS1003, RTP57, and SYSMESSAGES errors.
What do I do now?
At 12 OCT 1999 07:54PM Warren wrote:
Did you have to restore the ARev directory or some other directory?
Were all users out and files closed when you did the restore and did you overwrite ALL files in the directory or was it an incremental backup/restore? If the latter, your REVMEDIA file maybe out of sync with the directory contents.
Are all the .LK and .OV files marked as read/write?
Can you log into SYSPROG?
At 12 OCT 1999 07:55PM Warren wrote:
What happens if you restore again?
At 12 OCT 1999 08:07PM Kristina Ruiz wrote:
I restored the directory that contains the AREV files and the data and the application. Everything.
There were no users in AREV and I stopped sharing (NT) of the directory. I overwrote all files in the directory. The backup was a full backup, not incremental.
All .LK and .OV are RW, and were RW when restored.
What is SYSPROG? Just going in to AREV? Yes, I can go in there.
At 12 OCT 1999 08:46PM Warren wrote:
Okay if you can just type AREV and get it that indicates that only the files for the Application/Account are messed up.
Most likely (depending on the version of ARev): LISTS, VOC, SYSTEMP.
From SYSPROG run the applications main menu, in version 3.x from TCL type "RUNMENU APPMAIN". This may or may not work in earlier version, try "RUNMENU MAIN".
From the Tables/Files menu do a SETALIAS or SETFILE to the above files, one at a time and do COUNT SYSALIAS or QFILE depending on version of ARev. If any of these files are corrupted it should show up during the count. If it is the LISTS or SYSTEMP file you can probably just do a CLEARFILE on SYSALIAS or QFILE and possibly fix the error that way. If not, do a LISTFILE on the appropriate volume, locate the file in question - this should give the the corresponding REVxxxx.* number and that file can be restored from this or a prior backup (provided the files weren't deleted and recreated for some reason changing the REVnumber).
If you're using the NT Service from Revelation, deleting the REVLOCKS file in the appropriate directory might do the trick. Check also that none of the REVPARAM files are corrupted or missing.
At 13 OCT 1999 07:53AM akaplan@sprezzatura.com - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
The problem is in the SYSMESSAGES file. Try just fixing that, or restoring it from an older backup. The FS1003 error is a frame read error and since it's in the SYSMESSAGES file, you keep getting the error as you try and display the error message, a catch-22.
It would be pretty strange if the back-up from before had a GFE in it as well, so since this is SYSMESSAGES, which shouldn't change much, try restoring from a slightly older backup.
akaplan@sprezzatura.com
At 22 OCT 1999 11:07AM André wrote:
andre@toledoinc.com
