Two problems encountered during CuteFTP usage

1. Smart rule settings:

I want to synchronize the provincial company data to a local folder.

 

* The target file refers to the local file to be synchronized. I set it to skip if the date is the same and the size does not matter, but sometimes an error occurs, it will create a file with a size of 0, so this setting will not work. Other people are set to skip as long as the volume is the same regardless of the date. I cannot analyze it because some files are not generated based on the actual data length. For example, if we use a database, it will increase by 50 MB at a time, that is, it will increase progressively. This is what it means. Of course, the TXT file does not have this problem.

 

Therefore, after debugging several times, you can skip this step only when the date is the same and the size is the same.

 

2.ftpte.exe abnormal process exit

The customer reported that CuteFTP cannot update the information. With a remote desktop, you can see that ftpte.exe is no longer running.

Then we found that he started with login and ended with logout. Both the customer administrator and I are using admini to log in. This will undoubtedly lead to an abnormal termination of ftpte. In addition, they are all tested several times. Although its global settings can be set to: do not end at logout. However, after logging out several times, the process is no longer running.

 

This is what I do later. Change the administrator password. No Logon is allowed. Then a Common Logon user and a new admin account (Administrator group) are added, and then the admin user is logged in remotely. open the account in the taskbar and connect to the adminsitrator user window.

Start the client and automatically start ftpte.

 

At the same time, I log on to the adminsitrator interface several times. When the mouse moves in the lower right corner, the ftpte icon disappears. It seems like the background program has no reason to die. Therefore, for insurance purposes, CuteFTP is executed every two hours in the scheduled task. In this way, the client can be started even if the IDC maintenance personnel restart or other causes of exceptions.