Hi, We have SharePoint web application. We are hosting it on Windows Sever 2008 along with SQL Server 2008. In the development environment the site works very smoothly. When we deployed the same on our live systems the web application because dead slow. It takes 20-30 mins to load a page and it never let anyone login from a Forms authenticated extention. The windows extention seems to be working fairly decent. I have no clue what is making the site go so slow. Thanks.--Oyshik

The server specs are : MOSS server: OS -> Windows server 2008 RAM -> 16 GB CPU -> P4 (4 in number) Exact same for the SQL 2008 server. the SharePoint LOG is appearing in GBs. And it is not consistent. I did the iisreset and when that did not help i restarted the server itself ...but still no clue. One observation... That authorization for the forms authenticated is not happening. I have a custome login page wherein I put custome logging statements. The code works perfectly fine and exits but the next page never loads up. My membership provider is not a trusted membership provider. Could that be an issue. I have no clue where to start looking. -thanks --Oyshik

Hi Oyshik, Are your database and sharepoint servers in different domains? Try making a reverse lookup entry in your database server for the sharepoint server. The most probable reason for slow rendering of the page, in this case, seems to be the sharepoint server continuously searching for the database server. Regards, Huzefa Mala.

Hi Huzefa, Thanks you for the reply. I tried doing a nslookup (both direction) and did not find any issues with that. And both the servers are in the same domain also. Actually, let me explain my problem in a more elaborated fashion. We have a web app which consists of 3 site collection. The web app is extended to 3 zones (default: Windows login , internet:Sql membership provider1 and intranet: Sql membership provider2) Now when I, log onto the app from the default zone, it is a little sluggish but I can live with that. The problem comes when I try and navigate it from the internet zone with a sql membership provider. When I try to login to the internet zone, it keeps me on the login page for 20-30 mins before aborting the process. I know that the session was validated because firstly, I had put custom logging statements that show that the entire code in the login page was executed. Secondly when I try and navigate to some other page (from the same browser session) after the login attempt was aborted, I start getting the logged in person name in the welcome.ascx part of the page. I have buried myself in tons of SharePoint logs trying to find out anything that makes sense. Thanks --Oyshik

Hi, I digged deeper .... nearly died doing so but I think I have my first clue at hand. As I had mentioned earlier the forms authentication extention is the problamatic extention so I searched in line of authentication. In one of the code piece there was a small line as follows: System.Web.Security.FormsAuthentication.SetAuthCookie(<UserName>, false); I commented out this line and tried working with the site and the site was working like a charm. Now that helped me from hyper- ventalating but now I am confused for the reasons why is it taking so much time for the app to set the auth cookie. Is there any specific setting that needs to be done for this to work? Thanks --Oyshik

Hi Oyshik, For setting the cookie you can do the following --> Internet Options of IE --> Privacy tab --> Click Advanced button --> Check override automatic cookie handling --> Check Always allow session cookies. This might help overcome the problem. But, this is something very browser-specific and it should have given the same problem in your test site. Try to use PerfMon and NetMon tools to monitor your network and system from the live server. Regards, Huzefa Mala.

Looking @ the hits I guess I should let everyone know of the solution. To dissapoint you all , I did not find one. We spent lot of money after the microsoft support who suggested that the problem was related to the role provider. We were using SQL membership provider to authenticate the users but we did not make use of the role provider. The Microsoft support told that if you do not mention the role provider corresponding to the entry made , the site response would be delayed. Well, after the microsoft guys handed over the system, just to make sure , I again removed the role related tags and still the application worked fine. I don't know anything more than this.--Oyshik