Moving from Novell -] Win2000 - Errors (AREV Specific)
At 04 JUL 2004 10:42:16PM HealthSolve wrote:
We have copied our app from a novell server to a win2000 server, installed the service and get the following message when logging into the app. sysprog and lanpack.
All networks driver 1.5.0.0
Unable to access linear hash files
Error=FS1104
Group=2100
Unable to open bootmedia map.
Anyone know what causes this?
At 04 JUL 2004 11:01PM Steve Smith wrote:
Check REVPARAM has SERVERONLY= set.
Check REVPARAM is in *every* path
Check REVPARAMS have at least one blank line at the bottom
Check that full access rights are assigned to each user in *every* path OI uses.
Check that there are no files marked read-only (this sometimes happens when transferring via CD or read-only media).
If in doubt, pull the app back to a local disk, disconnect the network, and change the network driver to non-networking, copy the app back to the server, until you've established that there are no further problems.
You can always call me here during office hours to talk through the steps.
Steve
State of the Art Systems
At 05 JUL 2004 01:48AM Donald Bakke wrote:
Steve,
Check REVPARAM has SERVERONLY= set. Check REVPARAM is in *every* path Check REVPARAMS have at least one blank line at the bottom
How would any of these improve connectivity with the service? I've always understood that the purpose of the REVPARAM file is to prevent accidental access to OI tables when the service isn't communicating correctly. Consequently, they don't assit OI's ability to talk to the service but rather they are there for protection.
Am I wrong about this?
At 05 JUL 2004 01:49AM Donald Bakke wrote:
All networks driver 1.5.0.0 Unable to access linear hash files Error=FS1104 Group=2100
What version of the service did you install? My guess it is 2.1 so you should run NetDrv.exe and change your client driver to All Networks Driver ver 2.1.
At 05 JUL 2004 04:02AM Steve Smith wrote:
Don,
I understand that Healthsolve work into the South Australian health market. I've had problems at hospitals in S.A. myself (RAH / Flinders) where many servers are configured by a third party company -the client (hospital staff) or the application provider has no direct control over the network config and possibly not even over the network administration or security access or workstation build! In some cases hospital workstations will attach to Novell and Windows servers concurrently and this can further complicate matters.
Could be awkward to install on this basis - I'm guessing as to the degree of control Healthsolve have over the network build.
It seemed sensible to pull back to a local drive to ensure the app was workable at least. Simplify the possible causes.
As to REVPARAM - thought checking this was a sensible part of ensuring the application's correct access to the Windows service. Especially given Healthsolve's recent transition from Novell. REVPARAM is mentioned here in terms of NT service setup.
Steve
At 05 JUL 2004 09:18AM Donald Bakke wrote:
Hi Steve,
Forgive me if my previous post came off sounding like I was challenging your suggestions for a proper network setup. Upon re-reading my words that's how it looked to me. Everything you posted is exactly what I would have said myself (including the blank line in the REVPARAM file…found that problem the hard way!)
I thought perhaps the discussion of the REVPARAM files in the context/order that you mentioned them might have confused HealthSolve. It read to me as if they can help eliminate connectivity problems, which is not the case as the article you linked me too seems to confirm.
Part of the reason for my jumping in is past experience with other consultants (including my own staff) who tend to forget that REVPARAM files don't force OI or the service to work better. I want to make sure your good suggestions weren't taken the wrong way.
At 07 JUL 2004 04:20AM Barry Stevens wrote:
Could there be a version compatibilty issue between the NT service and the Arev "All networks" driver Version Nos.
At 07 JUL 2004 09:10AM Donald Bakke wrote:
That's exactly what I said. They are using the 1.5 All Networks driver but I suspect they are using the 2.1 Service.
At 07 JUL 2004 09:20AM christopher h caravaglia wrote:
check your global software setting and make sure the say N to nlm and network version is set to nt. We did the same thing our selves. We went from a Novell 4.11 to Win2003. When i installed the rev service for testing everything was ok until i copied the recent data onto the 2003 server when we went live. It reset all the setting back to a novell eniv