KNOWN ISSUE: BESR IC - String was not recognized as a valid DateTime

Article:TECH39659  |  Created: 2008-03-20  |  Updated: 2010-08-28  |  Article URL http://www.symantec.com/docs/TECH39659
Article Type
Technical Solution

Issue



The log file shows the following errors:

Source: Symantec.Serialization.Serializable.convertStringToObject
Description: String was not recognized as a valid DateTime. ( Unhandled exception.  Type=System.FormatException Msg=String was not recognized as a valid DateTime. Src=mscorlib
StackTrace=
   at System.DateTimeParse.GetDayOfNNY(DateTimeResult result, DateTimeRawInfo raw, DateTimeFormatInfo dtfi)
   at System.DateTimeParse.ProcessTerminaltState(Int32 dps, DateTimeResult result, DateTimeRawInfo raw, DateTimeFormatInfo dtfi)
   at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
   at System.DateTime.Parse(String s, IFormatProvider provider, DateTimeStyles styles)
   at System.DateTime.Parse(String s, IFormatProvider provider)
   at System.DateTime.Parse(String s)
   at Symantec.Serialization.Serializable.convertStringToObject(String value, String typeName) )


Environment



- NS6.0 SP3 + BESR IC
- Windows 2003 SP2
- SQL2005 sp2

Cause



BESR IC is supporting only the English (US) language at the moment, but this is by design already and the development team working on the resolution.

Solution



As workaround you will need to change the Regional and Language settings to English (US) in Windows. 


Legacy ID



41005


Article URL http://www.symantec.com/docs/TECH39659


Terms of use for this information are found in Legal Notices