iis disable debug

In IIS to disable debug do the following.

Modify the Web.config File Open the Web.config file in a text editor such as Notepad.exe. Web.config file is typically located in the application directory.

Modify the compilation element and set debug=”false”

<compilation debug=”false” />

Save the Web.config file. The ASP.NET application automatically restarts.

Modify the Machine.config file . . . → Read More: iis disable debug

iis 7.5 The format of the specified network name is invalid – IIS Error 0x800704BE

Problem IIS 7.5 is holding on to an IP and you cannot get it to listen to the right IP.

You might see this error message:

The format of the specified network name is invalid – IIS Error 0x800704BE Solution

You will need to remove and add the listening ip via netsh (see below)

Determine . . . → Read More: iis 7.5 The format of the specified network name is invalid – IIS Error 0x800704BE

IIS 6.0 Redirect HTTP to HTTPS javascript

To redirect in IIS 6.0 using pure javascript create a file called “redirect.htm” and have IIS6 listen on port 80 and redirect to that file:

function redirectToHttps() { var httpURL = window.location.hostname+window.location.pathname; var httpsURL = “https://” + httpURL ; window.location = httpsURL ; } redirectToHttps(); . . . → Read More: IIS 6.0 Redirect HTTP to HTTPS javascript

psexec icacls remote computer

Set proper permissions in IIS 7.x on a remote computer

We will be using psexec icacls on the remote comptuer

Objective: Grant NT AUTHORITY\NetworkService the proper permissions for a particular website on “somecomputer” using credentials “somedomain\someuser somepassword”

The Command to Run psexec -u somedomain\someuser -p somepassword -e \\somecomputer cmd /c (^ mkdir c:\temp1\Common ^ & . . . → Read More: psexec icacls remote computer

Trace ASP.NET Application

You’ll need to edit the web.config


Place the following after system.web tag:

Trace ASP.NET Application

Those options only allow you to see the trace from the server itself. RDP in to the server

Connect to:


Could not load file or assembly ‘System.Web.Helpers, Version=

[wp_ad_camp_1] I recently ran in to this error on an IIS 6 server using MVC 3 Razor.

Check this first

your exception:

System.IO.FileNotFoundException: Could not load file or assembly ‘System.Web.Mvc, Version=

It is trying to load MVC version 1. You probably need to do an assembly binding redirect in your test project as well, same . . . → Read More: Could not load file or assembly ‘System.Web.Helpers, Version=

iisapp find app pool w3svc

Determine the site’s application pool:

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319>C:\Inetpub\AdminScripts\adsutil.vbs get w3svc/1975602314/root/apppoolid apppoolid : (STRING) “some_app_pool_name”

Restart the site’s application pool:

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319>cscript %SystemRoot%\System32\IIsApp.vbs /a some_app_pool_name /r Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. Connecting to server …Done. Application pool ‘some_app_pool_name’ recycled successfully.

iis 6.0 site running wrong version of .net

Have you ever noticed your IIS 6.0 site is running the wrong version of .net?

This post explains how to change the asp.net version of a specific iis 6.0 website to asp.net 4.0

First find your website using

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319>aspnet_regiis -lk

I have limited the output for simplicity below (a you can see the site is . . . → Read More: iis 6.0 site running wrong version of .net

asp.net tab missing iis6

If you’ve got a 64-bit server you can test this out for yourself by following these steps.

Install IIS 6.0 on the server and then open the Properties of the Default Web Site. You should see the Asp.Net tab as shown here

If you now run the following command at this point :

cscript . . . → Read More: asp.net tab missing iis6

set up asp mvc3 iis6

Original article from http://haacked.com/archive/2010/12/22/asp-net-mvc-3-extensionless-urls-on-iis-6.aspx

If you have a server running IIS 6, ASP.NET 4, and ASP.NET MVC 3 (or even ASP.NET MVC 2. I haven’t tried ASP.NET MVC 1.0), your website should just work with the default extensionless URLs generated by ASP.NET MVC applications. No need to configure wildcard mappings nor *.mvc mappings. In fact, . . . → Read More: set up asp mvc3 iis6