WSCFG Messages 100-199
|
|
101
Open file "configfile" error
Description
A file IO error was detected while opening the specified SALT configuration file, which may be a SALT deployment file, a WSDF file or a WS-Policy file.
Action
Please make sure the file path is valid and the file has read permission.
102
File "configfile" is not well-formed
Description
The specified SALT configuration file is not a well-formed XML document.
Action
Check your SALT configuration file and make sure it is a well-formed XML document.
109
No available <WSGateway> definition found
Description
wsloadcf did not find any WSGateway instance definition in the SALT deployment file.
Action
Define at least one WSGateway instance in the SALT deployment file.
See Also
BEA SALT Administration Guide
112
Not a valid Policy attachment file. <wsp:Policy> root element is not found
Description
The reference policy file path points to an invalid WS-Policy file. The file does not contain <wsp:Policy> root element.
Action
Modify the policy location with a valid WS-Policy file path.
See Also
BEA SALT Administration Guide
125
Unable to find view file for VIEW "view_name"
Description
VIEW view_name was detected while loading a Tuxedo service definition from Tuxedo Service Metadata Repository. View file description was expected to check the consistency between the Tuxedo Service Metadata Repository definition and the view file definition. But the view file description for view_name could not be found.
Action
Add view_name to the VIEWFILES (environment variable) list, and make sure that VIEWDIR environment variable is set to the directory where viewfiles can be found.
See Also
tmloadrepos(1), viewfile(5)
126
Unable to find view file for VIEW32 "view_name"
Description
VIEW32 view_name was detected while loading a Tuxedo service definition from Tuxedo Service Metadata Repository. View file description was expected to check the consistency between the Tuxedo Service Metadata Repository definition and the view file definition. But the view file description for view_name could not be found.
Action
Add view_name to the VIEWFILES32 (environment variable) list. Make sure that VIEWDIR32 environment variable is set to the directory where viewfiles can be found.
See Also
tmloadrepos(1), viewfile(5)
128
Data type "data_type" for VIEW definition is not supported in the current release
Description
SALT configuration parser detected data type data_type was defined for VIEW structure. The conversion between XML data and VIEW structure data type data_type is not supported in the current BEA SALT release.
Action
Avoid using data type data_type in your view file definition.
See Also
viewfile
129
Data type "data_type" for VIEW32 definition is not supported in the current release
Description
SALT configuration parser detected data type data_type was defined for VIEW32 structure. The conversion between XML data and VIEW32 structure data type data_type is not supported in the current BEA SALT release.
Action
Avoid using data type data_type in your view file definition.
See Also
viewfile
133
Unable to find field table definition for parameter "field_name"
Description
FML/32 field field_name was detected while loading a Tuxedo service definition from Tuxedo Service Metadata Repository. Field table file description for this FML/32 field was expected to check the consistency between the Tuxedo Service Metadata Repository definition and the field table definition. But the field file description for field_name could not be found.
Action
Add field_name to the field table file, add the field table file name to the FIELDTBLS/32 (environment variable) list. Make sure that FLDTBLDIR/32 environment variable is set to the directory where field table files can be found.
See Also
tmloadrepos(1), field_tables(5)
134
Parameter "field_name" is not unique at the same FML/32 embedded level
Description
FML/32 field field_name was defined more than once as service parameters at the same embedded level in the Tuxedo Service Metadata Repository. This was not a valid service definition for BEA SALT.
Action
Check Tuxedo Service Metadata Repository input. Avoid defining the same parameter more than once within the same FML/32 buffer embedded level.
See Also
tmloadrepos(1)
137
Error accessing Metadata Repository: tperrno-tpstrerror
Description
A tuxedo system error was detected while retrieving Tuxedo Service Metadata Repository definition via TMMETADATA server.
Action
Check that TMMETADATA server is started successfully. Try to resolve the failure reason with the indicated tperrno.
See Also
TMMETADATA(1)
138
Error allocate FML32 buffer for the Service Metadata Repository access
Description
An attempt to dynamically allocate FML32 typed buffer using tpalloc() failed while retrieving Tuxedo Service Metadata Repository definition.
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 and/or swap space on the machine.
139
Unable to find service "service_name" definition in the Service Metadata Repository
Description
Service service_name definition could not be found in the current Service Metadata Repository.
Action
Check that the service name specified in the SALT configuration file is correct. If the desired Tuxedo service is not present in the Tuxedo Service Metadata Repository, execute the tmloadrepos command to add the service definition into the repository.
See Also
tmloadrepos(1)
140
Unable to find VIEW/32 view_name member description from either Service Metadata Repository or view file
Description
This message indicated that either VIEW/32 view_name members were not defined as parameters in Service Metadata Repository or the view file for VIEW/32 view_name could not be found.
Action
Add view_name to the VIEWFILES32 (environment variable) list. Make sure that VIEWDIR32 environment variable is set to the directory where viewfiles can be found.
See Also
tmloadrepos(1), viewfile(5)
141
View name is not specified for VIEW/32 data type
Description
view name was not defined for the VIEW/32 data type in the Service Metadata Repository while loading a Tuxedo service definition. Defining VIEW/32 buffer without view name is valid for Tuxedo Service Metadata Repository syntax, but it's prohibited in the BEA SALT configuration parser.
Action
Define proper view name for any VIEW/32 data type and update Tuxedo Service Metadata Repository accordingly.
See Also
tmloadrepos(1)
142
Parameter "parameter_name" contains invalid occurrence setting
Description
Un-reasonable parameter occurrence setting was detected for parameter parameter_name in the Service Metadata Repository. Parameter count attribute value must be no less than parameter requiredcount attribute value semantically.
Action
Check that the parameter count attribute value is no less then requiredcount attribute value. Update the service definition in Service Metadata Repository if needed.
See Also
tmloadrepos(1)
143
Parameter data type "data_type" is not supported in the current release
Description
SALT configuration parser detected FML/32 fields with data type data_type was defined as parameters in the Service Metadata Repository. The conversion between XML data and FML/32 field data type data_type is not supported in the current BEA SALT release.
Action
Avoid using FML/32 fields with data type data_type in the Tuxedo Service Metadata Repository.
144
No metadata definition for VIEW/32 view_name
Description
This message indicated that VIEW/32 view_name members were not defined as parameters in Service Metadata Repository. The view file for VIEW/32 view_name should be loaded by BEA SALT.
Action
Check that view_name is added to the VIEWFILES32 (environment variable) list. Make sure that VIEWDIR32 environment variable is set to the directory where viewfiles can be found.
145
TMMETADATA server is not available
Description
TMMETADATA server was detected unavailable while trying to load the service definition from the Service Metadata Repository.
Action
Make sure TMMETADATA server is started successfully. Check ULOG for TMMETADATA server related information.
See Also
TMMETADATA(1)
146
Inconsistent parameter "parameter_name" definition between metadata(type="parameter_type") and field table(type="field_type")
Description
Parameter parameter_name data type defined in the Tuxedo Service Metadata Repository was not the same as the field table definition for field parameter_name.
Action
Either change Tuxedo Service Metadata Repository definition or change the field table definition with the proper and consistent data type definition.
See Also
tmloadrepos(1), field_tables(5)
147
VIEW32 "view_name":member("parameter_name"):undefined in viewfile
Description
Parameter parameter_name for VIEW32 view_name specified in the Tuxedo Service Metadata Repository could not be found in the view file for VIEW32 view_name.
Action
Compare the Tuxedo Service Metadata Repository definition and the view file for VIEW/32 view_name. Make sure no unwanted view members are defined as parameters in the Tuxedo Service Metadata Repository.
See Also
tmloadrepos(1), viewfile(5)
148
VIEW "view_name":member("parameter_name"):undefined in view file
Description
Parameter parameter_name for VIEW view_name specified in the Tuxedo Service Metadata Repository could not be found in the view file for VIEW view_name.
Action
Compare the Tuxedo Service Metadata Repository definition and the view file for VIEW view_name. Make sure no unwanted view members are defined as parameters in the Tuxedo Service Metadata Repository.
See Also
tmloadrepos(1), viewfile(5)
151
VIEW32 "view_name":member("parameter_name"):type mismatch("parameter_type"<==>"view_member_type")
Description
Data type definition has been detected mismatch between parameter parameter_name of VIEW32 view_name defined in the Tuxedo Service Metadata Repository and the view member parameter_name defined in the view file of VIEW32 view_name.
Action
Check that the parameters definition for VIEW32 view_name in the Service Metadata Repository are consistent with the definitions in the view file. Update and reload the Service Metadata Repository if needed.
See Also
tmloadrepos(1), viewfile(5)
152
VIEW "view_name":member("parameter_name"):type mismatch("parameter_type"<==>"view_member_type")
Description
Data type definition has been detected mismatch between parameter parameter_name of VIEW view_name defined in the Tuxedo Service Metadata Repository and the view member parameter_name defined in the view file of VIEW view_name.
Action
Check that the parameters definition for VIEW view_name in the Service Metadata Repository are consistent with the definitions in the view file. Update and reload the Service Metadata Repository if needed.
See Also
tmloadrepos(1), viewfile(5)
153
View32 "view_name":member("parameter_name"):requiredcount value conflict
Description
Parameter parameter_name "requiredcount" value of VIEW32 view_name defined in the Service Metadata Repository has been detected different from the "count" value of the member parameter_name defined in the view file of VIEW32 view_name.
Action
Check that the parameters definition for VIEW32 view_name in the Service Metadata Repository are consistent with the definitions in the view file. Update and reload the Service Metadata Repository if needed.
See Also
tmloadrepos(1), viewfile(5)
154
View "view_name":member("parameter_name"):requiredcount value conflict
Description
Parameter parameter_name "requiredcount" value of VIEW view_name defined in the Service Metadata Repository has been detected different from the "count" value of the member parameter_name defined in the view file of VIEW view_name.
Action
Check that the parameters definition for VIEW view_name in the Service Metadata Repository are consistent with the definitions in the view file. Update and reload the Service Metadata Repository if needed.
See Also
tmloadrepos(1), viewfile(5)
155
View32 "view_name":member("parameter_name"):count value conflict
Description
Parameter parameter_name "count" value of VIEW32 view_name defined in the Service Metadata Repository has been detected different from the "count" value of the member parameter_name defined in the view file of VIEW32 view_name.
Action
Check that the parameters definition for VIEW32 view_name in the Service Metadata Repository are consistent with the definitions in the view file. Update and reload the Service Metadata Repository if needed.
See Also
tmloadrepos(1), viewfile(5)
156
View "view_name":member("parameter_name"):count value conflict
Description
Parameter parameter_name "count" value of VIEW view_name defined in the Service Metadata Repository has been detected different from the "count" value of the member parameter_name defined in the view file of VIEW view_name.
Action
Check that the parameters definition for VIEW view_name in the Service Metadata Repository are consistent with the definitions in the view file. Update and reload the Service Metadata Repository if needed.
See Also
tmloadrepos(1), viewfile(5)
157
View32 "view_name":member("parameter_name"):size value conflict
Description
Parameter parameter_name "size" value of VIEW32 view_name defined in the Service Metadata Repository has been detected different from the "size" value of the member parameter_name defined in the view file of VIEW32 view_name.
Action
Check that the parameters definition for VIEW32 view_name in the Service Metadata Repository are consistent with the definitions in the view file. Update and reload the Service Metadata Repository if needed.
See Also
tmloadrepos(1), viewfile(5)
158
View "view_name":member("parameter_name"):size value conflict
Description
Parameter parameter_name "size" value of VIEW view_name defined in the Service Metadata Repository has been detected different from the "size" value of the member parameter_name defined in the view file of VIEW view_name.
Action
Check that the parameters definition for VIEW view_name in the Service Metadata Repository are consistent with the definitions in the view file. Update and reload the Service Metadata Repository if needed.
See Also
tmloadrepos(1), viewfile(5)
163
GW Instances number exceeds max_gw_num. Ignores
Description
Too many GWWS instances had already been defined in the SALT deployment file. At most 1024 GWWS instances can be defined in one SALT deployment file. Ignore the latter GWWS definitions.
Action
No action required.
180
Unknown property "property_name"
Description
The specified property "property_name" is not supported in the current BEA SALT release.
Action
Correct the property name in your configuration file.
See Also
BEA SALT Administration Guide
189
No supported policy assertion is defined in the policy file
Description
wsloadcf did not find any supported WS-Policy assertion while parsing the specified WS-Policy file.
Action
Make sure the customized WS-Policy file is supported by BEA SALT.
See Also
BEA SALT Administration Guide
 |
 |
 |