WCF Service Migrated to IIS 10 - Consistent 503 - asp.net

A computer hosting a WCF service at my work was swapped out from a Windows 7 instance running IIS 7 to a Windows 10 instance running IIS 10.
The WCF service is a third party service that allows remote control of the robotic system the computer is connected to, so I have no access to the source code.
I've tried using MS Deploy to migrate, I've tried perfectly replicating every single setting in IIS and installing all the necessary .Net Framework versions, and I've completely re installed .Net Framework twice.
No matter what I do it always results in a 503 - Service Unavailable. The logs in HTTPERR simply state "N/A" for each failed request to the svc file.
Yes, I've added the svc Mime type and handler.
Also Server Manager has been no help, as it's Windows 10 and not actually a server.
EDIT:
Here are the settings I've copied over:
Application pool for default site uses .Net CLR 4.0, with Application Identity and 32-bit applications disabled.
Application pool for the WCF service uses .Net CLR 4.0, with Network Application as its identity and with 32-bit applications enabled.
It works perfectly fine on the old server, so I'm still at a loss as to why it doesn't work on the new one.


Thanks to Travis Acton for the suggestion to check netsh http show urlacl!
I decided to run the delete command for the port despite it not being shown, and it indicated that the port reservation was successfully deleted. For some reason it was unlisted by netsh.
So now it's all working fine! Thanks so much for the help!

Related

IIS hosted WCF using net.tcp

A version of this question has been asked many times. I cannot find a solution to my particular problem.
IIS 7.5 is hosting a web app as well as a WCF service using tcp. I have this running fine on several development boxes running Windows 7.
I get the error "Could not find a base address that matches scheme net.tcp for the endpoint with binding NetTcpBinding..." when I try running this on a Windows Server 2008 R2. --Even when trying to access it locally, from the same box.
I've enabled the proper bindings (net.tcp)
I've enabled the proper windows features (non-http activation, etc.)
the appropriate Windows services are running (net.tcp listener adapter, etc.)
Anyone have any ideas what else might be the problem?

Master Data Services Web Application Issue

I am trying to create a Master Data Service Web Application. So far, I have not succeeded with this activity.
I have check on internet for possible solutions but:
The .NET 3.5 and 4.5 features are checked, the svc file is present, but everytime I run the Master Data Configuration Manager I see the the warning about Internet Information Services.
I do not what else do I need to install or configure. When I try to access the URI of the web application, this does not show anything.
I am using Windows 8 and Sql Server 2014

When this happened to me I discovered I needed to execute the MDS Configuration Manager on the virtual machine's operating system rather than my local machine.
These IIS settings exist on that Windows Server, not your local machine.

"ORA-03134: Connections to this server version are no longer supported."

I am trying to understand why the same C# Oracle access code works under VS2010 environment but not under IIS.
I am building a web service to access Oracle 9.2 database on the remote machine. The web service must be hosted in the IIS under Windows 2003 machine. The same machine is hosting Oracle 9.2 database.
The web service must be compiled for x86 CPU because of Windows 2003 that is 32-bit architecture.
My Visual Studio project is WCF Application.
When I run the service under ASP.NET Development Server everything works fine. The database is connected and all CRUD operations are possible.
When I deploy everything under IIS on my machine or any other machine the I am getting "ORA-03134: Connections to this server version are no longer supported." at the time of connecting.
I supposed it is some kind of permission problem so I run the service under special Application Pool with LocalSystem account. I even gave to the Oracle client folder installed on my machine Full Control permissions for IIS users but this should not be needed because of LocalSystem account.
Anyway I tried and nothing. It is always the same error.
What could be the reason ?

404 error when accessing WCF Rest service hosted in ASP.net on Windows Server 2008

I have a WCF Rest Server hosted in an ASP.net Application. It was set up using the simple RouteTable setup in global.asax. ON my development machine with IIS 7, it works perfectly, but when I deployed to A windows Server 2008 machine with similar IIS settings, it does not work, I get a 404 error when my ajax methods tries to access the service. I was wondering if WCF is able to be hosted like I have on my development machine on an actual production server? If so what must I do to get it to work.

turns out from careful googling it turned out to be a missing attribute on system.webserver modules section: runAllManagedModulesForAllRequests="true"
Source:
http://www.west-wind.com/weblog/posts/2011/Mar/27/ASPNET-Routing-not-working-on-IIS-70

In my case, it was even more simple!
The symptom was that all POST requests returned 404s.
I'd only just enabled IIS (via Programs and Features -> Turn Windows features on and off) on a new Dev machine that already had Visual Studio fully installed.
I had to enable .NET 4.5 for IIS (via C:\\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i) and then all was well.
It's confusing, because I had already set the IIS App Pool to run under .NET Framework v4.0.30319. There was no warning that I had to separately run regiis.

Why is IIS not serving aspx pages?

I'm deploying an ASP.NET application to Windows Server 2003 under IIS
IIS is serving html pages fine but I get a page not found when I try and serve IIS pages

You may need to "register" IIS for ASP.NET applications. As an administrator, run the command "%systemroot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i". In addition, you may need to convert your web site to an application through the IIS management console.

By default, IIS has ASP support disabled in IIS6.
A server running a member of the Microsoft® Windows® Server 2003 family supports application server functionality, with Microsoft ASP.NET as an option that you can enable when configuring the application server role. To deploy ASP.NET Web applications to a production server, you must be sure to enable the ASP.NET and Internet Information Services (IIS) roles on the production server before you distribute the application.
See here for instructions to enable it:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/9fc367dd-5830-4ba3-a3c9-f84aa08edffa.mspx?mfr=true

Other possible reason could be Web Service Extensions, where ASP.NET version could have been disabled. My other post here explains steps to solve this.

Make sure the right .NET framework is installed properly
Make sure the ASP.NET extension is enabled
Under website properties, ASP.NET tab, make sure the right version is set.

After having this same issue and trying all of the above without any luck. We reinstalled SP2 for Windows 2003 and this resolved our issue. I too have seen this problem resolved a few times with the other answers. Most of the time just reinstalling .Net 2.0 resolves the issue but not this time.

For future reference, this could also be the issue:
IIS on a Windows Server 64-bit can only to run in either 32 or 64 bit mode.
In short you need to:
1) run adsutil.vbs to enable 32 bit asp.net apps on win 64
2) re-register IIS calling aspnet_regiis.exe
3) re-open IIS Manager, go into Web service extension list and ensure ASP.Net version {2/4.xxx} (32-bit) is set to Allowed
(You might need to do Steps 2 and 3 for both Framework 2.0 and 4.0 if you want to run asp.net apps on both versions)
Full details are in the following link: http://support.microsoft.com/kb/894435

Another future reference in case this is helpful to anyone who used a similar path to mine.
My back end for the ASP.NET app was MySql not Sql Server, which for me meant having a mysql connector, the reason my IIS was not serving the .aspx file is because on my development environment I was using a different version of the MySql connector than the one installed on my production environment, I updated the MySql connector on the production server to match the version Im using on the development environment and it worked great.

Resources