´╗┐ Constants
IrDA Framework
ContentsIndexHome
PreviousUpNext
Constants

The following table lists constants in this documentation.

Name 
Description 
The base error code for the WCL system/common errors.  
A connection is active.  
The base error code for all connection errors.  
The connection has been closed.  
A connection is not active.  
The connection has been terminated by unknown reason.  
The connection has been terminated by user.  
Unable to create connection complete event object.  
Unable to create a communication thread initialization event.  
A server was not able to create or init client connection instance.  
Unable to create communication termination event object.  
A server was not able to find a specific client connection class.  
Unable to create communication thread.  
Unexpected error.  
One or more arguments passed into the method or function are invalid.  
Access denied.  
The component is already subscribed for the IrDA hardware change event.  
The requested attribute's class was not found.  
The requested attribute was not found.  
The base code for the IrDA errors.  
Connection already exsist.  
Connection has been rejected.  
Connection has been terminated by a user.  
Client disconnected by remote device.  
The Lazy Discovering is already running.  
The Lazy Discovering is not running.  
The IrDA subsystem or the associated service provider has failed.  
The specified handle type is not supported for IrDA communication.  
No more handles (descriptors) are available.  
A blocking call is in progress, or the service provider is still processing a callback function.  
An invalid argument was supplied.  
The descriptor is not a valid handle.  
The service provider returned an invalid or incomplete procedure table to the IrDA initialization.  
The service provider returned a version other than 2.2.  
A limit on the number of tasks supported by the IrDA implementation has been reached.  
No buffer space is available. The handle cannot be created.  
A successful IrDA subsystem initialization must occur before using this function.  
The underlying subsystem is not ready for communication.  
The component is not subscribed for the IrDA hardware change event.  
The IrDA is not supported. An infrared adapter and device driver is not installed on the local computer.  
The initialization parameter is not a valid pointer or One of the option value or the option length parameters is not a valid part of the user address space, or the option length parameter is too small.  
The specified protocol is not supported.  
An IrDA device or specific service was not found (address or service is invalid).  
The service provider failed to initialize. This error is returned if a layered service provider (LSP) or namespace provider was improperly installed or the provider fails to operate correctly.  
Timeout occured.  
Unable to create Lazy Discovering synchronization object.  
Unable to create Lazy Discovering thread.  
Unable to create socket event.  
Unable to create IrDA socket.  
Unable to get a read buffer size.  
Unable to get a write buffer size.  
Unable to select socket events.  
Unable to set a IrLMP communication mode.  
Unable to set a read buffer size.  
Unable to set a write buffer size.  
Unable to resolve a remote IrDA device address.  
Unexpected or unknown IrDA error.  
The option is unknown or unsupported by the indicated protocol family (IrDA).  
The version of IrDA subsystem support requested is not provided by this particular IrDA implementation.  
This connection mode can not be used for IrDA server.  
The specified protocol is the wrong type for this handle.  
The base error code for the message broadcaster.  
The message broadcaster can not initialize the hardware monitoring thread.  
The message broadcaster can not start the hardware monitoring thread.  
The message broadcaster was not created.  
A message receiver has already been subscribed.  
A message receiver has not been subscribed.  
There is the error with the references counter.  
The messaging subsystem is already running.  
The message broadcaster can not create the hardware monitoring object.  
The message broadcaster can not create a mutex synchronization object.  
The message broadcaster can not register for hardware changes notifications.  
The base error code for the message receiver.  
A message receiver has already been closed or not opened.  
A message receiver was not opened yet.  
A message receiver has already been opened.  
A thread synchronization object has not been created.  
A message receiver can not create a thread synchronization object.  
A message receiver can not register for threads synchronization.  
A message receiver can not synchronize threads and notify a "main" thread about new received message.  
The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs.  
The server was acting as a gateway or proxy and received an invalid response from the upstream server.  
The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).  
The base error code for OBEX errors.  
Indicates that the request could not be processed because of conflict in the request, such as an edit conflict between multiple simultaneous updates.  
An OBEX client is already connected to an OBEX server.  
The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent).  
The request has been fulfilled, resulting in the creation of a new resource.  
Indicates that the client requests that something be placed into a database but the database is full (cannot take more data).  
Returned when the client wishes to access a database, database table, or database record that has been locked.  
The error code indicates that the OBEX session has been disconnected by a remote side.  
The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.  
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.  
Indicates that the resource requested is no longer available and will not be available again.  
The server does not support the HTTP protocol version used in the request.[  
A generic error, given when an unexpected condition was encountered and no more specific message is suitable.  
The operation can not be executed at this time. This error appears if for example an application calls Terminate for Connect, Disconnect or SetPath operations.  
The request did not specify the length of its content, which is required by the requested resource.  
A request method is not supported for the requested resource.  
This and all future requests should be directed to the given URI.  
The response to the request can be found under another URI using the GET method.  
Indicates multiple options for the resource from which the client may choose.  
The server successfully processed the request and is not returning any content.  
The server is a transforming proxy that received a WCL_E_SUCCESS from its origin, but is returning a modified version of the origin's response.  
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.  
An OBEX client is not connected to an OBEX server.  
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.  
The server either does not recognize the request method, or it lacks the ability to fulfill the request.  
Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.  
An OBEX operation is in progress.  
The current operation has been terminated because a remote device is disconnected.  
The current operation has been terminated by a user.  
The server is delivering only part of the resource due to a range header sent by the client. The range header is used by OBEX clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.  
Reserved for future use.  
The server does not meet one of the preconditions that the requester put on the request.  
The client must first authenticate itself with the proxy.  
The server timed out waiting for the request.  
The request is larger than the server is willing or able to process.  
The server successfully processed the request, but is not returning any content. Unlike a WCL_E_OBEX_NO_CONTENT error, this error requires that the requester reset the object.  
The response to the request can be found under another URI using the GET method.  
The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. Also this error indicates that wrong Connect ID or Target used.  
Similar to WCL_E_OBEX_FORBIDDEN, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource.  
Unexpected or unknown OBEX result code.  
The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.  
The URI provided was too long for the server to process.  
The requested resource is available only through a proxy, the address for which is provided in the response.  
Out of system memory.  
Operation completed with success.  
Thread user initialization failed.  
Unable to register thread message.  
The thread is not running.  
The thread is already running.  
Unable to post signal to the thread.  
Unable to create thread window.  
Unable to create thread.  
Unable to create thread initialization event.  
An asynchronous operation cancelled.  
An asynchronous operation completed with error.  
Failed to read asynchronous operation status.  
The base WinRT subsystem error code.  
Unable to detach raw buffer.  
WinRT initialization failed.  
Unable to active instance of the required class.  
Unable to create interface of the required class.  
Unable to create synchronization mutex for WinRT control.  
Unable to create string.  
unable to load WinRT core DLL.  
unable to load WinRT string DLL.  
Bluetooth Framework messages category.  
The connections and connection providers messages category.  
IrDA Framework messages category.  
Kinect Framework messages category.  
Serial Framework messages category.  
System messages category.  
USB Framework messages category.  
User defined message categories should start from this Category ID.  
WiFi Framework messages category.  
Wii remote Framework messages category.  
The Hardware Change message's ID.  
Copyright (c) 2006-2018. All rights reserved.