1

Lookup failed on linenumber value in File value.

3001

InformNC Manager Initialization successfully finished

2

ReceiveHandShakeResponse FALSE byte not correct.

N/A

500

Socket Error: value.

N/A

501

<system call> failed while launching Application handler : <error message>.

N/A

1002

InitializePlatformSocket failed for value.

Use the Administrator to check the configuration settings for NetNodeNotify.

1003

No platform host for InformOV.

Use the Administrator to check the configuration settings for NetNodeNotify.

1006

Reconfiguration: InitializePlatformSocket failed for value.

Check Notify page in the Administrator.

1007

CInformOVEventSocket::Init() failed with invalid operation: value.

Use the Administrator to check the configuration settings for NetNodeNotify.

1039

Unable to launch Application handler: value.

If error says "Too many open files" close some open files. If error says "fork failure" close some applications.

1040

Perl subroutine value failed: message.

1500

The connection to value was closed.

1505

value. The address is already in use.

Make sure you are not running two instances of the same application on the same machine.

1506

value. The connection was aborted due to timeout or other failure.

Make sure the physical network connections are present.

1507

value. The attempt to connect was refused.

Make sure the server is running on the remote host.

1508

value. The connection was reset by the remote side.

Make sure the remote peer is up and running.

1509

value. A destination address is required.

A destination address or host name is required.

1510

value. The remote host cannot be reached.

Make sure the routers are working properly.

1511

value. Too many open files.

Close any open files.

1512

value. The network subsystem is down.

Reboot the machine.

1513

value. The network dropped the connection.

Make sure the peer is running and the network connections are working.

1514

value. No buffer space is available.

This might be because you are running several applications, or an application is not releasing resources.

1515

value. The network cannot be reached from this host at this time.

Make sure the routers are functioning properly.

1516

value. Attempt to connect timed out without establishing a connection.

Make sure the machine is running and on the network.

1517

value. The host cannot be found.

Make sure you can ping the host. Check your hosts file or DNS server.

1518

value. The network subsystem is unavailable.

Make sure the network services are started on machine.

1519

value. Invalid host name specified for destination.

The host name cannot be resolved to an IP address. Enter the name to the hosts file or DNS server.

1520

value. The specified address in not available.

Make sure the host name is not zero -- try pinging the host.

2001

Command line too long: value.

Check the Windows Command Action. Command line exceeds maximum allowed length of 2048 characters.

2006

Fire Trigger Action error: Invalid node name: value.

A node name was specified directly in an action and that node doesn't exist in the system.

2007

Fire Trigger Action error: Invalid property name: value.

A property was specified directly in an action and that property doesn't exist in the system.

2008

Fire Trigger Action error: Invalid subobject: value.

A subobject was specified directly in an action and that subobject doesn't exist in the system.

2009

Inform OV send Packet Failed for platform socket value.

3001

Inform OV Manager Initialization successfully finished.

3002

CInformOVEventSocket::OnClose with code value.

1002

Initialization failed.

Check WriteBuiltInTriggers.

1100

Unknown database exception.

Check NerveCenter database. Log segment might be full.

1101

Failed to connect to database.

Check NerveCenter database. Check ODBC connection string.

1102

Failed to connect to database.

Check NerveCenter database. Check ODBC connection string.

1103

Version table validation failed. NC_Version table doesn't exist in database.

1104

Write to database failed.

Log segment might be full or the database might have gone down.

1203

Can't enable discovery model.

Check the alarm table and the state of alarms (off or on).

3001

Database Thread Initialization successfully finished.

3002

The database state has changed. Either it has gone down or come up.