NSM/web 3.1 Installation Guide (H06.23+, J06.12+)

Troubleshooting
HP NonStop Release 3.1 NSM/web Installation Guide—663861-001
3-4
Problems Contacting the NSM/web's Comm Server
Process

The WebServer has cached a stale version of the factory's IOR (Interoperable
Object Reference) file. To fix this problem, you can flush the WebServer's cache
(/usr/tandem/webserver/conf/vcache script).
You can also add the following to the WebServer's
/usr/tandem/webserver/conf/ local.config:
Region */Common/FactoryIORs {
NoCache
}
Sometimes the attempted change to local.config does not work. In that case:
1. Remove the addition.
2. Stop NSM/web.
3. Stop and restart the WebServer (if doing so will not affect other applications).
4. Restart NSM/web.

The TCP/IP port numbers specified during the NSM/web installation are already in
use. NSM/web requires two consecutive port numbers for its use. To fix this
problem, reinstall NSM/web with unused TCP/IP port numbers. To find out the port
numbers in use, use the SCF STATUS PROCESS command for the TCP/IP
processes you plan to use for NSM/web
Problems Contacting the NSM/web's Comm
Server Process
If you attempt to log on and you receive the following message:
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201
completed: No
Either of these conditions could be the problem:

The NSM/web server Factory is running but the Comm Server process is not
running. To fix this problem, stop and restart NSM/web.

The NSM/web server Factory and the Comm Server processes are not running. To
fix this problem, stop and restart NSM/web.
Note. If the WebServer was installed by the super user ID (255, 255), you must have
super-user privileges to flush the WebServer’s cache.
Note. The TCP/IP port numbers you choose must not be used by any other applications
on the system. Do not use the port numbers less than 1024. They are reserved for special
services like TELNET, FTP etc.
Note. Issue the following OSS command to determine if the Comm Server process is
running:
./statusNSMweb