I've been working on a website, using VS2010/C# to develop it, and using a SQL Server 2008 instance to house my application data, as well as my ASP member data. In this case I'm using the same DB for both.
Somewhere while trying to get the authentication to work properly, I dropped the ball and broke the entire site; so I restored my code into a new location, using a copy I sent to my adviser a couple of days ago. Opened up the project in VS2010, built it without any problems and tested successfully it using the built-in server in Visual Studio. I published it to wwwroot and tested it there as well, and all was good.
But now I can't get to the ASP.NET config tool; I get the dreaded error,
"An error was encountered. Please return to the previous page and try again. "
And certainly I have all the membership/role tables populated. The log-in feature works superficially, because if I submit a bad name or password, it fails. Therefore we know that the system is talking to the database all right.
What could be wrong? It is true that I'm running the old code in a new location, but so what? If that were a problem I wouldn't expect the login to work at all.
Somewhere while trying to get the authentication to work properly, I dropped the ball and broke the entire site; so I restored my code into a new location, using a copy I sent to my adviser a couple of days ago. Opened up the project in VS2010, built it without any problems and tested successfully it using the built-in server in Visual Studio. I published it to wwwroot and tested it there as well, and all was good.
But now I can't get to the ASP.NET config tool; I get the dreaded error,
"An error was encountered. Please return to the previous page and try again. "
And certainly I have all the membership/role tables populated. The log-in feature works superficially, because if I submit a bad name or password, it fails. Therefore we know that the system is talking to the database all right.
What could be wrong? It is true that I'm running the old code in a new location, but so what? If that were a problem I wouldn't expect the login to work at all.
Comment