Home » Community » Developer Space » Community Server 2008 » Site Reliability Issues; w3wp.exe crashing?

Site Reliability Issues; w3wp.exe crashing?

Open Support Ticket

Call Support:
Direct: (214) 420-1337
Toll Free: (877) 522-6334

Monday through Friday
8 a.m. to 6 p.m. Central (GMT-6)

Join our Community
Details
  • 5 Replies
  • 0 Subscribers
  • Posted6 months ago
Options

Site Reliability Issues; w3wp.exe crashing?

  • newtrackmedia
    Posted by
    on Thu, Nov 8 2012 8:11 PM

    Thanks all, in advance for your help.  While familiar with the ways of the web I am no developer and am humbly reaching out for your help.

    We're facing a serious up-time issue with a couple of 2008.5 installs; occasionally connections will slow to a crawl and cause the site to, more or less, shut down.  Rebooting the servers (database and site are on separate machines) will bring us back online but in only a few days we're back to crawling/restarting again.

    Our community moderators and members are understandably upset and ready to migrate elsewhere.  I've explored a change in hosting solutions but don't see any indication through usage reports that the machines or network are the issue.

    Our hosting provider recently reported that a crash of w3wp.exe caused the most recent outage—I'm waiting to hear back on a history of this app crashing and any cause, but at this point (and by this dialog, stackoverflow.com/.../common-asp-net-intermittent-hang-ups, which fits our symptoms) it's the most likely lead I've found.

    I've reached out to Telligent support who pointed me toward these developer forums for assistance.

    • Has anyone else seen similar issues with CS2008.5 or can confirm w3wp.exe is where we need to look for an explanation?

    • Are any developers who have addressed this issue available to help?
  • Rob Howard
    Posted by
    on Thu, Nov 8 2012 8:45 PM

    First of all, that is an old, old version of our software!

    More importantly, you still shouldn't see this type of instability.  What I would recommend looking at is that memory limits your application pool is using.  It is very likely that the ASP.NET cache is attempting to use more memory than is available and without a memory limit this can cause some very odd problems.  You need a memory limit to ensure the ASP.NET cache knows when to stop consuming memory ... otherwise it will behave as a memory leak.
  • Justin Couto
    Posted by
    on Thu, Nov 8 2012 8:46 PM

    It sounds like you need to look at how the application pool is doing.  You might need to set a limit on the amount of memory it will use and force it to recycle when that limit is hit.

    Good Luck,

  • Adam Seabridge
    Posted by
    on Thu, Nov 8 2012 8:52 PM

    I would agree with Justin and Rob. Usually these kind of issues are down to incorrect configuration or poor maintenance.

    You can find info on app pool settings here:

    telligent.com/.../4088.aspx

    it is for a newer version of the product but the advice holds true for CS2008.5 as far as I know.

    I would also go through he whole check-list here to ensure you have everything set-up as recommended:

    telligent.com/.../tuning-and-performance.aspx

    hope this helps.
  • newtrackmedia
    Posted by
    on Fri, Nov 9 2012 1:59 AM

    Rob, Justin,

     Thanks for your recommendation to look at the memory allocations.

    Adam,

     Thanks for your support of Rob and Justin's replies and providing these links.

     It looks like I've got my work cut out for the night but can't thank you enough for pointing me in the right direction!
  • wijaya25
    Posted by
    on Wed, Jan 16 2013 11:40 PM

    Whent w3wp exe crashing problems you should act quickly to locate the right solution and stop this annoying trouble. Messing with a windows registry by yourself is quite complicated and risky, so you have two choices: 1) hire a professional (very pricey); or 2) use a special registry cleaner. The latest in registry fixing programs from reliable developers has the power to automatically restore your registry to its optimal state. I suggest that you download and install a registry repair tool and see what a free scan does for your computer; i am confident you will find that this annoying problem and many others like it will be a thing of the past in no time - you're on your way to error-free computing!

    ---