The information in this article applies to:
SYMPTOMS
Winsdmp.exe performance is not acceptable when trying to dump the WINS
database of a WINS server with large version ID. An example of a large
version ID would look like the following:
Hex: 0x1d88100000000 Converting the value to decimal would be: 5.195235390915e+14 Winsdmp.exe would start counting in intervals of hexadecimal 0x7cf or 1999 decimal. Even when dumping at these intervals, it would take years to reach the high version ID listed above. CAUSEWinsdmp.exe was designed to start from record 0 and serially count up until the highest version ID was reached. RESOLUTION
A supported fix that corrects this problem is now available from Microsoft,
but has not been fully regression-tested and should be applied only to
systems experiencing this specific problem.
http://support.microsoft.com/support/supportnet/default.asp The English version of this fix should have the following file attributes or later:
NOTE: If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support. For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base: ARTICLE-ID: Q154871 TITLE : Determining If Your Product Is Eligible for No-Charge Technical Support STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. MORE INFORMATIONThis fix now seeks to cells that actually have records instead of serially starting from record 0.
Keywords : kbbug4.00 kbfix4.00 |
Last Reviewed: November 9, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |