Community
Showing results for 
Search instead for 
Do you mean 
Reply

The string was not recognized as a valid datetime

Accepted Solution Solved
Platinum Elite Contributor
Posts: 14,384
Country: Australia
Accepted Solution

The string was not recognized as a valid datetime

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?


Accepted Solutions
Solution
Accepted by topic author GLComputing
‎09-25-2015 03:20 AM
Platinum Elite Contributor
Posts: 14,384
Country: Australia

All Replies
Platinum Elite Contributor
Posts: 6,537
Country: USA

Re: The string was not recognized as a valid datetime

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.

Greig Hollister

Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: The string was not recognized as a valid datetime

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?
Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: The string was not recognized as a valid datetime

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
Solution
Accepted by topic author GLComputing
‎09-25-2015 03:20 AM
Platinum Elite Contributor
Posts: 14,384
Country: Australia
Bronze Elite Contributor
Posts: 2,545
Country: New_Zealand

Re: The string was not recognized as a valid datetime

[ Edited ]

Greig,

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

Graeme Leo
Xact Software - consultants and developers
Follow us on Twitter and check out our Blog


Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: The string was not recognized as a valid datetime

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
Copper Super Contributor
Posts: 96
Country: New_Zealand

Re: The string was not recognized as a valid datetime

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 .

Copper Super Contributor
Posts: 96
Country: New_Zealand

Re: The string was not recognized as a valid datetime

Greg,

 

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

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: The string was not recognized as a valid datetime

Jim,

 

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