When I'm publishing the website to staging and trying to go
https://26e33c03a5fc48e9a26089b858345c9d.cloudapp.net/
I'm immediately redirecting to https://26e33c03a5fc48e9a26089b858345c9d.cloudapp.net/Error/Http404/?aspxerrorpath=/Account/Login
this issue is new and first occurred after Azure down time,
any idea why this happens?
The code work perfectly on my Machine.
i lately added the RazorEngine 3.0.8 Beta
the solution was upgrade from mvc3 to mvc4 but i published it few times and it did work.
again, this is working on my machine but not on the server, any idea why?
V3.0.8 uses the older version of System.Web.Razor published with MVC3. Try updating to v3.1.0 which is now built around Razor 2 which came with MVC4
The issue solved after removing the RazorEngine 3.0.8 Beta, i suggest to be careful as the beta causing real issues.
Related
My client just updated me that they are facing some issues with the CMS today so tried to login as admin however could not, it gives me the login page but then is stuck on initializing page.
Versions
Composite C1 3.2 Build 3.2.4497.34793
.net 4.0
IIS 6.0 (I know old :) )
Steps taken
Restarted the site in IIS.
Same issue on all the browsers.
We have several sites built using Composite C1 the rest are working
fine, they are same version same build. In fact the preview
version of this same site works fine.
Similar issue reported here - However my build is already updated to the version informed here.
It would be great help if anyone has faced a similar issue and knows how to proceed with trouble shooting this issue.
I'm trying to implement OAuth in my existing MVC4 website. I had everything working in a test site, and everything was working fine on this particular site. I'm presently getting this error , but my web.config looks like this: . I tried this fix, I've tried GACing the components, I've tried uninstalling and re-installing the NuGet packages, I've tried clearing out the ASP.NET temp files, I honestly don't know what else to try... except maybe put my fist through my monitor.
Does anyone have any ideas? Thanks.
BTW, I solved the problem. It was because the project was upgraded from MVC 3, and I had the MVC 4 assembly in the list. Once I rebuilt the web.config from a new MVC4 project , the bindings stopped getting their wires crossed and the app started working again.
If you run into the same problem and want more details, reply here and I'll post them.
So I just upgraded my website to a MVC 4 site from MVC 3. My Web host does not have MVC 4 installed but was advised that I can just upload the dlls and all will be alright. I was directed to this link which apparently can be applied when installed
http://weblogs.asp.net/scottgu/archive/2011/01/18/running-an-asp-net-mvc-3-app-on-a-web-server-that-doesn-t-have-asp-net-mvc-3-installed.aspx
I did what is instructed on the following link but then I'm getting an error on my ViewExtensions which apparently (after a 2 hour research) is related to my upgrade (eg. http://s77.codeinspot.com/q/2109234) . Anyway this is the error being thrown.
filterContext.Exception.Message :\hostingpath............... error
CS0121: The call is ambiguous between the following methods or
properties:
'Torneyo.Infrastructure.Helpers.ViewExtensions.AccountProfile(System.Web.Mvc.ViewMasterPage)'
and
'Torneyo.Infrastructure.Helpers.ViewExtensions.AccountProfile(System.Web.Mvc.ViewMasterPage)'
Which doesn't make sense as it's the same and it's just coming from my viewextension class. Following is the part which is being called on my masterpage.
//-----------for master pages
static public User AccountProfile(this System.Web.Mvc.ViewMasterPage view)
{
return (Profile)view.ViewBag.AccountProfile;
}
So these were all working perfectly before the upgrade on the webhost. It runs perfectly on my local before and after the upgrade. I'm not really sure what else I need to do.
Please make sure that you have the correct binding redirects in your web.config. Chances are that parts of the app are referencing MVC3 and other parts are referencing MVC4. A binding redirect from MVC3 to MVC4 will "unify" everything to MVC4.
Check out the "upgrade" guide here: http://www.asp.net/whitepapers/mvc4-release-notes#_Toc303253806
Finally fixed it. So I tried wiping out the DLLs and reinstalled it but it still doesn't work. What I had to do was to remove everything (Files in the wwwroot folder). And then published it again. Everything worked fine after that.
I am trying to deploy the default empty internet application template from .Net MVC 4, my app gives the same problem so figured start with the simplest app I could.
The server is 2008 R2 running .Net 4 (app has been changed to 4 from 4.5). I have other sites running on that machine with .Net 4 and MVC 3 but the MVC 4 app just brings up a blank page. I have confirmed HttpRedirection and HttpErrors are installed (and the MVC 3 apps run fine).
I have tried the solution from Michel van Engelen here I am getting a blank page while deploying MVC application on IIS and confirmed it works on my machine but still a blank page.
I ended up adding ELMAH to try get info on the exception that was causing the problem and the site started working, I am not sure what changes to the web.config to install ELMAH resulted in the site starting but did the same thing to my other original app and all is now fine.
I've been trying to figure out why my views are returning 404 in my staging environment, but not my development environment.
Windows Server 2008 R2
IIS 7.5
MVC 2 Beta definitely installed.
The first Route entry in my Global.asax is as follows:
routes.MapRoute(
"FindStore",
"FindStore",
new { controller = "FindStore", action = "Index" });
All views are definitely present and in the proper directories.
Basically if I go to http://StagingServer/FindStore I get a 404 error. Every other answer I've seen has to do with IIS 6. which I'm not running.
We had a similar problem. We checked integrated mode, permissions, and runAllManagedModulesForAllRequests. No dice. Eventually this windows hotfix fixed it.
It ended up being because my App Pool was running in Classic mode.
I am not sure if this will help but there was an issue reported on Stack Overflow that uses both technologies and involves a similar problem:
Getting an ASP.MVC2/VS2010 application to work in IIS 7.5
I would check it out and see if it helps.
I had the same problem, my App Pool was set to Classic and I had changed it to use the .NET 4.0 Framework, but it didn't start working until I recycled the App Pool.