System Messages: WSCFG Catalog 200-299
|
![]() |
![]() |
209 |
Schema validate initialization error | |
|
Description |
Xerces initialization failed before validating the XML document. |
Action |
This error was mostly due to the system memory allocation error. Please make sure sufficient memory can be used by the current process. | |
211 |
XML Exception(err_string) | |
|
Description |
An attempt to parse the XML document failed, see err_string for further information. Xerces library throws an XML Exception. |
Action |
See Xerces reference for XML Exception. | |
212 |
DOM Exception(errcode:err_string) | |
|
Description |
An attempt to parse the XML document failed, see errcode and err_string for further information. Xerces library throws a DOM Exception. |
Action |
See Xerces reference for DOM Exception. | |
219 |
Parameter schema ("param_schema_val") not recognized | |
|
Description |
GWWS cannot find the XML Schema definition file according to the XML Schema namespace URI of the |
Action |
Make sure the | |
See Also |
| |
220 |
Buffer schema ("param_schema_val") not recognized | |
|
Description |
GWWS cannot find the XML Schema definition file according to the XML Schema namespace URI of the |
Action |
Make sure the | |
See Also |
| |
221 |
ERROR: Memory Allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
Action |
Make sure 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. | |
222 |
ERROR: Same advertised Tuxedo service [svc_name] is referenced more than once | |
|
Description |
GWWS detects two outbound Tuxedo services are associated with the same Tuxedo service name. |
Action |
Advertising two outbound Tuxedo services with the same service name may result unexpected behavior. Customers need to manually update the | |
223 |
ERROR: Could not open *OPERATION section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
Try to recreate a new echo " " >$SALTCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact Oracle Technical Support. | |
See Also |
| |
224 |
ERROR: Could not open *WSDF section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
225 |
ERROR: Could not access No.seq_num *WSDF entry in SALTCONFIG | |
|
Description |
The While trying to access the |
Action |
See message 223 above. | |
See Also |
| |
226 |
ERROR: Could not allocate memory for No.seq_num *WSDF entry | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
Action |
Make sure 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. | |
227 |
ERROR: Could not open *BINDING section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
228 |
ERROR: Could not access No.seq_num *BINDING entry in SALTCONFIG | |
|
Description |
The While trying to access the |
Action |
See message 223 above. | |
See Also |
| |
229 |
ERROR: Could not allocate memory for No.seq_num *BINDING entry | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
Action |
Make sure 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. | |
230 |
ERROR: Could not open *ENDPOINT section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
231 |
ERROR: Could not access No.seq_num *ENDPOINT entry in SALTCONFIG | |
|
Description |
The While trying to access the |
Action |
See message 223 above. | |
See Also |
| |
234 |
ERROR: Could not open *GATEWAY section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
235 |
ERROR: Could not find Gateway gateway_id settings | |
|
Description |
GWWS cannot find the Gateway gateway_id information from the |
Action |
Make sure the gateway instance id is correctly defined in both SALT deployment file and in the UBBCONFIG file. | |
236 |
ERROR: Could not allocate memory for GWWS information | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
Action |
Make sure 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. | |
237 |
ERROR: Could not open *RESOURCES section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
238 |
ERROR: Could not access *RESOURCES entry in SALTCONFIG | |
|
Description |
The While trying to access the |
Action |
See message 223 above. | |
See Also |
| |
240 |
ERROR: Could not open *POLICY section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
241 |
ERROR: Could not access No.seq_num *POLICY entry in SALTCONFIG | |
|
Description |
The While trying to access the |
Action |
See message 223 above. | |
See Also |
| |
242 |
ERROR: Could not allocate memory for No.seq_num *POLICY entry | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
Action |
Make sure 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. | |
243 |
ERROR: Could not allocate memory for policy reference | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
Action |
Make sure 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. | |
244 |
ERROR: Could not open *PLUGIN section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
245 |
ERROR: Could not allocate memory for *PLUGIN entry | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
Action |
Make sure 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. | |
246 |
ERROR: WSBinding Number Exceeds the Limit 2048 | |
|
Description |
An attempt to parse WSBinding of the imported WSDF file failed because the WSBinding number exceeds the limit. 2048 is the max value. |
Action |
Make sure there are no too many WSBindings defined in the WSDF file. | |
250 |
ERROR: Missing attribute " | |
|
Description |
Missing attribute |
Action |
Use the correct SAML key metadata file, or restore it from backup, or recreate it. | |
251 |
ERROR: Missing element " | |
|
Description |
The required XML element |
Action |
Use the correct SAML key metadata file, or restore it from backup, or recreate it. | |
252 |
ERROR: Bad SAML Metadata Magic " | |
|
Description |
An invalid SAML key metadata magic were found, the key metadata file is either invalid or corrupted. |
Action |
Use the correct SAML key metadata file, or restore it from backup, or recreate it. | |
253 |
ERROR: Unsupported signature algorithm " | |
|
Description |
An unsupported signature algorithm were found in SAML key metadata file, the key metadata file is either invalid or corrupted. |
Action |
Use the correct SAML key metadata file, or restore it from backup, or recreate it. | |
254 |
ERROR: More than one Metadata "< | |
|
Description |
A duplicated XML element with tag name |
Action |
Use the correct SAML key metadata file, or restore it from backup, or recreate it. | |
255 |
ERROR: More than one Metadata "< | |
|
Description |
Only one |
Action |
Use the correct SAML key metadata file, or restore it from backup, or recreate it. | |
257 |
ERROR: File permission error.( | |
|
Description |
Unable to access SAML key metadata file |
Action |
Corret the file permission problem for the SAML key metadata file. | |
258 |
ERROR: The specified filename is not a file.( | |
|
Description |
The specified SAML key metadata filename |
Action |
Use the correct SAML key metadata file. | |
259 |
ERROR: Unknown file operation error on file | |
|
Description |
There was a file operation error on SAML key metadata file |
Action |
Use the correct SAML key metadata file, or change it with correct permission. | |
260 |
ERROR: File | |
|
Description |
A file with the same name as SAML key metadata file |
Action |
Either use the existing file as SAML key metadata file, or change its name to something different, or specify different file name for SAML key metadata file. | |
261 |
ERROR: File " | |
|
Description |
The specified SAML key metadata file |
Action |
Use the correct SAML key metadata file filename, or create it. | |
262 |
ERROR: File " | |
|
Description |
The specified file |
Action |
Use the correct SAML key metadata file, or restore it from backup, or recreate it. | |
263 |
ERROR: Output SAML metadata file " | |
|
Description |
An error encountered while generating XML based SAML key metadata file |
Action |
Check and correct the file permission and filesystem free space; if error persist contact your Oracle technical support. | |
264 |
ERROR: Encrypt binary data failed.( | |
|
Description |
Failed to encrypt binary data in the SAML key metadata file. The |
Action |
Contact your Oracle technical support. | |
265 |
ERROR: Memory allocation failed.( | |
|
Description |
Memory allocation failed while processing SAML key metadata file. The |
Action |
Free system memory and try the processing again; if problem persist contact your Oracle technical support. | |
266 |
ERROR: Base64 encoding failed.( | |
|
Description |
A BASE64 encoding failure occurred while processing the SAML key metadata. The |
Action |
Contact your Oracle technical support. | |
267 |
ERROR: At least one of the two element must be specified.( | |
|
Description |
At lease one of the element in |
Action |
Use the correct SAML key metadata file, or restore it from backup; if problem persists contact your Oracle technical support. | |
268 |
ERROR: SAML metadata validation failure.( | |
|
Description |
The SAML key metadata validation failed at data |
Action |
Use the correct SAML key metadata file, or restore it from backup, or recreate it. | |
269 |
WARN: SAML issuer not found.( | |
|
Description |
The specified issuer with |
Action |
Either use a correct issuer name or local reference id for updating the SAML key metadata, or check whether the SAML SSO request is coming from an authentic source. | |
270 |
ERROR: Random numbers generation failure.( | |
|
Description |
A cryptographic random number generation operation failed with reference to |
Action |
Contact your Oracle technical support. | |
271 |
WARN: SAML gateway not found.( | |
|
Description |
A gateway with |
Action |
Correct the SAML key metadata file by adding the requseted gateway record. | |
272 |
ERROR: Failed to create temporary file. | |
|
Description |
Unable to create temporary to hold SAML key metadata while processing request. |
Action |
Check for write permission of current working directory and correct it. | |
273 |
ERROR: Bad SAML Metadata Magic " | |
|
Description |
An invalid SAML key metadata magic were found, the key metadata file is either invalid or corrupted. |
Action |
Use the correct SAML key metadata file, or restore it from backup, or recreate it. | |
274 |
ERROR: Invalid SAML Metadata file, missing | |
|
Description |
The SAML key metadata file processed missing an element of |
Action |
Use the correct SAML key metadata file, or restore it from backup, or recreate it. | |
275 |
ERROR: Gateway metadata already exists. | |
|
Description |
The operation adding gateway record failed because it already exists. |
Action |
Delete the gateway record and then try it again. | |
276 |
ERROR: Gateway | |
|
Description |
The operation adding gateway record with instance |
Action |
Delete the gateway instance | |
277 |
ERROR: Issuer | |
|
Description |
The operation adding issuer record with |
Action |
Delete the issuer | |
278 |
ERROR: SAML metadata validation failed. | |
|
Description |
SAML key metadata validation failed. |
Action |
Use the correct SAML key metadata file, or restore it from backup, or recreate it. | |
279 |
INFO: SAML | |
|
Description |
The SAML key metadata operation |
Action |
Correct the command and try it. | |
280 |
INFO: SAML | |
|
Description |
The SAML key metadata operation |
Action |
Correct the command and try it. | |
281 |
ERROR: SAML key metadata password does not match. | |
|
Description |
The entered the SAML key metadata administrative password does not match. |
Action |
Use the correct password. |
![]() |
![]() |
![]() |