148 RDE-00000 to RDE-08001
- RDE-00000: no error
-
Cause: Operation was successful.
- RDE-00001: unspecified error
-
Cause: An unknown error occurred. This is an internal error.
- RDE-00002: provider busy
-
Cause: The provider is processing a request.
- RDE-00003: no value found for service tag string.
-
Cause: A value was not found for the given service tag.
- RDE-00004: operation timeout
-
Cause: A FIND or REGISTER operation timed out.
- RDE-00005: invalid universe: "string"
-
Cause: An unknown universe was specified for the address.
- RDE-00006: invalid protocol: "string"
-
Cause: An invalid protocol was specified in an address.
- RDE-00009: data too large for buffer. Buffer length: number. Required: number.\n
-
Cause: This error is internal and normally is not seen by users.
- RDE-00010: not found
-
Cause: A value was not found in a list.
- RDE-00011: invalid type: number
-
Cause: The type given for a piece of data was invalid.
- RDE-00012: no list name specified.
-
Cause: A name was not given for a list.
- RDE-00013: name busy.
-
Cause: This is an internal error.
- RDE-00014: operation was interrupted.
-
Cause: An operation was interrupted.
- RDE-00015: load of provider library failed.
-
Cause: The load of a library which implements the interface for a provider failed.
- RDE-00016: no provider libraries found.
-
Cause: It was not possible to locate any provider libraries.
- RDE-00017: provider error.
-
Cause: A provider generated an error.
- RDE-00018: regular expression compilation failed. Pattern "string" Error: number.\n
-
Cause: The creation of a pattern for use in a comparison failed.
- RDE-00019: pattern match failed. String: "string" Pattern: "string" Error: number.\n
-
Cause: A comparison against a regular expression failed.
- RDE-00020: no host name or IP address
-
Cause: An address must contain either the name of the server or its IP address.
- RDE-00021: no providers found for universe "string".
-
Cause: A provider was not found for the specified universe.
- RDE-00022: property not found.
-
Cause: A provider property was not found.
- RDE-00023: provider not found. Universe "string".
-
Cause: A provider was not found for the specified universe.
- RDE-00024: address invalid
-
Cause: The address is not in the correct format.
- RDE-00025: service type not specified.
-
Cause: The service type is not specified in the address.
- RDE-00026: expected delimiter not found. Expected: "string" Found: "string"
-
Cause: The delimiter expected in the address was not found.
- RDE-00027: port number not found.
-
Cause: When a colon (":") follows the host name, it must be followed by a port number.
- RDE-00028: initialization failed.
-
Cause: Initialization of RD failed.
- RDE-00029: no server found.
-
Cause: No server for the specified provider could be found to perform the desired operation.
- RDE-00030: memory allocation failure.
-
Cause: An operation failed because it was not possible to allocate enough process memory.
- RDE-00031: invalid domain: number.
-
Cause: The application specified an invalid number for the domain.
- RDE-00032: length of service type "string" (number) is greater than than the maximum allowed: number
-
Cause: The user specified a service type which is longer than that permitted by the provider.
- RDE-00033: no universe specified.
-
Cause: The user did not specify a universe in the address.
- RDE-00034: address not registered: "string"
-
Cause: The application attempted to use an address which does not exist.
- RDE-00037: invalid service instance tag: number
-
Cause: The value for a service instance tag was incorrect.
- RDE-00038: invalid protocol type: "string" Valid protocols: string
-
Cause: The user specified a protocol which is not supported by the provider.
- RDE-00039: invalid host name: "string"
-
Cause: The name of the host specified was not in the correct format.
- RDE-00040: invalid search domain: "string"
-
Cause: The name of the domain searched by the service was not in the correct format.
- RDE-00041: no protocol or domain specified.
-
Cause: The service name was followed by a period separator, but no protocol or domain was found after it.
- RDE-00042: invalid port number: "string"
-
Cause: The port specified in the service address was not valid. A port number may only be a positive decimal number.
- RDE-00043: no search domain specified.
-
Cause: No search domain followed the period separator.
- RDE-00044: no protocol specified.
-
Cause: No protocol was specified for the service.
- RDE-00045: port number required to register with a generic address.
-
Cause: Because of the requirements of some providers, the port number must be specified when registering using a generic address.
- RDE-00046: invalid attribute
-
Cause: An attribute was specified using an incorrect format.
- RDE-00047: no name specified for attribute.
-
Cause: A value was given for an attribute but no name was specified.
- RDE-00048: no attribute specified.
-
Cause: An attribute was not found in the address where it was expected.
- RDE-00049: expected separator not found. Expected: "string" Found: "string"
-
Cause: The separator expected to be present between the mandatory and optional sections of the address was not found.
- RDE-00050: provider initialization for universe "string" failed.
-
Cause: The operation failed because providers could not be initialized for the specified universe.
- RDE-00051: provider "string" error.
-
Cause: The specified provider failed to perform an operation.
- RDE-00052: invalid numeric value specified: "string".
-
Cause: The value specified as a number was not valid.
- RDE-00053: invalid or null service instance.
-
Cause: The service instance used for an operation is either invalid or null.
- RDE-00054: invalid operation: number.\n
-
Cause: The operation specified was not valid.
- RDE-00055: no providers available.
-
Cause: No providers were available for an operation. This may be caused by the failure of a process or service needed by the provider (e.g. the mDNS service).
- RDE-00056: registration of service instance "string" failed.
-
Cause: The registration of the specified service instance failed.
- RDE-00057: unregistration of service instance "string" failed.
-
Cause: The deletion of the registration of the specified service instance failed.
- RDE-00058: confirmation of service instance "string" failed.
-
Cause: The confirmation of the specified service instance failed.
- RDE-00059: location of service types "string" failed.
-
Cause: It was not possible to retrieve types of services supported by Resource Discovery.
- RDE-00060: service instance "string" was not found.
-
Cause: The location of the specified service.
- RDE-00061: retrieval of details about service instance "string" failed.
-
Cause: It was not possible to get details about the specified service instance.
- RDE-00062: termination failed.
-
Cause: The call to terminate the use of Resource Discovery failed.
- RDE-00063: operation failed.
-
Cause: A FIND or REGISTER operation failed.
- RDE-00064: retrieval of a provider for universe "string" failed.
-
Cause: It was not possible to retrieve a provider descriptor for the specified universe.
- RDE-00065: creation of service instance failed.
-
Cause: An error occurred while trying to assemble a service instance using components.
- RDE-00066: parsing of service instance "string" failed.
-
Cause: An error occurred while trying to parse the specified address.
- RDE-00067: location of domain failed.
-
Cause: An error occurred while trying to locate domains of the specified type.
- RDE-00068: length of universe component "string" (number) is longer than the maximum: number.
-
Cause: The string specified for the universe-specific portion of the service instance is longer than the maximum allowed by the provider.
- RDE-00069: property "string" is read-only.
-
Cause: An error occurred while trying to set a property value. Property had read-only access and could not be altered.
- RDE-01999: internal error
-
Cause: RD failed due to some unforeseen reason.
- RDE-02000: invalid service type: "string"
-
Cause: The user specified a service type which does not conform to the standard specifed by RFC's 1034 and RFC 1123. The service type must be one or more characters and must start and end with a letter or digit. The interior characters may be letters, digits, or hyphens.
- RDE-02001: failed to connect to the mDNS responder.
-
Cause: The provider was unable to make a connection with the multicast / Domain Name Server (mDNS) responder.
- RDE-04000: client waiting
-
Cause: The client uses this error to signal to the server that it is waiting for query results.
- RDE-04001: no error
-
Cause: Operation was successful.
- RDE-04002: unknown error has occurred
-
Cause: An unknown error has occurred.
- RDE-04003: no such name
-
Cause: A record could not be found with the given name.
- RDE-04004: memory allocation failed
-
Cause: An operation failed because it was not possible to allocate enough process memory.
- RDE-04005: invalid parameter
-
Cause: A record contained an illegal or nonexisting value.
- RDE-04006: invalid reference
-
Cause: An unknown DNS record was found.
- RDE-04007: invalid state
-
Cause: This is an internal error.
- RDE-04008: invalid flags
-
Cause: This is an internal error.
- RDE-04009: unsupported operation
-
Cause: The provider interface attempted to perform an operation which is not supported by the provider.
- RDE-04010: not initialized
-
Cause: This is an internal error.
- RDE-04011: no cache allocated
-
Cause: A Domain Name Server (DNS) query failed because no cache was allocated.
- RDE-04012: service already registered
-
Cause: The user attempted to register a service that was already registered.
- RDE-04013: service name conflict
-
Cause: The user attempted to register a service whose name already exists.
- RDE-04014: invalid record entry
-
Cause: The provider interface attempted to perform an operation whose record contained invalid or nonexistent data.
- RDE-04015: client software incompatible with server
-
Cause: The version of the client software used by the provider interface is not compatible with the version of the server software.
- RDE-04016: invalid interface
-
Cause: The provider interface attempted to use an unknown interface.
- RDE-04017: cache size must be increased
-
Cause: The size of the cache maintained by the provider interface was insufficient and should be increased.
- RDE-04018: configuration changed
-
Cause: The server configuration changed during an operation.
- RDE-04019: client should free resources
-
Cause: This error is used as an internal status indicator and should not be visible outside of the provider.
- RDE-06000: no more data
-
Cause: This error is used internally to signal that there is no more data to be passed by the SLP provider.
- RDE-06001: no error
-
Cause: Operation was successful.
- RDE-06002: language not supported
-
Cause: No service could be found that supports the language required.
- RDE-06003: parse error
-
Cause: The SLP message rejected by a remote SLP agent.
- RDE-06004: invalid registration
-
Cause: The SLP provider attempted to register a URL which is malformed.
- RDE-06005: scope not supported
-
Cause: This is an internal error.
- RDE-06006: authenticator not provided
-
Cause: The SLP provider failed to authenticate itself.
- RDE-06007: authentication failed
-
Cause: The SLP provider failed to authenticate itself.
- RDE-06008: invalid update
-
Cause: An update for a nonexisting registration was issued, or the update includes a service type or scope different than that in the initial registration.
- RDE-06009: refresh rejected
-
Cause: Attempts were made to refresh a registration more frequently than the minimum refresh interval.
- RDE-06010: feature unimplemented
-
Cause: An unimplemented feature was used.
- RDE-06011: buffer overflow
-
Cause: An outgoing request overflowed the maximum network MTU size.
- RDE-06012: network timed out
-
Cause: An reply to an SLP request did not arrive in the configured timeout interval.
- RDE-06013: network initialization failure
-
Cause: The network failed to initialize properly.
- RDE-06014: memory allocation failed
-
Cause: The SLP provider was unable to allocate enough process memory.
- RDE-06015: invalid parameter
-
Cause: The provider attempted to pass an invalid parameter.
- RDE-06016: network error
-
Cause: The network failed to initialize properly.
- RDE-06017: internal system error
-
Cause: The SLP subsystem failed for unknown reasons.
- RDE-06018: handle in use
-
Cause: The SLP provider attempted to recursively use a handle.
- RDE-06019: generic error
-
Cause: The provider failed for unknown reasons.
- RDE-06020: unicast query must be sent.
-
Cause: The provider must send a unicast query.
- RDE-08000: invalid service type: "string".
-
Cause: This is an internal error.
- RDE-08001: failed to connect to the GNS server.
-
Cause: A connection with the Grid Naming Service (GNS) server failed.