SCOM 2007 R2 – Reporting : Value of ‘1/01/0001 12:00:00 AM’ is not valid for ‘Value’. ‘Value’ should be between ‘MinDate’ and ‘MaxDate’

Hi Guys,

Yesterday, I migrated a SCOM 2007 R2 reporting module from a SQL Server Reporting Services 2005 to a SQL Server Reporting Services 2008 R2. The migration worked perfectly, the reports were available, I was able to start it, everything seems ok, but…

when I checked the scheduled reports, the schedule date/time display was set At 12:00 AM on 1/1/001. Confused smile

image

And when I tried tried to edit a scheduled reports I’ve got the following error :

clip_image002

Hopefully the scheduled reports itself were still running fine, only the display was incorrect and an error message when I tried to edit it. I did some search and I found the following links :

http://wmug.co.uk/blogs/aquilaweb/archive/2008/10/14/reporting-error-value-of-1-1-0001-00-00-00-is-not-valid-for-value.aspx

http://qa.social.technet.microsoft.com/Forums/eu/operationsmanagerreporting/thread/06d79194-2919-4236-bddf-371c7f1cc022

http://nocentdocent.wordpress.com/2010/02/23/reporting-error-when-a-different-locale-is-used-for-srs-and-console/

http://nocentdocent.wordpress.com/2011/03/04/issue-with-reports-and-non-en-us-locale/

All my servers were in English US format, none of the link above solved my problem. Finally, I found this thread :

http://social.technet.microsoft.com/Forums/en-US/operationsmanagerreporting/thread/c070e435-862b-4ccd-ab4a-d2202c61aab3

Update:

I opened up a case with Microsoft Support and resolved the issue. Apperantly this is a known issue and the bug will be addressed in CU6. Microsoft was able to give me a hotfix (QFE_MOMEsc_4724.msi) which I applied on all systems that have SCOM Console. I am told that this issue occurs when SCOM 2007 R2 CU5 runs on SQL 2008 R2.

I hope it helps to others that run into same problem.

ZMR 

I contacted my Microsoft Premier Support Contact and they sent me the hotfix. (Reference : Hotfix for MOMEscalation 4724).

This hotfix is simply a new DLL, Microsoft.MOM.UI.Common.dll, that you will have to place in the Operations Manager installation folder on all the machines where you run the Operations Manager Console. When done, just restart the Operations Console, and you will be able to see the Schedule information and edit the jobs without any error message.

image

As this hotfix is not public, you will have now other choice than contacting the Microsoft Support to get it. I received the confirmation that this hotfix will be included in the SCOM Cumulative Update 6, but we don’t know the release date yet.

Christopher KEYAERT

clip_image001 clip_image002 clip_image004 clip_image005 clip_image007 clip_image008

Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+Email this to someoneShare on TumblrPin on PinterestDigg thisShare on RedditFlattr the authorBuffer this pageShare on StumbleUpon

About Christopher Keyaert

Christopher Keyaert is a Consultant, focused on helping partners to leverage the System Center and Microsoft Azure cloud platform. He is also a Microsoft Most Valuable Professional (MVP) for Cloud and Data Center Management and a Microsoft Certified Trainer (MCT).
This entry was posted in Uncategorized. Bookmark the permalink.

One Response to SCOM 2007 R2 – Reporting : Value of ‘1/01/0001 12:00:00 AM’ is not valid for ‘Value’. ‘Value’ should be between ‘MinDate’ and ‘MaxDate’

  1. Shiva says:

    To check your short date format (on Windows Server 2003 / 2008) go to Control Panel and select Regional and Language Options then click Customize on the Regional Options tab. This will open a new window where you can select the Date tab and check the short date dormat and alter as necessary.

    this worked for me

Leave a Reply

Your email address will not be published. Required fields are marked *