Managing NerveCenter - Running the NerveCenter Server - Troubleshooting:Running the NerveCenter Server -
Previous: Running the NerveCenter Server     Next: Connecting to the NerveCenter Server

Troubleshooting:Running the NerveCenter Server

The following list contains some common problems users have when running the NerveCenter Server.

UNIX will not start the NerveCenter Server

Problem: The environment variables are not set.

Solution: Execute one of the following shell scripts:

• <install_path>/userfiles/ncenv.sh
• <install_path>/userfiles/ncenv.csh
• <install_path>/userfiles/ncenv.ksh

where <install_path> is typically /opt/OSInc/.

See "Running the NerveCenter Server on UNIX" on page 42.

An alarm causes the NerveCenter Server to crash every time I start it

Problem: Any alarm that is enabled when a NerveCenter Server stops is still enabled when the NerveCenter Server starts again.

Solution: Start the NerveCenter Server with all its alarms turned off by typing at the command prompt ncserver -off &.

See "Running the NerveCenter Server on UNIX" on page 42 or .

The NerveCenter Server does not start on Windows NT

Problem: The NerveCenter Server was installed as a manual service.

Solution: Start the NerveCenter Service manually by typing at the command prompt ncstart -s.

See .

I need to get a better idea of what the NerveCenter Server is doing on Windows NT. Can I temporarily run it as a process?

Problem: NerveCenter typically runs as a Windows NT service, which causes a number of its functions to be hidden to users.

Solution: You can start NerveCenter Server as a Windows NT process by typing at the command line: