Error and Information Messages

 

The CFGEN and FTGEN configuration tools provided with the eLink Adapter for CORBA issue error, warning, and informational messages to their log files and to the console during execution. The following sections describe the error and informational messages and the appropriate action to take.

 

---

Log File Messages for CFGEN and FTGEN Utilities

The CFGEN and FTGEN utilities issue the following log file error and informational messages:

101:INFO	Method <methodName> for object <interfaceName> returns a data type not supported by FML, Service not Added
	DESCRIPTION	A CORBA object method defined in the Interface Repository returns a data type not compatible with FML32. Non FML data types are not supported by the Adapter. A Service is not added to the configuration for the CORBA object method.
	ACTION	None.
102:INFO	Method <methodName> for object <interfaceName> takes an argument with a data type not supported by FML, Service not Added
	DESCRIPTION	A CORBA object method defined in the Interface Repository takes argument(s) of a data type not compatible with FML32. Non FML data types are not supported by the Adapter. A Service is not added to the configuration for the CORBA object method.
	ACTION	None.
103:INFO	Adding Service <serviceName> to the configuration.....
	DESCRIPTION	Service <serviceName> has been added to the configuration file.
	ACTION	None.
104:INFO	Service <svc.serviceName> already exists not added to configuration
	DESCRIPTION	Service <serviceName> is already on the configuration file. Duplicate Service names are not allowed on the configuration file.
	ACTION	None.
105:INFO	FML Field Table <filename> created containing <number of fields> field definitions
	DESCRIPTION	An FML Field Table <filename> has been created containing <number of fields> field definitions
	ACTION	None.
201:WARN	Unrecognized parameter : <configuration parameter>
	DESCRIPTION	An invalid parameter was encountered in the input configuration file.
	ACTION	Check the parameter name to ensure it is spelled correctly.
202:WARN	Config file specifies more PARAMS than IR for Service : <serviceName> Type information not available for Argument : <argumentName>
	DESCRIPTION	The PARAMS parameter for <serviceName> has more arguments than the IDL loaded on the Interface Repository.
	ACTION	Verify the Interface in the Interface Repository and correct the PARAMS parameter to match.
203:WARN	Config file specifies more FACTORYPARAMS than IR for Service : <serviceName> Type information not available for Argument : <argumentName>
	DESCRIPTION	The FACTORYPARAMS parameter for <serviceName> has more arguments than the IDL loaded on the Interface Repository.
	ACTION	Verify the Interface in the Interface Repository for the FACTORYOBJECT/FACTORYMETHOD and correct the FACTORYPARAMS parameter to match.
204:WARN	Interface name matching <interface name> not found on Interface Repository.
	DESCRIPTION	An interface that matches the full or partial interface name entered during CFGEN initialization was not found on the Interface Repository.
	ACTION	Check spelling of the full or partial interface name entered to ensure it is correct. Verify that the desired interface exists on the Interface Repository. Make any necessary corrections and re-execute the CFGEN utility.
301:ERROR	Service <serviceName> found multiple times in existing configuration
	DESCRIPTION	The input configuration file contains duplicate Service names.
	ACTION	Locate the duplicate Service names on the existing configuration and rename or delete one of the Services.
302:ERROR	Argument <fieldName> not added, definition already exists for this Service <serviceName>
	DESCRIPTION	A Service definition contains multiple PARAMS or FACTORYPARAMS with the same argument name.
	ACTION	Ensure that each argument name for a Service definition is unique.
303:ERROR	Existing argument <fieldName> appears multiple times with different data types
	DESCRIPTION	An argument name appears multiple times in the configuration file. Each occurrence does not have the same data type.
	ACTION	Verify that each occurrence of an argument name in the configuration defines arguments of the same data type.
304:ERROR	Existing Configuration contains a Service with no Service Name
	DESCRIPTION	A Service definition in the configuration file has a blank SERVICENAME parameter.
	ACTION	Populate the SERVICENAME with a valid adapter service name.
305:ERROR	Existing Configuration Service : <serviceName> has no Object Name
	DESCRIPTION	Service definition <serviceName> does not have a value for the OBJECTNAME parameter.
	ACTION	Populate the OBJECTNAME with the valid CORBA object name.
306:ERROR	Existing Configuration Service : <serviceName> has no Method Name
	DESCRIPTION	Service definition <serviceName> does not have a value for the METHODNAME parameter.
	ACTION	Populate the METHODNAME with the valid CORBA method name.

 

---

Console Error Messages for CFGEN and FTGEN Utilities

The CFGEN and FTGEN utilities issue the following console error and informational messages:

401:ERROR	Host name parameter is required to generate configuration
	DESCRIPTION	Host name was not entered when attempting to run CFGEN or FTGEN.
	ACTION	Enter the host name for the WLE domain that will be executing the Adapter server. This information can be found in the ISL server definition in the UBBCONFIG file for the WLE domain.
402:ERROR	Port number parameter is required to generate configuration
	DESCRIPTION	Port number was not entered when attempting to run CFGEN or FTGEN.
	ACTION	Enter the port number for the WLE domain that will be executing the Adapter server. This information can be found in the ISL server definition in the UBBCONFIG file for the WLE domain.
403:ERROR	New configuration file name is required to generate configuration
	DESCRIPTION	The new configuration file name was not entered when running CFGEN.
	ACTION	Enter a file name for the new configuration file generated by CFGEN at the prompt.
405:ERROR	Configuration file name is required to generate FML Field Table
	DESCRIPTION	An input configuration file name is required when running FTGEN.
	ACTION	Enter the name of the configuration file containing the FML fields to be added to the FML Field Table.
406:ERROR	FML Field Table name is required
	DESCRIPTION	A file name is required for the FML32 field table that is generated by FTGEN.
	ACTION	Enter a file name for the FML32 field table.
407:ERROR	Unable to open output file <fileName> ; <errorDetail>
	DESCRIPTION	An Error was encountered when trying to open output file <filename>.
	ACTION	Verify that the path exists where the file name is to be created. Verify file permissions on the directory where the file is to be created.
408:ERROR	Input file <configFile> access failed ; <errorDetail>
	DESCRIPTION	Unable to open or read the input file <configFile>.
	ACTION	Verify that the file exists in the current working directory or in the path specified. Verify file permissions to ensure read access.
409:ERROR	Unable to connect to Interface Repository ; <errorDetail>
	DESCRIPTION	An error occurred when trying to connect to the CORBA Interface Repository.
	ACTION	Verify that the WLE domain that the Interface Repository belongs to is booted (and is running the TMIFRSVR and ISL servers). Verify the Host name and Port number used to connect to the Interface Repository.
410:ERROR	Unable to access the Interface Repository ; <errorDetail>
	DESCRIPTION	An error occurred when trying to access to the CORBA Interface Repository.
	ACTION	Verify that the WLE domain that the Interface Repository belongs to is booted (and is running the TMIFRSVR and ISL servers). Verify the Host name and Port number used to connect to the Interface Repository.
411:ERROR	Attempt to access Method <method> arguments failed for Object <object> ; <errorDetail>
	DESCRIPTION	An error occurred when trying to access to the CORBA Interface Repository.
	ACTION	Verify that the WLE domain that the Interface Repository belongs to is booted (and is running the TMIFSVR and ISL servers). Verify the Host name and Port number used to connect to the Interface Repository.
450:ERROR	Unhandled exception encountered ; <errorDetail>
	DESCRIPTION	Execution Error.
	ACTION	Verify that WLE environment variables are set correctly (including TUXDIR and PATH).

 

---

Error Messages for eLink Adapter for CORBA Server

The eLink Adapter for CORBA server issues the following error and informational messages:

1001:INFO	Server shutdown
	DESCRIPTION	The e2a server has terminated. Services advertised by this server are no longer available.
	ACTION	None
1002:INFO	Received buffer type <buffer type> <subtype>
	DESCRIPTION	The buffer type and subtype received with the service request.
	ACTION	None
1003:INFO	getField - Occurs - Field <num> time(s) -- Parameter <num> time(s)
	DESCRIPTION	The number of occurrences of each data item.
	ACTION	None
1004:INFO	getField - FML('<fieldname>',<field type>) << value(<argument type>)
	DESCRIPTION	The FML field of name and type is being loaded from the CORBA argument of <argument type>
	ACTION	None
1005:INFO	Factory Listing - Id <id> Kind
	DESCRIPTION	<id> and <kind> for each factory returned from FactoryFinder
	ACTION	None
1007:INFO	C_Config:~C_Config() recovering resources
	DESCRIPTION	Configuration parameters have been unloaded from memory.
	ACTION	None
1008:INFO	Service list built
	DESCRIPTION	All services from the configuration file have been parsed and loaded.
	ACTION	None
1010:INFO	Found service '<service name>' in service map
	DESCRIPTION	A service request was received and a matching configuration SERVICENAME was located.
	ACTION	None
1011:INFO	advertising service <num>) <service name>
	DESCRIPTION	<service name> was advertised as an ATMI service to BEA Tuxedo based on the configuration loaded.
	ACTION	None
1012:INFO	Configuration loaded. Advertising services...
	DESCRIPTION	The configuration file has been parsed successfully. Valid services will be advertised to BEA Tuxedo.
	ACTION	None
1013:INFO	Service '<service name>' factory method '<method name>' has <num> FML parameter(s)
	DESCRIPTION	Configuration <service name> is mapped to CORBA method <method name> with <num> parameters.
	ACTION	None
1014:INFO	Factory OperationDef contains <num> parameter(s)
	DESCRIPTION	The factory method to be invoked calls for <num> parameters.
	ACTION	None
1015:INFO	Service '<service name>' :method '<method name>'
	DESCRIPTION	Configuration <service name> is mapped to CORBA method <method name>
	ACTION	None
1016:INFO	Service '<service name>':'<method name>' has <num> FML field(s) and <num> parameter(s)
	DESCRIPTION	Service to Method map with matching number of arguments in Interface Repository and Configuration file.
	ACTION	None
1017:INFO	Default context obtained
	DESCRIPTION	CORBA default context will be used throughout server operation.
	ACTION	None
1018:INFO	C_Service:~C_Service() recovering resources
	DESCRIPTION	A service's parameters have been unloaded from memory.
	ACTION	None
1019:INFO	Located Object Interface in IR
	DESCRIPTION	Interface Repository lookup was successful
	ACTION	None
1020:INFO	Located the operation '<operation name>' in IR
	DESCRIPTION	Interface Repository lookup was successful.
	ACTION	None
1021:INFO	Located OperationDef in IR
	DESCRIPTION	OperationDef object was constructed successfully.
	ACTION	None
1022:INFO	C_Service:getNVList() Getting empty NVList
	DESCRIPTION	An NVList was successfully created from the OperationDef.
	ACTION	None
1023:INFO	factory result is type <type>
	DESCRIPTION	The OperationDef of the Factory method specifies a return type of <type>.
	ACTION	None
1024:INFO	C_Service:getObject() '<object name>'
	DESCRIPTION	Attempting to acquire an Object reference to <object name> from WLE.
	ACTION	None
1025:INFO	Creating request
	DESCRIPTION	Attempting to create a CORBA:Request object
	ACTION	None
1026:INFO	Invoking one-way request
	DESCRIPTION	The CORBA method was defined as oneway. The request will be attempted and no results will be processed.
	ACTION
1027:INFO	Request complete
	DESCRIPTION	The request was successful. The CORBA method was invoked.
	ACTION	None
1028:INFO	Invoking request
	DESCRIPTION	The CORBA method is about to be invoked.
	ACTION	None
1029:INFO	Server raised Exception
	DESCRIPTION	The CORBA method raised an Exception.
	ACTION	None
1030:INFO	setBuffer - Field('<fieled name>',<field type>) >> Parameter-<idx> ('<name>',<type>)
	DESCRIPTION	FML field <field name> is being used to populate method parameter <name>.
	ACTION	None
1031:INFO	setBuffer - Occurs - Field <num> time(s) -- Parameter <num> time(s)
	DESCRIPTION	Specifies array depth.
	ACTION	None
1032:INFO	setBuffer - Unknown type found
	DESCRIPTION	Method contained an argument of unknown or unsupported buffer type.
	ACTION	Consult documentation for supported buffer types.
1033:INFO	setBuffer - SKIPPING parameter[<idx>] <argument name>
	DESCRIPTION	<argument name> is not an 'in' or 'inout' method argument.
	ACTION	None
1034:INFO	return type - <type>
	DESCRIPTION	The OperationDef specifies a return argument of type <type>.
	ACTION	None
1035:INFO	getBuffer - SKIPPING parameter[<idx>] <argument name>
	DESCRIPTION	<argument name> is not an 'out' or 'inout' method argument.
	ACTION	None
1036:INFO	Locating Name Service <NameService name>
	DESCRIPTION	Using <NameService name> to lookup Objects.
	ACTION	None
1037:INFO	Resolving object for <object name> in <registry>
	DESCRIPTION	Trying to locate <object name> using registry type <registry>.
	ACTION	None
1038:INFO	Executing service <service name>
	DESCRIPTION	Attempting to invoke method(s) associated with <service name>.
	ACTION	None
3001:ERROR	Configuration filename must be specified in the CLOPT
	DESCRIPTION	The '-C <filename>' parameter in the UBB CLOPT statement was not present.
	ACTION	Use tmunloadcf to verify that the e2a server has CLOPT= -- -C <filename> parameter.
3002:ERROR	Invalid buffer type received '<buffer type>'
	DESCRIPTION	A service call was received that was not an FML32 buffer type.
	ACTION	The Adapter only accepts service calls that contain FML32 data buffers.
3003:ERROR	Option requires an argument
	DESCRIPTION	The CLOPT -C argument was not followed by a filename.
	ACTION	Specify a valid filename after the -C in the Adapter CLOPT parameter.
3004:ERROR	Unrecognized option
	DESCRIPTION	An invalid argument was specified in the UBB CLOPT.
	ACTION	Remove extraneous arguments from the CLOPT parameter of the server.
3005:ERROR	Failed to initialize, correct CLOPT errors and retry tmboot
	DESCRIPTION	An error was detected trying to start the server.
	ACTION	Correct errors noted in previous ULOG messages.
3006:ERROR	No services to advertise. Startup aborted
	DESCRIPTION	After parsing the configuration file, no valid services were detected.
	ACTION	Correct errors in service definitions or add valid service definitions to the configuration file.
3007:ERROR	Unexpected CORBA Exception detected during initialization.
	DESCRIPTION	CORBA:Exception was received from WLE.
	ACTION	Troubleshoot problems with WLE.
3009:ERROR	CORBA Exception <IDL exception name>
	DESCRIPTION	CORBA:Exception was received from WLE.
	ACTION	Attempt to diagnose the cause of the Exception generated from WLE.
3012:ERROR	Unable to locate InterfaceRepository. Make sure that TMIFRSVR is running.
	DESCRIPTION	The Adapter was unable to access the InterfaceRepository in WLE.
	ACTION	Make sure that TMIFRSVR is running and has a valid .ifr database.
3013:ERROR	Missing variable in Service '<service name>' factory object '<factory>' method '<method name>'
	DESCRIPTION	A required configuration parameter is missing.
	ACTION	Specify all required parameters in the *SERVICE section of the Adapter configuration file.
3014:ERROR	SERVICE <service name> factory parameter count mismatch. config <num> != repository <num>
	DESCRIPTION	The factory method OperationDef argument count did not match the number of fields specified in the configuration file.
	ACTION	Make sure the number of FML Fields in the configuration file match the number of arguments in the IDL definition loaded in the repository.
3015:ERROR	SERVICE <service name> parameter count mismatch. methods <num> != parameters <num>
	DESCRIPTION	The CORBA method OperationDef argument count did not match the number of fields specified in the configuration file.
	ACTION	Make sure the number of FML Fields in the configuration file match the number of arguments in the IDL definition loaded in the repository.
3018:ERROR	SERVICE <service name> requires a RETURN field. Method return type is not void.
	DESCRIPTION	The CORBA method OperationDef result count did not match the number of fields specified in the configuration file.
	ACTION	Make sure the number of FML Fields in the configuration file match the number of arguments in the IDL definition loaded in the repository. Use void in the configuration file if the return type is void.
3019:ERROR	SERVICE <service name> has a void return type and configuration specifies a RETURN.
	DESCRIPTION	The CORBA method OperationDef result count did not match the number of fields specified in the configuration file.
	ACTION	Make sure the number of FML Fields in the configuration file match the number of arguments in the IDL definition loaded in the repository. Use void in the configuration file if the return type is void.
3020:ERROR	Invoking factory method < factory method> - CORBA Exception <exception name>
	DESCRIPTION	A CORBA:Exception occurred while trying to invoke the factory method.
	ACTION	Investigate CORBA exception from given factory method invocation.
3021:ERROR	getField(<field name>) failed. Unable to retrieve parameter.
	DESCRIPTION	The FML buffer did not contain the field <field name>.
	ACTION	All fields specified in the configuration file for input arguments to methods must be specified in the FML buffer used when invoking the service.
3033:ERROR	Unable to locate '<object name>' in '<registry type>'
	DESCRIPTION	The Object reference to <object name> could not be obtained.
	ACTION	Make sure the CORBA implementation of this object is loaded in the ORB.
3035:ERROR	'<operation name>' is not a CORBA Operation
	DESCRIPTION	The method name specified in the configuration file is not defined this way in the Interface Repository.
	ACTION	Correct the file or database in error.
3036:ERROR	'<interface name>' is not a CORBA Interface
	DESCRIPTION	The Object name specified in the configuration file is not defined this way in the Interface Repository.
	ACTION	Correct the file or database in error.
3037:ERROR	Failed to locate Object '<object name>' in Interface Repository.
	DESCRIPTION	The <object name> could not be found in the Interface Repository.
	ACTION	Load the Interface Repository with the corresponding IDL.
3038:ERROR	At least one method name must be specified
	DESCRIPTION	The method parameter in the configuration file was not found.
	ACTION	Fix the service definition in the configuration file that is in error.
3039:ERROR	Advertising service '<service name>' - <tperrno> - <tpstrerror>
	DESCRIPTION	A BEA Tuxedo error has occurred.
	ACTION	See BEA Tuxedo System messages for proper action(s). tpadvertise failed with an error.