Error when navigating by date: String was not recognized as a valid DateTime

Document ID : KB000023172
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:


If a customer has set the regional settings incorrectly (i.e. any non-US standard setting), NPC will error out when navigating through various time periods with the error:

"String was not recognized as a valid DateTime"

 

Cause:

This error can be caused by various invalid dates in the data due to the regional settings being incorrect. For more information see here: TEC573085

Note: This will only resolve the date format in new data. Old data will not be updated, so you will still see errors when looking
at older data from before the changes.


Resolution:
  • Set the regional settings to US where it is M/D/Y instead of D/M/Y.
  • Reboot the server.
  • Back up the registry.
  • Search the registry for all keys where the name is sShortDate.
    • Make sure its value is set to M/d/yyyy.
  • Search the registry for all keys where the name is sLongDate.
    • Make sure its value is set to dddd, MMMM dd, yyyy.
  • Reboot the server.

 

Additional Information:

You can run the USsettings.exe support tool to perform the registry changes automatically.

Check this Techdoc:TEC573085 for complete reference