Background

We have four file servers each running AREV3.12. The data files are stored in the main office file server while the 3 file servers at each remote site are loaded with the program files only. Each file server has a full development license of AREV with unique serial numbers. All of these were originally AREV 1.16 systems that went through the ?trade-up? process. All file servers are Novell 4.11 running the AREV NLM 1.5.

New File Server

We are now adding an additional file server for a new remote site. A new ?clean? version of AREV3.12 was installed. Here is the problem. When we log into SYSPROG on the new remote system and go to Options | Applications, we get the following message when we enter the name of our application and its location which is on the file server in the main office.

The object code for DICT_MFS_BUILD cannot be found in the SYSOBJ table.

DICT_MFS_BUILD is also not cataloged.

The object code for INDEX.CONTROL cannot be found in the SYSOBJ table.

INDEX.CONTROL is also not cataloged.

However when we login to our main file server, the $DICT_MFS_BUILD and $INDEX.CONTROL records are in the SYSOBJ file under the REVBOOT directory.

Rule out Network Issues

To rule out any network complications, two directories were created on a local PC. One directory contains our application and the other contains the new AREV3.12 installation.

We got the same errors when trying to define where our application was.

Work-Around

To test a possible work-around, I replaced the AREV.EXE file on our working system with the AREV.EXE file from the new AREV3.12 installation. I can start up my old application just fine and the license number and number of licensed users is consistent with the new AREV3.12 system that I just purchased.

Therefore, we are thinking of loading our entire working system, program and data files, from the main file server to the new remote file server. Then replace the old AREV.EXE file with the new one from the 3.12 system we just purchased. We would delete out the datafiles from the remote server. The remote server logon verb would then attach the data directories from the main system.

If anyone has an idea of what may be causing the error messages or does the proposed work-around seem to make sense?

Thanks

wally

[email protected]

Saw a similar situation a few years ago. Couldn't figger out what was causing it so I did just what you propose. Worked fine then and works fine now. Make sure that the drive mappings on the workstations are correct.

Don Miller

C3 Inc.

Wally

The SYSOBJ file is GLOBAL and will reside in each remote copy of AREV, hopefully in the Revboot volume. Therefore the messages I guess relate to the fact that Arev cannot see $DICT_MFS_BUILD in your remote application SYSOBJ - not the one on the central file server.

Check that the $DICT_MFS_BUILD exists in the new remote SYSOBJ and that SYSOBJ lives in the Revboot volume. Then check that the central system does not have a copy of SYSOBJ in the locations that you are attaching (I assume you aren't specifying the remote Revboot).

Finally you can create a voc pointer to the routines (i.e. catalogue them) altough this shouldn't be necessary if they are in SYSOBJ.

Please also note tha I have just come back from a very long lunch when reading any of the above

Tony

What happens when you replace the new EXE with an existing one to the new setup?

(Not related): Could be a quickattach/image issue.

View this thread on the forum...