BUG: WSALookupServiceNext Returns Incomplete Data (250461)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
This article was previously published under Q250461 SYMPTOMS
When you are doing a namespace query for the SVCID_HOSTNAME globally unique identifier (GUID) and use the WSALookupServiceNext Winsock API to dynamically determine the buffer size required for the WSAQUERYSET, the subsequent call to WSALookupServiceNext with the allocated buffer returns incomplete data and should not be relied upon.
RESOLUTION
To work around this problem, you can allocate an appropriately sized buffer before you make the first call to WSALookupServiceNext.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 11/20/2003 |
---|
Keywords: | kbAPI kbBug kbnetwork kbWinsock KB250461 |
---|
|