DOCERR: GetQueuedCompletionStatus() Error Code

Article ID: Q139460
Creation Date: 09-NOV-1995
Revision Date: 16-NOV-1995

The information in this article applies to:

Microsoft Win32 Software Development Kit (SDK) versions 3.5, 3.51

SYMPTOMS

Windows NT provide a powerful mechanism for performing file I/O asynchronously by using I/O Completion Ports. For more details, please see the Win32 SDK Help file and the Pop3srv sample.

An application may post aynchronous ReadFile and WriteFile messages and then carry on further processing. After some time it may call GetQueuedCompletionStatus() to find out the status of the ReadFile and WriteFile operations. It is possible that the pending file operation may still not have completed. In such a case, if there is a timeout associated with GetQueuedCompletionStatus(), the function will return FALSE and GetLastError() will return 258.

Typing "net helpmsg 258" returns this message:

   258 is not a valid Windows NT network message number.

RESOLUTION

258 (0x102) is a WAIT_TIMEOUT. For more information, please refer to the Win32 SDK Winbase.h and Winnt.h files. Please note that this API is not available under Windows 95.

STATUS

This behavior is not documented as well as it should be.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.