PRB: ERROR_INVALID_PARAMETER from WriteFile() or ReadFile()

Last reviewed: November 26, 1997
Article ID: Q110148
The information in this article applies to:
  • Microsoft Win32 Application Programming Interface (API) included with: - Microsoft Windows NT versions 3.1, 3.5, 3.51, 4.0 - Microsoft Windows 95 version 4.0

SYMPTOMS

The WriteFile() or ReadFile() function call may fail with the error ERROR_INVALID_PARAMETER if you are operating on a named pipe and using overlapped I/O.

CAUSE

A possible cause for the failure is that the Offset and OffsetHigh members of the OVERLAPPED structure are not set to zero.

RESOLUTION

Set the Offset and OffsetHigh members of your OVERLAPPED structure to zero.

STATUS

This behavior is by design. The online help for both WriteFile() and ReadFile() state that the Offset and OffsetHigh members of the OVERLAPPED structure must be set to zero or the functions will fail.

MORE INFORMATION

In many cases the function calls may succeed if you do not explicitly set OVERLAPPED.Offset and OVERLAPPED.OffsetHigh to zero. However, this is usually either because the OVERLAPPED structure is static or global and therefore is initialized to zero, or the OVERLAPPED structure is automatic (local) and the contents of that location on the stack are already zero. You should explicitly set the OVERLAPPED.Offset and OVERLAPPED.OffsetHigh structure members to zero.

Keywords          : BseFileio
Version           : winnt:3.13,3.5,3.51,4.0;
Platform          : Win95 winnt
Issue type        : kbprb


================================================================================


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.

Last reviewed: November 26, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.