System Messages: GWWS Catalog 1600-1699
|
|
|
|
1600 |
ERROR: SCO extension for module mod is not found | |
|
|
Description |
Could not find context extension for module mod. |
|
Action |
Contact Oracle Customer Support. | |
|
1601 |
ERROR: Memory allocation failure.(mod:ref) | |
|
|
Description |
Memory allocation failure occurred in module mod with reference data ref. |
|
Action |
Increase system memory. If condition persist contact your Oracle support. | |
|
1602 |
ERROR: SCO extension for module mode is not found | |
|
|
Description |
Could not find context extension for module mod. |
|
Action |
Contact Oracle Customer Support. | |
|
1603 |
ERROR: Memory allocation failure.(mod:ref) | |
|
|
Description |
Memory allocation failure occurred in module mod with reference data ref. |
|
Action |
Increase system memory. If condition persist contact your Oracle support. | |
|
1639 |
ERROR: Missing required configuration information, outbound X509 security is not enabled. | |
|
|
Description |
The required configuration information such as private key and X.509 certificate is not configured, outbound X.509 security feature is not enabled. |
|
Action |
If X.509 security feature is desired correct the configuration information to include X.509 certificate and private key location. | |
|
1640 |
ERROR: Failed to find user private key!(fname) | |
|
|
Description |
Failed to find user private key in PEM format from the configured file fname. |
|
Action |
Check whether configuration is correct; if it is correct make sure the proper private key in PEM format is in the file. Also make sure a proper password for the private key is configured if the private key is protected by encryption. | |
|
1641 |
INFO: No password specified for pemfile, assume not encrypted. | |
|
|
Description |
Informational message indicating there is no password configured for PEM file of the name pemfile. |
|
Action |
Informational only, no action required. | |
|
1642 |
ERROR: Failed to canonicalize message body.(reason) | |
|
|
Description |
Error occurred while canonicalizing the message body; the reason of failure is reason. |
|
Action |
Contact you Oracle support. | |
|
1643 |
ERROR: Failed to map to remote user.(gid,uid) | |
|
|
Description |
The credential mapper plug-in failed to map a local Tuxedo user with gid and uid to a remote user. |
|
Action |
Check the credential mapper configured for the correct mapping of local user with gid and uid to a remote user. | |
|
1644 |
ERROR: Memory allocation failure.(fname:line) | |
|
|
Description |
Memory allocation failure occurred in module fname at line line. |
|
Action |
Increase system memory. If condition persist contact your Oracle support. | |
|
1645 |
ERROR: Failed to retrieve user certificate.(certfile) | |
|
|
Description |
Failure occurred to retrieve a user X.509 certificate from the PEM file certfile. |
|
Action |
Check whether the certfile exists and contains the proper user X.509 certificate in PEM format. | |
|
1646 |
ERROR: X509 Authentication is required, but a policy assertion is not supported. | |
|
|
Description |
Outbound X509 authentication is required but at least one policy assertion is not supported. |
|
Action |
Contact your Oracle Support. | |
|
1647 |
ERROR: Failed to add binary security token.(retcode) | |
|
|
Description |
Failure occurred while adding binary security token to the message. The error return code is retcode. |
|
Action |
Contact your Oracle support. | |
|
1648 |
ERROR: Failed to load user private key!(keyfile) | |
|
|
Description |
Unable to load user private key from the the keyfile. |
|
Action |
Check whether the keyfile contains the correct private key in PEM format and whether the configured private key password is correct. | |
|
1649 |
ERROR: Failure occurred while creating signature.(code) | |
|
|
Description |
Failed to register plug-in during sign creation; the error code is code. |
|
Action |
Contact your Oracle support. | |
|
1650 |
ERROR: Failure occurred while signing message body.(code) | |
|
|
Description |
Failure occurred while signing the message body. The error code is code. |
|
Action |
Contact your Oracle support. | |
|
1651 |
ERROR: Failure occurred while adding signature value.(code) | |
|
|
Description |
Encountered an error while adding signaure value to the security header of the message. The error code is code. |
|
Action |
Contact your Oracle support. | |
|
1652 |
SOAP Error: Failed to generate Signature. | |
|
|
Description |
An error occurred cause no signature is generated for the message. |
|
Action |
Check for prior error message in the Tuxedo ULOG file that is related to this message for proper action. | |
|
1653 |
ERROR: Could not get PEM file name from the principal. | |
|
|
Description |
Failed to detemine the PEM file name from the principal information. |
|
Action |
Check for prior error message in the Tuxedo ULOG file that is related to this message for proper action. | |
|
1654 |
WARN: Password not found for name.(type) | |
|
|
Description |
Unable to retrieve user password from the metadata for username name. The type of name used is indicated in type. |
|
Action |
Add user password to the SAML metadata file. | |
|
1655 |
INFO: User directory dir as Certificate Store. | |
|
|
Description |
Informational message for information about which directory is used as Certificate Store. |
|
Action |
No action required. | |
|
1656 |
INFO: Use 'certs' directory as Certificate Store. | |
|
|
Description |
Informational message stating that 'certs' directory is used as Certificate Store. |
|
Action |
No action required. | |
|
1657 |
INFO: use current working directory as Certificate Store. | |
|
|
Description |
Informational message stating that current working directory is used as Certificate Store. |
|
Action |
No action required. | |
|
1661 |
ERROR: File mif does not exist | |
|
|
Description |
File with name mif does not exist |
|
Action |
Add the MIF file mif to the file system. | |
|
1662 |
ERROR: Cannot open env file env to write | |
|
|
Description |
Failed to open environment file env to write. |
|
Action |
Set proper access right to the envirnment file env so that the "write" operation can succeed. | |
|
1663 |
ERROR: Could not get the Repos file data | |
|
|
Description |
Unable to get data from Tuxedo metadata repository. |
|
Action |
Check the Tuxedo ULOG for any failure that is related to metadata repository. If problem persist contact Oracle Customer Support. | |
|
1664 |
ERROR: Repository file cannot be opened ret:rtn | |
|
|
Description |
Failed to open repository file with return code rtn. |
|
Action |
Check Tuxedo ULOG for error code and fix the problem accordingly. | |
|
1665 |
ERROR: cannot MIF filemif | |
|
|
Description |
Could not open MIF file mif to read. |
|
Action |
Check the Tuxedo ULOG for error code and correct the problem. | |
|
1666 |
ERROR: updateOutbound cannot read WSDF fname | |
|
|
Description |
Could not read WSDF defined in file with name fname. |
|
Action |
Make sure the WSDF file fname exists with correct permission. | |
|
1667 |
ERROR: basename token not found | |
|
|
Description |
The basename token can not be found. |
|
Action |
Contact Oracle Customer Support. | |
|
1668 |
ERROR: filename token not found | |
|
|
Description |
The filename token can not be found. |
|
Action |
Contact Oracle Customer Support. | |
|
1669 |
ERROR: WSDL not in correct format | |
|
|
Description |
The WSDL file is not correctly formatted. |
|
Action |
Correct the WSDL file format. | |
|
1670 |
ERROR: /wsdl:definitions token not found | |
|
|
Description |
Could not find the "</wsdl:definitions" token in the WSDL file. |
|
Action |
Correct the WSDL file to be properly formatted. | |
|
1671 |
ERROR: cannot open the WSDL file wsdlfile | |
|
|
Description |
Failed to open WSDL file wsdlfile to write. |
|
Action |
Make sure the WSDL file wsdlfile exists with proper permissions. | |
|
1672 |
ERROR: allocating embedded receive FML32 buffer for Metadata Repository access | |
|
|
Description |
Could not allocate a FML32 buffer to access one service information defined in Metadata Repository. |
|
Action |
Increase system memory. | |
|
1673 |
ERROR: getting embedded receive FML32 buffer for Metadata Repository access errcode | |
|
|
Description |
Could not find embedded service informaton from the received FML32 buffer for Metadata Repository. |
|
Action |
Base on the errcode and correct the problem. | |
|
1674 |
ERROR: getting embedded receive FML32 buffer for Metadata Repository service creation errcode | |
|
|
Description |
Could not find service information from the received FML32 buffer for Metadata Repository service creation. |
|
Action |
Base on the errcode and correct the problem. | |
|
1675 |
ERROR: getting embedded receive FML32 buffer for Metadata Repository service deletion errcode | |
|
|
Description |
Could not find service information from the received FML32 buffer for Metadata Repository service deletion. |
|
Action |
Base on the errcode and correct the problem. | |
|
1676 |
ERROR: getting svcname FML32 buffer for Metadata Repository access | |
|
|
Description |
Could not find service information from the received FML32 buffer for Metadata Repository. |
|
Action |
Check the Metadata Repository for incorrectly configured service and correct it. | |
|
1677 |
ERROR: processWSDLfile in wsdlFileBrowser ret:code | |
|
|
Description |
Error occurred while process WSDL file in wsdlFileBrowser with return code code. |
|
Action |
Check Tuxedo ULOG file for any error related to this and correct it. If problrm persist contact Oracle Customer Support. | |
|
1678 |
ERROR: processWSDLfile in createOutboundservice ret:code | |
|
|
Description |
Error occurred while process WSDL file in createOutboundservice with return code code. |
|
Action |
Check Tuxedo ULOG file for any error related to this and correct it. If problrm persist contact Oracle Customer Support. | |
|
1679 |
ERROR: allocating send FML32 buffer for Meatadata Repository service creaction | |
|
|
Description |
Failed to allocate a FML32 buffer to create service in the Metadata Repository. |
|
Action |
Increase system memory. | |
|
1680 |
ERROR: allocating send FML32 buffer for Metadata Repository access | |
|
|
Description |
Failed to allocate a FML32 buffer for access Metadata Repository. |
|
Action |
Increase system memory. | |
|
1681 |
ERROR: allocating send FML32 buffer for Metadata Repository service deletion | |
|
|
Description |
Failed to allocate a FML32 buffer for deleting service from Metadata Repository. |
|
Action |
Increase system memory. | |
|
1682 |
ERROR: allocating receive FML32 buffer for Meatadata Repository service creaction | |
|
|
Description |
Failed to allocate a FML32 buffer to create service in the Metadata Repository. |
|
Action |
Increase system memory. | |
|
1683 |
ERROR: allocating receive FML32 buffer for Metadata Repository access | |
|
|
Description |
Failed to allocate a FML32 buffer for access Metadata Repository. |
|
Action |
Increase system memory. | |
|
1684 |
ERROR: allocating receive FML32 buffer for Metadata Repository service deletion | |
|
|
Description |
Failed to allocate a FML32 buffer for deleting service from Metadata Repository. |
|
Action |
Increase system memory. | |
|
1685 |
ERROR: allocating receive FML32 buffer TMIB access:errcode | |
|
|
Description |
Failed to allocate a FML32 buffer for accessing TMIB, the error code is errcode. |
|
Action |
Increase system memory. | |
|
1686 |
ERROR: getting CLOPT value for TMETADATASERVER access:errcode | |
|
|
Description |
Failed to get CLOPT information for accessing Metadata server, the error code is errcode. |
|
Action |
Check the errcode and make the correction. If problem persist contact Oracle Customer Support. | |
|
1687 |
ERROR: getting Metadata option ret=rc, rep filerepos | |
|
|
Description |
Error occurred while getting Metadata option; the return code is rc, and the repository file is repos. |
|
Action |
Check the Tuxedo ULOG file for related error message to determine the cause of failure, and correct the problem accordingly. | |
|
1688 |
ERROR: problem occured when adding operation to the metadata repository | |
|
|
Description |
Problem occurred when adding operation to the Metadata Repository. |
|
Action |
Contact Oracle Customer Support. | |
|
1689 |
ERROR: operation could not be added to the repository file | |
|
|
Description |
Error occurred when adding MIF to Metadata Repository file. |
|
Action |
Check any error message in Tuxedo ULOG file and fix it. If problem persist contact Oracle Customer Support. | |
|
1690 |
ERROR: tpcall in addMifTree2Repos errno:errno, errstr | |
|
|
Description |
The |
|
Action |
Check errno and errstr and fix the problem accordingly; it the problem still there contact Oracle Customer Support. | |
|
1693 |
WARNING: Attributes are not supported that contain FML32 data type | |
|
|
Description |
The attributes contains FML32 data type are not supported. |
|
Action |
Remove the offending attribute or change the offending attribute. | |
|
1694 |
WARNING: Attributes are not supported that contain VIEW32 data type | |
|
|
Description |
The attributes contains VIEW32 data type are not supported. |
|
Action |
Remove the offending attribute or change the offending attribute. | |
|
1695 |
WARNING: Attributes are not supported that contain XML data type | |
|
|
Description |
The attributes contains XML data type are not supported. |
|
Action |
Remove the offending attribute or change the offending attribute. | |
|
1696 |
WARNING: Attributes are not supported that contain CARRAY data type | |
|
|
Description |
The attributes contains CARRAY data type are not supported. |
|
Action |
Remove the offending attribute or change the offending attribute. | |
|
1697 |
ERROR: Required parameter from WSDL not present in message:name | |
|
|
Description |
Required parameter of name name does not present in message. |
|
Action |
Correct the WSDL. | |
|
1698 |
ERROR: input WSDL file size len greater then supported MAX size: max | |
|
|
Description |
The input WSDL file size, len bytes, exceed the supported maximum size of max. |
|
Action |
Modify the WSDL file to be smaller than the maximum allowed size. | |
|
1699 |
ERROR: Could not open private key file "keyfile" | |
|
|
Description |
Could not open a private key from the PEM file keyfile. |
|
Action |
Check whether the file exists, whether it contains a private key, and also check whether a proper password is configured for the user who own private key. | |
 |
 |
 |