Defining the Time Zone for Microsoft Dynamics NAV Web Services


With Microsoft Dynamics NAV 2009 R2, you can configure Microsoft Dynamics NAV Server to specify the time zone in which web services calls are run. You do this by configuring the WebServicesDefaultTimeZone setting in CustomSettings.config file, the Microsoft Dynamics NAV Server configuration file.

The following table describes the possible values for the WebServicesDefaultTimeZone setting.

Value Description
UTC Specifies that all business logic for web services on the server runs in Coordinated Universal Time (UTC). This is the default value. This is how all web services business logic was handled in Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 2009. This is the default value.
Server Time Zone Specifies that web services use the time zone of the computer running Microsoft Dynamics NAV Server.
ID of any Windows time zone Specifies any Windows time zone as defined in the system registry on the computer running Microsoft Dynamics NAV Server, under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones. For example, if you want all web service calls to be run in the time zone for Tbilisi, Georgia, you would configure this setting with this value:

<add key=”WebServicesDefaultTimeZone” value=”Caucasus Standard Time”/>

One flaw has been found with this new setting. The default value for WebServicesDefaultTimeZone is UTC. However, some versions of Windows do not contain a UTC value in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones subkey in the registry. If there is no UTC value in the registry, the Microsoft Dynamics NAV Server and Microsoft Dynamics NAV Business Web Services services cannot start when the WebServicesDefaultTimeZone setting is set to UTC.

One way to remedy this problem is by setting WebServicesDefaultTimeZone to a null string, which causes all business logic for web services to run in UTC. Another way is just to set the parameter to another valid value, as in the example above.

Comments (0)

Skip to main content