I´m trying to start a project I pulled from a colleague. No errors, no visible issue in the project.
The project starts without problems, but immediately force me to login to Umbraco. When I enter credentials for the Admin I am returned to a view that is forcing me to upgrade Umbraco version, something I do not want to do since the project is live on the Umbraco I´m currently on.
I have worked with Umbraco before on several project and never experienced this issue.
The project is running fine on my colleagues computer, connected to the same umbraco database. He has no changes that are not committed to the repository I´m pulling the project from.
Any ideas what might be causing this situation?
Umbraco v6.2.6 (Assembly version: 1.0.5906.18846)
Thanks and best regards, Martin
Check that the version of Umbraco in the core DLLs matches the one that's in the "umbracoConfigurationStatus" appSettings key in your web.config file. If they're different, it'll try and get you to upgrade. Compare against your colleagues machine as well to see if there's a difference between what's on his machine and yours.
You get the upgrade message when Umbraco detects a mismatch between the version it's running and what the web.config file says the site is running.
Related
I am working on bringing a working web application onto a new computer running Visual Studio 2022 version 17.4.2 and .NET Framework 4.7.2. When running on local IIS (version 10.0) host there is a "local host redirected you too many times" issue. It suggests clearing cookies which has been done with no effect.
The same code works on other machines with no issues. Is there anything in IIS set up/configuration or that may be missing from Visual Studio or other installations? Thanks in advance.
So far we have tried debugging the code and including breakpoints for where the issue may be occurring, ensuring that the installations of windows feature and IIS management is the same as another where the program is working. Also created a .txt file that can be reached on local host and is in same location as the rest of the project.
Here are a few things you can try:
Try on another machine.
Try to remove as much rules as possible from web.config and keys and so on. Or if it's a single page you're having the error with try to remove as much code from it especially if there are redirect codes. And add breakpoints and debug.
Check the LOCAL application pool version if it's set same as the online .net framework version.
I'm about to deploy a site where some functionality is omitted to get the website launched as soon as possible. This means that after the site has been deployed to a live server, some development still needs be done.
I have mainly been used to working on local projects, and have just been playing around with opening the site as a FTP project in VS2012.
This seems to be the way to go, but unfortunately, IntelliSense doesnn't play nice (not all namespaces are recognized) and when re-building the project, it seems as the whole Umbraco project is recompiled (which creates an enormous overhead). And I have not found a way of excluding Umbraco specific folders from the project.
Another thing is that the project is recognized as a WebForms project and not MVC4, for which I would also like a fix :)
Any suggestions on how to carry on from here? Suggestions and best practices is very welcome!
I have a similar question to this one;
IIS 7.5
Server 2008
ASP.Net 4.0 web site
The error I get when trying to run the site is this:
HTTP Error 404.17 - Not Found
The requested content appears to be script and will not be served by the static file handler.
...
Most likely causes:
The request matched a wildcard mime map. The request is mapped to the static file handler. If there were different pre-conditions, the request will map to a different hander.
Now here comes the weird part:
THE WEIRD PART
The weird part is that on the develop server -- which is similar in every aspect to the production server -- everything runs smoothly.
Here's a list of things I cannot try, because I don't want to mess with the sever (it hosts many other sites):
Reinstalling .Net
Reinstalling IIS
Reinstalling anything
Running aspnet_regiis
Here's what I did try:
Republishing the site
Restarting the application pool
Changing the application pool to .Net 2.0 and back to .Net 4.0
Switching around between Integrated and Classic pipeline mode
Enabling 32-bit mode
Taking a look at Handler Mappings
Eventually I created a new application pool, and it sort of started working.
Q) "Sort of"?
A) Yes, sort of.
Now the site only works when the (new) app pool is set to .Net 4.0, Integrated,
and the site's Authentication has ASP.NET Impersonation set to Disabled.
Any change to these settings sets the server yelping "404.17" all over again.
Q) What's wrong with that?
A) What's wrong with that is that I NEED ASP.NET Impersonation for the site to function properly.
As always, your guidance is most needed.
HTTP Error 404.17 - Not Found
The requested content appears to be script and will not be served by the static file handler.
Usually this error occurs when you have the right IIS version installed to the respective .net framework. If it was a version (not installed) issue then you would have got a different error message. Anyways, I think by now you have resolved your matter, but I like to share some words with anyone else having this problem. These error messages gave me so much headache all last week and I had tried everything.
Best remedy is always to re install the latest .net in latest visual studio. And the important thing to do is uninstall the existing IIS(express or whichever you have) and re install it first. Then download the latest visual studio. This way visual studio installation can easily access you IIS and add the necessary application pool.
As for the error 404.17, it could simply be because the right application pool has not been assigned for the appropriate dot net version. If the right version is not there re installing visual studio is the only way I know. Also, I think you can try downloading another version of the Visual Studio too. For eg, download the ultimate if you have professional or vice versa. Hope this helps someone with similar problem.
Installing this windows server feature http activation is, what was missing for me.
We had a working website built on framework 2.0 with membership. After we converted it to framework 3.5 using the Visual Studio automated conversion mechanism by opening it in Visual Studio 2008 and following the prompts, the membership system is now broken. Dammit, all we wanted was some newer AJAX.
The rest of the site appears to be functioning fine, but when it comes to logging in or managing security on the site, it fails.
So the errors we receive when trying to manage security via the built-in admin pages, seem pseudorandom; everything from 'user cannot log in to database' to 'this file is being used by another process' to 'there's a problem with your datastore'.
What sort of datastore are you using? SQL Express MDF file in your App_Data folder? External SQL Server? Did you change anything in web.config?
So far as I know, there were no real changes to Membership features between 2.0 and 3.5... I think you've got something else going on.
You can rollback your changes and test the old system, right?
Thanks Bryan for your response, but this turned out to be a complete disaster and it's something I would NEVER do again. I just came back to say this to anyone who tries it in the future: "You just made a very bad mistake."
Yes, we ended up rolling back, if that's what you call it when you have to re-get everything from SourceSafe to a completely new directory because there is no auto-rollback feature with the framework conversion, only a backup folder that has been screwed with and dumped into another folder and will never work again because all references are now broken and the web.config has a bunch of illegal entries, and the IIS metabase ended up corrupted, and intermittent database locking caused permissions to be wiped, and around 15 or 20 other problems.... there is no solution to this issue. Not really.
Of course I've personally updated many projects using the Visual Studio upgrade system. But never a website, and never one this complex. And now, never again. :-)
I have an ASP.Net 2.0 web site, using the DotNetNuke framework (4.09), and it will not compile, but when I hit the site in a browser, it works. Even the parts that don't compile will work. How is IIS able to compile and run this site, when Visual Studio can't? Everything is the same in both places... I copied the entire web site from the remote server on to my local machine, then I set it up in IIS the same way. On my local machine, Visual Studio can't compile the site, but it still runs. How can this be possible?
The specific errors are not important, as there are 189 of them, from every possible part of the site. I'm not trying to fix the errors... what I want to know is how it's possible for the web server to run the site, regardless of the errors. Please pay attention to what I have written - everything is exactly the same in both places. There are no missing DLLs, no different configurations, nothing on the machine itself... remember, the site runs fine on my local machine.
Is this a web site or a web application? If it's a web application, you're probably still running off the last successfully built bits in the bin.
The site is using old dlls, or possibly you have references missing in your local version that the server has just fine.
As Mitchel said, we need to see the error before we can really answer your question.
To give you an answer on this we would need to know what the errors are.
Your local machine cached the 'working' copy and is using that maybe?
The site was compiled successfully at one point as it works on the remote server. Thus, copying it to your local machine and hitting the local site will also work. However, there can be several reason why you can't re-compile it on your local machine including; missing references, web.config entries, third party control licensing, etc..
I realize you are not trying to correct the 189 errors, but there are clues, if not answers, in the error listing that will get you moving in the right direction.