Does updating urlscan.ini require iisreset? - iis

I'm wondering if I have to do iisreset upon updating the urlscan.ini file. Is this required or will IIS pick up the new ini file immediately?

This depends on the version of UrlScan. The UrlScan reference site says:
UrlScan 3.0 added change notifications for the UrlScan.ini file, so it is no longer necessary to restart IIS after updating your UrlScan.ini file.
Hence, it does not require to restart IIS.

in my case URLscan config wasnt loaded until i did reset iis , i have URLScan 3.1 with windows 2008 R2 and IIS 7.5

Related

IIS has no websites

I'm configuring Windows 10 machine for web development. Installed Visual Studio and want to configure websites. Installed IIS manager but for some reason it doesn't have... anything. No websites, no application pools, no features at all. And it doesn't let me to add any of that.
Has anyone faced this kind of behavior?
Found it. It turned out that something messed up IIS config files (in Windows\System32\inetsrv\Config). So all IIS features were referencing invalid DLLs in the GAC and therefore were silently failing. I only found a trace of that in the Windows Event Log.
Took clean administration.config file and IIS started correctly.

Could not load file or assembly 'Microsoft.Web.Administration, Version=7.9.0.0

The server is Windows 2008 R2 SP2 with IIS 7.5. I am running a PreReq utility to confirm it is setup prior to installing Infor Approva 10.0.
The utility keeps returning the above error. After some research it seems that error is usually thrown because IIS Express is installed and the wrong reference is being used which is fixed by either uninstalled IIS Express or changing the binding in aspnet.config. However I've confirmed that IIS express is not installed, so I was wondering why this error is being thrown? There aren't any existing references in the aspnet.config or the machine.config files.
Microsoft.Web.Administration.dll is located in folder %windir%\System32\inetsrv. You can find it on your machine and check its version.
I think this issue is caused by a wrong assumption of Approva's PreReq, and you should contact their technical support for assistance.
It is very likely that the vendor misunderstood IIS and IIS Express, and had a wrong reference to MWA set in their product.

Migrating EPI5 from IIS6 to IIS7.5

Trying to move an EPI5 site from a server with IIS6 to a server with IIS7.5.
Having problems because of the configuration being set up for IIS6. Ive tried to follow instructions
http://world.episerver.com/en/Documentation/Items/Tech-Notes/EPiServer-CMS-5/EPiServer-CMS-5-R2-SP1/Changes-Between-IIS6-and-IIS7/#Changes in web.config
Does anyone have experience of following this guide or reconfiguring from IIS6 to IIS7.x?
What I've done in this situation (numerous times) is install a fresh (blank/demo) EPiServer 5 site on a server with IIS 7 and use those config files as a template when moving the real site from IIS 6 to IIS 7.
EPiServer 4 on Windows 2008 with IIS7 is not officially supported. You can get it to work though - one key is to run the application pool in Classic mode.
EDIT: You also need to turn on the pool's "32-bit" setting.

ColdFusion10 Developer and Windows7 (IIS7.5)

I am trying to learn ColdFusion and have installed the developer edition (CF10) on my Win7 computer and this brings up the localhost administrator page correctly but I have a test helloworld.cfm file in inetpub/wwwroot and when I try & access this with localhost/helloworld.cfm windows opens a dialogue box saying what program should open this .cfm file?
(in IIS Mime type there is none for .cfm & when I tried to add one it didn't work...).
Several posts on the internet say ensure IIS has CGI enabled and ISAPI Extensions
IIS Metabase and IIS 6 configuration compatibility which I have.
I'm not sure what is wrong here-can anyone advise me clearly & simply if I can view and use .cfm in IIS & how?
We know IIS is the problem because your administrator works, so CF is running correctly.
What I do is the following
create a site in IIS, just basic. no setting changes
install coldfusion 10
During install coldfusion will ask me if it has to configure all current IIS sites
if you let it do that, it should all work like a charm.
Did you do it like this?
I would uninstall and re-install as something must have gone wrong connecting IIS to COldFusion
CF10 does not require the IIS 6 compatibility. If you don't need that for any other web technology connections, then remove that. You do need CGI, .Net Extensibility, ASP.NET, ISAPI Extensions and ISAPI Filters. I believe the connector configurator for ColdFusion especially uses the .Net Extensibilty to "wire things up".

VS2010 throws exception while opening project

When I try opening a project I get an exception saying Web application is configured to use IIS.
Error : The Web Application Project EntityServices is configured to use IIS. To access local IIS Web sites, you must install the following IIS components:
IIS 6 Metabase and IIS 6 Configuration Compatibility
In addition, you must run Visual Studio in the context of an administrator account.
NOTE - I have already installed IIS 7. My box is a x64 bit Windows 7 box.
Go to Control Panel, Programs and Features, Turn Windows Features On or Off, and enable IIS 6 Metabase and IIS 6 Configuration Compatibility.
Have you installed IIS6 Metabase support? It is a seperate install from IIS7, although in the same area.
Turn Windows Features ON and OFF -> IIS Services-> Web Management Tools -> IIS Management Compatibility and check IIS Metabase and IIS 6 configuration Compatibility
This also happened to me when I had reconfigured the TCP Port on IIS to port 81. I was running TCPTrace, capturing traffic on port 80 and forwarding it to IIS at port 81.
After a reboot, I had to reconfigure IIS' TCP Port to 80 and the problem was resolved.
I got the same error the solution is that you should open with notepad (web project)it's csproj file and remove this tag
<UseIIS>True</UseIIS>
you need to turn on asp.net :
controlpanel- Turn Windows Features ON and OFF -> IIS Services-> www- > application Dewvelopment features check the asp.net on
In my case (Same error)
i solved my problem with following steps.
1-)open your project file with a text editor.
2-)find "USEIIS" tag and replace its value with "False". save and exit.
3-)reopen your project file with visual studio

Resources