ASP.Net site timing out

[alex_read]

Hi Everyone!!!

I've got an asp.net site which runs from IIS 5. On 4 customers sites, this site runs ok. On our main customers site, one of the pages takes a little while to process a request & times out - giving the user a "The page cannot be displayed" error message.

In the web.config file, and any timeout settings in IIS I can find, I've tried to set the timeout to an hour (a bit excessive, but I'm testing at the mo). These are the settings I've put in the web.config file:

<authentication mode="Forms">
	<forms name=".AFormName" loginUrl="WebPageName.aspx" 
protection="All" timeout="60" path="/" slidingExpiration="true" />
</authentication>

<httpRuntime executionTimeout="3600" />

<sessionState 
        mode="InProc"
        cookieless="false" 
        timeout="600" 
/>

In IIS, I've put these settings:

Web Site tab > Unlimited connections with a timeout of 3600 seconds.
Home directory tab > Configuration button > App options tab the session state reads 60 minutes and the timeout again 3600 seconds.

Is there another setting I've missed or another cause to this problem please?
Thanks,
Alex

[Mike Hildner]

What are the operating systems where it works ok and does not work ok? Wondering if this has anything to do with max connections in a non-server OS?

[alex_read]

Hi Mike, thanks for the reply!

All of the test sites are running either windows 2000 or windows xp client platforms (not server versions).

What do you mean with the max connections part exactly please?e

[Mike Hildner]

To be honest, I don't know a whole lot about it - I'm quite new to ASP stuff. But the other day, I was running my app and got some error about maximum number of connections has been reached. Of course I have one browser instance running this app, so I thought it was a little strange. Anyway, from what I've read, you can get this error when you're not running a server OS, although it can take a while to get the error.

Apparently it's something Microsoft has built in as non-server OS's are meant to be for development and not deployment.

Not even sure if this is your same error, wish I know more about it.

[alex_read]

Ok thanks, it looks as if that may be going down a different path as I think I may have got a different error screen but I'll check it out nonetheless.

Thanks for the suggestion

[update]Nope, looks as though that one's a different issue.

[Mike Hildner]

Sorry to lead you astray, like I said, I don't know much about this. I have managed to create some errors, though, imagine that.

When you say in your original post "one of the pages takes a little while to process a request" - are you uploading a file or anything? I have seen where a large upload (> 4 or 8 MB) will bring you to the "page not found". If so, that's a default setting and can be modified, somewhat.

Of course, I may be well off the mark.

[alex_read]

Now that one was a decent suggestion! just off again, I should've put - the page calls a script written in omnimark to transform an MsWord file into an XML file - depending upon the file size this can take a little while.

Unfortunately nope, it's not uploading files this page (though I did have to battle that one earlier)