Connection To SharePoint Site Times Out
Hello All,I have medium sized farm with 3 loadbalanced WFE running on Windows NLB. I noticed a month later that connection to the SharePoint site times out with a Host Not Found from ISA. Ins ome cases, I get the error - An unexpected error has occurred. Troubleshoot issues with Windows SharePoint Services.However, I still have access to someother unclustered sites without the NLB.Also, I heard the network infrastructure was upgraded lately . . . last week.Please any help towards solving this will be appreciated.Ifeatu
February 9th, 2010 12:58pm

1) What are the errors you found previosly 2) Do you have specific exceptions in EventLog and 12Hive folder?! 3) Did you profile you application for the performance?!SharePoint 2007 - 2010 Tips & Tricks Portal | Microsoft MVP | My Blog about Information Management | My twitter
Free Windows Admin Tool Kit Click here and download it now
February 9th, 2010 1:09pm

Thanks Mike,I checked event logs and there was no issues. I cannot remember having any issues yet. How do I Profile the Application for Performance please? However, I am still looking at the Network Infrastructure - the NLB. I can browse the site normally on the Application Server that was first installed. One of the WFE shows up fine but another WFE, just like other clients on the network is not showing up fine - it times out.Also note that an attempt to open the website with SharePoint Designer throws an error:"The Server Unexpectedly Closed the Connection"Thanks once more.
February 9th, 2010 1:36pm

For performance monitoring I'd recommend to use Idera SharePoint Performance Monitor http://www.idera.com/Products/Free-Tools/SharePoint-perf-monitor/ Before going to NLB investigation, I recommend to use SPTraceViewer to monitor the 12hive logs any related exceptions. Any errors on database?! The reason I'm suggesting this is to nail down the areas that gives you a timeout - either IIS, or DB What relates to NLB I'd recommend to turn off each of the nodes one by one and test request against the remaining servers to understand which node cause you a troubles. Then after you find the WFE with timeout I would check the IIS logs (http://www.iis.net/downloads/default.aspx?tabid=34&g=6&i=1864) and tried to match them with the EvenLog and 12Hive logs with by time. SharePoint 2007 - 2010 Tips & Tricks Portal | Microsoft MVP | My Blog about Information Management | My twitter
Free Windows Admin Tool Kit Click here and download it now
February 10th, 2010 12:04pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics