application-pool

In IIS (6.0 specifically), under the Home Directory tab, if I change the local path, will this cause either IIS to restart or the application pool to recycle? Related, is there a reference that outlines which changes to the IIS metabase will trigger either a restart or app pool recycle? I haven't been able to find this yet. Changing the path to a website in the Home Directory path won't cause the worker process to restart. It will however cause the Application Domain for the website to tear down and restart. Worker process restarts can be caused by a number of events, most commonly: If any of

For IIS 7, Help for Recycling Conditions for Application Pool says that Private Memory Usage is ...privately allocated system physical memory ... (The property is named Maximum Used Memory in IIS 6.) And, Event Log entry when application pool recycles; "A worker process with process id of '4824' serving application pool '(thepool)' has requested a recycle because it reached its private bytes memory limit ." Thus, if its private bytes then it must be the committed memory which physical memory + page file . But, help says its physical memory(in that case property must be named private working

I would like to write a script and run it from my local PC to stop and start an application pool and site that exists on a server. Value of App Pool and Site - Test Value of server - SERVER1 Any guidance would be much appreciated. Daniel Minnaar Run Command Prompt with Administrative rights, and type the following: C:\Windows\System32\inetsrv\appcmd start apppool /apppool.name:"MYAPPPOOLNAME" or use the stop command. You could save this in a batch file, but it must be executed with higher privileges. For the application pool on a remote server, you could use PsExec : Psexec \\{Computer Name of

The Problem: When new IIS Application Pools are created and set to use the Application Pool Identity for permissions, I am unsure how to add those identities to User Groups such as Administrator or Performance Counter Users. The Background: I'm currently writing a C#.NET library which uses Microsoft.Web.Administration in order to do the following: Detect if IIS 7.x is installed, and if so, what components. Install or upgrade IIS 7.x to a provided list of required components. Create/manage one or more web sites through IIS. Automatically create/manage one application pool per web site The

I have a very simple web application (asp.net MVC3, .net 4, using IIS not Visual Studio's embedded server, 64-bit Windows 7). When I change the settings in the application pool for my application and set 'Enable 32-Bit Applications' to False, my application's view shows up, but none of the static content (Content/Site.css or Scripts/myScript.js) shows up. Instead, I get status code 500 on those requests. HTTP Error 500.0 - Internal Server Error The page cannot be displayed because an internal server error has occurred. The reason I'm changing this value is that I'm trying to use the 64-bit

Thanks for viewing: Hopefully this not only helps others later, but helps us now! (and please be gentle, this my first Question on Stack though I've been a long time user/contributor) Situation (SNAFU) An AD Site aware application is pulling some information out of AD. This application must only connect to controllers within the Active Directory site the server is hosted; if no controllers are found for that site, we have bigger issues but code will handle that possibility. To accomplish this we intend to: Get the site name in which the server hosting the web application resides. Utilize that

I have a number of ASP.NET (4.0) web applications that appear to leak (a small amount) of memory during each request. It is such a small amount, that for most use-cases, it will not grow to become a problem for weeks or even months at a time. I generally try to be good with closing any connections managed by the application, avoiding state-variables (or instance variables for my singleton), etc. My question is this - is this normal behavior for ASP.NET applications? I had turned off the default (IIS 7) behavior of recycling the app pool after 20 minutes of being idle. I do this since the

I need to know how I can detect the current application pool I am running under, so I can do a Recycle on it programmatically. Does anyone know how to do this for IIS6? My current code for recycling the app-pool is: /// <summary> /// Recycle an application pool /// </summary> /// <param name="IIsApplicationPool"></param> public static void RecycleAppPool(string IIsApplicationPool) { ManagementScope scope = new ManagementScope(@"\\localhost\root\MicrosoftIISv2"); scope.Connect(); ManagementObject appPool = new ManagementObject(scope, new ManagementPath("IIsApplicationPool.Name='W3SVC/AppPools/"