CS0016 compiler error when browsing a deployed asp.net website IIS 7.5 WIN7
I met this problem when trying to browse my website. I searched a lot on the Internet, but I could not make it even when I gave full control to everyone in the security tab of several temp folders. Any ideas on this problem?
I finally resolved this issue by using cmd to uninstall and install asp.net in IIS7.5. Hope this will help others.
Related
I am very new to web services. I have wrote a web service application. When I run it from visual studio, everything works fine and my local website comes up. But after I deployed it in IIS, I can't browse it from iis and i get the following error! I am confused about this error for a day! Can some one help me?
XML Parsing Error: no root element found
Location: http://localhost:99/WebService.asmx
Line Number 1, Column 1:
I faced a similar issue when I deployed a project on my local new computer. By default, ASP.NET is installed but disabled in Windows.I had to enable it before my project run. See Install IIS and ASP.NET Modules for details.
Make sure that all the required modules are enabled.
I had same issue, but had ASP.NET modules installed. Apparently had to change .NET Framework Version from v2.0 to v4.0 and site was showing as it should. You need to go to IIS, Application Pools, double click the one that has older version of .NET and set the relevant one. Maybe this will be helpful for someone else.
I'm having a hard time fixing an error that I currently have and I hope you can help me with it.
I am developing a little ERP-WebSite that is going to be used within an intranet. Naturally I want to use Windows authentication to make it as comfortable as possible for the user. I developed the Website using Visual Studio 2008 and its integrated development server. Recently I migrated to VS2013 and .NET 4.5. Code wise everything went good and I am able to build everything but here comes the problem. Because I am using VS2013 now I also have to use IIS Express. When I try to debug the Website i receive a 401.2 Error. Error Code 0x80070005. On VS2008 everything worked perfectly and I am 99% sure I have the IIS config set up currectly. Here are the relevent parts:
applicationhost.config:
I also set the according values in the Project Settings in VS2013.
I'm kind of lost right now. Any help will be much appreciated!
EDIT--------------------------------------------------------------------------------------------------------------------------
After playing around with IISExpress for way to long now, I finally got it to work again. Something must have been wrong with my previous eddits of the applicationhost.config file of the IIS Express. I just deletet it and let VS13 recreate it. Afterwards I was able to run my site using IISExpress. I hope this might help someone who has the same problem as I do. Sadly i realized that it is painfully slow. It takes almost 2 minutes for some pictures to get loaded etc.. What could be the cause of that ? I also tried using the full IIS Version (with Win-authentication installed) but when I run my site using the local IIS I receive an XML-parsing error: No element found. Using the local IIS would be a lot faster than using IISExpress, so I'd very much like to fix this Error.
Thanks for any help in advance.
I just installed IIS 8.5 on Windows 8.1. I installed it after installing Visual Studio 12 and the 4.5 version of the .NET framework. I created a new site and now I am getting this error:
HTTP Error 404.3 - Not found
The page you are requesting cannot be served because of the extension configuration.
I have seen posts here and elsewhere regarding this error and none of the fixes have worked. I have tried running aspnet_regiis.exe - the correct 64 bit version. I have also installed all the ASP.NET development tools, including the .BET 4.5 Extensibility feature. Still I am getting this error. I haven't found a post yet with a fix I have not tried.
Has anyone fixed this issue a different way?
I know that this question is old but I've managed to solve this issue on Windows Server 2012 without reinstalling anything, so just in case I leave my solution for future reference:
I just went to 'Add roles and features' and in the Features part I checked 'HTTP activation' on '.Net Framework 4.5 Features->WCF Services'.
The solution turned out to be quite simple. I removed IIS completely, rebooted, and installed it again, making sure to include all the Asp.NET development features the second time.
I think that's where I went wrong the first time. I installed IIS without those features and tried to add them in later. It seems like that should work, but it didn't. The total re installation did, though.
404.3 is the MIME type restriction, it means the server is not serving files with an .aspx extension. That's okay, it is not suppose to. But it has to be defined under the Handler Mappings like this:
If there entries are not there, add them.
On IIS 8.5, Open Server Manager, navigate to the Server Roles screen Scroll down the list to the "Web Server (IIS)" --> "Web Server" and check all the options under "Application Development". That should work!
having a real problem getting VS2010 to debug IIS.
I've searched on the internet for a few days now and tried every single solution I can. VS2008 works perfectly but I've installed VS2010 and when trying to debug an IIS site (by pressing F5 on a project that uses IIS) I get the error message
"unable to start debugging on the web server. Microsoft Visual Studio Debugging Monitor (MSVSMON.EXE) failed to start. If this problem persists, please repair your Visual installation via "add or remove programs" in the control panel."
when i try attaching the process manually, i get the same message.
I've tried repairing the software. I tried it, it failed, so I uninstalled using the Microsoft Visual Studio 2010 Uninstall Utility (http://archive.msdn.microsoft.com/vs2010uninstall/Release/ProjectReleases.aspx?ReleaseId=4321), then reinstalled and it still has the same problem. With the SP1 update this still happens. I can run the website fine when running "start without debugging" and it runs fine.
I've gone through all the guides I can and all tried all the settings on IIS I can and still no luck. I'm using Windows 7 64bit if that means anything. I can detail much more about all the things i've tried.
also have a laptop and have done the same, installing VS2010 and TFS (also on win7 64bit), and this works perfectly for debugging. Didn't have to mess around at all. I can't see any difference between this and my PC with the problem. I'm scratching my head here and thinking I might have to format my PC and try again from a fresh install (which would be seriously annoying!)
Thanks to anyone that reads this,
Dan Gent
I had a HOSTS file entry resolving the project URL to a DEV server instead of local machine. Changing the entry to point to 127.0.0.1 fixed the problem.
Are you installing from a purchased disc or did you download it? Either way, you need to download a fresh copy and install that (sounds like original is corrupted).
Also, make sure you have all the IIS & Web components installed on your machine. Is your OS home or basic?
http://technet.microsoft.com/en-us/library/cc731911.aspx
i've fixed it now. ended up formatting machine, reinstalling windows 7, and then taking backups everytime i installed a new program so i could roll back. installed VS2010 first, F5 worked. then installed VS2008 & everything else and debugging still works on VS2010. not sure what happened as the above problem happened on a fresh install. something must have corrupted something somewhere
thanks for all your help and narrowing this problem down to something that was worth formatting my PC to fix.
cheers,
Buswell
This can also be caused if you are using a host name in IIS and make a mistake in your hosts file.
Check that the hosts ip is set to the local machine 127.0.0.1 and not somewhere else. In my case I had accidentally set it to the development server.
Have you tried starting MSVSMON manually? I had the same problem you are and found the service was stopped. So I tried enabling the service and made sure that it was using the correct credentials.
I hope this helps!
Thanks!
Don
The only thing that worked for me after I tried practically every solution on the Web is to right-click the project on the solution explorer, and select Debug->Debug as Administrator.
Right click on Project, "Use Custom web server" checkbox will be selected, select check box "Use local IIS web server".
I resolved this issue with this and its working.
Managed to resolve this error by At solution explorer-> right click the project->select Debug->Start new instance.
I think it was because i had copied the project folder from another server.
I've worked with ASP.NET once before and had a project where it was potentially useful, so I started creating an ASP.NET website as part of a solution that contained several C# class libraries.
I'm using Visual Studio 2010 Ultimate Edition and Windows 7 Professional x64. The issue is that when I try to debug my website project, I get the following error message:
Unable to launch the ASP.NET Development Server
There's no other information (it seems a popular variant is the "port in use" error).
Interestingly, I can run single pages on the application by right-clicking on the ASPX and selecting "View in Browser". This does not allow me to debug into my breakpoints, though.
I have no clue what the problem could be. I'm running VS2010 in Administrator mode. One of the questions that popped up here suggested I uncomment the "127.0.0.1 localhost" line from my HOSTS file, which I did, and restarted VS with no luck. I also tried both setting a static port for the web server to run on as well as let it dynamically generate one. Both do not help the situation.
Any help?
Thanks.
Added on 5/20/2010 at 9:25 CT
I can debug by attaching to the process. However, this is still a painful way to debug quickly so I'd still like a solution to the problem.
There are some things to check before listed here
Please eliminate issues on the link and check whether you may debug
Hope this helps
Myra
The problem was I had a InstallShield Lite project which was apparently causing problems. Once I unloaded that project, I can launch the development server in debugging mode.