Login Issues
We are using 2.0.5 and are having a login issue. On the Main.aspx page, we enter our forms based user login and the page tries to repost but reaches its time out and get the "Internet Explorer could not display the Web Page" error page.
If at any time after clicking the login button (or clicking back after getting the error page), I click on the Home link (upper left corner), I am given the Main.aspx page as if I am fully logged in (it even says Logout "User" in upper right.
What could be causing the page not to reload properly?
Any help would be greatly appreciated!
Thanks-
|
ADP1
· 1 |
|
| Friday, November 17, 2006, 3:46:09 PM | |
0
|
Is this an upgrade? If so please make sure you are using the new web.config file. Please check the error log table. |
||||
|
|||||
0
|
This is an initial install. There are no error records in the errorlog table. |
||||
|
|||||
0
|
What is the spec of your server + SQL? Does this happen all the time? |
||||
|
|||||
0
|
Server is Win2K3 .NET 2.0 and SQL 2005. I do not have a SQL 2000 installation. Yes, it occurs every time on login. As I mentioned, in the background, the user actually gets 'logged in', but the page will not post back properly.
|
||||
|
|||||
0
|
Try putting Gemini in its own application pool with 1 worker process (IIS settings). |
||||
|
|||||
0
|
Gemini uses it's own Application Pool (Gemini) and the Worker Process is set to 'Recycle worker process at the following time (06:00). Nothing else is checked on the Recycling tab of the Application Pool. Same results when login attempt.
|
||||
|
|||||
0
|
Is it only the login page that gives you this behavior? |
||||
|
|||||
0
|
I get something similar on the 'User Security' Screen of the Admin user. The first time I click on it it takes a long tome but if I go to another page and then click back on 'User Security' it loads with no problem. All other screens appear normal. |
||||
|
|||||
0
|
Do you run with SQL 2005 express? |
||||
|
|||||
0
|
SQL Server 2005 Standard Edition |
||||
|
|||||
0
|
Sorry, but we have run out of ideas! The only other thing to suggest is a new install and try to run with .NET 1.1. |
||||
|
|||||




