This is wierd. After seeing this anomaly in a Beta 2 app I carried over into
RTM 2.0 I've confirmed the anomaly in two different basic page applications
I created for testing using two fresh instances of a SQL 2005 database with
Membership applied. Each time I use the Website Administrator there are two
instances of the user in the aspnet_Users table. Furthermore, the time stamp
is 6 hours ahead of my actual system time.
I've tracked this down to using Roles. If I use the Website Administor to
create a user there is only one instance of the user in aspnet_Users (as
expected) but the user is time stamped 6 hours into the future in the
LastActivityDate column. As soon as I add that user to a Role there are two
instances of the user in aspnet_Users and the redundant record is also time
stamped 6 hours into the future.
I am very puzzled about this and have no idea how it can be occurring. I
thought the box may need a CMOS battery replacement but how could a flakey
battery continue to keep system time current and stable yet be responsible
for data entries being recorded 6 hours into the future?
Something is stinky here. Do you have any ideas?
<%= Clinton Gallagher
