"not a valid date and time"

Roddy · Post by **Roddy** » Mon Nov 30, 2009 3:46 pm

Hi, at some point I think since upgrading to 11.1.15 (I'm now on 11.1.18), I get a dialog box with the following error for some of my Macros, and even some of the sample ones. "17/Jun/2008 13:53 is not a valid date and time.". The date and time is different depending on the Macro, and doesn't appear for all of them. The message appears when you click on the group in the main browser, but also when saving changes to a macro, or trying to create a new one. Is this a known issue, with a known fix, or should I just try deleting everything and starting again (reimporting the macros).

Post by **Marcus Tettmar** » Mon Nov 30, 2009 7:48 pm

Not aware of this but how did you upgrade and from what version? You can n not and should not upgrade from v10 or lower. Instead install separately and import your macros.

Is there a pattern to this? What do all the macros that cause this have in common?

Have you changed your system date format at any time? Macro Scheduler should not care about the system date format, but can you tell me what your regional settings are for dates and I'll double check there's no bug there.

Wait up ... I guessed your short-date format from your message and set mine to dd/MMM/yyyy and got the same issue. So I'm glad that I have replicated and can now work on a fix. In the mean time if you change the short-date format to dd/MM/yyyy instead (month number instead of name) you should be all right.

Sorry about this. Date format shouldn't matter. We'll get it sorted ASAP.

jpuziano · Post by **jpuziano** » Mon Nov 30, 2009 8:19 pm

mtettmar wrote:Sorry about this. Date format shouldn't matter. We'll get it sorted ASAP.

Sounds great thanks Marcus. Who knows what a user might set their "short-date" to on their machine... but as long as the MS commands provide consistant results in all cases, we're happy.

Thanks for reporting this Roddy... this will help us all.

jpuziano · Post by **jpuziano** » Thu Dec 10, 2009 5:48 pm

Hi Marcus,

Anything further on this issue? Did you find a fix?

Post by **Marcus Tettmar** » Wed Dec 16, 2009 5:17 pm

Yes, this is fixed in dev.

jpuziano · Post by **jpuziano** » Wed Dec 16, 2009 8:10 pm

Thanks Marcus, sounds good... and thanks again Roddy for reporting it.

Take care