## SLPError Codes

The following is an explanation of the SLP error codes are returned by SLP functions:

SLP_LAST_CALL | 1 | 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 use this to signal the main body of the client code that no more data will be forthcoming on the operation, so that the main body of the client code can break out of data collection loops. On the last call of a callback during both a synchronous and synchronous call, the error code parameter has value SLP_LAST_CALL, 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 SLP_LAST_CALL.
SLP_OK | 0 | indicates that the no error occurred during the operation.
SLP_LANGUAGE_NOT_SUPPORTED | -1 | No DA or SA has service advertisement or attribute information in the language requested, but at least one DA or SA indicated, via the LANGUAGE_NOT_SUPPORTED error code, that it might have information for that service in another language
SLP_PARSE_ERROR | -2 | 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.
SLP_INVALID_REGISTRATION | -3 | 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 deregistered service url does not conform to valid service url syntax. The service url being deregistered is not registered this means that either it was never registered via a call to SLPReg() or that the registration lifetime has expired. SLP_INVALID_REGISTRATION is commonly returned when an attempt is made to deregister a service that was registered by a call to SLPReg() on a different host.
SLP_SCOPE_NOT_SUPPORTED | -4 | The API returns this error if the SA has been configured with net.slp.useScopes value-list of scopes and the SA request did not specify one or more of these allowable scopes, and no others. It may be returned by a DA or SA if the scope included in a request is not supported by the DA or SA.
SLP_AUTHENTICATION_ABSENT | -6 | 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.
SLP_AUTHENTICATION_FAILED | -7 | If the SLP framework supports authentication, this error arises when a authentication on an SLP message failed
SLP_INVALID_UPDATE | -13 | 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, etc.
SLP_REFRESH_REJECTED | -15 | 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 minimum refresh interval to use.
SLP_NOT_IMPLEMENTED | -17 | If an unimplemented feature is used, this error is returned.
SLP_BUFFER_OVERFLOW | -18 | An outgoing request overflowed the maximum network MTU size. The request should be reduced in size or broken into pieces and tried again.
SLP_NETWORK_TIMED_OUT | -19 | When no reply can be obtained in the time specified by the configured timeout interval for a unicast request, this error is returned.
SLP_NETWORK_INIT_FAILED | -20 | If the network cannot initialize properly, this error is returned. Will also be returned if an SA or DA agent (slpd) can not be contacted. See SLPReg() and SLPDeReg() for more information.
SLP_MEMORY_ALLOC_FAILED | -21 | Out of memory error
SLP_PARAMETER_BAD | -22 | If a parameter passed into a function is bad, this error is returned.
SLP_NETWORK_ERROR | -23 | The failure of networking during normal operations causes this error to be returned.
SLP_INTERNAL_SYSTEM_ERROR | -24 | 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.
SLP_HANDLE_IN_USE | -25 | In the C API, callback functions are not permitted to recursively call into the API on the same SLPHandle, either directly or indirectly. If an attempt is made to do so, this error is returned from the called API function.
SLP_TYPE_ERROR | -26 | If the API supports type checking of registrations against service type templates, this error can arise if the attributes in a registration do not match the service type template for the service.