We have a sitefinity 3.7 installation with a custom membership provider and it has worked perfectly for many years. We're in the process of upgrading our user database and part of that change is changing some ID's from integers to Guids.
I've made a very small change in our membership provider, changed an int to a guid to use the new ID's, and everything seemed perfect. We are now able to login to sitefinity with the new database table design, and everything works perfectly.
So I push it from my local machine to our development environment, and I get this error. After an hour and a half of struggling to figure out the problem last Friday, I decided to restart the website in IIS, and that seemed to fix the problem and it worked on the Dev server. About an hour later, the error was coming up again with no changes to any files or the database what so ever, it simply decided to be broken again. And this time restarting the website, recycling the app pool, or even restarting the whole server has no effect on it.
This puts a huge road block in our project, as we cannot deploy to live with this issue. Any help is greatly appreciated.
To sum up:
1. Changed one line of code in our custom membership provider that worked for years:
In addition, can you please try deleting the temporary asp.net files on the server, and let us know if the behavior persists after applying the suggested steps in the forums and clearing the temporary internet files?
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items