Managing NerveCenter - Troubleshooting NerveCenter - Common problems -
Previous: Appendix: Troubleshooting NerveCenter     Next: Using Trace Counters to Troubleshoot NerveCenter

Common problems

The following list includes some of the more common problems users face when administering NerveCenter.

The NerveCenter Server

UNIX will not start the NerveCenter Server.

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

The NerveCenter Server does not start on Windows NT.

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?

UNIX will not start the NerveCenter Administrator.

While trying to connect to a NerveCenter Server I get the message: The server did not respond.

I misspelled a server name while trying to connect and now the misspelled name appears in the NerveCenter Administrator Server Name list.

When I try to connect to a NerveCenter Server it tells me: Number of allowed client connection exceeded.

When I try to connect to a NerveCenter Server it tells me: Number of allowed client connection exceeded.

When I try to connect to a NerveCenter Server it tells me: Number of allowed client connection exceeded.

I need to make the same changes to several NerveCenter Servers.

Importing imputil.ini caused unwanted changes to a NerveCenter Server.

NerveCenter's node list

NerveCenter is not filtering a node by a capability.

After setting an IP filter, a node that should be masked out still appears in the node list.

Even though I have enabled Process Traps From Unknown Nodes, NerveCenter does not update its node list when it receives a trap from an unknown node.

NerveCenter does not recognize my network management platform as a valid source of node data.

NerveCenter is not receiving node data from my network management platform.

The IPSweep behavior model will not work.

The NerveCenter node list contains two nodes with the same address but different names.

NerveCenter deletes a node I added manually.

NerveCenter adds a node I deleted manually.

I'm seeing several errors recorded in the application event log window stating that ipsweep.exe is not running.

Alarm actions

NerveCenter is not sending SMTP mail notifications.

Microsoft mail notifications are not being sent as NerveCenter.

NerveCenter is not dialing pages correctly.

The logs created by my behavior models are using too much disk space.

The NerveCenter database

The server shut down gracefully, but event log said that the database was not found. Where did the updates to the database go?

Running SerializeDB from the command line keeps failing.

SerializeDB won't work from the application or the command line.

The data in the database is not what was imported from the serialized file.

Importing a 2.6 database won't work.

Management Information Bases (MIBs)

A MIB won't compile.

A MIB won't load.


Previous: Appendix: Troubleshooting NerveCenter Next: Using Trace Counters to Troubleshoot NerveCenter
Please send comments or corrections to Information Development
This file was last updated on 10 October © 2002