8
Hello,
Has anyone ever experienced data corruption when using the .NET 2.0 Membership API security framework and SQL Server 2000? I wrote a web app for a client that has 300 users. Most of the users are fine, but a handful are complaining that they use their account for a week or two and then "all of a sudden" their password is not valid anymore.
They also claim that when they try to use the password reset utility after their password goes bad, they get an error that their security answer (required on this system) is incorrect -- really mind boggling since I added code to make the security answer case insensitive, and they use really simple answers like "car" or "bus".
Mind you, the account I set up for myself on their live system has been perfectly intact for 10 months now. And we know that data generally doesn't magically change itself.
The first thing that comes to mind is user input error. But I've been arguing with the client for 3 weeks now, and they insist they are entering the correct password and/or security answer.
Has anyone ever experienced this phenomenon? Does anyone have any ideas?
Thanks for your help.
