FreeFileSync Forum

It says, Fixed error during process initialization while connecting with quick launch, so sounds like it should be there. therube, 13 Sep 2023, 19:22

Thank you. I haven't seen this point in the release notes.

I can confirm that this error doesn't come up with version 13.

What would be a good open source alternative to open SSH on Windows?
To make windows into an SFTP server.


Good question. I'm also interested in free solutions. But I didn't find many options. If you want to use it in commercial environments the majority of the products I found are paid software ...

OK, thank you for the quick answers. I will try if everything is working fine after updating to FreeFileSync 13.

With OpenSSH there's a character limit because of using the Win32 API of Windows. Other SFTP server software doesn't use the Win32 API and so there's no issue with long paths.

I still don't know, what's meant by

Quick Launch\User Pinned" is required to adapt the app user model id of the FFS launcher link (if existing).

And is the change in 12.6 BETA also implemented in 13?

Hi all,

with FreeFileSync 13 there's big change regarding the synchronization. So I'm asking what happens with the old jobs created with former versions? Will they work as they worked in the past? Or do we have to adapt the jobs because of the new synchronization features?

Thank you.

It looks like OpenSSH is the source of the issues. With another SFTP server software on the Windows server there are no issues with long paths. I will see the next days if there are more or other issues regarding the switch to SFTP.

Hi all,

in the past I synced files between two Windows servers with FreeFileSync via SMB shares. This worked very good.

In the near future, the target server will be a Linux based NAS. So the sync with FreeFileSync will then be switched to SFTP.

Now, as preparation of this change and for testing ...

Oh, you switched from English to Italian? Then the log entries are probably Italian, too. So you have to change it in the script. There you find entries for English and German. Here you have to set the Italian wordings so that the script can find the log lines with errors or warnings.

Regarding Windows Server 2022: I don't have an idea. Check the firewall settings regarding open ports for outgoing traffic for SMTP and SMTPS. Set the logging option for blocked connections in a file for the firewall. So you can see if there's a blocked connection by the firewall. Or there are ...

Thank you for this Beta version. The error message isn't shown in the logs any more.

"Quick Launch\User Pinned" is required to adapt the app user model id of the FFS launcher link (if existing).

What does this mean and what happens when FFS can't adapt the app user model ID of the FFS launcher ...

Thank you. I've now updated FreeFileSync to 12.6 Beta and will try if this works. I will give you feedback.

"Quick Launch\User Pinned" is required to adapt the app user model id of the FFS launcher link (if existing).

What does this mean?

And what's more confusing: On a Windows 10 system there are 3 different synchronization jobs running. But the error happens on only 2 jobs. I expected that all 3 jobs are getting the error message.

On other systems the error is always logged.

The error has always been there, but the latest FFS version has become extremely thorough with regards to error reporting:

FreeFileSync 12.5 [2023-07-21]
------------------------------
Log and report errors during cleanup or exception handling


The path isn't available on Windows Server ...

Revert to previous version to confirm that the issue goes away. It will likely still be present.
If it works with a previous version of FFS, then reinstall the current version and see if it is still an issue.
Also, check the SMART data of the drive with gsmartcontrol and run a chkdsk if it is ...

Hi all,

since updating to version 12.5 I get the error

Error during process initialization.
Cannot open directory "C:\Users\<username>\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned".
ERROR_PATH_NOT_FOUND: Das System kann den angegebenen Pfad nicht finden. [FindFirstFileEx ...

Yes, this is possible. But again, you can't be sure that the script has finished before the computer is shutting down. And the shutdown is then always waiting the delay time even if it's not needed. For example when the sync is successful and the mail script doesn't have to search for errors in the ...

For me it's not clear what the variables 'intShutdown' and 'strAbort' are standing for because they aren't used in the rest of the code.

If the shutdown is working this way I can add an option to the script to do a shutdown, too. So it will be safe that all steps of the script are done before ...

Yes, the script doesn't support the shutdown of the system. The shutdown in the batch is triggered by FreeFileSync itself. The script is waiting for the exit of FreeFilesync and has to do some more steps after finishing the synchronization. But if FreeFileSync is shutting down the computer all these ...

Hi all,

thank you for your ideas for changing the script and the implementations you've done. I changed now the script by adding the new constants 'IncludeServerNameInSubject' and 'IncludeSyncResultInSubject' to allow users to specify what to include in the email subject.

Here you can find the new ...

Hi bdum,

good to hear that everything is now working as expected.

When I understand you right, you wish to have the status and the computer name in the subject line. Is this correct? This is possible but the subject line will then get longer. You then will not see the complete subject in many mail ...

As already written, you have to set plain text format for the log files in FreeFileSync. The script will then only show error lines in the mail body If there are errors.

Changing the log file format to plain text doesn't change the behavior of the script itsself: The mail title is the same as with HTML formated log files. But if there are errors with the synchronization all error lines in the log file are written completely to the mail body so you don't have to look ...

Yes, I can change the script to write status and computer name to the mail title if this would be helpful. At the moment I'm on holidays. So I can't do this now. Maybe I will change the script next week. I will update this thread when the new version of the script is available.

Looking at your last ...

It's possible to attach the log file to the mail. But does it make sense? The script searches the log file for errors and shows the complete lines of the errors in the log file if there are errors.

I fixed a little bug in the VBScript and uploaded the new file to viewtopic.php?f=2&t=2095&p=18563#p18563.

Hello all,

the actual build, 10.25, of FreeFileSync seems to have issues with synchronizing folders with leading spaces in the folder name. It's bad that there are users who are creating folders with leading spaces in the folder name but in the past with older releases of FreeFileSync I didn't get ...

@TheExpert
Hello,
I saw you were using a VB script to parse log files. I began to write a parser in Python, but I'm really short of time! Could you, please, send me your VB script?
I'd be very grateful!
Thanks.


@Malbec
Hello,
here you can get the VB script I'm using and maintaining: https ...

Hello all,

under viewtopic.php?f=2&t=2095&p=18563#p18563 you can find a new version of the VB script with a little bug fix.

Kind Regards

TheExpert

Why are the errors logged twice in the plain text log files? It's nice that there's a short list of the error messages when opening and reading the log file manually but when the files are parsed the errors are parsed twice. At the moment I have no idea how to prevent the second parsing.