I am trying to publish a WCF service to IIS in Windows 8 using Web deploy. The publish process is failing with the following error:
Web Deployment task failed. There was an error reading IIS configuration schema from 'C:\windows\system32\inetsrv\config\schema
Yes, I am running VS2010 in admin mode.
Thanks for your help.
This is a known issue when using WS2012 with Windows 8 and IIS 8
http://support.microsoft.com/kb/2735834/en-us?fr=1
I`m migrating to VS2012, let`s see if this really solves the issue.
Related
Remote debugging an Azure App Service is failing due to the following error message:
I have both 64 and 32-bit remote debugging tools installed. The deployed application is an asp.net core application compiled in Azure Devops using Any CPU.
Any ideas?
You should change Platform in General settings in App Service Configuration from 64 bit to 32 bit
link to screen of setting
I have created a simple web API using .Net Core and trying to publish it to IIS. But getting HTTP 500.
I followed https://docs.asp.net/en/latest/publishing/iis.html article and did exactly whatever mentioned in that.
I Installed only https://www.microsoft.com/net/download as
DotNetCore.1.0.1-WindowsHosting.exe OPT_INSTALL_REDIST=0
NOTE : I am able to deploy and access MVC application successfully but cannot access WebAPI application with the same steps.
In the IIS logs i am seeing below error.
Failed to start process with commandline '"dotnet" .\Project-1.dll', ErrorCode = '0x80070002'.
I am using the default web api template provided in Visual Studio 2015
am i missing something. Is WebAPI deployment is different to MVC app deployment w.r.t .net core ?
When you install the .NET Core Windows Server Hosting bundle, it won't restart all of the IIS processes if IIS is currently running. This is a good thing, since on a production server you wouldn't want them just to restart, but it would be nice if it was made a little clearer. First, check your System (not User) PATH variable to ensure that the path to Dotnet is there. Then, go into services and restart the Windows Process Activation Service. This will restart all of the IIS bits and get it to update the path. Once you've done this, IIS should serve up your .NET Core app just fine.
I am using
msbuild D:\SVN\QM\QMsln\QM.sln /p:DeployOnBuild=true;PublishProfile=Prof.pubxml
where publish prof Prof.pubxml deploys the web app in my local machine.
It works fine. But now I want to deploy it on remote server. I created a ftp server in my remote machine. And while I tried publishing using VS2012. It throws an error
FTP Passive mode is not available
I googled the issue and inserted
<FtpPassiveMode>True</FtpPassiveMode>
in the Prof.pubxml. But still the problem persists.
Also If I use msbuild it says
This specific web publishing is not yet supported on msbuild command line.
Any idea?
Hope somebody can give me some info regarding this.
I have a silverlight web app (.NET 4). I would like to use msdeploy to deploy it to IIS 7 running on a Windows 7 64 bit machine.
I have read many pages and have tried a lot of the steps in them so far but am still struggling.
What I have done:
1. Installed Web Platform Installer.
2. Installed msdeploy
3. Started and set to automatically start: "Web Deployment Agent Service" and "Web Management Service"
4. Created a web site in IIS 7 and set permissions.
5. Tested the website "http://server/page and get a blank directory browsing because nothing is added yet.
So now I would like to deploy but am getting an error : "No connection could be made because the target machine actively refused it:10.224.201.117:8172
I have tested telnet'ing to the address on port 8172 which fails.
It is suggested that msdeploy is not configured correctly and I need to Enable Remote Connections. However it does not seem that Windows 7 IIS 7 has the icons in IIS to do this. (No "Management Service" option under add / remove features of IIS)
Does this mean i can not deploy to Windows 7 IIS 7?
Or is there another way to enable remote connections, perhaps using powershell?
Any help is greatly appreciated
Tx
Neill
I am trying to publish an MVC 2 application to my local Win 7 IIS 7.
The app pool is Integrated 2.0, not classic.
The app is .net 3.5.
The project was originally started in VS2008, but I have upgraded to 2010.
I publish the app through the VS wizard to a file location, I have also tried publishing again in VS, but web deploy to localhost - neither makes a difference.
The app spins up fine when I just hit F5 in VS and work in debug mode.
Any ideas? I have googled about, but nothing has sorted it.
Thanks in advance.
Did you make sure the AppPool is set to allow 32bit apps?