I'd like to enabled Umbraco directory urls for an Umbraco project I'm working on. I've set the umbracoUseDirectoryUrls config setting to true. Unfortunately I'm now getting 404 errors on all pages without extension (with extension they're still working). Below are the configuration details:
IIS 7.5 on Windows 7 x64
Umbraco version 4.0.1
Application pool is running in .Net 2.0 classic mode
I've added a wildcart script mapping in IIS to aspnet_isapi.dll before the StaticFile handler
The 404 error always originates from the StaticFile handler. I don't understand why it doesn't go through the isapi handler.
Unfortunately I will not be able to upgrade Umbraco, change to integrated mode, or change to .NET 4 at this moment.
tried "republish entire site" after setting the usedirectoryurls to true ? You can find it when right clicking the content node in the content section
It probably had something to do with some other configuration setting. After I started with an original Umbraco web.config I was able to switch to integrated mode, which made everything a lot easier.
Related
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".
I need to do some work on an old ASP Classic site, so I’m trying to host it on my IIS, but when I try load a page I get:
An error occurred on the server when processing the URL. Please contact the system administrator.
If you are the system administrator please click here to find out more about this error.
When I follow the link, it takes me to a Microsoft site and talks about running ASP Classic on IIS 7, but none of the pages help and nothing I found on Google will get it to work. I have all the elements under turn Windows features on and off - IIS - WWW services - app dev features.
This was bugging me earlier today and it turned out I had an error in my script.
This assumes you have installed the ASP/ISAPI extensions via the Control Panel's "Add/Remove Windows Features."
By default, errors will not be sent to the browser. To enable sending errors to the browser, go to the site in your IIS manager. Double click the ASP icon and expand "Debugging Properties." Set "Send Errors to Browser" to True.
I had this same problem and it turns out you need to set application pool to classic .net for it to work.
I'm trying to install a default Umbraco installation on IIS7, and I'm getting the following error on my (unmodified) web.config file, any ideas?
Config Error
The configuration section 'system.web.extensions' cannot be read because it is missing a section declaration
Thanks,
I'm going to assume you are using the current version of Umbraco 4.5.2 as offered on the Codeplex site...
By default, Umbraco is configured to use .Net 2.0 (not .Net 4.0). Go to your IIS Management Console, select ApplicationPools and double-click your website. Make sure the .Net Framework is set to 2.0.
Also make sure the server you are running the IIS on has .Net 2.0 installed!
If you can provide more information from the server's error page, I can help better pinpoint the error...
I have a project which I have upgraded to .Net 4.0, but when I try to access it, I retrieve the following error:
HTTP Error 404.2 - Not Found
The page you requested could not be displayed because of the settings for the list of ISAPI and CGI restrictions on web server.
ErrorCode: 0x800704ec
Handler PageHandlerFactory-ISAPI-4.0_32bit
Do I need to do something extra to the IIS 7 or APP pool, when converting an existing site to a .NET 4.0 site?
Also if I look at ISAPI both 32bit and 64bit of the .Net 4.0 is installed.
In IIS, enable .NET 4.
Here is image:
I take it you're running on IIS6 right now..
Open the IIS manager, and go to the Web Service Extensions area.. You'll be able to enable .NET 4 in there.. All new extensions are disabled by default :)
If you're running on IIS7, .NET might not have registered in IIS.. Then open up an admin command prompt and navigate to the .NET 4 framework folder (C:\Windows\Microsoft.NET\Framework\v4.{version}). If you're on a 64 bit machine go to the Framework64 folder instead of the Framework folder.
Then run aspnet_regiis -i in there
I had this same issue. Strangely, for me it would run in integrated mode but not in classic mode for .NET 4. After enabling the .NET 4 extensions via the Isapi and Cgi restrictions section in IIS 7, it then began working in both modes. The Isapi and Cgi restrictions section is located at the server level node in IIS manager. This option should not be confused with the Isapi Filters section at the site level.
I was developing an ASP.NET MVC web app on Windows XP and Visual Studio 2008 (using the Visual Studio web server). I recently installed Windows 7 64 bit Ultimate edition, IIS 7.5 and migrated my app using appcmd.
If I set the flag enable32BitAppOnWin64 == false on my application pool my application works fine. As soon as I set it to true (since I want it to run in 64 bit) it throws this exception:
Screen Shot of error
HTTP Error 500.0 - Internal Server Error
Calling LoadLibraryEx on ISAPI filter "C:\Windows\Microsoft.NET\Framework\v2.0.50727\\aspnet_filter.dll" failed
If I go and delete all ISAPI filters but leave ASP.Net_2.0.50727-64 then this error goes away.
How do I resolve this?
Your key is in the path mentioned in the error:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\\aspnet_filter.dll
Notice there is an extra slash in the path. At an elevated command prompt, navigate to ../Framework/v2.0.50272 directory and run the following command:
aspent_regiis -r
Alternatively, use IIS to modify the correct path of the filter.
So no magic dust needed...you just need to register the right path. :)
It sounds like you need some 64 bit ISAPI filters.
32 bit DLL's will not run on a 64 bit machine unless you sprinkle some magic pixie dust on them. This is why the enable32BitAppOnWin64 flag exists.
Set the flag to true and bask in the glory of the pixie dust.
It sounds like the Handler Mapping preConditions for your site are a bit messed up. In IIS MMC browse to the site and open the Handler Mappings feature. In the Actions pane on the right, click the 'Revert To Parent' link.
Just had this happen to a project deployment.
Changing the application pool for the website did the trick.
Found the answer on Rick Strahl's weblog