W559 error and more (AREV Specific) [Revelation On-Line Wiki]

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 17 OCT 1997 10:43:21AM Maggie Woo wrote:

AREV Specific

I posted this to the other site before it disappeared (was it yesterday?). Anyway, this is a weird one, and any help would be great!

Besides the W559 error (error trying to run a null program), we've also seen physical error reading filename*account (no matter what filename).

The only clue we have is that when we do LISTVOLUMES, the data volume in question lists with no "File Type". (See the bottom of this message for a copy.)

The system is a networked AREV 2.03 application; Banyan Vines Network. Network drives are still attached and available. All files available.

IN FACT – here's the weird part – this problem seems to be USER and PC specific. The same AREV user on a different PC works just fine. Some other AREV user on the affected PC works just fine. It is not related to network logon (any network user who logs in as this specific USER on this specific PC has this problem). The PC is a 486 Windows 3.x (don't know model or RAM, but can find out).

This happened at this installation one other time (May 20) on a Windows 95 PC same symptoms, different user. That problem we solved by creating a new user for that person.

Does anyone know what might be causing this? We're pretty sure we can "band-aid" this problem by creating a new user for this person, but it would be great to solve the problem in the first place.

TIA

Maggie Woo

The Nature Conservancy

[email protected]

Below is the print-screen of the LISTVOLUMES that shows that the BCDDATA volume doesn't have a FILE TYPE:

+——————————————————————————+

¦ List of Volumes Currently Attached ¦

¦——————————————————————————¦

¦ ¦Volume Name ¦File Type ¦Location ¦Volume Label ¦

¦—+——————+————+—————–+————————¦

¦ 1]BCDDATA ¦ ¦G:\AREV\BCDDATA ¦09:43:35 01 FEB 1988 ¦

¦ 2¦BCDSYS ¦AdvRev/LH ¦G:\AREV\BCDSYS ¦09:54:14 01 FEB 1988 ¦

¦ 3¦DATAVOL ¦AdvRev/LH ¦DATAVOL ¦11:08:39 30 DEC 1993 ¦

¦ 4¦DOS ¦OperSystem ¦ ¦DOS File ¦

¦ 5¦INDEXING ¦AdvRev/LH ¦INDEXING ¦INDEXING ¦

¦ 6¦MEMORY.RESIDENT ¦Memory ¦ ¦MEMORY.RESIDENT ¦

¦ 7¦REVBOOT ¦AdvRev/LH ¦ ¦AREV.11:57:24 15 JUL 1 ¦

¦ 8¦SYSCOLUMNS ¦SysCols ¦ ¦SYSCOLUMNS ¦

¦ 9¦TRANSACT ¦AdvRev/LH ¦TRANSACT ¦TRANSACT ¦

+——————————————————————————+

At 17 OCT 1997 11:09AM Victor Engel wrote:

It looks to me like there is a problem with the REVMEDIA file for that volume, although I don't know why that would be user specific, unless the volume is located on the local computer. If I were investigating this, I would log on to the SYSPROG account ATTACH volume REVMEDIA and EDIT REVMEDIA * looking through all the entries to see if the look right.

At 17 OCT 1997 12:59PM Maggie Woo wrote:

Thanks! I'll forward your suggestion. Crossing my fingers that something will raise its head…

View this thread on the forum...