Managing NerveCenter - Error Messages - Error Messages - Action Manager Error Messages -
Error Messages      Alarm Filter Manager Error Messages

Action Manager Error Messages

Following is a list of Action Manager error messages.

Action Manager Error Messages

Error Number Error Resolution

1

Action Manager Initialization failed with send trap socket

N/A

3

Send trap action: CreateTrapRequest failed

N/A

4

Send trap action: Send trap failed

N/A

500

Socket Error: value

N/A

501

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

N/A

1001

Action Manager connect to database failed

Check NerveCenter database. Check ODBC connection string.

1002

InitializePlatformSocket failed for value

Use the Administrator to check the configuration settings for NetNodeNotify.

1004

Can't open database

Check NerveCenter database. Check ODBC connection string.

1005

No connection string for Log to Database action

Check ODBC connection string.

1006

Reconfiguration: InitializePlatformSocket failed for value

Check Notify page in NC Admin.

1010

Log to Event View error: RegisterEventSource for value failed with error code value

Check system configuration.

1011

Log to Event View error: ReportEvent failed with error code value

Check system configuration.

1012

Socket Creation Failed in InitSmtpSocket With Error = value

Check socket resource on the computer.

1013

Protocol Bind Failed in InitSmtpSocket With Error = value

Check TCP/IP configuration.

1014

Connect to SMTP Host Failed in InitSmtpSocket With Error=value

Use the Administrator to check the configuration settings for SMTP host name.

1015

Ioctlsocket Failed (Setting Non-Blocking Mode) in InitSmtpSocket With Error=value

Check TCP/IP configuration.

1016

Send Packet Failed in SendSmtpPacket With Error= value

Check SMTP server.

1017

Receive Packet Failed in RecvSmtpPacket for %1 With Error= value

Check SMTP server.

1018

Received Unexpected Response= value in RecvSmtpPacket

Check SMTP server.

1019

Log to Database error: Database connection not open

Check NerveCenter database. Check SQL Server.

1020

Log to Database error: can not open log table

Check NC_Log table in NerveCenter database.

1021

Log to Database exception: value

Check NerveCenter database. Check SQL Server. Check NC_Log table in NerveCenter database.

1022

Logging to a File error: No filename presented to Log To File action.

Make sure there is a file name associated with LogToFile action for alarm transitions.

1023

Logging to a File error: Unable to Write LogFile: value Error Code = value.

Check security on file system. Make sure the file is writable.

1024

Logging to a File error: Unable to Create LogFile: value Error Code = value.

Check security on file system. Make sure the file is writable.

1025

Logging to a File error: Unable to Seek EOF for LogFile: value Error Code = value

Check security on file system. Make sure the file is writable.

1026

Logging to a File error: Unable to Truncate LogFile.

Delete the file or repair the file format.

1027

Could Not Logoff from MAPI value, Error=value

Check MAPI service in the system.

1028

Could Not Load MAPI32.DLL.

Search mapi32.dll in the system and ensure sure it is in the system path.

1029

Could Not Get MAPILogon Address.

Check mapi32.dll in the system and ensure it is a good version.

1030

Could Not Get MAPILogoff Address.

Check mapi32.dll in the system and ensure it is a good version.

1031

Could Not Get MAPISendMail Address.

Check mapi32.dll in the system and ensure it is a good version.

1032

Could Not Logon to MAPI value, Error=value.

Check MAPI configuration and ensure to have created the profile.

1033

Could Not SendMail to MAPI value, Error=value.

Check MAPI configuration and ensure to have created the profile.

1034

Paging action error: Dial failed.

Check modem configuration.

1035

Running an NT Command error: No Command Presented to Run Command.

Make sure there is a command associated with all Windows Command actions specified for alarm transitions.

1036

Running an NT Command error: Command value Completed with ReturnCode value

Check command line.

1037

Command action value failed : Application handler value was killed

NCServer will bring it up for the next Command action

1038

Command action <action> failed : value

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

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.

2002

Send trap action failed for alarm alarm name due to the following reason: string

Check the source or destination host name. Check the enterprise. If this action was not caused by a trap, it will fail if the enterprise is $P. Check to see that the varbinds are legal for the currently loaded MIB.

2003

Tapi initialize failed, paging will not work

Check the comm port/modem configuration and check the tapi32.dll version.

2004

Empty host for SMTP mail

If SMTP actions are used, use the Administrator to enter the SMTP mail host name.

2005

Empty profile for MAPI, MS Mail will not work

If MS mail actions are used, use the Administrator to enter the SMTP mail host name.

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.

2010

Error Sending SMTP Mail. Value messages may have been lost.



Error Messages Alarm Filter Manager Error Messages
29 July 2003