Troubleshooting

This section describes problems that you may encounter when you use the Solstice AdminSuite product. If you run into any of these problems, follow the advice that is provided.

Running the admin_install Script

• If the admin_install script hangs, try re-running the script after waiting a few minutes. If the script continues to hang, try running it using another UID in the sysadmin group. If this fails, try adding yourself to the sysadmin entry in the /etc/group file on the system you wish to install.

• If the admin_install script (running on system installed with Solaris 2.3 or 2.4 release) hangs after the following message is displayed:

  Installing Solstice enabling packages ...

You can recover by becoming root and using the following commands.

# /usr/lib/nfs/mountd
# umount /usr/snadm/classes/tmp_system.2.1

Launching the Solstice AdminSuite

• If you logged in as root and used the su command to become a member of group 14, the Solstice AdminSuite software may reject your requests. Log in as a user who is a member of group 14 rather than as root.

• If you attempt to launch the Solstice AdminSuite software on a station manager using the solstice command and receive the following error message:

  Solstice Registry Error [-14]: unable to locate registry

There are two possible conditions that can cause this error to arise.

• The administration system was not installed with the software supporting its native platform. Reinstall the Solstice AdminSuite 2.3 software using the admin_install script, and add the software for the administration system's platform (for example, SPARC or x86).

• The administration system was inadvertently installed using the automounter managed host mount method, when the /etc/vfstab file option should have been selected. Create the following links:

  # ln -s /basedir/platform/SUNWadm /opt/SUNWadm # ln -s /basedir/all/SUNWadmd /opt/SUNWadmd

In these commands,

Upgrading to the Solaris 2.4 OS Release

• If you upgrade a system installed with the Solstice AdminSuite 2.3 software and the Solaris 2.3 release to the Solaris 2.4 release, Printer Manager will not function properly. This occurs because an incorrect version of the FNS software is installed.

  To correct this problem, you must remove the installed FNS software packages and replace them with correct versions found on the Solaris 2.5 or Solaris 2.5.1 CD.

  Remove the FNS software:

  # pkgrm SUNWfns SUNWfnspr

This step assumes that your system is running Volume Management. Insert the Solaris 2.5 or Solaris 2.5.1 CD into your CD-ROM drive, and install the correct version of the FNS software:

# pkgadd -d /cdrom/cdrom0/s0/Solaris_2.5 SUNWfns SUNWfnspr