Attachmate Worldwide  |   Contact Us  |   NetIQ.com
Home » Support » Solution Library

Technical Notes

Troubleshooting VCP Exception COMM_FAILURE
Technical Note 10031
Last Reviewed 22-Jul-2004
Applies To
Verastream Integration Broker version 9.0 or higher
Summary

This technical note outlines possible causes of the Verastream Control Protocol (VCP) error "VCP Exception COMM_FAILURE."

Symptom

Your application or log files may show an error:

VCP Exception COMM_FAILURE minor=0, 1:COMPLETED_NO

or

VCP Exception COMM_FAILURE minor=0, 2:COMPLETED_MAYBE

Troubleshooting Tips

To troubleshoot the error message, examine the logged messages before and after the error. For information about enabling logging, see Technical Note 10234.

Network-related Problems

Network-related problems are indicated by the following examples:

connect(fd=11,address=(as001=192.168.22.5):58403)=-1: errno=146: Connection refused

or

recv(fd=444,buflen=12)=-1: errno=10054: Connection reset by peer

or

send(fd=444,buflen=76)=-1: errno=10054: Connection reset by peer

In these cases, the TCP/IP software is returning an error. Following is a list of possible causes:

  • Remote system is down
  • Firewall blocking connection
  • Bad IP or DNS configuration
  • System not reachable
  • System overwhelmed with requests
  • Network link down (router rebooted, power failure, etc.)

Problems Related to VCP Server Component

The following example indicates a problem with your VCP server component:

COMPONENT '<name>' METHOD '<method>': Cannot connect to server.

In this case, the server component and/or sntcpd log(s) should be checked to determine why the server component could not start. Following is a list of possible causes:

  • Server component not registered
  • Server component registered, but the .pia or .fle file is not present in the registered directory (as appearing in VCP Component Directory Explorer or <VIB>/pardir/snregtab.dat file)
  • UNIX file system permissions issue
  • Bad SNDIRECTORYSERVER environment variable configuration
  • Firewall blocking runtime registration communication from VCP server component to sntcpd daemon
Related Technical Notes
10035 Verastream Integration Broker and the Microsoft Windows Firewall (Included in XP Service Pack 2)
10036 Port Numbers Used by Verastream Integration Broker
10234 Enabling and Using Logging in Verastream Integration Broker
10999 Verastream Integration Broker Technical Notes

Did this technical note answer your question?

Yes    No    Somewhat     Not sure yet

Additional comments about this tech note:

Need further help? For technical support, please contact Support.