NZE-28890: Entrust Login Failed

NZE-28890: Entrust Login Failed

Cause: An application s attempt to log in to an Entrust Profile failed. This could be caused by a number of problems including: 1. Entrust Admin or Authority was not online. 2. Invalid password for Entrust profile was specified. 3. Invalid path to Entrust profile was specified 4. Invalid Entrust initialization file was specified. 5. Entrust Server Login program was not executed (server-side only).

Action: Make sure that: 1. Entrust Authority is online; 2. Password for Entrust profile is specified correctly; 3. Path to Entrust profile is specified correctly; 4. A valid Entrust initialization file is provided; 5. Entrust Server Login program is run before the database startup. For more information, enable Oracle Net tracing and the trace output should indicate the exact Entrust failure codes.

NZE-28885: No certificate with the required key usage found.

NZE-28885: No certificate with the required key usage found.

Cause: Certificate not created with the appropriate X509v3 key usage extension.

Action: Refer to Oracle Wallet Manager documentation to find out the supported key usages.

NZE-28884: invalid cipher suite

NZE-28884: invalid cipher suite

Cause: An invalid cipher suite to a string has been specified in the product s configuration file.

Action: Refer to the product documentation for information about the supported cipher suites.

NZE-28875: SSL: use server-gated cryptographic suites

NZE-28875: SSL: use server-gated cryptographic suites

Cause: This error is used as a internal status indicator and not really an error.

Action: This error is not normally visible to the user. Enable Oracle Net tracing and attempt the connection again. If the error persists, contact Oracle customer support.

NZE-28874: SSL: I or O closed - override goodbye kiss

NZE-28874: SSL: I or O closed - override goodbye kiss

Cause: This error is informational only. It indicates that the connection closed without error.

Action: This error is not normally visible to the user. Enable Oracle Net tracing and attempt the connection again. If the error persists, contact Oracle customer support.

NZE-28873: Invalid parameter

NZE-28873: Invalid parameter

Cause: A function was presented with a null parameter.

Action: This error is not normally visible to the user. Enable Oracle Net tracing and attempt the connection again. If the error persists, contact Oracle customer support.

NZE-28872: Invalid peer certificate format

NZE-28872: Invalid peer certificate format

Cause: The peer certficate does not conform to the X.509v3 standard.

Action: Refer to Oracle Wallet Manager documentation to find out how to get the peer certificate. Then contact Oracle customer support with the peer s certificate.

NNF-04006: Could not create outputfile

NNF-04006: Could not create outputfile

Cause: An output file could not be created in the current working directory

Action: Change the permissions of the current directory and restart the conversion tool.

NNF-04005: Cannot open inputfile

NNF-04005: Cannot open inputfile

Cause: The specified input file could not be found.

Action: restart the conversion tool with the correct input file.

NNF-04004: Invalid string in inputfile

NNF-04004: Invalid string in inputfile

Cause: the input file contains invalid lines.

Action: Check that the syntax of the input file is correct.

NNF-04003: Entry in inputfile is too long

NNF-04003: Entry in inputfile is too long

Cause: The makedbm program, limits entries in mapfiles to 1017 characters. Therefor, the conversion tool will not process TNS addresses which are longer than 1017 characters.

Action: Shorten the offending entry.

NNF-04002: Outputfile already exists

NNF-04002: Outputfile already exists

Cause: An old output file already exists in the current directory

Action: Remove the existing file, and restart the conversion tool

NNF-04001: Error converting input file

NNF-04001: Error converting input file

Cause: The input file contains lines that cannot be converted by the conversion program.

Action: Check that the syntax of the input file is correct.

NNF-04000: File succesfully converted

NNF-04000: File succesfully converted

Cause: The requested conversion is performed.

Action: Normal condition, no action necessary.

NNF-03004: DNS Class mismatch (string)

NNF-03004: DNS Class mismatch (string)

Cause: The query response packet returned a class different from the ones expected by the interface.

Action: Verify that the error is generated by the BIND functions on this platform. Notify Worldwide Customer Support of the error.

NNF-03003: Format error parsing server response

NNF-03003: Format error parsing server response

Cause: The query response packet returned from the BIND (DNS) API did not conform to the format listed in RFC 1035.

Action: Verify that the error is generated by the BIND functions on this platform. Notify Worldwide Customer Support of the error.

NNF-03002: Unknown BIND error code: string

NNF-03002: Unknown BIND error code: string

Cause: The return code in the BIND (DNS) query response did not conform to those values listed in RFC 1035.

Action: Verify that the error is generated by the BIND functions on this platform. Notify Worldwide Customer Support of the error.

NNF-02005: NIS key string does not exist in map string

NNF-02005: NIS key string does not exist in map string

Cause: The requested name was not found.

Action: For an unused name, no action is required, as this is the expected error. Otherwise, add the name to the map and reload the NIS (YP) maps.

NNF-02004: NIS map string does not exist

NNF-02004: NIS map string does not exist

Cause: The requested attribute does not exist.

Action: For an unused attribute, no action is required, as this is the expected error. Otherwise, add the attribute and reload the NIS (YP) maps.

NNF-02003: Unknown NIS error code: string

NNF-02003: Unknown NIS error code: string

Cause: An error code returned by a NIS (YP) function was not in the list expected by this program.

Action: Verify that the error is generated by the YP functions on this platform. Notify Worldwide Customer Support of the error.

NNF-02002: NIS value does not conform to adapter schema: string

NNF-02002: NIS value does not conform to adapter schema: string

Cause: The values in the maps used by the NIS adapter must conform to a specific set of internal formatting rules. This value returned did not conform to those rules.

Action: Should not be visible, unless you are attempting to create your own maps. If the error persists, contact Worldwide Customer Support.

NNF-02001: NIS client error string: string

NNF-02001: NIS client error string: string

Cause: A call to an NIS (YP) function failed. This message contains the text of the NIS error code returned.

Action: Should only be visible when returned as part of another error. If the error persists, contact Worldwide Customer Support.

NNF-01008: XDS attribute syntax string incorrect for Oracle Names syntax string

NNF-01008: XDS attribute syntax string incorrect for Oracle Names syntax string

Cause: The syntax as specified in the XDS object is different than that which is expected for the given Oracle names syntax.

Action: For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-01007: DCE long strings are not supported

NNF-01007: DCE long strings are not supported

Cause: A query returned a object which has a XOM OM_S_LONG_STRING. The current implementation does not support such objects.

Action: For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-01006: Attribute string not available

NNF-01006: Attribute string not available

Cause: A insertion call attempted to use an attribute which did not have a translation to a DCE attribute.

Action: Use another attribute, or insert the translation into DCE.

NNF-01005: Internal XOM class violation

NNF-01005: Internal XOM class violation

Cause: A DCE XOM call returned statuses inconsistent with the class definitions in the DCE documentation.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-01004: DCE returned unspecified error string

NNF-01004: DCE returned unspecified error string

Cause: A DCE call returned an status that was not in this implementation s list of possible status values for this DCE call.

Action: Verify that this platform s DCE release is not beyond those supported by this Oracle application. If the error persists, contact Worldwide Customer Support.

NNF-01003: DCE could not find cell name

NNF-01003: DCE could not find cell name

Cause: A DCE call returned an error that it could not find the cell name in its configuration file.

Action: Check that this machine has been configured for a DCE cell. Chcek that the DCE configuration file is not corrupted. On Unix, this file is dce_cf.db. Check if a simple call to dce_cf_get_cell_name() succeeds.

NNF-01002: DCE could not open configuration file

NNF-01002: DCE could not open configuration file

Cause: A DCE call returned an error that it could not access its configuration file.

Action: Check that the DCE configuration file for this platform is present, and accessable. On Unix this file is dce_cf.db. Check if a simple call to dce_cf_get_cell_ name() succeeds.

NNF-01001: ds_initialize: workspace initialization failed

NNF-01001: ds_initialize: workspace initialization failed

Cause: The DCE workspace as setup by ds_initialize() failed to initialize.

Action: Verify that conditions necessary for a successful ds_initialize() call are present on this platform (e.g is there enough memory?). Check that there is not another workspace user in this program. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-00540: Failed to insert name: string

NNF-00540: Failed to insert name: string

Cause: Failed to insert name into the native service.

Action: Verify that the name is not already in the native namespace and the appropriate access permissions are set for the namespace.

NNF-00110: no values exist

NNF-00110: no values exist

Cause: Test program help text.

Action: None.

NNF-00005: Functionality not implemented

NNF-00005: Functionality not implemented

Cause: The operation requested is not supported in this implementation.

Action: If this is retrieved from a production release, contact Worldwide Customer Support. Otherwise, check the release notes as to the restrictions in this release.

NNL-00262: Request forwarding is currently disabled

NNL-00262: Request forwarding is currently disabled

Cause: Control program general message.

Action: None.

NNL-00261: Request forwarding is currently enabled

NNL-00261: Request forwarding is currently enabled

Cause: Control program general message.

Action: None.

NNL-00260: Server-generated requests now do not require authoritative answers

NNL-00260: Server-generated requests now do not require authoritative answers

Cause: Control program general message.

Action: None.

NNL-00259: Server-generated requests now require authoritative answers

NNL-00259: Server-generated requests now require authoritative answers

Cause: Control program general message.

Action: None.

NNL-00258: Server-generated requests currently do not require authoritative answers

NNL-00258: Server-generated requests currently do not require authoritative answers

Cause: Control program general message.

Action: None.

NNL-00257: Server-generated requests currently require authoritative answers

NNL-00257: Server-generated requests currently require authoritative answers

Cause: Control program general message.

Action: None.

NNL-00256: Server-generated requests now do not request forwarding

NNL-00256: Server-generated requests now do not request forwarding

Cause: Control program general message.

Action: None.

NNL-00255: Server-generated requests now request forwarding

NNL-00255: Server-generated requests now request forwarding

Cause: Control program general message.

Action: None.

NNL-00254: Server-generated requests currently do not request forwarding

NNL-00254: Server-generated requests currently do not request forwarding

Cause: Control program general message.

Action: None.

NNL-00253: Server-generated requests currently request forwarding

NNL-00253: Server-generated requests currently request forwarding

Cause: Control program general message.

Action: None.

NNL-00252: DEFAULT-FORWARDER-ONLY mode is now disabled

NNL-00252: DEFAULT-FORWARDER-ONLY mode is now disabled

Cause: Control program general message.

Action: None.

NNL-00251: DEFAULT-FORWARDER-ONLY mode is now enabled

NNL-00251: DEFAULT-FORWARDER-ONLY mode is now enabled

Cause: Control program general message.

Action: None.

NNL-00250: DEFAULT-FORWARDERS-ONLY mode is currently disabled

NNL-00250: DEFAULT-FORWARDERS-ONLY mode is currently disabled

Cause: Control program general message.

Action: None.

NNL-00249: DEFAULT-FORWARDERS-ONLY mode is currently enabled

NNL-00249: DEFAULT-FORWARDERS-ONLY mode is currently enabled

Cause: Control program general message.

Action: None.

NNL-00248: General request processing is now disabled

NNL-00248: General request processing is now disabled

Cause: Control program general message.

Action: None.

NNL-00247: General request processing is now enabled

NNL-00247: General request processing is now enabled

Cause: Control program general message.

Action: None.

NNL-00246: General request processing is currently disabled

NNL-00246: General request processing is currently disabled

Cause: Control program general message.

Action: None.

NNL-00245: General request processing is currently enabled

NNL-00245: General request processing is currently enabled

Cause: Control program general message.

Action: None.

NNL-00244: Processing of modification requests is now disabled

NNL-00244: Processing of modification requests is now disabled

Cause: Control program general message.

Action: None.

NNL-00243: Processing of modification requests is now enabled

NNL-00243: Processing of modification requests is now enabled

Cause: Control program general message.

Action: None.

NNL-00242: Processing of modification requests is currently disabled

NNL-00242: Processing of modification requests is currently disabled

Cause: Control program general message.

Action: None.

NNL-00241: Processing of modification requests is currently enabled

NNL-00241: Processing of modification requests is currently enabled

Cause: Control program general message.

Action: None.

NNL-00240: Starting string ...

NNL-00240: Starting string ...

Cause: Control program general message.

Action: None.

NNL-00239: Resetting of statistic counters is now disabled

NNL-00239: Resetting of statistic counters is now disabled

Cause: Control program general message.

Action: None.

NNL-00238: Statistic counter reset interval is now string

NNL-00238: Statistic counter reset interval is now string

Cause: Control program general message.

Action: None.

NNL-00237: Resetting of statistic counters is currently disabled

NNL-00237: Resetting of statistic counters is currently disabled

Cause: Control program general message.

Action: None.

NNL-00236: Statistic counter reset interval is currently string

NNL-00236: Statistic counter reset interval is currently string

Cause: Control program general message.

Action: None.