ISNAT Messages 1300-1399
|
|
1304
ERROR: Invalid argument to -C option: val
Description
The -C option for the ISL command requires an argument of detect, warn, or none.
Action
Ensure that the -C option of the ISL command is detect, warn, or none. Check your spelling.
1305
WARN: Unofficial connection from client (network address is unknown)
Description
An unofficial connection was established from a client application with an unknown network address. The official way for a CORBA client application to connect to the IIOP Server Listener/Handler is via a Bootstrap object. An unofficial connection is established directly from an IOR. The use of unofficial connections can cause problems for remote client applications that use transactions.
Action
Check that the host name specified in the Tobj_Bootstrap() constructor or in the TOBJADDR environment variable exactly matches the host name specified in the -n option of the ISL command. The names must match exactly in both spelling and case.
See Also
The ISL command. For information about the ISL command, see the Administration Guide.
1306
WARN: Unofficial connection from client at address
Description
An unofficial connection was established from a client application at the network address address. The official way for a CORBA client application to connect to the IIOP Server Listener/Handler is via a Bootstrap object. An unofficial connection is established directly from an IOR. The use of unofficial connections can cause problem for remote client applications that use transactions.
Action
Check that the host name specified in the Tobj_Bootstrap() constructor or in the TOBJADDR environment variable exactly matches the host name specified in the -n option of the ISL command. The names must match exactly in both spelling and case.
See Also
The ISL command. For information about the ISL command, see the Administration Guide.
1307
ERROR: Unofficial connection from client (network address is unknown)
Description
An unofficial connection was established from a client application with an unknown network address. The official way for a CORBA client application to connect to the IIOP Server Listener/Handler is via a Bootstrap object. An unofficial connection is established directly from an IOR. The use of unofficial connections can cause problems for remote client applications that use transactions.
Action
Check that the host name specified in the Tobj_Bootstrap() constructor or in the TOBJADDR environment variable exactly matches the host name specified in the -n option of the ISL command. The names must match exactly in both spelling and case. Also check that the client application connects to the IIOP Server Listener via a Bootstrap object only.
See Also
The ISL command. For information about the ISL command, see the Administration Guide.
1308
ERROR: Unofficial connection from client at address
Description
An unofficial connection was established from a client application at the network address address. The official way for a CORBA client application to connect to the IIOP Server Listener/Handler is via a Bootstrap object. An unofficial connection is established directly from an IOR. The use of unofficial connections can cause problems for remote client applications that use transactions.
Action
Check that the host name specified in the Tobj_Bootstrap() constructor or in the TOBJADDR environment variable exactly matches the host name specified in the -n option of the ISL command. The names must match exactly in both spelling and case. Also check that the client application connects to the IIOP Server Listener via a Bootstrap object only.
See Also
The ISL command. For information about the ISL command, see the Administration Guide.
1309
ERROR: Unable to open TUXCONFIG file to Resources section
Description
While attempting to read the application password, the IIOP Server Listener or the IIOP Server Handler had a problem opening the RESOURCES section of the TUXCONFIG file.
Action
Ensure that the TUXCONFIG environment variable points to the appropriate configuration file. If the configuration file does not exist, you can create it from the UBBCONFIG file using tmloadcf. If it does exist, the file may be corrupted, or may have been a file generated by an older release of the WLE software. Shut down the system, remove the file, and recreate it with tmloadcf.
1310
ERROR: Unable to open Resources section of TUXCONFIG file
Description
While attempting to read the application password, the IIOP Server Listener or the IIOP Server Handler had a problem reading the RESOURCES section of the TUXCONFIG file.
Action
Ensure that the TUXCONFIG environment variable points to the appropriate configuration file. If the configuration file does not exist, you can create it from the UBBCONFIG file using tmloadcf. If it does exist, the file may be corrupted, or may have been a file generated by an older release of the WLE software. Shut down the system, remove the file, and recreate it with the tmloadcf command.
1311
ERROR: Possibly corrupted key in database
Description
While the IIOP Server Handler or the IIOP Server Listener was reading the TUXCONFIG file, an invalid password was detected.
Action
Ensure that the TUXCONFIG environment variable points to the appropriate configuration file. If the configuration file does not exist, you can create it from the UBBCONFIG file using tmloadcf. If it does exist, the file may be corrupted, or may have been a file generated by an older release of the WLE software. Shut down the system, remove the file, and recreate it with tmloadcf.
1312
ERROR: Error while decrypting password
Description
While the IIOP Server Handler or IIOP Server Listener was reading the TUXCONFIG file, an invalid password was detected.
Action
Ensure that the TUXCONFIG environment variable points to the appropriate configuration file. If the configuration file does not exist, you can create it from the UBBCONFIG file using tmloadcf. If it does exist, the file may be corrupted, or may have been a file generated by an older release of the WLE software. Shut down the system, remove the file, and recreate it with tmloadcf.
1313
ERROR: Invalid password in TUXCONFIG file
Description
While the IIOP Server Handler or IIOP Server Listener was reading the TUXCONFIG file, an invalid password was detected.
Action
Ensure that the TUXCONFIG environment variable points to the appropriate configuration file. If the configuration file does not exist, you can create it from the UBBCONFIG file using tmloadcf. If it does exist, the file may be corrupted, or may have been a file generated by an older release of the WLE software. Shut down the system, remove the file, and recreate it with tmloadcf.
1314
ERROR: Invalid parameter
Description
An error occurred while the application password was being encrypted.
Action
Contact BEA Technical Support.
1315
ERROR: Memory allocation failure
Description
While an encryption schedule was being created, the system ran out of memory.
Action
Check the memory on the system where the process was running.
1316
ERROR: Invalid parameter
Description
An error occurred while the application password was being encrypted.
Action
Contact BEA Technical Support.
1317
ERROR: Invalid parameter
Description
An error occurred while the application password was being manipulated.
Action
Contact BEA Technical Support.
1318
ERROR: Memory allocation failure
Description
While a key was being created, the system ran out of memory.
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.
1319
ERROR: Invalid parameter
Description
An error occurred while a session key being retrieved.
Action
Contact BEA Technical Support.
1320
ERROR: Memory allocation failure
Description
While a session key was being created, the system ran out of memory.
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.
1328
ERROR: Failed to update registry table information
Description
The IIOP Server Handler failed to update the client application information in the Bulletin Board's registry table. The IIOP Server Handler therefore unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error.
Action
Check the user log for other error messages that may indicate the exact nature of the problem and reason for this failure.
1329
ERROR: Error assigning connection request, can't create any more handlers
Description
The IIOP Server Listener was unable to start a new Handler.
Action
The most likely problem is that the maximum number of IIOP Server Handlers specified in the configuration file have been started. To increase this number, the CLOPT -M maxh value must be changed. This can be done in two ways: first, shut the application down and change the configuration file and reboot the application, or second, change the value dynamically with tmconfig(1), and shut down and reboot only the IIOP Server Listener server.
Another possible source of the problem could be that the number of processes allowable by a user (ulimit) has been reached. If the ulimit has been reached, consult with your system administrator to increase this limit.
1330
ERROR: Failed to initialize network protocol information (error)
Description
The IIOP Server Handler or IIOP Server Listener could not initialize its network.
Action
Ensure that the network is viable on the machine. If the network is viable, contact BEA Technical Support.
1335
ERROR: Memory allocation error: error_info
Description
An attempt dynamically to allocate memory from the operating system failed. Additional information about the problem is printed as part of the message.
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.
1336
ERROR: Memory allocation error: error_info
Description
An attempt dynamically to allocate memory from the operating system failed. Additional information about the problem is printed as part of the message.
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.
1337
ERROR: Cannot send system exception
Description
The IIOP Server Listener/Handler attempted to return a CORBA system exception to the client application, but could not write the message to the network.
Action
The client application cannot be reached on the network, which probably means that the client application process disconnected.
1338
ERROR: Cannot send error message
Description
The IIOP Server Listener/Handler attempted to send a GIOP error message to the client application, but could not write the message to the network.
Action
The client application cannot be reached on the network, which probably means that the client application process disconnected.
1339
ERROR: Cannot send close connection message
Description
The IIOP Server Listener/Handler attempted to send a GIOP close-connection message to the client application, but could not write the message to the network.
Action
The client application cannot be reached on the network, which probably means that the client application process disconnected.
1340
ERROR: Received unexpected GIOP message type (type)
Description
The IIOP Server Listener/Handler received a GIOP message with an unknown or unexpected message type. 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 that the client is GIOP 1.0 compliant.
1341
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.
1342
ERROR: Cannot encode locate reply
Description
The IIOP Server Listener/Handler failed to encode a GIOP locate reply message. This should not happen. The IIOP Server Listener/Handler returns a GIOP error message to the client application.
Action
Contact BEA Customer Support.
1343
ERROR: Cannot send locate reply
Description
The IIOP Server Listener/Handler attempted to send a GIOP locate reply message to the client application, but could not write the message to the network.
Action
The client application cannot be reached on the network, which probably means that the client application process disconnected.
1344
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.
1345
ERROR: Received invalid object key
Description
The IIOP Server Listener/Handler received a GIOP request message which contains a non-WLE object key. This could happen if a client application reuses an old CORBA Interoperable Object Reference (IOR) that was created for another CORBA Object Request Broker using the same network address as the IIOP Server Listener/Handler.
Action
Make sure the offending IOR was received from a WLE server.
1346
ERROR: Received unexpected type type object key
Description
The IIOP Server Listener/Handler received a GIOP request message that contains a WLE object that is not recognized. This should not happen.
Action
Contact BEA Customer Support.
1347
ERROR: Invalid internal buffer: error_info
Description
An internal buffer is corrupted. Additional information about the problem is printed as part of the message.
Action
Contact BEA Customer Support.
1348
ERROR: Invalid internal buffer: error_info
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal network buffer. Additional information is printed as part of the message.
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.
1349
ERROR: Cannot allocate call buffer: error_info
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal WLE buffer. Additional information is printed as part of the message.
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.
1350
ERROR: Cannot reallocate call buffer: error_info
Description
The IIOP Server Listener/Handler failed to increase the size of an internal WLE buffer. Additional information is printed as part of the message.
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.
1351
ERROR: Cannot set TGIOP host and port: error_info
Description
An internal error occurred in IIOP Server Listener/Handler.
Action
Contact BEA Customer Support.
1353
ERROR: Invalid internal buffer: error_info
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal network buffer. Additional information is printed as part of the message.
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.
1354
ERROR: cannot allocate reply buffer: error_info
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal WLE buffer. Additional information is printed as part of the message.
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.
1355
ERROR: Cannot decode reply message header
Description
The IIOP Server Listener/Handler failed to decode the header of a TGIOP message received from a WLE server.
Action
Contact BEA Customer Support.
1356
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.
1357
ERROR: Cannot decode locate reply header
Description
The IIOP Server Listener/Handler failed to decode the header of a TGIOP locate reply message received from a WLE server.
Action
Contact BEA Customer Support.
1358
ERROR: Cannot send locate reply
Description
The IIOP Server Listener/Handler attempted to send a GIOP locate reply message to the client application, but could not write the message to the network.
Action
The client application cannot be reached on the network, which probably means that the client application process disconnected.
1359
ERROR: Invalid internal buffer: error_info
Description
In internal buffer is corrupted. Additional information about the problem is printed as part of the message.
Action
Contact BEA Customer Support.
1360
ERROR: Invalid internal buffer: error_info
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal network buffer. Additional information is printed as part of the message.
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.
1361
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.
1362
ERROR: Cannot encode IOR
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.
1363
ERROR: Cannot allocate memory for IOR string
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.
1364
ERROR: Cannot encode IOR
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.
1365
ERROR: Cannot allocate memory for IOR string
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.
1366
ERROR: No protocol machine registered in protocol group
Description
The IIOP Server Listener/Handler did not initialize properly.
Action
Contact BEA Customer Support.
1367
ERROR: Invalid protocol machine discriminator return
Description
An internal error occurred in the IIOP Server Listener/Handler.
Action
Contact BEA Customer Support.
1368
ERROR: Error allocating protocol group table
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal structure.
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.
1369
ERROR: Invalid protocol group
Description
An internal error occurred in the IIOP Server Listener/Handler during initialization.
Action
Contact BEA Customer Support.
1370
ERROR: Missing group discriminator
Description
An internal error occurred in the IIOP Server Listener/Handler during initialization.
Action
Contact BEA Customer Support.
1371
ERROR: Error allocating global protocol machine table
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal structure.
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.
1372
ERROR: Error allocating local protocol machine table
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal structure.
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.
1373
ERROR: Cannot allocate protocol machine context
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal structure.
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.
1374
ERROR: Unexpected object key number
Description
The IIOP Server Listener/Handler received a valid WLE object key for an unknown or unexpected internal interface.
Action
Contact BEA Customer Support.
1375
ERROR: Invalid internal buffer: error_info
Description
An internal buffer in the IIOP Server Listener/Handler is corrupted. Additional information about the problem is printed as part of the message.
Action
Contact BEA Customer Support.
1376
ERROR: Memory allocation error: error_info
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal network buffer. Additional information is printed as part of the message.
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.
1377
ERROR: Cannot open named pipe file_name
Description
Solaris only. The IIOP Server Listener failed to open the named pipe file_name to communicate with an IIOP Server Handler.
Action
Shut the IIOP Server Listener down, remove file_name from the APPDIR directory and reboot the IIOP Server Listener/Handler. If the problem persists, contact BEA Customer Support.
1378
ERROR: Named pipe file_name is not a streams pipe
Description
Solaris only. The IIOP Server Listener/Handler expects file_name to be a named pipe. There is an existing file by that name that is not named pipe.
Action
Shut the IIOP Server Listener down, remove file_name from the APPDIR directory and reboot the IIOP Server Listener/Handler. If the problem persists, contact BEA Customer Support.
1380
ERROR: Cannot pass connection to handler
Description
Solaris only. The IIOP Server Listener uses a named pipe to pass a newly received connection to its handler. If this error occurs, the selected handler is probably dead.
Action
Wait a few seconds and try again (that is, restart the client application). If the problem persists, contact BEA Customer Support.
1381
ERROR: Invalid handler index
Description
HP-UX, AIX and Tru64 UNIX only. An internal table is corrupted in the IIOP Server Listener.
Action
Contact BEA Customer Support.
1382
ERROR: Cannot create UNIX socket, errno = error_number
Description
HP-UX, AIX, and Tru64 UNIX only. The IIOP Server Listener failed to create a UNIX socket to communicate with an IIOP Server Handler. Error_number is the UNIX error number.
Action
Make sure the operating system parameters are set correctly to handle UNIX sockets.
1383
ERROR: Cannot connect to handler socket file_name, errno = error_number (error_message)
Description
HP-UX, AIX, and Tru64 UNIX. The IIOP Server Listener failed to connect the UNIX socket name to an IIOP Server Handler. Error_number is the UNIX error number, and error_message is a string description of error_number.
Action
Shut the IIOP Server Listener down, remove file_name from the APPDIR directory and reboot the IIOP Server Listener/Handler. If the problem persists, contact BEA Customer Support.
1384
ERROR: Cannot callocate control
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal structure.
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.
1385
ERROR: Cannot pass connection to handler
Description
HP-UX, AIX and Tru64 UNIX. The IIOP Server Listener uses a named pipe to pass a newly received connection to its handler. If this error occurs, the selected handler is probably dead.
Action
Wait a few seconds and try again (that is, restart the client application). If the problem persists, contact BEA Customer Support.
1386
ERROR: Cannot open handler process: error_info
Description
Windows NT only. The IIOP Server Listener is trying to access an IIOP handler to pass a connection. The handler process cannot be reached. Error_info provides more information.
Action
Make sure the handler process is still alive. Wait a few seconds and try again (i.e. restart the client application). In case of failure, make sure that the number of handles used by all the processes on the machine is not too large. Make sure enough handles are available on the system for WLE software to operate normally.
1387
ERROR: Cannot duplicate connection handle: error_info
Description
Windows NT only. The IIOP Server Listener is trying to duplicate a connection handle in order to pass the connection to an IIOP Server Handler. The handle cannot be duplicated. Error_info provides more information.
Action
Make sure that the number of handles used by all the processes on the machine is not too large. Make sure enough handles are available on the system for WLE software to operate normally.
1389
ERROR: Cannot accept connection on UNIX socket
Description
HP-UX, AIX and Tru64 UNIX only. The IIOP Server Handler encountered an error when accepting a UNIX socket connection from the IIOP Server Listener. This UNIX socket connection between listener and handler is used to pass a network connection from a client application.
Action
Make sure the operating system parameters are set correctly to handle UNIX sockets.
1390
ERROR: Cannot allocate control
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal structure.
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.
1391
ERROR: Cannot receive fd
Description
HP-UX, AIX and Tru64 UNIX only. The IIOP Server Handler encountered an error when trying to receive a network connection file descriptor from the listener.
Action
Make sure the number of file descriptors available per process is large enough to accommodate all the client application connections on the handler plus a few control file descriptors, such as the UNIX socket connection between listener and handler. Make sure the number of file descriptors available on the machine is large enough to accommodate all the client application's connections on the machine, all the control file descriptors, and all the other processes running on the machine.
1392
ERROR: Missing protocol machine information
Description
An internal error occurred in the IIOP Server Listener/Handler.
Action
Contact BEA Customer Support.
1393
ERROR: Missing protocol machine information
Description
An internal error occurred in the IIOP Server Listener/Handler.
Action
Contact BEA Customer Support.
1394
ERROR: Missing protocol machine information
Description
An internal error occurred in the IIOP Server Listener/Handler.
Action
Contact BEA Customer Support.
1395
ERROR: No : separator in network address
Description
The IIOP Server Handler process was invoked with a -n option that specified an incorrect network address. The network address argument to option -n of the IIOP Server Handler must be in one of the following formats:
"//hostname:port_number"
"//#.#.#.#:port_number"
The colon is missing in the argument.
Action
This is an internal error. Contact BEA Customer Support.
1396
ERROR: No memory for host variable
Description
The IIOP Server Listener/Handler failed to allocate memory for an internal structure.
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.
1397
ERROR: Cannot register WSH protocols
Description
While initializing the IIOP Server Handler, an internal error occurred.
Action
Check the user log for other error messages that may indicate the exact nature of the problem and reason for this failure.
1398
ERROR: Cannot allocate memory for named pipe name
Description
Solaris, HP-UX, AIX, and Tru64 UNIX only. The IIOP Server Listener/Handler failed to allocate memory for an internal structure.
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.
1399
ERROR: Cannot create named pipe file
Description
Solaris only. The IIOP Server Handler creates a named pipe to communicate with an IIOP Server Listener. The file for the named pipe cannot be created.
Action
Shut the IIOP Server Listener down, remove all files with names that begin with ISH.pipe from the APPDIR directory and reboot the IIOP Server Listener/Handler. If the problem persists, contact BEA Customer Support.
 |
 |
 |