Second Call to FtpOpenFile() Without Write Permission HangsID: Q236178
|
When a program makes a second FtpOpenFile() function call to a file on a File Transfer Protocol (FTP) server, the program may stop responding (hang) if you do not have write permissions to the site.
In this case, a stop command is sent to the server because the file was not completely read. A reply is sent to the client from the server that the stop was successful. However, Wininet.dll does not read the response before the socket is closed. Therefore, when the socket is reopened for writing, the "stop successful" response is still in the buffer. This situation causes the send commands and responses to get out of synchronization. Being out of synchronization causes the client to hang.
A supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next Internet Explorer service pack
that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support Services
phone numbers and information on support costs, please go to the following
address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
Date | Time | Size | File name | Platform |
---|---|---|---|---|
07/22/1999 | 12:23 p.m. | 5.00.2719.2200 | Wininet.dll | (x86) |
Q154871 Determining If You Are Eligible for No-Charge Technical Support
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.
Additional query words:
Keywords : msiew95 msient msiew98
Version : WINDOWS:5
Platform : WINDOWS
Issue type : kbprb
Last Reviewed: August 3, 1999