What are the Regional Settings Required for NFA, ADA, and UCM
search cancel

What are the Regional Settings Required for NFA, ADA, and UCM


Article ID: 21400


Updated On:


CA Application Delivery Analysis MTP (NetQoS / ADA) CA Infrastructure Performance CA NetVoyant (NetQoS / NV) CA Network Flow Analysis (NetQos / NFA)


Having incorrect Regional settings on the server can cause various errors in the web interface and in the product logs (any product) with errors referencing invalid Int32 strings, invalid input string, and/or invalid DateTime entries.

This issue is caused when Windows servers is/are using non-US regional settings, or using date formats set to: dd MMMM yyyy.
An example of this is having regional settings set to "English (United Kingdom)".
All products require that the Regional Settings on the server be set to US Regional settings with the proper sShortDate and sLongDate settings in the registry.


Windows Server 
Any of the NetQoS Products


Follow the steps below:

  • Enter the Windows regional settings menu through Control Panel on the server itself.
  • Modify this setting to "English (United States)".
  • Click OK.
  • Now, enter the Windows Registry, and highlight My Computer.
  • Go to Edit > Find, and search for the following registry keys and update them to the following values:

sLongDate = dddd, MMMM dd, yyyy

sShortDate = M/d/yyyy

sLanguage: ENU

Locale: 00000409

LocaleName: en-US

sCountry: United States

sDecimal: .

  • Use the F3 key to continue searching the registry for more instances of these keys.
  • Then search for the following
  • Keep doing so until it states it has finished searching the registry.
  • The regional settings change in the control panel doesn't always update every registry entry and that can still affect the database if all entries are not updated manually in the registry. This is a windows issue, so the full search through the registry is necessary.
  • After all changes are made, Restart the Server to apply the registry changes.


Additional Information

You might also reference this site for any further registry changes that need to be made to resolve errors. The above steps should be all that is needed in most cases: