[Solved] FileZilla Server Stopping

[CrimpOn]

Recently install new FileZilla server 1.0.1 on Windows 10. Two days in a row the FileZilla Server service has stopped. I keep the Admin panel open on my desktop to see which security cameras are uploading motion files (windows minimized in the Task Bar) and just happen to notice that it is no longer connected. Click "connect", which fails, and then have to restart the service.

Is there a way to provide information about this that is more detailed than the Windows Event Log?

Faulting application name: filezilla-server.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: msvcrt.dll, version: 7.0.19041.546, time stamp: 0x564f9f39
Exception code: 0x40000015
Fault offset: 0x000000000002da1e
Faulting process id: 0x1064
Faulting application start time: 0x01d7b6509a441a28
Faulting application path: C:\Program Files\FileZilla Server\filezilla-server.exe
Faulting module path: C:\WINDOWS\System32\msvcrt.dll
Report Id: 9c2ea140-fd36-47b4-ba22-90ec4c276c6d
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: filezilla-server.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: msvcrt.dll, version: 7.0.19041.546, time stamp: 0x564f9f39
Exception code: 0x40000015
Fault offset: 0x000000000002da1e
Faulting process id: 0x1fdc
Faulting application start time: 0x01d7b544467b5ba0
Faulting application path: C:\Program Files\FileZilla Server\filezilla-server.exe
Faulting module path: C:\WINDOWS\System32\msvcrt.dll
Report Id: 976c95b4-eeda-41db-846f-c4b0d8471589
Faulting package full name:
Faulting package-relative application ID:

[CrimpOn]

Failed again today.

Is there a better way to contact "someone who knows things" than posting in this forum?

Would someone have a link to the previous version, which ran smoothly for a couple of years?
(I did not realize that I should have kept a copy in case the new release was unreliable.)

[boco]

https://download.filezilla-project.org/server

[oibaf]

Hi, thanks for the report.

To help us solve the issue, it would be necessary to do two things:

• enable debug logs.
  To do this, go in the Administration UI, find the Logging tab and: set the Logging level to 5 - Debug; make sure the Log output is set to some path of your likings.
• activate the Windows Error Reporting system for the FileZilla Server executable.
  To do that, please download the attached file and open it with the default action. It should prompt you for administration permissions, which you'll want to grant.

After that, make sure the filezilla-server.exe service crashes again. You should then find a file named filezilla-server.exe.<somenumber>.dmp under C:\Windows\System32\config\systemprofile\AppData\Local\CrashDumps. If there's more than one, pick the most recent one.

Then, please send that file to tim.kosse@filezilla-project.org, together with log file(s).

Thanks.

[CrimpOn]

Thank you for the instructions. I saw no prompt for admin credentials, so I logged in with my admin account and did it that way.

Server failure is not predictable, although it appears to be about once a day.
p.s. I had not realized that the default setting on this forum was not to send an email notification of replies. The other forums I participate in have the opposite default.

[CrimpOn]

Want to "close the loop" on this issue. Version 1.1.0 has been running for a week now with zero crashes.

Some forums have a mechanism to mark posts "Solved". If this forum does, I did not find it.

[boco]

phpBB has no such mechanism. I have tagged the first post.

[botg]

Version 1.1.0 has been running for a week now with zero crashes.

Excellent, thanks for letting us know.