Reply

bgarnier Posted: Fri, Apr 18 2008 4:57 PM

rated by 0 users

 Hi,

I'm testing out CS 2008 locally. Any time that I try to browse to the control panel I get a very non descriptive timeout error. Any help here would be appreciated, I don't have much to go on right now.  Thanks!

 Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Request timed out.

Source Error:

[HttpException (0x80004005): Request timed out.]

Server Error in '/cs' Application.

---

Request timed out.

Reply

Ben Tiedt replied on Fri, Apr 18 2008 5:21 PM

rated by 0 users

It could be a timeout attempting to retrieve the URL fo the announcements feed for the control panel sidebar.

Try

1.  Open your communityserver.config file and set announcementRssUrl="" (blank out the URL)

2.  Restart you web site

Does this resolve the issue with access the control panel?

Reply

bgarnier replied on Fri, Apr 18 2008 6:24 PM

rated by 0 users

That worked like a charm, thanks!

Reply

njsmk replied on Fri, Apr 25 2008 5:35 AM

rated by 0 users

Ben Tiedt:

1.  Open your communityserver.config file and set announcementRssUrl="" (blank out the URL)

Thanks for this tip. Every time I tried to access control panel on a new install of CS 2008, the application pool was shutting down. No .NET errors shown in the browser, just Service Unavailable. Event log was reading Application pool is being automatically disabled due to a series of failures in the process(es) serving that application pool. I though the pool was corrupt, but recreating a couple of times did nothing. Removing the announcementRssUrl did the trick.

Any ideas how we can re-enable the announcements and not have this issue?

Reply

Ben Tiedt replied on Fri, Apr 25 2008 8:18 AM

rated by 0 users

njsmk:

Any ideas how we can re-enable the announcements and not have this issue?

If your announcementRssUrl was not set to "http://dev.communityserver.com/blogs/announcements/rss.aspx", could you update it to this URL?

Other than that, I'm not sure why it would cause either of the errors identified on this thread (even in Medium trust without a web proxy).