
Troubleshooting a Site Manager Problem
7-3
3. Make sure that the environment variable PATH contains only the path to
the protocol stack that you want Site Manager to use.
Otherwise, the PC will boot, but Site Manager may use the wrong protocol
stack; it uses the first winsocket library it finds when searching the directories
in the environment variable PATH.
Working Directory or Path Is Invalid Message
These messages appear when the properties of the PC (personal computer) Site
Manager icon fail to match the installation and configuration. Do the following:
1. Click the PC/Site Manager icon.
2. Select File➔Properties.
The Program Item Properties window appears.
3. Make sure the settings in the Command Line and Working Directory
match the directory of the WFSM.EXE and configuration files.
Unable to Find UDP Port Numbers for SNMP Message
The SERVICES file is in
• The NETMANAG directory if you are using Chameleon.
• The ETC directory if you are using Distinct TCP/IP.
Make sure the SERVICES file contains the following lines:
snmp_trap 162/udp
snmp 161/udp
Site Manager Won’t Start on a UNIX Workstation
If you are having problems starting Site Manager, do the following:
1. Verify that the workstation meets all of the minimum system
requirements.
2. Enter the wfchkenv command to verify that the path variables and
environment variables are set up correctly.
Make sure the link /usr/wf points to the directory where you installed Site
Manager.
3. Enter the wfchkinst command to verify the installation.
Commentaires sur ces manuels