FS109 with OI 16bit app attaching AREV win2000 network data (Networking Products)
At 04 JAN 2005 12:31:46AM Janet S Scott wrote:
Hi all
I've got a problem that I think might be a network service (or lack of ~) or maybe an open insight problem.
Open Insight v3.7 on a c drive on a pc with all networks 1.5.0.0 - doesn't run at all if I change it to standalone.
doesn't attach the data files on the network drive.
The network drive contains an AREV 3.? system running with windows 2000 service revsoft\ntservice\lhsrvc.exe on a windows 2000 server. There are no revparam files anywhere. They only break things.
I can attach the network data files using AREV installed on the c drive of the same pc with the open insight system. I don't know what lanpack this c drive arev has because I get an error about LHIPXTSR when I try "arev lanpack" from the command line (windows xp client).
The open insight application will not attach the network data. I can't even do it from syseditor. The error attach_table produces is
FS109 Open or Create media error. The name K:\APPNAME\DATA is an invalid directory label.
The login/pc has full access to K drive. K drive has an IP or UNC mapping but neither work. The drive is mapped after login when you run the app. This isn't a problem for AREV but it is a problem for the Open Insight.
The mapping commands look something like
net use K:\\192.168.0.20\sharename /user:username\thingy
or
net use K:\\servername\sharename /user:username\thingy
(not quite sure about the syntax of the servername mapping because I forgot to write it down)
What I'm wondering now (and can't test) is, do I need to install some sort of network product on the open insight system on the client PC hardrive? Would it be better to put the open insight system on the same drive as the arev data that it needs to attach?
Note: We have the OI app installed on pc hard drives and attaching data on network drives for other customers, but none of them use windows 2000 servers yet, and none of them dynamically map the network drives used. And they do use UNC mappings not TCP/IP address mappings.
I tried changing the flag for SYSENV SYS_TABLE_TYPES RTP57 but it didn't make any difference that I noticed.
Any ideas and wild guesses appreciated
Janet
happy new year?! saw my first rainbow cale in rainbow mode on Sunday :) http://www.amonline.net.au/fishes/fishfacts/fish/oacropt.htm
At 10 JAN 2005 12:28AM David Goddard wrote:
G'day Janet,
Long time between drinks!
Ok, this is what you need to do.
Login to the AREV app then go to TCL and type WHO. This will tell you what network driver AREV is using. I'm guessing that AREV is running the ALL Networks Driver v2.1
This will tell you what version of the Widnows 2000 service you are using. My guess is V2.1
Your customer should have the original Windows 2000 Service disks somewhere. You will need to perform the client disk install to install the All Network Driver v2.1 into your OpenInsight system.
Once this is done you should have no trouble accessing the LH tables from OI.
Let me know how you go
Best regards,
David Goddard
Revelation Software Australia Pty Ltd
david.goddard@revelationsoftware.com.au