SLPError(3N)															      SLPError(3N)

NAME

       SLPError - Service Location Protocol (SLP) error codes

SYNOPSIS

DESCRIPTION

       SLP APIs return error code when the call does not succeed.  These SLP error codes are defined in

       The various SLP Error codes returned by the SLP APIs, their values and their explanations are as follows:

		     Passed to callback functions when the API library has no more
	      data  for them and therefore no further calls will be made to the callback on the currently outstanding operation.  The callback can
	      then signal to the main body of the client code that no more data will be forthcoming on the operation.  The main body of the client
	      code  will  then	break  out  of	data collection loops.	On the last call of a callback during both an asynchronous and synchronous
	      calls, the error code parameter has value and the other parameters are all NULL.	If no results are returned by  an  API	operation,
	      then only one call is made, with the error parameter set to

		     Indicates that no error occurred during the operation.

		     There is no DA or SA service advertisement or attribute information
	      in  the  language  requested.   However, at least one DA or SA indicates that there might be information for that service in another
	      language by returning the error code.

		     The SLP message was rejected by a remote SLP agent.
	      The API returns this error only when no information was retrieved, and at least one SA or DA indicated a protocol error.	 The  data
	      supplied through the API may be malformed or a may have been damaged in transit.

		     The API may return this error if an attempt to register a
	      service was rejected by all DAs because of a malformed URL or attributes.  SLP does not return the error if at least one DA accepted
	      the registration.

		     The API returns this error if the SLP request packet did not
	      specify one or more of the scopes that neither slpd running on local machine has been configured with through the  net.slp.useScopes
	      property in the configuration file nor is there slpd running on any other machines which support them.

		     If the SLP framework supports authentication,
	      this error arises when the UA or SA failed to send an authenticator for requests or registrations in a protected scope.

		     If the SLP framework supports authentication,
	      this error arises when a authentication on an SLP message failed.

		     An update for a non-existing registration was
	      issued or the update includes a service type or scope different than that in the initial registration or successive incremental reg-
	      istrations.

		     The SA attempted to refresh a
	      registration more frequently than the minimum refresh interval.  The SA should call the appropriate API function to obtain the mini-
	      mum refresh interval to use.

		     If an unimplemented feature is used,
	      this error is returned.

		     An outgoing request overflowed the
	      maximum network MTU size.  The request should be reduced in size or broken into pieces and tried again.

		     This error is returned when no reply can be
	      obtained in the time specified by the configured timeout interval for a unicast request.

		     This error indicates that the network cannot initialize
	      properly.  This error will also be returned if an SA or DA agent (slpd) can not be contacted.  See and in libslp(3N) for more infor-
	      mation.

		     Out of memory error.

		     This error is returned when the parameter passed to the function
	      is bad.

		     A networking failure during normal operations causes this
	      error to be returned.

		     A basic failure of the API causes	this error to be returned.
	      This occurs when a system call or library fails.	The operation could not recover.

		     In the C API, callback functions are not permitted to
	      recursively call into the API on the same either directly or indirectly.	If an attempt is made to do so,  this  error  is  returned
	      from the called API function.

		     If the API supports a type checking of registrations against
	      service  type  templates,  this error occurs if the attributes in a registration do not match the service type template for the ser-
	      vice.

SEE ALSO

       libslp(3N).

																      SLPError(3N)