SP1 supported only dates from January 1, 1900, through June 6, 2079 so I assume you added that date programmatically, those pages are not editable.

There are 2 bugs fixed in R2:

1. PropertyDate does not validate input values when assigning Value (only in the constructor)
2. PropertyDate has min/max values that do not correspond with database types

So, in R2 the values are validated both from code and in edit and the min/max values are upgraded to January 1, 1753, through December 31, 9999.

Thanks for the info. The wierd thing is that i can access them in edit in SP1(maybe is SP2), not sure about saving though. But in R2 i can't even expand that node.

Shouldn't I be able to have the date '9999-12-31 23:59', or do I need to use one day before this date?

You can view the page in R1 but you can't save it, this invalid state was caused by one of the fixed bugs above.

You can use the static property PropertyDate.MaxValue to find out the maximum supported value, in R2 its defined as new DateTime(9999, 12, 31). In R1 it is defined as new DateTime(2079,06,06).

Ok, the problem in this case is that i've used DateTime.MaxValue.

PropertyDate.MaxValue = 12/31/9999 12:00:00 AM
DateTime.Maxvalue = 12/31/9999 11:59:59 PM

I will use PropertyDate.MaxValue instead, but is there a reason why they have to differ?

DateTime.MaxValue is actually 23:59:59.9999999 which cannot be represented in SQL2005 so it gets rounded off to a lower value of 23:59:59.997. Not a perfect match between the types.

I also receive this error when i import from Epi7 to Epi 7.5, even content do not have this kind of date range. 

You must enter a value between 01/01/1753 and 12/31/9999 for "EPiServer.Core.PropertyDate".

Is there any solution ?