I am facing one issue. Deployed my application on IIS 7.5 with windows 2009 R2. My observation is when I request page for the first time, IIS takes lots of time to render (which is understood as it is initialising the application). While this is going on of another user tries to use the website, they are getting time out. How do I improve it? Needs help you guys.
Thanks in advance.
Cheers,
Kiran
For IIS 7.5 - on Windows Server 2008 R2, not 2009... - have a look at the Application Initialization Module. Or better, upgrade to IIS 8.5 on Windows Server 2012 R2 (if possible), where it's built in.
Related
I recently upgraded one of our application servers from Server 2008 R2 to Server 2012 R2. Everything seems to be working fine except for our little Intranet. When trying to get to it, you are immediately greeted with Error 503 Service is unavailable.
I did some troubleshooting but nothing has seemed to helped. I made sure the app pool associated with the website is running and double checked the identity. (It's using ApplicaionPoolIdentity). What else can I try? Thanks all!
It turns out the the application pool that our intranet runs from was set to use .NET CLR Version 1.1 instead of version 2.0. After switching to version 2.0 and recycling/refreshing the site, the intranet came right up. Thanks all!
Does anyone have an idea if it is possible to downgrade IIS version 7 to lower version of IIS on windows server 2008?
I have an ASP program on win 2000 server and I am planning to migrate this program on new setup on better hardware and software but I am getting HTTP 500 which in detail error logs I see complain of classic asp and IIS 7. In my case obviously the the ASP used (by another programmer) is and old classic ASP platform and now with this conflict I cannot get my web sever operating properly.
Any help/idea would be really appreciated.
Thanks,
Alan
I have an application already deployed on a couple of customers utilizing signalr for communication. It works on windows 2003 server with IIS 6.0 with the mappings configuration, also works on win 7 and iis express. But for windows 2008 R2 with IIS 7.5 the hubs file although it's served, the signalr.hub with the list of server methods is NOT included in the script therefore clients can't connect to the hub.
Help is appreciated!!!
Ok, so here is what I found. We have a setup project that installs our product. I haven't looked into the process in detail but what it does is: creates a website under iis default, then assigns an app-pool that runs with Frw 4.0 and I think it also registers the framework at some point of the process. So, for some reason the javascript hub file was being generated without the actual definition of the hub. After so many teaks I decided to remove the website from iis and added it back manually and it got fixed. So, I don't know what setting was impeding signalr to initiate the hub but that was how I solved it.
Thanks
Also, if an application works on IIS 7, would it be cool on the new version (if there is any)?
Err...even Microsoft's marketing material(dead link) is confusing! (says both IIS 7.0 and 7.5). However, I believe that Windows Server 2008 Web comes with IIS 7.0 and Windows Server 2008 R2 Web comes with IIS 7.5 FYI.
And yes, if you have an app working on IIS 7, it will work fine on IIS 7.5.
Edit: Appears Microsoft has update their site since this was posted, leaving link up for anyone looking for information on Server and Server R2.
http://www.microsoft.com/windowsserver2008/en/us/product-information.aspx
IIS version 7.5.
My guess is if Microsoft doesn't suck, an app working in 7.0 should be fine on a newer subversion, there should be no core changes. Then again, it is Microsoft, so I can't say that for certain.
I have a few ASP pages. One of them is using Server.Transfer to load another ASP page. But the page does not get called. If I change it to Response.Redirect, it is working fine. Can anyone help me?
By the way, it is working fine on IIS 6 on Windows Server 2003. It only has problem when I moved to IIS 7 on Windows Server 2008.
Thanks
transfer can only support within same domain...
Try changing your code from Server.Transfer to Server.TransferRequest.
I have found this works for IIS 7 applications running in Integrated Mode.