Universal Driver - Unable to access Linear Hash Files (OpenInsight 32-Bit)
At 09 SEP 2005 12:06:27PM Emily Dotsias wrote:
We have a situation where we are running an OI application from 2 different locations.
Location A, our central office, contains our OI application server (Windows 2000 Server). On OI application server, we have the installed the universal driver (3.0.0.3) and the Linear Hash service is up and running perfectly. The registry and revparam was set up according to the installation guide:
Registry:
AnonymousUsername: ServiceLogOn
NamedPipeName: LHSRVC
TcpIpPort: Allocate
revparam:
ServerOnly=true
Location B, our regional office, has their own server (Windows 2003 Server). On the regional office server, we have the installed a copy of the OI application and we have mapped the regional office's version of OI to point back to the database on the central office OI application server. Executing OI from a workstation from the regional server produces the following error message:
* Unable to access Linear Hash File
* Filing system installation failed (REPOS_BFSFS1100)
* OpenInsight boot failed
Is there something incorrect with our configuration?
Do we need to install the universal driver on our regional server?
Thanks for your help.
Emily Dotsias
At 09 SEP 2005 01:36PM Pascal Landry wrote:
Depending on line speed between the 2 sites, I would make everyone run off the same server.
If line speed is an issue, you could always setup some type of terminal service or citrix connection to the location B.
Otherwise, on location B. I imagine that you would have setup the same Revparam file in the application root with one exception, serveronly=0.
At 09 SEP 2005 01:41PM Kevin Ruane Revelation wrote:
Emily,
Here are some quick answers that we can get into more depth if needed:
The settings on your main server are for both NP and TCP/IP. Can you go for pure TCP/IP? You will only be able to use pure TCP/IP at the remote site.
If you are storing data at the remote site, you will want to have a copy of the Service there.
Have you taken a look at this Knowledge Base article? It might point you in the right direction for what you are doing.
Hope it helps,
Kevin
At 13 SEP 2005 02:32PM Emily Dotsias wrote:
Thanks Kevin and Pascal.
We do not have data files on the regional office server. The regional office server has the application files. The regional office OI application is mapped to the central office OI application server where the data files reside in a datavol directory.
Regional Central
OI OI
|——————–|—–]Datavol
We have changed our central office OI application server to run TCP/IP only:
The application server new registry setting:
AnonymousUsername: ServiceLogOn
NamedPipeName: None
TcpIpPort: 9998
new revparam setting:
ServerOnly=true
NamedPipeName=None
TcpIpPort=9998
I am not exactly sure how to setup the regional office server; do we do anything to the registry, and does it have a revparam file? Right now the regional office server setup does not have anything in the registry. Also, we do not have a revparam file in the application directory on the regional server. We tried some different revparam file configurations (ServerOnly=true, NamedPipeName=None, TcpIpPort=9998) but the revparam file did not seem to resolve our problems so we removed it.
Executing OI from a regional office workstation using the application residing on the regional server produces the following error message:
* Unable to access Linear Hash File Error=FS1020
* Filing system installation failed (REPOS_BFSFS1100)
Thanks.
Emily Dotsias
At 13 SEP 2005 04:37PM Kevin Ruane Revelation wrote:
Emily,
Please see the "Hiding Data in Windows Networks" section of the White Paper I linked you to. It will instruct you on what needs to happen on the regional server as well as on the home office server.
Hope it helps,
Kevin
At 13 SEP 2005 05:26PM Emily Dotsias wrote:
Thanks Kevin -
Things are becoming more clear. But there are still some issues that we need to resolve. We appreciate your help!
In our configuration the central office application server has the UD installed on it. The regional office server does not have the UD installed on it.
The central office application server has a copy of OI with the datavol that contains all the data. The regional office server has copy of OI without datavol (through the database manager we are mapping to the machine address and path where datavol resides on the central office application server).
When we run the OpenInsight executable from the central office application sever OI works perfectly.
When users from their central office workstations access the central office application server and run the OpenInsight executable from the central office application sever OI works perfectly.
When we run the OpenInsight executable on the regional office sever OI works perfectly and successfully connects to the datavol that resides on the central office application server.
Where errors occur is when users from the regional office workstations access the regional office server and run the OpenInsight executable located on the regional office sever . . we do not successful connect to the datavol that resides on the central office application. Running the OI executable returns the Unable to access Linear Hash File Error=FS1020 and Filing system installation failed (REPOS_BFSFS1100) error messages . . upon entry.
Are we having a configuration problem or do we need a UD installed on the regional server?
The example provided is great, but the example seems to be for a configuration that has an instance of OI on a single server where that server has the UD installed. The goal of the example seems to be to hide files in a separate directory on the same server (where the UD is installed). Or am I missing something, which could be the case. To me the example does not provide guidance on the setup/configuration of a second server (as in my instance, where the second server does not have the UD . . the registry setup that contains UD setting). So, that part is a little confusing. I am having particular trouble figuring out the setup with the revparam and registry settings on the second (regional office) server. The example certainly has some good concepts that we will test.
Thanks!
At 06 OCT 2005 11:05AM Emily Dotsias wrote:
A second Universal Driver solved the problem.