MySQL Bugs: #25313: Scheduled Backup gives "00:00 is not a valid date and time"

Bug #25313	Scheduled Backup gives "00:00 is not a valid date and time"
Submitted:	28 Dec 2006 15:44	Modified:	11 Jan 2007 10:22
Reporter:	Marco Dal Zotto	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.2.8	OS:	Windows (XP Pro)
Assigned to:		CPU Architecture:	Any
Tags:	Scheduled Backup;

Description:
Saveing the backup project after setting up a scheduled backup, gives "(time inserted in the format hh:mm) is not a valid date and time". It does't matter the options I choose in the "Execution Time".

I had the same problem with the last version I tried (1.2.4)

How to repeat:
Setting up a scheduled backup project.

Suggested fix:
--

Thank you for a problem report. Please, specify the exact version of MySQL server used, and send the results of:

SHOW VARIABLES LIKE 'sql_mode';

'00:00' worked OK for me with local 5.0.27, hence the request.

MySql Version: "MySQL 5.0.24a-community-nt-log via TCP/IP"

SHOW VARIABLES LIKE 'sql_mode';

'sql_mode', 'STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'

Please, try to repeat with a newer version of server, 5.0.27, and inform about the results.

With the 5.0.27 MySql release I get the same error.

I've got the solution!!!

I have a XP Pro Ita (Italian) and I have seen the time format in the schedule is 12.00 intead of 12:00. So I have applied this format in the date/time field (ex. 10.15) and worked!

Thanks anyway for the support.

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #24888

Sorry, I couldn't find my bug report.