Is there a way to set the processorThreadMax configration in IIS7.5 at a per website level? I can set the value for all of IIS, but when I look at the value in the website's ASP.NET settings, it's grayed out.
Related
I have an ASP.net Web Site project in IIS 8.5.96. In the web config on the server is this:
<system.web>
<sessionState timeout="12000" />
On one domain - (it's used for a simple login) it works fine - the session lasts for days.
(note, it's a legacy site, I know using session for login isn't ideal but we need this site to work as is).
We just pointed a different domain at this exact same website folder. Nothing else was changed.
Now the user is logged out after 20 minutes.
Shouldn't the new site take the figure from the web.config? If I check IIS (ASP.NET / Session State / Cookie Settings / Time-out) - that is 12000 under the new site - as specified in the web config (I presume that is the same setting?).
I've found some links, eg:
How do you change session timeout in IIS 8.5?
This suggests changing various settings in IIS - but this was never required before. I'd rather change these things in the web.config.
How can I get the session to last as long as it used to and take the web.config setting?
And why would pointing a different domain at the same site cause this?
I am trying to follow some instructions for an IIS setup which says:
Double click Server node in IIS (not web site node). Ensure ISAPI and
CGI Restrictions property setting for ASP.NET 2.0 and 4.0 is set to
‘Allowed’
After spending some time finally I was able to find ISPAI and CGI Restrictions. But I cannot find the place to set something to Allowed on it per instructions.
Should I enable something else first before it shows up?
This is how far I got:
In order to be able to update certain files on an IIS ASP.NET website like .aspx files, you need to publish it with the "Allow precompiled site to be updatable" option selected in the advanced precompile settings dialog in Visual Studio. However, what about after the site has been published? Where is this setting stored? What if I published a website with that setting off, but I want to enable it? Do I have to republish the whole site? In any case, where is that setting stored?
That setting is not stored anywhere, and after pre-compilation it is lost. If you published a site with that setting off, you will have to republish so as to have it on.
Windows 7 Ultimate
IIS7
At first I enabled all settings in IIS, the default page of IIS could be viewed but when I tried to view pages in C:\inetpub\wwwroot\MyWeb, I used to get a 404 error.
Then I tried:
ASP
ISAPI extensions
Request filtering
It didn't show me the default IIS page even. Then I tried:
ASP
ASP.NET
ISAPI Extensions
Default document
Static content
Request filtering
It showed me the default page but when I tried to view files in the directory, Chrome said that the link appears to be broken. At present my settings are:
IIS management console
.net extensibility
asp
asp.net
cgi
isapi extensions
isapi filters
server-side includes
default document
static content
request filtering
Still, I am getting the "link broken" message.
Oh, and I am using Dreamweaver CS5 and when I preview the ASP page from Dreamweaver it asks me if I would like to specify a testing server. I choose No as I am new to this and not aware of how to specify a server. Is that the problem?
This is the official site for your problem:
http://www.iis.net/learn/application-frameworks/running-classic-asp-applications-on-iis-7-and-iis-8
The first entry is probably what you need.
I recently set up ASP on IIS8 by simply installing the server features you listed first (ASP and ISAPI Extensions). Maybe you have another problem, like a wrongly setup website in IIS. You could enter a simple default.asp or maybe you should try a iisreset and check that some static file is available where you expect the asp files to work.
I am having a problem setting up a website under IIS 7. I have created an application and the application pool for the application. Application pool is using .Net Framework 4.0 as my .net app is written in .Net Framework 4.0. Application pool is set to use classic Pipeline Mode. MIME Types have been automatically added to .asp & .aspx.
When I run the website windows explorer is showing me "View Downloads" and trying to download "application name localhost" when it downloads the file I notice that its the html of my default.aspx. I have checked Default Document and it contains Default.aspx.
If I remove .asp & .aspx MIME Types then I get an error: HTTP Error 404.17 - Not Found The requested content appears to be script and will not be served by the static file handler.
I have seen this problem many times. IIS is not serving aspx pages and most likely is not running for the entire server or that site.
For the entire server: Check to see if iis world wide web service is running.
For the site alone: Hit run inside IIS.
You can easily know if IIS is running properly by going to IIS and hit the browse option from inside a web site.
With the data you have put these are the things I would try in order if I were you:
Check in Server Manager/ Features if ASP.NET is installed (ServerManager/Roles/Web Server(IIS) look for ASP.NET
Check IIS Manager if everything is ok by:
Try to browse a test.html file to see if you are able to browse normal
Check Basic settings by clicking Test Settings
Check Handler Mappings to see if aspx is there.
Try to browse a sample test.aspx page with test data.
Check Application pool settings.
Reinstall Framework 4.0
Reboot machine ( a classical)
If you gave us more info and/or the ouput of my proposed tests maybe can help more. Good Luck :)
I had the 404.17 error happening on a server today. As you and cad mentioned, I checked the framework of the Application Pool that my site was using to make sure it was set to ASP.Net 4.0, and it was. What happened in my case is that my site was not using the application pool that I thought it was. My site was nested under another site, meaning my site pointed to a subfolder but another site was pointing to the root folder. Even though I had my site set to use the ASP.Net 4.0 Application Pool, the root site used a different Pool that had ASP.Net turned off, it was set to "No managed code". When I set the framework to 4.0 for the Pool the parent site was using, then my site started working.
In my case the solution was fixing the Handler mappings as explained here: http://forums.iis.net/post/1943489.aspx
IIS Manager->high-light you web site->click Handler Mappings icon on
the home pane->click Revert to Parent...
on the right Actions pane