Portable Client File Transfer Issue

[dcipher]

Hi

We created portable clients for our customers as an alternative to the HTML5 interface. One of our clients wants to save a file to her a net work drive on her local computer. She picks the drive and gives the file a name. Then our application copies the data to the file. The problem is that it never terminates. Our application says the data is copied but the application is busy and non-responsive. We have been doing this with other customers and with MS Terminal Services for years without a problem so we are wondering what might be wrong. There are no error messages.

We are using TSPlus 7.7 on Windows 2012 Server and the client is running Windows 8. Is the portable client dependent on the version of TSPlus because the client was built using TSPlus 7.6?

Simon

[John]

Hello,

If you are using the TSplus file transfer utility then I recommend you to update your connection client. If you are using the standard drive redirection then it is not necessary.
more information about that feature can be found here : terminalserviceplus.com/docs/file-transfer

[dcipher]

We are not using the File Transfer program. We simply use Windows File dialog to choose the file location and then copy our application copies the data to the file at the specified location.

Simon

[admin]

You should try the file transfer utility which is more stable, any connection issue can lead to a file transfer issue if you just drag and drop items from a remote session to your client computer. Antivirus can also have a negative behavior with this, preventing a file from being copied properly as it is considered a threat.

If you are experiencing frequent connection issue I recommend you to set up this group policy : tsplus.net/support/kb/faq.php?id=18

[dcipher]

Hi

I have tried the File Transfer but the issue is that it is very slow to load the directory from the client computer and then the user must know which folder to look in. It is much simpler to have the application copy the file directly into a folder on the client machine. The other problem is that it cannot be automated. We have a lot of tasks that run on the server and automatically copy files to the client computer so we really need the copy file function to work. It has worked for years under MS Remote Desktop so I hope you can make it work properly from TS Plus.

We are using the standard Remote Desktop drive redirection.

The Group Policy suggestion made no difference.

Simon

[admin]

Hello,

If you prefer using the hard drive redirection, you could optimize your file transfer by creating a virtual drive letter linked to a folder.

Follow this procedure : tsplus.net/support/kb/faq.php?id=25
and in the generated script type in subst Y: \\tsclient\c\name of the folder

doing so your user will be able to have access to his C: hard drive.
If you would prefer to redirect their "My documents" folder or any other specific folder then type in :

subst Y: \\tsclient\c\Users\%USERNAME%\Documents

[dcipher]

Hi

My application already does the following:

copy to file \\tsclient\k\031315.csv

The copy command eventually times out after about 20minutes with an error message as shown in the attached image. So I am not sure that creating a mapped drive will help the situation but I will give it a try.

Simon

[dcipher]

Hi

I tried mapping the folder to drive Y: but the result is the same.

Simon

[dcipher]

Could the file extension have anything to do with the file copy problem? The reason I ask is that one client can successfully copy their export files to their local drive without issues but they use a file that has "cus" file extension. Whereas the customers that are having problems use files with "csv" and "xls" file extensions.

Simon

[dcipher]

Hi

We have discovered that not all the clients experience this problem. The same application is used by all the customers but for some the the export to their local drive works perfectly and for others we get the messaged shown earlier. We have not yet narrowed down the cause because this feature use to work for all the customers when we were using MS Terminal Services.

Simon