The string was not recognized as a valid datetime

[GLComputi…]

I have a user:

•   ACT PRO 2011 Version 13 HotFix2 (New Zealand)
•   Windows 7

When opening ACT!, we get this error:
"The string was not recognized as a valid datetime. There is a unknown word starting at index 5"
If you click OK it seems to be fine... except:

When the user goes to schedule a CALL or MEETING a dialogue pops up saying:
"Resolution of the dependancy failed, type = "ACT.ULAvailControl" name = "Eception message is: The current build operation (build key Build Key{Act.UL.AvailControl, null}; failed. The string was not recognised as a valid Date Time. There is a unknown word starting at index 5. (Strategy type BuildPlanStratefgy, index 3)”

Any ideas?

[ghollister]

Hi Mike,
Does this happen with the Demo database or a new database? It sounds like an invalid value in the database, possibly a date field or in the Activity Types list. It may also be a conflict with the regional date/time settings on the machine.

[GLComputi…]

One person said they heard it was a "known issue" with Mexico and New Zealand regional settings and there was a workaround.

Any chance you could check that?

[GLComputi…]

Sage Australia's solution was to close and re-open ACT! before every update to an activity...

I have found a MUCH simpler and permanent solution and will be posting it to my blog later

[GLComputi… · Accepted solution]

Blog article posted:
http://blog.glcomputing.com.au/2010/10/act-2011-string-was-not-recognized-as.html

[gleo]

Greig,

This bug was identiifed about 13th September and is slated to be fixed in SP 1. Defect # 93519

[GLComputi…]

At least now there's a nice simple fix.

Shame no-one in NZ beta tested it early enough to get it fixed in the gold release

[jpenney]

Mike the problem was not in the Gold version as far as I know, I first noticed it after HF2 was released.   It was then common in any new installs.

I couldn't get a copy of the Beta to test so cannot be sure if there was a problem in testing.

Greg, we seem to have at least three separate threads covering this MP/94484-#M18072; MP/98276 -#M40291 and one other which came up with the AM/PM vs a.m./p.m.  change to regional settings.

Would seem logical to combine  all threads or at least  generate a link to each .

[jpenney]

Greg,

The problem was in the local databases and in the ACT! 2011 Demo Database  in the Australia/Asia version.

[GLComputi…]

Jim,

Graeme said it was identified in September ... thet's the Gold version