• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1457
  • Last Modified:

Timeout Error when "Customize Home Page" in Sharepoint

Hello everyone.  
Every so often in our WSS 2.0 environment, we get a situation where we are unable to "customize home page" from site settings.  After awhile of clocking, we get the following (partial) error displayed...

Server Error in '/' Application.
--------------------------------------------------------------------------------
Request timed out.
[HttpException (0x80004005): Request timed out.]
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2379; ASP.NET Version:1.1.4322.2379

When we try to open the site's default.aspx page to modify it in FrontPage, we get "Error Message: The server could not complete your request.  Contact your ISP or Web server administator to make sure the server has the FrontPage server extensions or Sharepoint Services installed.  Details say "Object Moved.  Object moved to here.

All other sites on this server we can customize using Sharepoint or open in FrontPage 2003 for editing.  It is somewhat random as to when it occurs, has occured on several different sites, and we end up just restoring from a previoius backup.

Has anyone seen this problem before and have a fix?  Is there a better way to recover from this besides restoring from a previous backup?  Thanks for the help.
0
jbenjamin
Asked:
jbenjamin
3 Solutions
 
Robbie_LeggettCommented:
Try opening the page in IE with the following extension:
http://server/site/default.aspx?contents=1 

Using this, a page is opened on which you can see which webparts are shown.
If a webpart is not behaving correctly (mostly it states 'error') you can
disable/reset/remove this webpart. After this you can open the site in
frontpage again.


0
 
jbenjaminAuthor Commented:
Thanks.  I tried that (http://connections/issite/default.aspx?contents=1) and just received a generic Sharepoint Error:  Request Timed Out message.  Not the same as before, but didn't allow me to see the webparts on the page (or anything for that matter).
0
 
Robbie_LeggettCommented:
Can you post the exact error please?

:-)
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
jbenjaminAuthor Commented:
Sure...

Error
 
Request timed out.

Troubleshoot issues with Windows SharePoint Services.

0
 
Robbie_LeggettCommented:
Have you looked at this:

http://support.microsoft.com/kb/888418
0
 
jbenjaminAuthor Commented:
Thanks again for the response.  I had read through that last night and wasn't sure of the applicability, but will share with my more technical server contact and see what he thinks.
0
 
rcmbCommented:
Try changing the asp.net1 version to asp.net2 from asp tab in site properties.
0
 
jbenjaminAuthor Commented:
Thanks.  I don't administer that server ( I assume that is where I would see the site properties) in order to try that change.  Will try after the weekend sometime.  
0
 
jbenjaminAuthor Commented:
We updated to ASP.net version 2 last night on the server and are still getting the same timout error as before -- the difference is it references the newer version of ASP / .NET.

Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832

I assume now the Microsoft kb 888418 item referred to above does not apply as that is a fix for 1.1.  Should we have done that first?  Any other ideas?
0
 
Robbie_LeggettCommented:
You may need to register asp.net.

The utility is aspnet_regiis.exe, it is located under %WindowsDir%\Microsoft.NET\Framework\vx.y.zzzz\ and you should call it with the -i parameter: aspnet_regiis.exe -i
0
 
jbenjaminAuthor Commented:
Thanks.  We had already registered it.
0
 
Robbie_LeggettCommented:
Rather than restoring from backup, why don't you create a new site and migrate the content. Sometimes it's just easier.

:-)
0
 
jbenjaminAuthor Commented:
Still not sure what is going on, but will provide an update.  We copied the site into our QA environment (A VM server already on .NET 2.0 and should have same configuration as PRD.)  It still didn't allow me to Customize the Page in Sharepoint or open in FrontPage (different time out error in Sharepoint and a SOAP related error in FrontPage -- I didn't screen shot them so can't provide the details here).   I did try the "?contents=1" suggestion again and was able to now see the web parts and two of them were labeled as "Error".  I selected the two with errors and deleted them.  After confirming I wanted to continue with the delete, the page returned and indicated I didn't have ANY web parts on the page (HUH? -- there were over 10 and I just deleted the two).  I selected RESET which returned all the web parts in the list again and tried the delete again (thinking I must have missed something)...same result though.  With web parts gone, however, I could now customize the site in Sharepoint, so will just re-add the web parts back next week.
0
 
jbenjaminAuthor Commented:
Interesting development...found out this morning that in both our QA and PRD environments we lost the ability to add web parts to a page through Sharepoint (we could in FrontPage).  It appears (based on this link http://www.netnewsgroups.net/group/microsoft.public.dotnet.framework.aspnet/topic17452.aspx) that customized/unghosted pages do not work with .NET 2.0.  When we reinstalled .NET 1.1 back into QA we were again able to add webparts through Sharepoint as well as the "Customize the Site" (the original problem).
0
 
jbenjaminAuthor Commented:
Put the .NET 1.1 back into PRD, which allows webparts to be added through Sharepoint, but DID NOT fix original problem of "Customize the Site" time out error.  Have not been able to determine what else is different between both environments.  May try the patch mentioned above that was for use with 1.1.
0
 
jbenjaminAuthor Commented:
We already had newest release of 1.1 with patch applied, so that was no help.  When we migrated the site from the QA environment where it was working back to PRD, it took some time to refresh or something, but the site now allows Customize the Site from Sharepoint without the timeout error.  It's still a mystery to me, but thanks for all the good suggestions.
0
 
CarmenxoxoCommented:
STS 2003 /Application
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now