The information in this article applies to:
SYMPTOMSA 16-bit Windows-based application, which uses many DDE connections, fails after a while when running on Windows NT. The application works correctly on Windows 3.1. CAUSEAfter more than 26 concurrent DDE connections have been created, an error 0x400f (a system API failed inside of the DDEML) is returned when closing the twenty-seventh connection. This problem is due to a timer, which is associated with a window, not being freed when the relevant window is destroyed. RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows NT 4.0 or
the individual software update. For information on obtaining the
latest service pack, please go to:
-or- http://www.microsoft.com/support/supportnet/overview/overview.asp NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee. For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base: Q154871 Determining If You Are Eligible for No-Charge Technical Support STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5. Additional query words: Exchange Dynamic Data 4.00 WOW
Keywords : kbbug4.00 kbfix4.00 nt4sp5fix |
Last Reviewed: November 9, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |