10-17-2013 02:04 PM
I have been using an application on my XP PC built with Labwindows 8.1 for some time now. The application FTP's files to another stand alone Single board computer. Never a problem.
I recently upgraded to Labwindows 2010. I build the application and launch it in either debug or release mode. Now I am having problems with the FTP.
When I issue the command:
InetFTPChangeDir (ftp_handle, "cd \\temp");
It just sits there for about 30 seconds and then returns the error:
Return Value = -4
System Socket Error
If I go back to using the app built with Labwindows 8.1 it works fine.
Any help would be greatly appreciated.
Thanks!
John W.
.
10-18-2013 07:02 PM
Hi,
based on the information I have seen, there are two of the most common reasons for a System Socket Error.
First, a port conflict or similar issue:
http://digital.ni.com/public.nsf/allkb/862567530005F09C862565ED0047E029?OpenDocument
or accidental use of a termination character.
10-28-2013 02:16 PM
Thanks for the reply. I don't think that is the cause of my problem.
In the original post I stated that my application works fine if built on Labwindows 8.1
When I build it on Labwindows 2010, I get the error when trying to change the directory on the SBC that my program is controlling
Thanks
John W.
10-29-2013 09:52 AM
When running 8.1 are you on the same computer, if so can you send the exact same string "cd \\temp" successfully? It appears the cd may be redundant as the command is expecting a const char * of the path.
A way to troubleshoot this could be through the use of the included FTP example which uses the same InetFTPChangeDir command to ensure the connection and function are working properly to narrow down where the issue lies.
The example can be found under:
<examples>\internet\ftpclnt\ftpclnt.cws