Opened 14 years ago

Closed 14 years ago

#4560 closed Bug report (fixed)

Error message "Timer creation failed." when update is downloaded

Reported by: JanRei Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc: vavrajj@…, mark@…
Component version: Operating system type: Windows
Operating system version: Windows 7 Build 7100


After the download of the new FileZilla version has been started there is an error message "Timer creation failed.". The download completes successfully despite of that, but there is no progress information shown and the progress bar stays empty.

Upgrading from version 3.2.4 works fine for me. I first saw this message when upgrading from version to 3.2.5-rc1. The issue seems to happen with 3.2.5-rc1 as well.

Attachments (1)

TimerCreationFailed.png (15.7 KB ) - added by JanRei 14 years ago.
Screenshot of the error message

Download all attachments as: .zip

Change History (6)

by JanRei, 14 years ago

Attachment: TimerCreationFailed.png added

Screenshot of the error message

comment:1 by Tim Kosse, 14 years ago

Resolution: fixed
Status: newclosed

Thanks for reporting. Will be fixed in 3.2.5

comment:2 by Jay, 14 years ago

Cc: vavrajj@… added
Resolution: fixed
Status: closedreopened

Just updated to 3.2.5 this morning and received the "Timer creation failed." dialog box. If it hadn't been listed as fixed in the recent changes I viewed before starting the download I would not have realized that waiting it out for the download to finish would work. The information was there for me, but I'm not sure the issue is resolved as intended.

comment:3 by Tim Kosse, 14 years ago

Resolution: fixed
Status: reopenedclosed

Obviously the problem will go away only until after you have installed 3.2.5

comment:4 by Zero-K, 14 years ago

Cc: mark@… added
Operating system version: Windows XP SP3Windows 7 Build 7100
Resolution: fixed
Status: closedreopened

I'm running Windows 7, just upgraded to 3.2.6 from 3.2.5 and I'm receiving the same error.

comment:5 by Tim Kosse, 14 years ago

Resolution: fixed
Status: reopenedclosed

You cannot get this error message if you upgrade from 3.2.5, the problem only existed in versions earlier than 3.2.5

Note: See TracTickets for help on using tickets.