I upgraded my machine to windows 10 release 2.0 from Windows 7 and installed Visual Studio 2017 which I earlier used was VS 2012. My application is not working after setting up IIS 10.
Getting this below error:
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
Is there something extra that needs to be configured for IIS 10?
From the asker in an edit to his question:
Running Visual Studio in admin mode solved the problem.
Related
I have an aspnetcore application version 5.0 that calls executables in its process when I'm in development environment, but when this application is installed on IIS, the process doesn't work.
I use the version of IIS installed on the "Windows Server 2016" server is: 10
I'm trying to run WCF Service based on 3.5 Framewor on Windows 8 with Visual Studio 2012 and IIS Express.
Service hosting fails with error "HTTP Error 404.17".
I'm trying with default Visual Studio WCF template setting framework 3.5.
Works fine if I select frameworks 4.0 or 4.5.
Is there a way to make 3.5 services works fine with IIS Express?
Http activation is enabled in Windows Features.
Tried install, re-install, remove and install Service Model via:
Framework64\v3.0\Windows Communication Foundation> .\ServiceModelReg.exe -i
Still not working.
Regards,
Dmitry
I have a MVC 4 application and runs well on my local machine.
What do I have to do further in Visual Studio 2012 to run my website in web server?
Do I have to make some files by VS 2012 to deploy a website in web server?
You don't need to do anything specific in Visual Studio.
Make sure you have .net 4.0 and MVC installed on your server.
Configure your app pool to be the same architecture as your Webapp(x86, x64).
Change your web.config
Create a virtual directory/application on your ISS.
Configure authentication options of your app(probably you will need anonymous and forms)
When you publish/build your website you can just copy the entire content to your IIS directory and it should work.
I just installed .net 4 on my server 2008 and I keep getting
Service Unavailable
HTTP Error 503. The service is unavailable.
messages from any application I try to run as .net 4. The application pool keeps stopping. Event view shows: "The worker process failed to pre-load .Net Runtime version v4.0.30319."
I was getting this same thing on a windows core 2008 R2 box.
Running 'oclist' showed that there were some missing windows features.
To install them, i needed to run the following commands:
ocsetup NetFx2-ServerCore-WOW64
ocsetup NetFx3-ServerCore-WOW64
Problem has been solved. I uninstalled .net 4 and reinstalled using the "web platform installer". restarted and now it works.
well, according to what I've found googling around, it's imposible... (maybe with with windows xp 64...)
but I thought that maybe someone could find a way to achieve it, or at least some workaround...
http://www.iisanswers.com/IISFAQ.htm
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.inetserver.iis&tid=14654991-875f-4cc6-a853-7e9f3bb96bc3&cat=en&lang=en&cr=&sloc=en-us&m=1&p=1
--
ps: I need to debug classic asp code, and my production environment is windows 2003, while my development machine is windows xp...
--
edit:
just to clarify, I can already debug classic asp code in iis 5 with vs 2003 and 2008, it's just that I stumbled upon a (very silly) bug that only appeared on iis 6 (when IIS 5 received and empty http status, it just assumed 200, while iis 6 kept asking for my credentials in an infinite loop, it was very silly in deed, but took me a lot of time -and cursing- to discover it)
IIS 6 cannot be installed on Win XP. However, debugging classic ASP code is possible on Windows XP / IIS 5.1 using Visual Studio 2003 and up. You will need to configure IIS 5.1 to "enable ASP server-side debugging" (disabled by default):
IIS settings http://www.freeimagehosting.net/uploads/f1a6f781b9.png
Here is a more detailed article on how to debug classic ASP pages in Visual Studio - link
(NOTE: When running on XP Pro/IIS 5, you need to attach to dllhost.exe instead of w3wp.exe)
You posting in your 2nd link is correct. And read the faq. That spells out why it can't be done.
One option you can do is have a virtual machine of Server 2003 running on your laptop.