Database Search
TechHome
 |
- !!NEWSFLASH!!
- !Limitations of the WinInet FTP Functions
- !List of Win32 Error Codes
- 12003 ERROR_INTERNET_EXTENDED_ERROR
- 12007 Error
- 12163 error trying to trying to open an FTP session
- Active vs Passive FTP Connections
- Allowing User to Accept Cookies
- Ascii vs Binary FTP Transfers
- Automating Web forms with Cookies
- Can WinInet Handle Framed Pages
- Change Phone Number of Connectiod-Ras entry
- Check for IE4
- Check if a File has been Modified on Web Server
- Check if FTP File Exists
- Check if iUrlOpen returns what your expecting
- Cookies Wont Go Through
- Delete Temporary Internet Files Cache
- Dialog Progress Bar not Working
- Download a Message directly to a Binary buffer
- Embed User Id and Password in URL
- Error 12045 Invalid Certificate
- Error 307 File Access Failed
- Error 321 iFtpFindNext failed
- Error code 632 on WinInet dial-up
- ERROR with iOptionSet
- FTP Directory Exist
- FTP File Exist
- Ftp Functions and OpenVms
- Ftp Issue with Large File Transfers
- FTP Keep Alive
- FTP Proxy Server and Passive Transfer
- FTP SSL
- FtpListFileNames UDF
- Get Wininet Error Description String
- Get Real Internet Address
- Get WinInet Error Description String
- Getting ERROR on iHttpOpen with HTTPS
- Handle Http Redirect
- How to Specifiy HTTP User Agent
- How to use iGetConState
- How to Use iHttpOpen - Do a Post - and Grab HTML
- HTTP and WinInet - An Opus
- HTTPDownload 1.4
- iBegin and Firewalls
- IE4 Dlls needed for Wininet Extender on 95
- iFtpCmd and MDTM command
- iFtpCmd and Quote Site
- iFtpCmd APPE Causes iWriteData to Crash using IE 7
- iFtpCmd APPE Example
- iFtpCmd Issues
- iFtpCmd RETR Crash on Windows 7 32-bit WinInet Only
- iFtpDirMake Error 318
- iFTPFileSize 300 Error FileOpen Failed
- iFtpFindInit Memory Leak
- iFtpFindInit Returns Zero
- iFtpFindInit Wildcards
- iFtpFindNext Problem with Date
- iFtpGet Newer Files Only
- iFtpGet to get INI file
- iFtpGet Wininet Error 12031
- iFtpPut Error 12002 ERROR_INTERNET_TIMEOUT
- iFtpPut Error 12003
- iFtpPut to Unix Server
- iGetConState Return Values
- iGetConState Returns False
- iGetConState(0) Returns 1 for No Connection
- iGetLastError Always Returns 2 with IE5
- iHostConnect and Return Codes
- iHostConnect Error 65535
- iHttpInit and 401 Error
- iHttpOpen Error 406
- iHTTPOpen Error Message 12044 ERROR_INTERNET_CLIENT_AUTH_CERT_NEEDED
- iHTTPOpen Not Returning 404
- Installation of a Certificate
- InternetCookieSetEx and InternetCookieGetEx
- iOptionSet Error
- Latitude and Longitude of An Address
- Logfile of FTP Session
- Make a WHOIS Request
- Multiple FTP Sessions
- Non Standard Port
- Post HTML Problem
- Print a Web Page
- Progress bar during HTTP download
- Removing Empty Directories with FTP
- Require Certificate for HTTPS Downloads
- Return Info on Web Server
- Sample code - Weather Watch
- Secure FTP Issues
- Select Links That Contain Java Script Code
- Syncronize FTP
- UrlEncode of Hebrew characters
- Website Forms with Viewstate and Eventvalidation
- Wininet and Cookies
- WinInet and JavaScript
- WinInet and OpenVMS Problem
- WinInet Errors
- WinInet Not Supported for Use in Services
- Yahoo Signin Form
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
iFTPFileSize 300 Error FileOpen Failed
Keywords: iFtpFileSize 300 Error FileOpen failed IE11 FireWall WInInet FtpOpenFile
Question:
I have written a Winbatch application that logs into an FTP Server and downloads any new Files found on this Server. This system has been working for years, but last week this system stopped working. It still successfully logs onto the FTP server and obtains the list of Files available. It then uses iFTPFileSize to obtain the Size of the file it wants to download but instead of the size being returned I get a 300 Error: FileOpen failed.I have investigated and found that I get this error if the Windows 7 Firewall is active. With the Firewall switched off the System works perfectly. We have not changed any Firewall Settings but I guess Microsoft may have patched something in a Windows Update?
I have rebuilt the system using the latest version of WinBatch and Extenders and get the same error. I have also checked the application on other computers and they work so the problem does relate to this Computer and the Firewall.
My FTP system has been tested on 10 different machines (nine Windows 7 and one Windows XP) and 8 of the 10 work fine with the Firewall enabled. The two that fail always fail at iFTPFileSize command with the "FileOpen failed" Error. And both work fine with the Firewall Switched off.
Any ideas what Windows 7 Firewall rule or Ports I should open to allow iFTPFileSize to work with the Firewall active?
Details:
WinBatch 2014A Wininet Extender Windows 7 IE 11 @FTPPASSIVE Other FTP tools like Firefox FTP client and CuteFTP also have problems downloading Files. Disabling the Firewall works 100% of the time. WWWBATCH.INI reports: [WWINT44I] LastError=12002 (iFtpFileSize(FtpOpenFile))
Answer:
The iFtpFindSize function is attempting to open the file in READ mode, using the Wininet Api function FtpOpenFile: http://msdn.microsoft.com/en-us/library/windows/desktop/aa384166%28v=vs.85%29.aspxThe error code 12002 from the call to FtpOpenFile iwritten to the wwwbatch.ini file indicates: ERROR_INTERNET_TIMEOUT. You might try adding code to your script to increase the timeout using iOptionSet.
control_send_timeout ( FTP Control channel send timeout ) by default is 300000. control_receive_timeout ( FTP Control channel receive timeout ) by default is 300000.Notes regarding the firewall: In Passive mode, the FTP server opens a port on its end and tells the FTP client the Port it needs to connect to. On the client end, it creates a new socket, binds it to a local Port and connects to the server's specified Port. Without seeing a trace log from a network packet sniffer, I would guess that the firewall on the client end is possibly blocking the outbound connection. Have you tried and active connection (@FTP) instead?
You might consider adding error handling to capture the error on the faulty machines. For more on error handling check out: http://techsupt.winbatch.com/webcgi/webbatch.exe?techsupt/nftechsupt.web+Tutorials+Trap~Errors.txt
You might also be dealing with this IE11/WinInet bug:
- https://connect.microsoft.com/IE/feedback/details/808279/ftpopenfile-and-internetwritefile-broken-changed-in-ie11
- http://support.microsoft.com/kb/2754804
- http://stackoverflow.com/questions/6990663/java-7-prevents-ftp-transfers-on-windows-vista-and-7-if-firewall-is-on-any-idea
User Reply:
I am still investigating this but I have found if I use iFTPFileExist before the iFTPFileSize command then this appears to report the File does not exist and does not error unlike iFTPFileSize. It does not solve the problem but at least now I know when it will not work.Article ID: W17619
Filename: iFTPFileSize 300 Error FileOpen Failed.txt
File Created: 2014:07:18:09:49:40
Last Updated: 2014:07:18:09:49:40