![]() |
![]() |
|
|
1600 |
ERROR: Cannot allocate call buffer: val | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1601 |
ERROR: Cannot allocate call buffer: val | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1602 |
ERROR: Cannot reallocate call buffer: val | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1603 |
ERROR: Cannot reallocate call buffer: val | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1604 |
ERROR: Cannot decode reply header | |
|
Description |
The IIOP Server Listener/Handler failed to decode the header of a TGIOP reply message received from a WLE server. |
Action |
Contact BEA Customer Support. | |
1605 |
ERROR: Type switch uninitialization failure | |
|
Description |
While processing a client application buffer, the buffer uninitialization function, _tmuninitbuf(), returned an error. |
Action |
Check the buffer type switch to see that it is correctly set up (that is, that the right uninitialization function is associated with the correct buffer type). If the buffer type is application defined, check the uninitialization function to see that it is coded correctly. | |
See Also |
The | |
1606 |
INFO: Ignoring non-request type messages | |
|
Description |
The IIOP Server Listener/Handler received a message that was not a request. The message is being ignored. |
Action |
none | |
1607 |
ERROR: Invalid internal buffer: val | |
|
Description |
An internal buffer is corrupted. Additional information about the problem is printed as part of the message. |
Action |
Contact BEA Customer Support. | |
1608 |
ERROR: cannot allocate reply buffer: val | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1609 |
ERROR: Cannot decode request header | |
|
Description |
The IIOP Server Listener/Handler received a GIOP request message that could not be decoded. This probably indicates that the client application is not GIOP 1.0 compliant. The IIOP Server Listener/Handler returns a GIOP error message to the client application. |
Action |
Make sure the client application is GIOP 1.0 compliant. | |
1610 |
ERROR: Cannot decode request header | |
|
Description |
The IIOP Server Listener/Handler received a GIOP request message that could not be decoded. This probably indicates that the client application is not GIOP 1.0 compliant. The IIOP Server Listener/Handler returns a GIOP error message to the client application. |
Action |
Make sure the client application is GIOP 1.0 compliant. | |
1611 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1612 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1613 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1614 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1615 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1616 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1617 |
ERROR: Cannot decode locate request | |
|
Description |
The IIOP Server Listener/Handler received a GIOP locate request message that could not be decoded. This probably indicates that the client application is not GIOP 1.0 compliant. The IIOP Server Listener/Handler returns a GIOP error message to the client application. |
Action |
Make sure the client application is GIOP 1.0 compliant. | |
1618 |
ERROR: Could not perform SSL connect to host/port val | |
|
Description |
The IIOP Server Listener/Handler was unable make a SSL connection to the host/port 'val'. |
Action |
Check the ULOG for messages indicating the nature of the failure. | |
1619 |
ERROR: Missing outbound connection | |
|
Description |
The IIOP Server Handler does not have the necessary outbound connection information to send the request. |
Action |
The error indicates an internal problem with the IIOP Server Handler. Contact BEA Technical Support. | |
1620 |
ERROR: Missing outbound connection | |
|
Description |
The IIOP Server Handler does not have the necessary outbound connection information to send the request. |
Action |
The error indicates an internal problem with the IIOP Server Handler. Contact BEA Technical Support. | |
1621 |
ERROR: Cannot send reply to caller: val | |
|
Description |
The IIOP Server Handler could not send the reply from the remote server application back to the caller (native client or server). |
Action |
Examine the ULOG for any immediately preceding messages for further information about the cause of the error. Contact BEA Technical Support. | |
1622 |
ERROR: Cannot send reply to caller: val | |
|
Description |
The IIOP Server Handler could not send the reply from the remote server application back to the caller (native client or server). |
Action |
Examine the ULOG for any immediately preceding messages for further information about the cause of the error. Contact BEA Technical Support. | |
1623 |
ERROR: Cannot send reply to caller: val | |
|
Description |
The IIOP Server Handler could not send the reply from the remote server application back to the caller (native client or server). |
Action |
Examine the ULOG for any immediately preceding messages for further information about the cause of the error. Contact BEA Technical Support. | |
1625 |
ERROR: Cannot encode IIOP profile | |
|
Description |
The IIOP Server Listener/Handler failed to allocate memory for an internal IIOP buffer. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1626 |
ERROR: Could not perform SSL accept from host/port val | |
|
Description |
The IIOP Server Listener/Handler was unable accept a SSL connection from the host/port 'val'. |
Action |
Check the ULOG for messages indicating the nature of the failure. | |
1627 |
ERROR: Error switching to the handler's context | |
|
Description |
The IIOP Server Handler was attempting to switch from a client application context to the IIOP Server Handler context when it experienced an error. |
Action |
The error indicates an internal problem with the IIOP Server Handler. Contact BEA Customer Support. | |
1628 |
ERROR: Could not read from SSL connection, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while reading from the SSL connection. |
Action |
Check the ULOG for messages indicating the nature of the failure. Contact BEA Customer Support. | |
1629 |
ERROR: Could not write to SSL connection, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while writing to the SSL connection. |
Action |
Check the ULOG for messages indicating the nature of the failure. Contact BEA Customer Support. | |
1630 |
ERROR: Could not set SSL callback, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while initializing SSL. SSL reported this error while trying to set the SSLPlus read callback functions. |
Action |
Contact BEA Customer Support. | |
1631 |
ERROR: Could not set SSL callback, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while initializing SSL. SSL reported this error while trying to set the SSLPlus write callback function. |
Action |
Contact BEA Customer Support. | |
1632 |
ERROR: Could not set SSL callback, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while initializing SSL. SSL reported this error while trying to set the random data object callback function. |
Action |
Contact BEA Customer Support. | |
1633 |
ERROR: Could not set SSL callback info, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while initializing SSL. SSL reported this error while trying to set the cipher negotiation callback function. |
Action |
Contact BEA Customer Support. | |
1634 |
ERROR: Could not set SSL callback info, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while initializing SSL. SSL reported this error while trying to set the random data object callback information. |
Action |
Contact BEA Customer Support. | |
1635 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1636 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1637 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1638 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1639 |
ERROR: Key is valid, but expired | |
|
Description |
During initialization of the IIOP Server Listener/Handler, the SSL package detected an expired private key. This occurred while opening a private key. |
Action |
Contact your certificate authority or BEA Customer Support. | |
1640 |
ERROR: Could not generate random bytes, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while attempting to get random data from the SSL random data object. |
Action |
Contact BEA Customer Support. | |
1641 |
ERROR: Invalid arguments, field id val not passed | |
|
Description |
Invalid arguments were passed to the IIOP Server Listener. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1642 |
ERROR: Invalid connection id val | |
|
Description |
An invalid connection id was passed to the IIOP Server Listener. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1643 |
ERROR: Cannot advertise val, tperrno = val | |
|
Description |
The IIOP Server Listener could not advertise the service used for asymmetric outbound IIOP. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1644 |
ERROR: Cannot advertise val, tperrno = val | |
|
Description |
The IIOP Server Listener could not advertise the service used for asymmetric outbound IIOP. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1645 |
ERROR: Cannot advertise val, tperrno = val | |
|
Description |
The IIOP Server Listener could not advertise the service used for asymmetric outbound IIOP. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1646 |
ERROR: Cannot unadvertise val, tperrno = val | |
|
Description |
The IIOP Server Listener could not unadvertise the service used for asymmetric outbound IIOP. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1647 |
ERROR: Cannot unadvertise val, tperrno = val | |
|
Description |
The IIOP Server Listener could not unadvertise the service used for asymmetric outbound IIOP. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1648 |
ERROR: Cannot unadvertise val, tperrno = val | |
|
Description |
The IIOP Server Listener could not unadvertise the service used for asymmetric outbound IIOP. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1649 |
ERROR: Error binding outbound connection request, can't create any more handlers | |
|
Description |
The IIOP Server Listener could not start another IIOP Server Handler to process the outbound request. |
Action |
Raise the maximum number of IIOP Server Handlers (ISL -M option). | |
1650 |
WARN: Failed to allocate a network resource (val) | |
|
Description |
The IIOP Server Handler or IIOP Server Listener could not allocate a network descriptor for a remote connection. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical mem ory on the machine. | |
1651 |
WARN: Failed to reestablish network address val | |
|
Description |
A previously suspended IIOP Server Listener server was administratively unsuspended but could not reestablish its network address. |
Action |
Failure to reestablish the network address is usually caused either by a failure of the network drivers on the machine to clear the previously held network address or by another process claiming the network address while the listener was suspended. In the former case, the network address eventually is released by the system and the IIOP Server Listener reestablishes its network address through its periodic retry mechanism; therefore, no action is required in this case. In the latter case, local commands (see below) may be used to determine what processes and users are occupying the network address; these processes and users should be asked to relinquish the address. | |
See Also |
The UNIX For information about the For information about the For information about the | |
1652 |
INFO: Reestablished network address val | |
|
Description |
A previously suspended IIOP Server Listener process has been unsuspended and has reestablished its network address. |
Action |
Informational message, no action required. | |
See Also |
The | |
1653 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1654 |
ERROR: Error switching to the handler's context | |
|
Description |
The IIOP Server Handler was attempting to switch from a client application context to the IIOP Server Handler context when it experienced an error. |
Action |
The error indicates an internal problem with the IIOP Server Handler. Contact BEA Customer Support. | |
1655 |
ERROR: descriptor allocation error | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1656 |
ERROR: descriptor allocation error | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1657 |
WARN: Received a non-GIOP message | |
|
Description |
The IIOP Server Listener/Handler received a non-GIOP message. This can occur when a client application other than an WLE remote client application attempts to connect to the IIOP Server Listener/Handler; for example, a JOLT client application, an ATMI client application, or an http client application. After this message is written to the ULOG, the IIOP Server Listener/Handler closes the connection with the client application. |
Action |
Make sure that only WLE remote client applications connect to the IIOP Server Listener/Handler. | |
1658 |
ERROR: Could not establish listening address on network val | |
|
Description |
This error occurs if the IIOP Server Listener cannot advertise its listening address on the network. This error could happen for one of the following reasons:
|
Action |
To correct the problem, match one of the following solutions with the previous problem descriptions:
| |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1659 |
ERROR: Handler received unexpected message | |
|
Description |
The IIOP Server Handler received a message without a client application context (that is, a message intended for the IIOP Server Handler that is not in the correct format). It is not a WLE message. |
Action |
The message is ignored. Contact BEA Customer Support. | |
1660 |
ERROR: Handler received unexpected message | |
|
Description |
The IIOP Server Handler received a message without a client application context (that is, a message intended for the IIOP Server Handler that is not in the correct format). The message received is not a WLE message. |
Action |
The message is ignored. Contact BEA Customer Support. | |
1661 |
ERROR: Couldn't change to client context val, continuing | |
|
Description |
The IIOP Server Handler could not switch to the client context. |
Action |
The error indicates an internal problem with the IIOP Server Handler, however, it was able to continue. Contact BEA Customer Support. | |
1662 |
ERROR: Sending of request message to server failed | |
|
Description |
While a request message was being sent to a remote server application, the operation failed. |
Action |
Check the ULOG for messages indicating the nature of the failure. This warning may indicate that the remote server application is no longer accessible (that is, either the network or machine has failed). Contact BEA Customer Support. | |
1663 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1665 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1666 |
WARN: setsockopt() for SO_KEEPALIVE failed | |
|
Description |
The KEEPALIVE handler-side networking option was configured for a IIOP Server Listener/Handler pair, but could not be enabled. |
Action |
This error is ignored and IIOP Server Handler processing continues normally. However, network errors may not be reported, or may be reported less promptly. Consider enabling the inactive client application timeout ( | |
See Also |
The | |
1667 |
WARN: KEEPALIVE option requested but not available on this platform | |
|
Description |
The KEEPALIVE handler-side networking option is configured for a IIOP Server Listener/Handler pair, but cannot be enabled because it is not available on this platform. |
Action |
This error is ignored and IIOP Server Handler processing continues normally. However, network errors may not be reported, or may be reported less promptly. Consider enabling the inactive client application timeout ( | |
See Also |
The | |
1668 |
ERROR: Could not connect to host/port val | |
|
Description |
The IIOP Server Handler could not connect to the host and port contained within the object reference. |
Action |
Determine if the remote machine has failed. | |
1669 |
ERROR: Hex address type not supported | |
|
Description |
The |
Action |
Correct the application configuration for the IIOP Server Listener/Handler
in the | |
1670 |
ERROR: Bad Internet type of listening address provided: val | |
|
Description |
The address is not a valid Internet address. |
Action |
Any address that starts with // must be a valid Internet address. The following formats are recognized by the system: | |
1671 |
ERROR: SSL package is not installed | |
|
Description |
Applications are trying to use the WLE Security features, but the WLE SSL package is not installed. |
Action |
Install SSL. | |
See Also |
For information about the | |
1672 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1673 |
INFO: SSL port = val | |
|
Description |
The IIOP Server Listener/Handler is using port 'val' for this connection. |
Action |
None | |
1674 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1675 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1676 |
ERROR: Invalid connection id val | |
|
Description |
An invalid connection id was passed to the IIOP Server Listener. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1677 |
ERROR: Could not close private key, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while trying to close the private key. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1678 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also, increase the space on the swap device. | |
See Also |
See the For UNIX systems, see the For Microsoft Windows NT systems, see the Microsoft Visual C++ online help. | |
1679 |
ERROR: Could not initialize SSL library, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while trying to initialize the SSL library. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1680 |
ERROR: Could not load SSL library val, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while trying to load the SSL library. |
Action |
The error indicates an installation problem with the WLE Security package. Contact BEA Customer Support. | |
1681 |
ERROR: Could not get SSL library init rtn, err = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while trying to read the SSL library initialization function from the SSL library. |
Action |
The error indicates an installation problem with the WLE Security package or an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1682 |
ERROR: Could not get server information for ISL, errno = val | |
|
Description |
The IIOP Server Listener/Handler received the error 'val' while trying to get security-specific information for ISL. |
Action |
The error indicates an internal problem with the IIOP Server Listener. Contact BEA Customer Support. | |
1683 |
ERROR: Mixing -R and -a options is not supported | |
|
Description |
Both the -R and -a command options were specified. This is not supported. |
Action |
Correct the command line options. | |
See Also |
The | |
1684 |
INFO: Only first requesting principal will be used | |
|
Description |
The security service context in the message contains more than one requesting principal. Only the first principal will be used. |
Action |
Verify that the version of the client software is correct. | |
1685 |
ERROR: Invalid permissions for security service context | |
|
Description |
The security service context contains invalid permissions. |
Action |
Verify that the -E option is specified and the specified principal is correct. Verify that the version of the client software is correct. | |
See Also |
The | |
1686 |
ERROR: Unknown security service context version = val.val2 | |
|
Description |
The security service context version val is not supported. |
Action |
Verify that the version of the client software is correct. | |
1687 |
ERROR: can't self-authenticate to principal 'val', engine error val | |
|
Description |
The security engine error val occurred when the ISH attempted to self authenticate with principal 'val'. |
Action |
Verify that the specified principal name is correct. | |
1688 |
ERROR: Could not decrypt admin key, errno = val | |
|
Description |
The password for the SEC_PRINCIPAL_NAME in the tuxconfig file could not be decrypted. |
Action |
Verify that the tuxconfig file is valid. Recreate the tuxconfig file and try again. | |
1689 |
ERROR: Could not init decrypt of admin key, errno = val | |
|
Description |
The password for the SEC_PRINCIPAL_NAME in the tuxconfig file could not be decrypted. |
Action |
Verify that the tuxconfig file is valid. Recreate the tuxconfig file and try again. | |
1690 |
ERROR: Could not get admin key, errno = val | |
|
Description |
The password for the SEC_PRINCIPAL_NAME in the tuxconfig file could not be decrypted. |
Action |
Verify that the tuxconfig file is valid. Recreate the tuxconfig file and try again. | |
1691 |
ERROR: Could not get server information for ISL, errno = val | |
|
Description |
The IIOP Server Listener process encountered an error while trying to
obtain server information about itself from shared memory.
The numeric value of |
Action |
Examine the user log for a prior message indicating a more exact cause of the error. Contact BEA Technical Support. | |
1692 |
ERROR: SEC_PRINCIPAL_NAME for this ISL is empty | |
|
Description |
The SEC_PRINCIPAL_NAME in the tuxconfig file is empty. A plugin may not be able to authenticate an empty principal name. |
Action |
Verify that the SEC_PRINCIPAL_NAME should be empty. | |
1693 |
ERROR: Authorization plugin error = val | |
|
Description |
The authorization preop operation failed with the val error from the authorization plugin. |
Action |
Look in the userlog for additional error messages from the authorization plugin. | |
1694 |
ERROR: Audit plugin error = val | |
|
Description |
The audit preop operation failed with the val error from the audit plugin. |
Action |
Look in the userlog for additional error messages from the audit plugin. | |
1695 |
ERROR: Authorization plugin error = val | |
|
Description |
The authorization postop operation failed with the val error from the authorization plugin. |
Action |
Look in the userlog for additional error messages from the authorization plugin. | |
1696 |
ERROR: Authorization plugin error = val | |
|
Description |
The authorization postop operation failed with the val error from the authorization plugin. |
Action |
Look in the userlog for additional error messages from the authorization plugin. | |
1697 |
ERROR: Authorization plugin error = val | |
|
Description |
The authorization postop operation failed with the val error from the authorization plugin. |
Action |
Look in the userlog for additional error messages from the authorization plugin. | |
1698 |
ERROR: Authorization plugin error = val | |
|
Description |
The authorization postop operation failed with the val error from the authorization plugin. |
Action |
Look in the userlog for additional error messages from the authorization plugin. | |
1699 |
ERROR: Authorization plugin error = val | |
|
Description |
The authorization postop operation failed with the val error from the authorization plugin. |
Action |
Look in the userlog for additional error messages from the authorization plugin. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|