We have an application written in OI 3.5 that attaches AREV data tables. Two of our installations recently upgraded from AREV 3.1 to AREV 3.12 Now OI cannot attach the AREV data and displays this message: FS109 Open or create media error. The name (path of data directory) is an invalid volume directory label.

The installations that are still on AREV 3.1 work fine.

It seems that the structure of the revmedia file for the 3.12 systems has changed. Does anyone have any suggestions as to what to do to get the 3.12 data to attach?

Thanks,

Mark Glicksman

Glenside, PA

Mark,

Have you tried 'removing' all tables from the definition and then 'adding' them back?

Each application has a .dbt file in the OpenInsight directory. I would suggest that you copy sysprog.dbt to appname.dbt. Then start the application and 'add' the tables you need.

We use 3.12 data with our oi systems so I know that works.

dsig@teleport.com onmouseover=window.status=you have seen the rest .. now try the best!;return(true)"

David Tod Sigafoos ~ SigSolutions

voice: 503-639-8080

OK- I tried what you suggeswted (good idea by the way!). When I try to re-add the tables to the database definition, OI doesn't "see" any tables in the data directory, i.e. there are no tables to chose from. It does "see" tables in the main AREV (REVBOOT) directory. This makes me think that maybe the revmedia file in the data directory is somehow corrupted in a way that allows AREV to read it but not OI. Any ideas?

Thanks,

Mark Glicksman

Glenside, PA

Hi Mark -

Please try from the command line:

run list_volume Any errors? Then try: run attach_table , 'REVMEDIA'

Any errors?

It doesn't sound like a database name mismatch … it could be a duplicate volume label … try detaching other volumes first.

Cameron Purdy

Revelation Software

I tried both list_volume and attach_table - both result in the same error message:

FS109: Open or Create Media error. The name "C:\BGBASE\DATA" is an invalid volume directory label.

The only thing I can think of is that there is something corrupted in the REVMEDIA file that prevents OI from reading - but still allows AREV to read it.

Any further ideas?

Thanks,

Mark Glicksman

Glenside, PA

I tried both list_volume and attach_table - both result in the same error message:

FS109: Open or Create Media error. The name "C:\BGBASE\DATA" is an invalid volume directory label.

The only thing I can think of is that there is something corrupted in the REVMEDIA file that prevents OI from reading - but still allows AREV to read it.

Any further ideas?

Thanks,

Mark Glicksman

Glenside, PA

Mark -

Try detaching attaching it in Arev from TCL to see if it errors there.

Cameron Purdy

Revelation Software

]]Try detaching attaching it in Arev from TCL to see if it errors there.

It works fine in AREV - just not in OI

Mark Glicksman

Glenside, PA

Mark,

So you did detach and re-attach in Arev?

Cameron Purdy

Revelation Software

Mark -

Just temporarily, change the OI network driver. Also, make sure only one (Arev or OI) is accessing the directory at a time. Check the file attributes, etc.

The attach logic, and the LH filing system implementation, is almost identical between Arev and OI. This is a stumper….

Cameron Purdy

Revelation Software

Okay ..

Have you tried copying the tables to a new directory .. then looking at OI?

dsig@teleport.com onmouseover=window.status=you have seen the rest .. now try the best!;return(true)"

David Tod Sigafoos ~ SigSolutions

voice: 503-639-8080

IS IT SERVER BASED AND DO YOU HAVE A REVPARAM FILE?

I'VE SEE SIMILAR ERROR IN OI WHEN MISSING THE REVPARAM FILE

DIMTRI

]]So you did detach and re-attach in Arev?

Yes… No problem in AREV. But, OI just doesn't "see" the volume.

Mark Glicksman

Glenside, PA

Mark,

This is certainly strange. If you have a support contract, can you zip up the files and get them to a technical support representitive so they can try to reproduce the problem?

Cameron Purdy

Revelation Software

Try opening up the media map and clear everything from field 3 down in each record.

akaplan@sprezzatura.com

Sprezzatura, Inc.

Just for the record, I finally solved the problem today. It seems that the AREV data location in question inadvertantly had a revparams file inserted into it with serveronly=1 Only, the data is not on a server. That caused the error message.

Yours very truly,

Mark Glicksman

Glenside, PA

I have a similar situation. We have Arev installed on two servers with two serial numbers (call them A and B). We have system A set up to use the REVELATION user but system B does not use the REVELATION user. We get this message when trying to access files on B when logged onto A but not vice versa. I'm wondering if adding the REVELATION user to the Netware list of users is all it would take to resolve the problem. In both cases, I am actually logged in and attached to both servers using the same combination of login ids (a different user id on each server). Hmmm. I just thought of something. The user id used to log on to system A and then attach to system B (unsuccessfully) is not a valid user on system B. Does Arev use the logged user id of the current server when attaching to a remote server rather than use an existing connection?

View this thread on the forum...