When you try to create a Calendar in Service Manager 2012 you get the error – Value cannot be null

In some environment, depending on the TimeZone settings - most important of all Daylight Saving, you may get this error message when you try to create a Calendar in the Service Manager 2012 Console which can also be seen in the Event Log:

 Application: System Center Service Manager
Application Version: 7.5.1561.0
Severity: Error
Message: Value cannot be null.
Parameter name: timeZone

System.ArgumentNullException: Value cannot be null.
Parameter name: timeZone
   at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ConsoleTaskHandler.DoTask(IList`1 navigationNodes, NavigationModelNodeTask task, List`1 parameterList)
   at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ConsoleTaskHandler.DoTask(IList`1 navigationNodes, NavigationModelNodeTask task)
   at Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobRecord.ExecuteBackgroundJob(Object sender, ConsoleJobEventArgs eventargs)
   at Microsoft.EnterpriseManagement.ServiceManager.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)


It seems that this issue arises when the check-box "Automatically adjust clock for Daylight Saving Time" in your Time Zone Settings is unchecked. This setting is stored as an instance of the TimeZoneInfo class and it makes this appear as a different time zone. Because this "custom" time zone would not match any known time zone, the parameter will be retuned as NULL for the time zone to be set as the default when opening the Calendar.

To solve this issue, just check the check-box for "Automatically adjust clock for Daylight Saving Time" in your Time Zone Settings:


Now you should be able to create Calendars without any issues 😀








Comments (3)

  1. Hi Ehab, sorry for that … for the moment you can only change your timezone …

  2. ehab says:

    I have this issue but our time zone Cairo doesn't have the option for Automatically adjust clock for Daylight Saving Time

    it doesn't exit.

  3. rbansal says:

    This issue is fixed in 2012 R2 UR4.

Skip to main content