Upgrade fails to import data - 0.9.60 to 1.6.1

[cgareau]

Hi Everyone,

We're building a new server and I've installed 0.9.60 beta on it and successfully copied over the folder structures as well as the FileZilla Server configuration, including the user profiles. All appears to be OK with the old build. When I try to install FileZilla_Server_1.6.1_win64-setup, it doesn't convert anything at all. The new version is not able to convert the data, so there are no profiles imported at all.

- Start install for FileZilla_Server_1.6.1_win64-setup.
- When it prompts to delete settings from 0.9.60, I click NO.
- Then I get this error. I have tried a few times even cycled the system in between.

ERROR DETAILS:
There was an error while executing service filezilla-server-config-converter.
Win32 code: 1067
Service code: 0


Any help with this would be greatly appreciated.
Thank you,
Chad

[cgareau]

Hello FileZilla Admins ... can someone please advise on this?



Thank you,
Chad

[oibaf]

Can you check if manually running the program filezilla-server-config-converter.exe works?

The syntax is the following:

Code: Select all

filezilla-server-config-converter.exe <path/to/FileZilla Server.xml> <absolute path to the configuration directory where new config files will be generated>

You will file the filezilla-server-config-converter.exe executable in the same directory as the server itself.

[cgareau]

Hi oibaf,

Thank you for replying. The 2nd parameter, is that the installation folder of the new version? Sorry if this seems trivial, I' really not familiar with the conversion as I've never done it before.



Chad

[boco]

Actually, the new server saves into the ProgramData directory, using a filezilla-server subdir.

[oibaf]

filezilla-server-config-converter.exe deals with the 2nd parameter according to whether it's an absolute path or a relative one. If it's absolute, it uses it as a folder under which to store the generated configuration files, if it's a relative path (and a simple "name" is a relative path as well) uses that as a folder name under the user's %LOCALAPPDATA% folder if it's a regular user, or %PROGRAMDATA% if it's the SYSTEM user.

That's why it's run as a service by the installer, so it can use the same user as the filezilla-server service [1].

By running the program by hand, depending on whether it fails or not, we can have an indication about what could the root cause be.

___

[1] This made me just realize that there's a bug in the installer, as it doesn't take into account the custom user name, if any is chosen, and tries to use the default SYSTEM user instead.

[cgareau]

Hi guys,

Thanks for the info so far. I posted on someone else's post as well as they were having similar issues. I was successfully able to go from 0.9.6 to 1.0.1, then to 1.3.0, then to 1.4.1. However, I cannot go to 1.5.0 because none of the users are migrated at all and I did try 1.6.1 as well, same results. Any suggestions on how to proceed at this point? I would like to get to 1.6.1, which is the most current release.


Thank you,
Chad

[boco]

Check the old data location,

Code: Select all

"%SytemRoot%\System32\config\systemprofile\AppData\Local\filezilla-server"

If your data is there, move it to

Code: Select all

"%ALLUSERSPROFILE%\filezilla-server"

while the server isn't running. Mayhaps the migration to the new directory failed?

[cgareau]

@boco ... you're awesome!! That worked : )


Thank you for your help, much appreciated!!
Chad