I created one webapplication and placed the default.aspx page in the root folder of the umbraco (i.e., httpdocs folder) and the application dll into the bin folder.
I used the name “Default.aspx” as the other names are not working.
Now the issue is all the pages are redirecting to the default.aspx page (I haven’t made any config changes anywhere in the umbraco setup)
I found this root cause and removed the default.aspx page and its respective dll from the bin folder.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /default.aspx
I stuck up here and struggling to resolve it.Please help me out on this
THanks,
Srilakshmi
Have you tried the 'republish website' option by right-clicking on the top level content folder icon after logging into Umbraco as an admin?
For what it's worth - and I know this is an old question - but this happens when default.aspx has been either overwritten, deleted or otherwise changed so that it doesn't call umbraco.UmbracoDefault. Just make sure that default.aspx contains only the following code :
<%# Page language="c#" Codebehind="default.aspx.cs" AutoEventWireup="True" Inherits="umbraco.UmbracoDefault" trace="true" validateRequest="false" %>
Thought this might help others as I overlooked it today with a similar problem :)
Related
We have an ASP.NET MVC website that runs happily at eg. www.test.com.
We would like to shunt it to a subfolder on www.test.com/xyz. Anyone visiting the root should get nothing - we are quite happy if the root location 404s or is blank or just shows a holding page index.htm. Basically we want to crudely obfuscate the site's new xyz location.
We don't have access to IIS on the hosting so would like to do this all just by moving the files around (and perhaps editing web.config).
From research done here on similar questions it seems that location of web.config is crucial. Ours is the version built by Visual Studio when generating a new MVC application so 140+ lines of configuration which we don't normally mess with too much and haven't had to understand in depth.
What we have tried:
web.config in the subfolder only
web.config in the root only
Neither of these above attempts work. e.g. if the web.config is in the root only we get an error:
Could not load file or assembly 'Microsoft.AspNet.TelemetryCorrelation' or one of its dependencies. The system cannot find the file specified.
at www.test.com, and a 500 error at www.test.com/xyz
I sense we need to split web.config and have some of it in the root (the bare essentials?) and the rest in the subfolder, but I am far from sure of the syntax.
This is my first ASP.NET MVC project. It had been speedy development. However, when I deploy to the server, I just can't get the site to see the controller.
I did a test project. I just create an ASP.NET MVC project with no changes; published on to local IIS and it works. Same project on the server, didn't work. I have an index.html on the root to see if the site is up. Indeed, it's up. I can see index.html. When I go www.test.com/home/index (which is my test site), I get HTTP error 404.0 - not found. The resource you are looking for has been removed had it's name changed, or is temporarily unavailable.
bin folder does have project dll.
App_start/routeconfig.cs default url is point to home controller and the index action.
Project is straight out of the box. It should work.
Can someone point me in the right direction?
Sincerely appreciated.
In case someone is having the same issue.
There are so many reasons for error 404.
In my case, the network guy didn't install ASP.net framework. See there's a fine line between developer and network guy.
It's not exactly what I was searching for, but it solved my problem.
aspnet_regiis.exe -ir does not work on windows 8
Tried creating a default MVC 2 application using the visual studio template and while setting up start page and browsing the application getting the http 404 (Resource not found error), have checked the controller classes for the naming conventions and also the option to set specific page in the project properties.
Kindly advice for any options to try out and also as I am new to MVC, so any help is highly appreciated.
Error Message
HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Hi, I am using the basic web template of Asp.Net MVC 2 Web Application template available in Visual Studio 2010 and have set up the start page.
Below the brief description of the error
Server Error in '/' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /Views/Account/LogOn.aspx
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1022
Do let me know if any additional information is required.
Regards
Arvind
Move:
/Views/Account/LogOn.aspx
To:
/LogOn.aspx
MVC uses routing to get to the Views folder. If you want to use legacy aspx HTTP handlers move it to the root folder.
I had the same problem, and I fixed it by this way:
In a first time, you have to check if your project configuration is correct:
Right click on the project properties, check if everything is ok.
Next, remove the file applicationhost.config. Visual Studio will re-create it automatically. You should find it in the folder "path_project/.vs/config" in the same folder of your project.
I've been developing an MVC 2 application under the built in Web-server in VS2010. On Friday, I moved it to a virtual directory under IIS 5 in my WinXP development machine. I had the usual problems, and added a wildcard mapping to the Virtual Directory configuration in IIS to map .* to aspnet_isapi.dll (Framework 4). Neither the check file exists box nor the Script Engine box is checked.
The routing works and brings up the correct page. But none of the css or js files are served. Fiddler shows them getting either 401 (Not Authorized) or 404 (Not Found) errors (with no apparent rhyme or reason to which one - sometimes both). I went back in and added IgnoreRoute statements to the mapping tables for .css and .js, files, but that made no difference. I also added LOCALMACHINE\ASPNET to the security settings on the directory, giving it (for right now) full control permissions (I know that's a security hole, but I'll fix it after I get it running.)
I have not seen this problem referred to in any of the blog posts on getting MVC running on pre-IIS 7 servers. Has anyone else seen it, and how did you solve it?
The simplest and most straightforward way I've found to get the scripts/graphics/css files working is to specifically remove the wildcard mapping to aspnet_isapi for your content directories (graphics, scripts, css), in the same way that you added them for the project directory.
Right click on your scripts folder and select properties, and hit Create. The configuration button will now be available; click it and hit Remove to remove the custom mapping that the folder inherited from it's parent; click okay. Now back in the properties dialog for the folder, click Remove, so it's no longer a virtual directory, and click OK. Repeat for other such folders.
This is because when your app servers url like : www.domain.com/Controller/Param1/Param2/Param3 it will try to get images from www.domain.com/Controller/Param1/Param2/Param3/images. Try to install firebug and see the net section. Good fix to this is use a helper method to add css reference that adds fully qualified path for css reference like: www.mydomain.com/css/my_css.css
I have an application that uses ASP.NET MVC. I have it deployed to a Crystal Tech server (hence, no direct access to IIS control panel).
Initialy this was running in the root directory and everything was OK. The client then decided that it needed to run in a subdirectory. I moved the app there and the home index page comes up, but every other page tries to access the the controller/action/page/view in the original root directory. I don't understand this, since the references were all contextual (i. e. using ../controller/action as opposed to mysite.com/controller/action).
Am I doing something wrong here? What are my options?
Thanks,
James
I would use the UrlHelper to generate the links. This would ensure that they are relative to the application path.
Link Text
and
<img src="<%= Url.Content( "~/images/myimg.jpg" ) %>" alt="My Image" />