WSCMD Messages 0-99
|
|
1
Usage: tmwsdlgen -c WSDF_file [-y] [-o wsdl_file] [-m {pack|raw|mtom}] [-t {wls|axis}]
Description
When the argument of tmwsdlgen is not valid, it will prompt the usage syntax.
Action
Reenter the command in correct syntax.
See Also
tmwsdlgen(1)
2
WARN: Configuration file name ignored. Longer than nchar characters.
Description
The length of configuration file name specified by "-c" option exceed specified characters. tmwsdlgen ignores the option.
Action
Use shorter configuration file name.
See Also
tmwsdlgen(1)
3
WARN: WSDL file name ignored. Longer than nchar characters.
Description
The length of WSDL file name specified by "-o" option exceed specified characters. tmwsdlgen ignores the option.
Action
Use shorter WSDL file name.
See Also
tmwsdlgen(1)
4
WARN: Invalid encoding style name ignored 'enc_style'. Must be 'doc' or 'rpc'.
Description
Invalid encoding style option has been specified by "-s" option. tmwsdlgen ignores the option.
Action
Use 'doc' or 'rpc'.
See Also
tmwsdlgen(1)
5
WARN: Invalid SOAP version name ignored 'soap_ver'. Must be '1.1' or '1.2'.
Description
Invalid SOAP version option has been specified by "-v" option. tmwsdlgen ignores the option.
Action
Use '1.1' or '1.2'.
See Also
tmwsdlgen(1)
6
ERROR: WSDF file must be specified using -c option.
Description
"-c" option is missing.
Action
Use "-c" option to specify the WSDF file.
See Also
tmwsdlgen(1)
7
WARN: WSDL file 'name' already exists. Overwrite(Y/N)[N]?
Description
The WSDL file exists. Please confirm if tmwsdlgen should overwrite it.
Action
Enter "Y" to overwrite the file, or enter "N" to quite tmwsdlgen.
See Also
tmwsdlgen(1)
8
ERROR: WSDL file generating failed.
Description
Failed to generate WSDL file.
Action
Check stderr and ULOG for detail.
See Also
tmwsdlgen(1)
9
INFO: WSDL file 'name' is generated.
Description
The WSDL file is generated successfully.
Action
None.
See Also
tmwsdlgen(1)
10
WARN: Invalid data mapping policy name ignored 'name'. Must be 'pack' or 'raw' or 'mtom'.
Description
Invalid data mapping policy name has been specified by "-m" option. tmwsdlgen ignores the option.
Action
None.
See Also
tmwsdlgen(1)
11
WARN: Invalid client toolkit name ignored 'name'. Must be 'wls' or 'axis'.
Description
Invalid client toolkit name has been specified by "-t" option. tmwsdlgen ignores the option.
Action
None.
See Also
tmwsdlgen(1)
19
WARN: Duplicate -c option. Overriding 'name1' with 'name2'.
Description
There are duplicate "-c" options in the command. The name1 option was specified but was then overridden by name2. The name2 option was used.
Action
Eliminate one of the options.
See Also
tmwsdlgen(1)
21
WARN: Duplicate -m option. Overriding 'name1' with 'name2'.
Description
There are duplicate "-m" options in the command. The name1 option was specified but was then overridden by name2. The name2 option was used. The two options specify contradictory or incompatible data mapping policy. The policy specified or implied in the option farthest to the right on the command line is used.
Action
Eliminate one of the options.
See Also
tmwsdlgen(1)
22
WARN: Duplicate -o option. Overriding 'name1' with 'name2'.
Description
There are duplicate "-o" options in the command. The name1 option was specified but was then overridden by name2. The name2 option was used. The two options specify different output WSDL file names. The file name specified or implied in the option farthest to the right on the command line is used.
Action
Eliminate one of the options.
See Also
tmwsdlgen(1)
23
WARN: Duplicate -t option. Overriding 'name1' with 'name2'.
Description
There are duplicate "-t" options in the command. The name1 option was specified but was then overridden by name2. The name2 option was used. The two options specify contradictory or incompatible client toolkit names. The client toolkit name specified or implied in the option farthest to the right on the command line is used.
Action
Eliminate one of the options.
See Also
tmwsdlgen(1)
25
WARN: Duplicate -s option. Overriding 'enc_style1' with 'enc_style2'.
Description
There are duplicate "-t" options in the command. The enc_style1 option was specified but was then overridden by enc_style2. The enc_style2 option was used. The two options specify contradictory or incompatible encoding styles. The encoding style specified or implied in the option farthest to the right on the command line is used.
Action
Eliminate one of the options.
See Also
tmwsdlgen(1)
26
WARN: Duplicate -v option. Overriding 'soap_ver1' with 'soap_ver2'.
Description
There are duplicate "-t" options in the command. The soap_ver1 option was specified but was then overridden by soap_ver2. The soap_ver2 option was used. The two options specify contradictory or incompatible SOAP version. The version specified or implied in the option farthest to the right on the command line is used.
Action
Eliminate one of the options.
See Also
tmwsdlgen(1)
27
ERROR: Error while obtaining the Bulletin Board parameters.
Description
An error was produced in tmwsdlgen while retrieving the Bulletin Board parameters. A more specific error explaining the situation should already exist in the user log.
Action
Check the user log for a more specific error message. Check that the TUXCONFIG is readable, and re-execute the tmwsdlgen command.
See Also
tmwsdlgen(1), UBBCONFIG(5)
28
ERROR: Execute permission denied, not application administrator.
Description
Execute permission was denied when a non-administrator was executing the tmwsdlgen process
Action
Only the BEA TUXEDO system application administrator can execute the command.
See Also
tmwsdlgen(1)
29
ERROR: Unable to initialize public key subsystem.
Description
An error occurred while initializing the public key subsystem. Many things could cause this failure, including a user implementation of a plug-in function returning a failure code.
Action
Ensure the registry is in a valid state with epifregedt. Ensure the implementation of the plug-in function did not return an error code.
See Also
epifregedt, _ec_sec_map_proof, _ec_sec_pki_init
30
ERROR: Cannot become a client - tperrno tperrno errno errno Uunixerr Unixerrno.
Description
The administrative client tmwsdlgen could not join the application.
Action
Only one tmwsdlgen may be run at a time.
See Also
tmwsdlgen(1)
31
ERROR: Failed to get current directory - errno errno.
Description
The tmwsdlgen could not get current directory.
Action
Check if current directory is valid.
32
ERROR: Cannot change to dir dirname.
Description
The tmwsdlgen could not change to the directory.
Action
Check if the specified directory is valid.
33
ERROR: command: syntax checking errors found.
Description
While executing tmwsdlgen, syntax errors were found during parsing the SALT WSDF file.
Action
Check the input WSDF file is well formatted and conforms to the SALT WSDF XML Schema definition.
See Also
tmwsdlgen(1)
34
WARN: Deprecated command line -v option. Please set version number using WSDF file.
Description
The -v option was specified on the tmwsdlgen command line. This option is no longer supported.
Action
Remove the -v option from the tmwsdlgen command line. Instead, define the SOAP version number in the input WSDF file.
See Also
BEA SALT Web Service Definition File Format Reference
35
WARN: Deprecated command line -s option. Please set doc/rpc encoding style using WSDF file.
Description
The -s option was specified on the tmwsdlgen command line. This option is no longer supported.
Action
Remove the -s option from the tmwsdlgen command line. Instead, define the SOAP encoding style in the input WSDF file.
See Also
BEA SALT Web Service Definition File Format Reference
36
(vtoc_errno 4: SALTCONFIG file is too small. Use tmadmin crdl to increase space.)
Description
The SALTCONFIG vtoc file is too small to load all SALT configuration items.
Action
Try to use tmadmin sub-command crdl to increase space for the SALTCONFIG file.
See Also
tmadmin(1), wsloadcf(1)
38
WARN: SALTCONFIG file not created: exiting
Description
While executing wsloadcf, the SALTCONFIG file did not exist. When asked if the SALTCONFIG file should be created, the administrator did not respond positively so the file was not created and loaded.
Action
No action required.
See Also
wsloadcf(1)
40
WARN: SALTCONFIG file not updated: exiting
Description
While executing wsloadcf, the SALTCONFIG file already exists. When asked if the SALTCONFIG file should be overwritten, the administrator did not respond positively so the file was not updated.
Action
No action required.
See Also
wsloadcf(1)
41
ERROR: SALTCONFIG environment variable not set
Description
While executing wsloadcf, the SALTCONFIG environment variable has not been set and exported.
Action
Set and export the SALTCONFIG environment variable and re-execute the command.
See Also
wsloadcf(1)
42
ERROR: SALTCONFIG environment variable must be an absolute pathname.
Description
While executing wsloadcf, the SALTCONFIG environment variable was not set and exported, or was not set to an absolute pathname (starting with /).
Action
Set and export the SALTCONFIG environment variable and re-execute the command.
See Also
wsloadcf(1), GWWS(1)
43
ERROR: SALTOFFSET environment variable must >= 0
Description
While executing wsloadcf, the SALTOFFSET environment variable is not set correctly to a non-negative integer offset.
Action
Set and export the SALTOFFSET environment variable to a non-negative integer offset and re-execute the command.
See Also
wsloadcf(1)
44
ERROR: SALTCONFIG not set or set incorrectly
Description
While executing wsloadcf, an error occurred in checking the SALTCONFIG device.
Action
Check that either the SALTCONFIG device or file does not exist (if it is being created for the first time) or that it exists and is a valid configuration file. Contact your BEA TUXEDO system Technical Support.
See Also
wsloadcf(1)
45
ERROR: Cannot create SALTCONFIG saltconfig
Description
While executing wsloadcf, creation of the SALTCONFIG file failed.
Action
A subsequent system message will indicate the nature of the failure. Correct the problem and re-execute the command.
See Also
wsloadcf(1)
46
INFO: A new file system has been created. (size = nblocks size-byte blocks)
Description
While executing wsloadcf, a new SALTCONFIG file or device was created with the specified size, nblocks.
Action
No action required.
See Also
wsloadcf(1)
47
ERROR: SALTCONFIG, SALTOFFSET device1 offset1 does not match first device entry in configuration device2 offset2
Description
While loading a SALTCONFIG file using wsloadcf, the device and offset specified by the SALTCONFIG and SALTOFFSET environment variables, device1 and offset1, don't match the information stored for the first entry in the configuration file, device2 and offset2. This occurs when the device (file) is moved from one name to another.
Action
Remove the configuration file before loading it with wsloadcf.
See Also
wsloadcf(1)
48
ERROR: Cannot create tablename
Description
While executing wsloadcf, a failure occurred while trying to create the specified tablename. One table is created for each of the objects defined in the SALTDEPLOY file and WSDF files.
Action
A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command.
See Also
wsloadcf(1)
49
ERROR: Cannot open tablename
Description
While executing wsloadcf, a failure occurred while trying to open the specified tablename. One table is created and opened for each of the objects defined in the SALTDEPLOY file and WSDF files.
Action
A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command.
See Also
wsloadcf(1)
50
ERROR: Cannot write tablename
Description
While executing wsloadcf, a failure occurred while trying to write the specified tablename. One table is created, opened and written for each of the objects defined in the SALTDEPLOY file and WSDF files.
Action
A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command.
See Also
wsloadcf(1)
51
ERROR: Failure opening SALTCONFIG section sectionname (vtoc_error=vtoc_errno)
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to update the SALTCONFIG file, wsloadcf got an error trying to open the specified sectionname. The section of the SALTCONFIG and a low level error code are printed in this message.
Action
Try to recreate a new SALTCONFIG. If the SALTCONFIG is a UNIX file, simply remove it. If it is stored on a raw disk, erase it by entering:
echo " " >$SALTCONFIG
If the error persists, check for disk-type error conditions that might cause problems writing to files.
Finally, contact BEA TUXEDO system Technical Support, making sure to have the vtoc_errno that was printed in the error message.
See Also
wsloadcf(1)
52
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while setting up a table to keep track of the information kept in the SALT configuration files.
Action
Ensure that 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.
53
ERROR: Failed to write the SALTCONFIG file (vtoc_errno=vtoc_errno).
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
An error occurred while writing to a section of the SALTCONFIG.
Action
If the SALTCONFIG file is a UNIX file, the file system that it
is in should be checked to see if it has enough free space.
The file should be checked to see if its permissions allow writing.
Try to recreate a new SALTCONFIG. If the SALTCONFIG file is a UNIX file, simply remove it.
If it is stored on a raw disk, erase it by entering:
echo " " >$SALTCONFIG
If the error persists, check for disk-type error conditions that might cause problems writing to files.
Finally, contact BEA TUXEDO system Technical Support, making sure to have the vtoc_errno that was printed in the error message.
See Also
wsloadcf(1)
54
ERROR: Current work directory path name is too long
Description
While executing wsloadcf, an attempt to get the current working directory path failed. This can indicate that either the directory pathname is greater than 78 characters in length or that the directory hierarchy is not readable.
Action
Check that the directory hierarchy has the proper permissions and is not longer than 78 characters, and re-execute the command.
55
ERROR: Invalid option
Description
The option specified is not a valid option to the wsloadcf command.
Action
Correct the options to the wsloadcf command as per the usage message.
See Also
wsloadcf(1)
56
Usage 1: command [-n] [-y] [-D loglevel] saltdeploy_file
Description
When the argument of wsloadcf is not valid, it will prompt the usage syntax.
Action
Reenter the command in correct syntax.
See Also
wsloadcf(1)
57
Usage 2: command [-n] [-y] [-D loglevel] -1 [-s {doc|rpc}] [-v {1.1|1.2}] salt_1.1_config
Description
When the argument of wsloadcf is not valid, it will prompt the usage syntax.
Action
Reenter the command in correct syntax.
See Also
wsloadcf(1)
58
ERROR: SALT deploy file must be specified
Description
While executing wsloadcf, SALTDEPLOY file path was not included
Action
Specify a SALTDEPLOY file path in the command line.
See Also
wsloadcf(1)
59
ERROR: Input file absolute path name is too long
Description
The length of the absolute path name of the SALTDEPLOY file is greater than MAXTLSTRING.
Action
Specify a shorter path name.
See Also
wsloadcf(1)
60
ERROR: command: errors found during syntax checking
Description
While executing wsloadcf, syntax errors were found during parsing the SALTDEPLOY file and referenced WSDF files, WS-Policy files.
Action
Check the input SALTDEPLOY file and referenced WSDF files, WS-Policy files are well formatted and conforms to the SALT XML Schema definition.
See Also
wsloadcf(1), BEA SALT Web Service Definition File Reference, BEA SALT Deployment File Reference
61
INFO: SALTCONFIG file filename created
Description
While executing wsloadcf, the input SALTDEPLOY file has been successfully processed and a new SALTCONFIG file or device, filename, has been created (that is, it did not exist and a new one was created).
Action
No action required.
62
INFO: SALTCONFIG file filename updated
Description
While executing wsloadcf, the input SALTDEPLOY file has been processed and an existing SALTCONFIG file or device has been updated with the information.
Action
No action required.
63
ERROR: '-1' option must be specified before setting '-s' option.
Description
wsloadcf supports to parse the SALT 1.1 configuration file. This error indicates that '-1' option was not specified or was specified behind the '-s' option in the command line when parsing a SALT 1.1 configuration file.
Action
Correct the options to the wsloadcf command as per the usage message.
See Also
wsloadcf(1)
64
ERROR: '-1' option must be specified before setting '-v' option.
Description
wsloadcf supports to parse the SALT 1.1 configuration file. This error indicates that '-1' option was not specified or was specified behind the '-v' option in the command line when parsing a SALT 1.1 configuration file.
Action
Correct the options to the wsloadcf command as per the usage message.
See Also
wsloadcf(1)
71
ERROR: Failed to parse the XML with location 'url_location'.
Description
An error occurred while wsdlcvt attempting to parse the imported XML Schema content from the downloadable location url_location.
Action
Check that the imported XML Schema is specified with the correct downloadable location. Correct the XML Schema URL location or correct the XML Schema content. Then re-execute wsdlcvt.
See Also
wsdlcvt(1)
72
ERROR: Failed to manipulate the XML document.
Description
An error occurred while wsdlcvt attempting to parse the imported XML Schema content and generate the Xerces DOM Tree.
Action
A subsequent Apache Xerces error message will indicate the nature of the failure. Refer to Apache Xerces Document for the explanation.
See Also
wsdlcvt(1)
73
ERROR: Failed to manipulate the XML document.
Description
See Message 72 above.
Action
See Message 72 above.
See Also
wsdlcvt(1)
74
WARN: Importing schema without location.
Description
wsdlcvt detects the specified WSDL file contains imported XML Schema (defined with <xsd:import>), but these XML Schemas are not associated with downloadable URL location.
Action
If you'd like wsdlcvt automatically import XML schema content, manually edit the WSDL file to define URL location value for imported XML Schema.
See Also
wsdlcvt(1)
 |
 |
 |