Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 05 DEC 2011 04:34:29PM victor b wrote:

I have an OI 8.0.8 installed in W2008 Svr 64 bits to work with Arev32, the databases (volumes) are in another W2003 Svr 32 bits.

There are several work stations that have two map network drive units (Application Arev32 in W2008 and the data W2003), since here everything works perfect.

The problem is in the W2008, I have a map network drive unit (the data W2003), I execute the Arev32 and I cannot see (Attach, ListVolume, Pdisk) the data unit, the error is: "FS109 Open or Create Media Error The name F:\MEX12 is an invalid volume directory label", however, if I enter to OpenInsight with the DataBase Manager I can see the tables without problems, I have also copied the data directory to the hard disk of the W2008 and it works well.

I thank any advice than can give me

Ahead of time thank you,

Ines


At 05 DEC 2011 08:54PM Bob Carten wrote:

Try using a unc path instead of mapped drives.

I suspect the problem is that the socket server is running as a service, so does not know about mapped drives.


At 07 DEC 2011 01:47PM victor b wrote:

Thank you for your answer Bob,

Indeed, the Socket Server is running as a service.

I made the following test using UNC path and neither works.

In Arev32, with F5, (TCL Command), I wrote:

"LISTVOLUME \\192.168.10.200\BDINTERPRES\MEX12"

The system responds:

"FS109 Open or Create Media Error The name \\192.168.10.200\BDINTERPRES\MEX12 is an invalid volume directory label"

What could be happening?, some other suggestion?

I thank your time a lot


At 07 DEC 2011 01:58PM bcarten wrote:

I think you are missing a backslash. Unc is \\server\share\folder

try \\192.168.10.200\BDINTERPRES\MEX12


At 07 DEC 2011 05:01PM victor b wrote:

In fact, I'm writing the double backslash, but here in the post does not appear \

Regards


At 08 DEC 2011 10:57AM Jared Bratu wrote:

OpenInsight 8.x has been known to run on Windows 2008 but it isn't officially supported as a platform. OpenInsight 9.x is recommended for Windows 2008 and 7 because it is fully DEP compatible. Are you able to reproduce the same problem with OpenInsight 9.x / AREV32 on your 2008 server?


At 08 DEC 2011 02:40PM victor b wrote:

Hi Jared,

I did the changes for OI9.1.0 and the result is the same (also change the server socket service)

What do you think?

Thank you


At 12 DEC 2011 04:23PM Jared Bratu wrote:

Do you have a LinearHash service installed on both servers? If not, what network driver is your Arev32 system using.


At 12 DEC 2011 08:30PM victor b wrote:

The LinearHash is only installed on the W2008 server.

The network driver:

 In OI8.0.8 with All networks Driver 2.1 (previous test)
 In OI9.1 with Universal driver in 3.0.0, I changed it to 4.6.0 and it is the same

At 13 DEC 2011 08:42AM Jared Bratu wrote:

OI 8.0.8 installed in W2008 Svr 64 bits to work with Arev32, the databases (volumes) are in another W2003 Svr 32 bits.

I think this could be part of the problem. Every computer that hosts shared .LK/.OV files must have a LinearHash service installed. This is this is the server component that coordinates access to the database files. Because your OpenInsight system is on one server and the database files are on another you should have two copies of the LinearHash services. One on the Windows 2008 server to manage concurrent access to the revboot directory (i.e. syslists) and another on the Windows 2003 server to coordinate access to the database itself.

The All networks 2.1 driver could work in a cooperative group locks mode without a LinearHash service but it is no longer supported as a configuration. If this worked in the past you may be experiencing this incompatibility.

One last item, you can't use the same copy of the LinearHash service because clients cannot attach to two different servers with the same LinearHash serial number.


At 15 DEC 2011 07:45PM victor b wrote:

Well, in that case we will try to develop in OI, to replace what we have in Arev32.

Thank you

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/4abb81d2000474542d5f75d00.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1