The specified request cannot be executed from current Application Pool

Does anyone know what this actually means and why I get it when I'm trying to look at someones My page or threads people might have written or replied to, or page 2 of friends lists, or page 2 of comments on My Page etc etc.?

It seems like it's the only answer there is to all Technical Problems on here, but why can't specified requests be executed?

Best wishes Chris

Click Here to see my photos

  • I'm not sure what it means but I constantly get it. I am having a lot of problems with this site at the moment with pages not loading up because it's so slow. It seems to take forever to log onto my own page and post comments. Website needs a good update I think.

  • I get it too - it is time someone sorted out all of these irritating technical problems.

  • Happened since I joined the forum over a year ago?

    Buzzard

    Nature Is Amazing - Let Us Keep It That Way

  • Hi Buzzard

    Buzzard said:

    Happened since I joined the forum over a year ago?

    Buzzard

    It almost sounds like you're suggesting that it's your fault, but I know you aren't. LOL

     

    Best wishes Chris

    Click Here to see my photos

  • Woodpecker said:

    Hi Buzzard

    Happened since I joined the forum over a year ago?

    Buzzard

    It almost sounds like you're suggesting that it's your fault, but I know you aren't. LOL

    [/quote]

    Well I get blamed for most things :-(

    Buzzard

    Nature Is Amazing - Let Us Keep It That Way

  • Hi all,

    It's not clear why this error is happening unfortunately. It does not happen all the time which makes it difficult to trace.

    Our priority is to get the community (and the rest of the website) off it's ailing hardware and onto a brand new infrastructure. This is going on as we speak but it is a mammoth task.

    I'm sorry to say that I don't think we can spend any time investigating this particular error because it would divert people from the hardware switchover (which is the ultimate solution to all of the problems we've been having).

    This is not the answer I want to give you but it is the reality. We really appreciate your patience in all of this.

    Best regards,

    Graham

     

    Got some feedback about our community? Let us know in the Feedback forum.

  • Hi Graham! 

    Thanks for the update! It's reassuring to know that the switchover is taking place! 

    Thanks to all of you working hard to make it happen! It's a job I don't envy one bit!

    "All weeds are flowers, once you get to know them" (Eeyore)

    My photos on Flickr

  • Hi Graham,

    Wonderful news that the switch over is taking place - it must be a nightmare for those involved.

    Thanks for the update. 

    Cheers, Linda.

    See my photos on Flickr

  • Hi Graham

    Thanks for the update.

    It's probably not what I wanted to hear, but maybe one day it will not appear when I try to click on someones My Page.

    Best wishes Chris

    Click Here to see my photos

  • I develop Web sites and have seen this message a few times. If it's the same error:

    Short version: an error has occurred when the Website was trying to tell you that an error has occurred.

    Long version: an error has occurred (database not accessible, poor connection / timeout, server too busy / doesn't want to play anymore, etc), the Website tries to fetch the custom error page, the page isn't accessible because it's on a different part of the server running in a different application pool (all Websites can have their own application pool), Web server throws a wobbly.

    If it is this error there are two suggested solutions:

    1. (After backing up the registry) add a new key to the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters. The key: DWORD, IgnoreAppPoolForCustomErrors, 1. The W3SVC service will have to be restarted via Services in Administrative Tools. 

    2. Use a separate error page in each application pool.

    Now, I bet you wish you'd never asked.

    Paul

    PS. Forgot to mention, when this problem is solved, you'll just see a different error page!!! But you might know why the error occurred, at least.

    Paul Weston