Technical article 108250

VisionFS installation tips and troubleshooting guidelines.

OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6UnixWare 7.0.0UnixWare 7.0.1UnixWare 7.1.1

Written · Last revised

Problem

Are there any useful tips I should know before I install the the SCO VisionFS that comes supplied as part of my SCO Operating System?

Solution

Following are installation and troubleshooting tips.
SCO VisionFS installation tips:
(1) TCP/IP must be successfully installed and configured on
your UNIX server before you try to install VisionFS.  In order
for TCPIP to be installed, you must first install a network
adapter card on your server.

NOTE: If your network configuration notes a single entry, localhost (IP address 127.0.0.1), then your network card is not yet successfully installed.

(2) Your TCP/IP network must be set up for name resolution,
either through the use of a name service like DNS or through
the use of host files. (This is because Windows workstations
network together through the use of names, not IP addresses.)
Some VisionFS processes will fail, if name resolution is not
fully-enabled, including licensing, and the ability for Windows
PC users to see the VisionFS from their PCs.  Can you ping in
both directions by NODE NAME?  Can the UNIX server ping its own
NODE NAME?  Does #hostname return the correct value?  If using
DNS, check with your DNS administrator if there are any name
resolution problems.  If using local host files, and you are
the UNIX System Administrator, check /etc/hosts for correct
entries.  Correct any name resolution problems early and you
will save yourself considerable trouble.

(3) It is a good idea to run SCOadmin and install your UNIX users before installing VisionFS.

(4) Similarly, it is a good idea to install the printers for your UNIX host before installing VisionFS.

If users and printers were not configured before installing VisionFS, stop and restart the VisionFS server after users and printers have been added.

#cd /<visiondir>/bin
#./visionfs stop
#./visionfs start

where default <visiondir> is /usr/vision or /usr/local/vision.

(5) SCO VisionFS and SCO Advanced File and Print Server cannot run simultaneously on the same UNIX server. If you are running AFPS, you will need to stop it before you install VisionFS:

# net stop server
# netbios stop
NOTES: VisionFS will detect the presence of AFPS software, and
whether or not it is currently running.  By stopping it beforehand,
you can ensure a slightly smoother installation.
Strictly speaking, it is VisionFS and the in-kernel NetBIOS that
cannot run concurrently.  You can use AFPS alongside VisionFS if
you run it on NetBEUI only.  See ta108360, "How do I run VisionFS
and AFPS on the same host?"
VisionFS 1.2 troubleshooting tips:

(1) If you tried to install VisionFS before you had installed and configured TCP/IP, you must remove VisionFS and install TCP/IP:

scoadmin software -> this server -> remove VisionFS

(2) If you're not sure how TCP/IP is configured on your UNIX server or Windows workstation, you must examine them both for typographical or configuration errors.

NOTE: See TA108223, "I'm running SCO Vision products over Microsoft TCP/IP. How can I find out what TCP/IP settings are installed at my site?"

(3) If VisionFS installed and worked correctly, but stops the next
time you leave and re-enter multiuser mode, it may be that SCO
Advanced File and Print Services have been started up automatically,
which will prevent VisionFS from starting.  If you think this may
be the case, run:
# net stop server
# netbios stop
# visionfs start
# visionfs status

If VisionFS works, examine the /etc/rc2.d directory for the files that start the in-kernel NetBIOS and AFPS. On most systems:

/etc/rc2.d/S86netbios
/etc/rc2.d/S95asusrv

To prevent AFPS from starting up automatically again on the next server multiuser-mode initialization, rename these files so that the first letter of the filename "S" is lowercase:

/etc/rc2.d/s86netbios
/etc/rc2.d/s95asusrv

This will allow VisionFS to function properly without any administrative intervention.

(4) If you are unable to run the VisionFS Profile Editor after
making a connection, it may be due to the fact that you have
logged into your Windows workstation as a user who does not have
a UNIX account on the UNIX server.  By default, only the VisionFS
administrator that you selected when you installed VisionFS can
access the Profile Editor the first time.

Make sure that you have logged on to your Windows workstation as that administrator, and try running the Profile Editor again.

NOTE: While running the Profile Editor, you can select other
UNIX users to have administration privileges as well.  See ta108359,
"How do I specify the VisionFS administrator?"

(5) If for some reason your VisionFS profile becomes corrupted, you can easily create another another at any time; save your /<visiondir>/vfsprofile/current.prf by renaming it to 'old.prf'. Then run the VisionFS setup script:

# <visiondir>/bin/visionfs setup
Selecting 'n' when asked if you want to accept these settings will
allow the VisionFS installation script to run again.  Your corrupt
profile will be replaced with a fresh version and you will lose
old corrupted configuration information.  You can always overwrite
this new 'current.prf' with the 'old.prf' if you choose to go back
to the corrupted profile (for instance, if it turns out to not
have been corrupted and running setup has not corrected the problem.)

(6) Only the version of VisionFS that is physically on the SCO Operating System CD-ROM will install using the SCOadmin Software Manager. If you've installed VisionFS, and yet it doesn't show up in the Software Manager, you may have installed software from the Vision DEMO CD-ROM, or perhaps you have downloaded the software directly from the website:

http://www.tarantella.com/vision

The default installation directory for the VisionFS that comes with SCO Operating Systems is /usr/vision. For all other versions of VisionFS, the default is /usr/local/vision.

(7) Once you have installed this VisionFS software using SCOadmin
Software, you must NOT install any other copy of VisionFS (from
http://www.tarantella.com/vision, or from the Vision97 Demo CD-ROM).
If for some reason you choose to try to install one of these, be
certain to run SCOadmin Software first and remove this version
first.  Failure to do so can cause corruption of the VisionFS files
which then become impossible to remove using SCOadmin.  Manually
searching and removing all Vision files is then the only way of
cleanly removing VisionFS from the system for a fresh install.
If this ever occurs, it is HIGHLY RECOMMENDED that you cleanly
remove ALL VisionFS files and do a fresh installation of VisionFS.
It will be well worth your time in the long run to do this.  See
your Operating System man pages for instructions on using the
'find' command.
NOTE:     Mixing the custom installable version of VisionFS with the versions
          from the web site or from the Demo CD-ROM will cause problems with
          system symbolic links as well as other runtime issues.  You will
          likely lose VisionFS functionality should this occur.

See also

TA108376, "The VisionFS host does not appear in my Network Neighborhood."

TA108360, "How do I run VisionFS and AFPS on the same host?"

TA108223, "I'm running SCO Vision products over Microsoft TCP/IP. How can I find out what TCP/IP settings are installed at my site?"

TA110112, "Which version of VisionFS is supplied as part of my SCO Operating System?"

TA108209, "How do I install the VisionFS 1.2 that comes with my OpenServer 5.0.4 product?"

From the Xinuos technical article database, record 108250. Reproduced with permission. The original is at www.sco.com/ta/108250, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.