Skip to main content

Error After Installation of Microsoft Dynamics Navision R2.

Hi Readers,

While trying to install the Navision 2009 R2, most of us get the below given error.

“Service 'Microsoft Dynamics NAV Server' (MicrosoftDynamicsNavServer) failed to start.  Verify that you have sufficient privileges to start system services.”

I tried to install it many times but faced same error again and again so I tried to look into windows Event Viewer to check the cause of problem, and I got the resolution at same point.

I copied the whole error description and I copied that.

The service MicrosoftDynamicsNavServer failed to start. This could be caused by a configuration error. Detailed error information:Microsoft.Dynamics.Nav.Types.NavConfigurationException: The configured time zone identifier "UTC" for the setting "WebServicesDefaultTimeZone" was not recognized. Please use the identifier (in quotes) following the display name of the time zone you wish to use among the following list of recognized time zones:

(GMT+05:30) Chennai, Kolkata, Mumbai, New Delhi: "Server Time Zone"
(GMT-12:00) International Date Line West: "Dateline Standard Time"
(GMT-11:00) Midway Island, Samoa: "Samoa Standard Time"
(GMT-10:00) Hawaii: "Hawaiian Standard Time"
(GMT-09:00) Alaska: "Alaskan Standard Time"
(GMT-08:00) Pacific Time (US & Canada); Tijuana: "Pacific Standard Time"
(GMT-07:00) Arizona: "US Mountain Standard Time"
(GMT-07:00) Chihuahua, La Paz, Mazatlan: "Mexico Standard Time 2"
(GMT-07:00) Mountain Time (US & Canada): "Mountain Standard Time"
(GMT-06:00) Central America: "Central America Standard Time"
(GMT-06:00) Central Time (US & Canada): "Central Standard Time"
(GMT-06:00) Guadalajara, Mexico City, Monterrey: "Mexico Standard Time"
(GMT-06:00) Saskatchewan: "Canada Central Standard Time"
(GMT-05:00) Bogota, Lima, Quito: "SA Pacific Standard Time"
(GMT-05:00) Eastern Time (US & Canada): "Eastern Standard Time"
(GMT-05:00) Indiana (East): "US Eastern Standard Time"
(GMT-04:00) Atlantic Time (Canada): "Atlantic Standard Time"
(GMT-04:00) Caracas, La Paz: "SA Western Standard Time"
(GMT-04:00) Santiago: "Pacific SA Standard Time"
(GMT-03:30) Newfoundland: "Newfoundland Standard Time"
(GMT-03:00) Brasilia: "E. South America Standard Time"
(GMT-03:00) Buenos Aires, Georgetown: "SA Eastern Standard Time"
(GMT-03:00) Greenland: "Greenland Standard Time"
(GMT-02:00) Mid-Atlantic: "Mid-Atlantic Standard Time"
(GMT-01:00) Azores: "Azores Standard Time"
(GMT-01:00) Cape Verde Is.: "Cape Verde Standard Time"
(GMT) Casablanca, Monrovia: "Greenwich Standard Time"
(GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London: "GMT Standard Time"
(GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna: "W. Europe Standard Time"
(GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague: "Central Europe Standard Time"
(GMT+01:00) Brussels, Copenhagen, Madrid, Paris: "Romance Standard Time"
(GMT+01:00) Sarajevo, Skopje, Warsaw, Zagreb: "Central European Standard Time"
(GMT+01:00) West Central Africa: "W. Central Africa Standard Time"
(GMT+02:00) Athens, Beirut, Istanbul, Minsk: "GTB Standard Time"
(GMT+02:00) Bucharest: "E. Europe Standard Time"
(GMT+02:00) Cairo: "Egypt Standard Time"
(GMT+02:00) Harare, Pretoria: "South Africa Standard Time"
(GMT+02:00) Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius: "FLE Standard Time"
(GMT+02:00) Jerusalem: "Israel Standard Time"
(GMT+03:00) Baghdad: "Arabic Standard Time"
(GMT+03:00) Kuwait, Riyadh: "Arab Standard Time"
(GMT+03:00) Moscow, St. Petersburg, Volgograd: "Russian Standard Time"
(GMT+03:00) Nairobi: "E. Africa Standard Time"
(GMT+03:30) Tehran: "Iran Standard Time"
(GMT+04:00) Abu Dhabi, Muscat: "Arabian Standard Time"
(GMT+04:00) Baku, Tbilisi, Yerevan: "Caucasus Standard Time"
(GMT+04:30) Kabul: "Afghanistan Standard Time"
(GMT+05:00) Ekaterinburg: "Ekaterinburg Standard Time"
(GMT+05:00) Islamabad, Karachi, Tashkent: "West Asia Standard Time"
(GMT+05:30) Chennai, Kolkata, Mumbai, New Delhi: "India Standard Time"
(GMT+05:45) Kathmandu: "Nepal Standard Time"
(GMT+06:00) Almaty, Novosibirsk: "N. Central Asia Standard Time"
(GMT+06:00) Astana, Dhaka: "Central Asia Standard Time"
(GMT+06:00) Sri Jayawardenepura: "Sri Lanka Standard Time"
(GMT+06:30) Rangoon: "Myanmar Standard Time"
(GMT+07:00) Bangkok, Hanoi, Jakarta: "SE Asia Standard Time"
(GMT+07:00) Krasnoyarsk: "North Asia Standard Time"
(GMT+08:00) Beijing, Chongqing, Hong Kong, Urumqi: "China Standard Time"
(GMT+08:00) Irkutsk, Ulaan Bataar: "North Asia East Standard Time"
(GMT+08:00) Kuala Lumpur, Singapore: "Singapore Standard Time"
(GMT+08:00) Perth: "W. Australia Standard Time"
(GMT+08:00) Taipei: "Taipei Standard Time"
(GMT+09:00) Osaka, Sapporo, Tokyo: "Tokyo Standard Time"
(GMT+09:00) Seoul: "Korea Standard Time"
(GMT+09:00) Yakutsk: "Yakutsk Standard Time"
(GMT+09:30) Adelaide: "Cen. Australia Standard Time"
(GMT+09:30) Darwin: "AUS Central Standard Time"
(GMT+10:00) Brisbane: "E. Australia Standard Time"
(GMT+10:00) Canberra, Melbourne, Sydney: "AUS Eastern Standard Time"
(GMT+10:00) Guam, Port Moresby: "West Pacific Standard Time"
(GMT+10:00) Hobart: "Tasmania Standard Time"
(GMT+10:00) Vladivostok: "Vladivostok Standard Time"
(GMT+11:00) Magadan, Solomon Is., New Caledonia: "Central Pacific Standard Time"
(GMT+12:00) Auckland, Wellington: "New Zealand Standard Time"
(GMT+12:00) Fiji, Kamchatka, Marshall Is.: "Fiji Standard Time"
(GMT+13:00) Nuku'alofa: "Tonga Standard Time"
   at Microsoft.Dynamics.Nav.Types.ServerUserSettings.ParseWebServicesDefaultTimeZone(String value)
   at Microsoft.Dynamics.Nav.Types.ServerUserSettings.LoadSettings()
   at Microsoft.Dynamics.Nav.Types.ServerUserSettings.get_Instance()
   at Microsoft.Dynamics.Nav.WindowsServices.NavServiceBase.OnStart(String[] args).

For more information, see Help and Support Center at

Then I found out that I need to change time zone in customsettings.config file in the service folder of Navision installation.
I replaced the UTC parameter of time zone to Server time zone (for India) and the service started successfully.

So if anyone is facing same problem can copy paste the time zone (according to their local time zone) from above list and replace same with UTC parameter in the custom setting.config file.

Saurav Dhyani


  1. I think People Keep Visiting this post, but either the problem is not resolved or this is not what they were looking for.
    Please revert back if you have any other error, i will get back on same.

  2. It resolved my issue.

  3. @Anonymous Thanks for the comment.

  4. i had a same problem and it resolved the problem.. thanks

  5. My issue was resolved as the services are now running, but now i cant connect my Role Tailored Client is not connecting to the NAS Server. Please help, thank you.

    1. Hi Dandy,
      Can you explain me the error message that you are getting or the issue that you have.
      Please send the details in my email address -

      Thanks & Regards,
      Saurav Dhyani

  6. Thank you very Much, i face this problem.

    1. Hi Mostafa,

      you are most welcome.

      Saurav Dhyani

  7. Wow..This is an Appreciable Post!!Keep Going Saurav!!


Post a Comment

Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

Dynamics 365 Business Central 2021 release wave 2 (BC19) Released.

Hi Readers, As we all were expecting Microsoft have Released Business Central 2021 Release Wave 2 Today a.k.a BC19. In this article we will see what all is announced with the General Availability.  Starting Today Customers & Partners can start using Business Central 19. #msdyn365bc #bc19

Navision Cannot generate SSPI context State ID HY000

Hi all, Sometime while trying to connect database in classic client with windows authentication or connect to Role Tailored Client we face an error message. Error - The following ODBC error occurred: Error: [Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context  State ID: HY000