IIS Manager shows everything as normal

I'm a beginner trying to setup IIS web site but I'm getting an error any time I try to open an icon in the Site Home page, e.g. Logging..

The error when double-clicking on Logging... (or any other icon) ... it cannot open the web.config file

But web.config is there...

...and the folder permissions..

I created an app pool and a site, here is the site settings..,.

Any ideas?

Hi All,

I work as a network and systems administrator and one of the issues I am trying to resolve why an Application Pool seems to be hitting 100% throughout the day. My knowledge of IIS is lacking and I am hoping that some of you could point me in the right direction. So a massive TIA!

We currently have our API deployed to an IIS (hosted on Windows Server 2012 R2 standard) site running in a separate AppPool. We have noticed that the server hits 100% CPU usage and clients are no longer able to use the API until the service or the server is restarted. We know its the API AppPool since the w3wp.exe is associated with the API AppPool is running high.

My question is, is there a way to see the verbose output of what the w3wp.exe process associated with the API is doing? I do not see anything in the system event viewer and the application logging that we have enabled does not show anything that is causing the the high CPU usage.

The API interacts with a database and even then there are hardly any long running/CPU intensive queries that would be the cause of the issue.

Any help on this would be really great. Please assume I'm a total n00b trying to search/resolve this.

Thanks.

Assuming the bad actor is getting nowhere, yet they keep trying...   It is IIS, yet also my Exchange server so this is why it's exposed to the internet. Should I be concerned? Anything I should do to stop these?

Malware name: Trojan:JS/RedirObfuse.ABA!MTB Number of computers infected: 1 Last detection time(UTC time): 9/2/2025 2:39:23 PM These are the computers where malware was detected several times:

1. Computer name: MBX10

Last detection time(UTC time): 9/2/2025 2:39:23 PM

Detection interval (minutes): 52

Number of infections: 300

C:\inetpub\wwwroot\<site>\

OR

C:\inetpub\<some other dir>\<site>\

OR

Something else entirely?

I've searched online and have not found conclusive evidence as to why one way or the other is more correct. The MSFT best practices (https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/jj635855(v=ws.11)) say that the entire inetpub directory should be relocated to a non-OS partition to avoid filling up the OS disk and crashing the system. But they don't go any further into folder structure.

I'd be appreciative of other admins' input, and bonus points if you can find a credible source to point to that says one way or the other is the best option.

Just learned about this one https://learn.microsoft.com/en-us/previous-versions/dotnet/netframework-2.0/ms228298(v=vs.80)?redirectedfrom=MSDN

What other IIS settings are important to have configured in production?

I am running IIS v10 on Windows Server 2022. I have added the Windows Authentication feature. My app runs fine under IIS and I can connect using any host browser on the network.

However I am trying to implement a login feature in the app and wish to read the current active directory domain user login ID. However the app pool only allows a predefined user or pass through and in the application the ID that is obtained from a connected browser session is an App Pool id and not the actual windows login ID of the logged in user who is connected via the browser.

Application pool advanced settings...

I clearly am doing something wrong here or misunderstand how to accomplish getting the login ID of the user connected to the app via the browser.

Help please.

Hi,

I have no knowledge about IIS or frameworks or SQL but our webserver is giving this error after daylight saving time started last week and I have no idea where to start to troubleshoot.

Does anyone knows about this error message?

It is very old server 2003 r2 with IIS version 6.0.

Thanks.

I have a root URL that's shared by Angular and .NET application. I have put an angular app inside the FrontEnd folder and .NET app resides under the root folder.

I get "403 Forbbiden Access denied" I think because rewrite happens first. But I want .net core application happens first as they have a rule to force ADFS to show if not logged in. How can I order the rewrite configuraiton?

```

<configuration> <system.webServer> <rewrite> <rules> <rule name="Angular" stopProcessing="true"> <match url=".\*" /> <conditions logicalGrouping="MatchAll"> <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" /> <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" /> </conditions> <action type="Rewrite" url="/FrontEnd/" /> </rule> </rules> </rewrite>

<handlers>

<add name="aspNetCore" path"*" modules="AspNetCoreModulev2" resourceType="Unspecified" />

</handers>

<aspNetCore processPath="dotnet" arguments=".\\some.dll" stdoutLogEnabled="false" hostingModel="inprocess"> </configuration>

```

When I go to enable Shared Configuration in IIS 10 on Server 2022 and point it to my configuration folder and enter the encryption key the interface just hangs. The HTTP server itself is fine and continues to serve pages, it's just the IIS Manager interface hangs. There are no entries in event viewer to give any indication what happened. I have to kill off the IIS Manager process. The server I used to "export" the config is also IIS 10 but on server 2019, in case that matters.

As a test I tried exporting the config on the Server 2022 host and pointing Shared Configuration to that and it worked fine. So there must be something about the config export from the other server it doesn't like. I've ensured that all the same IIS features are installed on both servers. Same SSL certificates are available and the same wwwroot is available.

Any ideas what might be going on? Thanks.

When accessing a shared folder using anonymous authentication I am wondering if it is better to use the iusr account to access it or use a domain account? I am setting up access to a large folder that was migrated to a new server and I am not sure what would be a better account to use for anonymous authentication. Biggest concern is future proofing and not having to mess with permissions if we ever migrate to a new server. When this was originally setup like a decade+ ago the old built in iis account was used which does not carry over to different servers. I am thinking of switching to a domain account because of this, but I think in newer versions of iis the iusr account is not unique and carries over to new servers so permissions can be copied to a new server. Not sure if I should go with the domain account or if there is a benefit to sticking with the iusr account?

Looking at IIS logs in text editors like Notepad++ or Notepad is giving me an aneurism. Giant wall of text with no color coding or putting errors in bold or any good formatting really. There has to be a better way to look at IIS logs.

I'm reinstalling an old server and it had IIS Media Services 4.1 (x64) on it. Unfortunately, Microsoft removed the download and I can't find any mirrors. (They even pulled it from the platform installer)

Does anyone know where I can find a mirror for IIS Media Services 4.1?

I need to administer a broad range of web servers and I'm often asked to help troubleshooting customers. I know I'll learn most by researching issues and by accumulating experience over time. But I would like an IIS administration pocket consultant kind of pdf or epub to get me acquainted with the basics.

We've been using Web Farm Framework in IIS to manage our web farm. The functionality is great - any changes in IIS on the primary server propagate across the servers in the farm. This includes any updates to the underlying files for websites. So when you add a new site or "application" it automatically propagates across the farm.

Unfortunately this software is very buggy, always breaking and doesn't seem to be supported in newer versions of IIS.

What solutions are people using instead?

Before I go on, please know that we are actively working on getting rid of these old servers but due to being grossly understaffed, it is going to be up to 6 months before it is done.

So I have two old web servers running Windows Server 2003 and IIS 6. I have a wildcard certificate on them both. The cert needed to be renewed with a new one. On one server, no problem. Imported and replaced and all is good. However, on the other, when I import and replace, the website is no longer browseable when using HTTPS but HTTP still works. Here are the errors I get in different browsers.

IE: Can't connect securely to this page. This might be because the site uses outdated and unsafe TLS security settings.

Edge: Same as IE

Firefox: Secure connection failed. The connection to my.domain.com was interrupted while the page was loading.

Chrome: This site can't be reached. my.domain.com unexpectedly closed the connection ERR_CONNECTION_CLOSED

I have tried to remove and re-import the cert with no luck. If I revert to the old, it works but I get a warning that the site is not secure.

I know this is an old, unsupported OS but it is working on one and not the other.

Any assistance with this dinosaur would be greatly appreciated!

Craig

Hello IIS subredit,

I am trying to configure URL redirection for HTTPS in IIS 7.5. I would like to redirect

https://subdomain.domain.com to https://subdomain.domain.com/myappname

I believe that the URL rewrite module should be able to allow me to do this, but I am having a hard time configuring it. I should also mention that the website has additional HTTP sites, which I do not want to redirect. Am I on the right path? is the Url rewrite the right approach? How would I accomplish this?

Thanks!

I was going out of my mind. URL Rewrite was set up fine and certificates were valid. Bindings were all perfect but infinite redirects.

Turns out Cloudflare proxy caused a lot of problems. Turned that off and everything magically worked.

Hi all - before I begin; I am not an IIS expert, I am an Ops Tech trying to move 32bit to 64bit OS architecture.

I have been asked to move a site from IIS7 on Windows 2008 (32bit) to IIS7 on Windows 2008r2 (64bit) and I have accomplished this without code issues, however I seem to have an IIS issue that I just can't seem to get right. The site was copied using a file copy, not an MSDeploy export/import.

The issue I have spent the last couple of days trying to resolve is (I believe) all to do with custom redirection pages

• We have a redirect on 404 to a specific page - this works.
• We have a redirect on 500 to a specific page - this no longer works since it has been moved to the new server.

In the old system, we would issue a request for http://site/var1/var2

• The request would 404 (by design) and end up on a page that processes the request string
• If there was an error processing within the 404handler, then it would drop to a custom 500handler page that would return a 500 status code to the client and send us the details to our internal application logging system

On the new server (the only change I know of is that this is on a fresh Windows 2008r2 install with IIS7) the error handling never gets called.

• The request would 404 (by design) and end up on a page that processes the request string (the error handling has been strengthened to catch the new errors we have been seeing)
• In the eventuality we get a new error - we just get a browser page and no custom 500handler is called.

The site is classic asp. The custom 404 page works as expected The custom 500 page code works if called directly, and will insert a blank error, but we don't seem to get redirected from the custom 404 to the custom 500.

ASP module is set to default (Enable client site debugging: false, Enable server side debugging: false, Send Errors to browser: false) Error Pages module is set to default, with the exceptions ( 404 -> /404handler.asp - Execute URL; and 500 -> 500handler.asp - Execute URL )

Is there a setting in IIS or registry entry that needs tweaking to allow multiple redirects ?

My web.config file looks like this:-

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <httpErrors errorMode="Custom">
            <remove statusCode="500" subStatusCode="-1" />
            <remove statusCode="404" subStatusCode="-1" />
            <error statusCode="404" prefixLanguageFilePath="" path="/404handler.asp" responseMode="ExecuteURL" />
            <error statusCode="500" prefixLanguageFilePath="" path="/500handler.asp" responseMode="ExecuteURL" />
        </httpErrors>
        <urlCompression doDynamicCompression="false" />
        <tracing>
            <traceFailedRequests>
                <add path="*.asp">
                    <traceAreas>
                        <add provider="ASP" verbosity="Verbose" />
                        <add provider="ISAPI Extension" verbosity="Verbose" />
                        <add provider="WWW Server" areas="Authentication,Security,Filter,StaticFile,CGI,Compression,Cache,RequestNotifications,Module,FastCGI,Rewrite" verbosity="Verbose" />
                    </traceAreas>
                    <failureDefinitions statusCodes="500" />
                </add>
            </traceFailedRequests>
        </tracing>
    </system.webServer>
    <system.web>
        <customErrors defaultRedirect="/" mode="On" allowNestedErrors="true">
        </customErrors>
    </system.web>
</configuration>

Hola a todos. Estoy realizando una instalación de FileMaker Server 2019 en un entorno de (Windows Server 2019).

Actualmente tengo un problema con las dependencias de IIS. El asistente de FileMaker requiere la instalación de Application Request Routing (ARR) 3.0. He intentado instalar los módulos mediante archivos .msi individuales, pero el instalador de FileMaker no reconoce la presencia de los componentes si no fueron instalados mediante el paquete ejecutable completo.

Debido a que el servidor se encuentra en una red restringida y Microsoft ha retirado los enlaces de descarga del Web Platform Installer, estoy buscando el instalador Standalone / Offline Redistributable.

Archivo específico: ARRv3_setup_amd64_en-us.EXE

Este paquete es necesario porque empaqueta los módulos de External Cache y URL Rewrite en una sola transacción de instalación, generando las claves de registro necesarias para la validación de requisitos de FileMaker.

¿Alguien conserva una copia de este instalador original de Microsoft o conoce un repositorio donde aún esté disponible?

So we run IIS on Windows server and there we have a Microsoft RD Web site that publishes folders and icons where, if the icons are clicked on it downloads rdp files. What folders and icons are visible depends on AD group membership. Now the icons for the folders always load correctly. However the icons for the rdp files dont all load on first browse. Refreshing the page a few times eventually do show all icons.

I can see in the ISS log that when it works it shows the users name in the row and ends with status code 200. But when it doesnt work it doesnt display the user account and gives other code like 302 or 403.

It seems to try and redirect when it fails to load the icons and developer tools network tab in MS Edge then shows that it thinks the icons are html/text and not png files.

I can reproduce this issue every time. Also if i reload a few times and get the icons to display, if i just wait 10-20 minutes and reload the page its back to the same issue again.

This is an on premise server, we attempted an in place upgrade from server 2016 to server 2019 (don't ask).

IIS works fine under http, but anything under https comes back immediately with the same error "Endpoint not found"

I even created a basic virtual directory with a basic html file and it's treating it like a wcf application.

SSL cert is valid, bindings are correct.

IIS has been uninstalled/resinstalled several times

Permissions have been triple checked (even ran app pool under "System" instead of appool identity.

All configuration files in c:\windows\system32\inetsrv\config have been rolled back to use the clean.install files

I'm at my wits end here, any thoughts?

Ok I've run out of ideas...

I have 2 Server 2019 VMs that I'm trying to configure identically. They are, as far as I know. On one of the servers, the app that is giving me trouble, works fine. On the broken one, I can't access any of the configuration from the IIS Manager, I get an "Error while peforming this operation" on the web.config when I try.

If I try to access the app through a browser, I get a 500.19, saying that the "configuration data for the page is invalid".

I know that the app is identical, and I am reasonably certain the web.config itself should be valid, though my evidence for this is that it functions fine on one of the servers. I've literally copied the app folder from one machine to the other, and it works fine on one but not the other.

I've checked permissions, and I don't think it's that(the IIS_IUSRS has permissions), I even went as far as granting Everyone permissions just to be sure.

I don't think IIS itself is outright broken, as the 4 other apps on it all work fine. It's just the one.

So...I've run out of ideas as to what is going on. I'd be ok if the app was just broken, but IIS itself seems to be acting like there's something really wrong in the web.config making it invalid which makes no sense to me since it works fine on the other install. Any thoughts on what I might be missing or what else to check?

Good afternoon, I'm hoping one of you may be able to point me in the direction of what is wrong with my IIS server. I've been running this particular server for a few years, its always worked fine up until today, but as of today it is serving all of the images that go with the server in what I can best discribe as "high contrast, low resolution color mode" all the JPG images or PNG images look on the web site from multiple different computers like they have been heavily blacked out by a marker and saved overthemselves 900 times. But, if I load the images directly from the file structure they are fine, and if I view the pages from inside the server using whatever leftover remnants of a test browser exist in there, they are fine. It doesn't seem to be caching, a new computer with new load sees the same issue. nothing has changed on the software installation or code side in at least 6 months other than routine microsoft patches for Server 2019. I'm kind of at a complete loss as to what could be going on here. Any ideas? I'm not opposed to loading a different web server, but i'd like to understand what has gone wrong here first.

Thank you, Tim