I have created WCF service and hosted it on remote server. i am able to browse the said service from remote as well as on my local machine (firefox)
But when i copy the same url and say "add service reference" to my vs 2012 project file it gives me error
You may want to check the MSDN link. I had a similar issue and it turned out that I wasn't having the right Handler Mappings in local IIS.
Extract from the above link:
If you installed IIS after Windows Communication Foundation (WCF) was installed you must run the following command.
"%WINDIR%\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe" -r
This registers the required script maps in IIS.
Related
**Hi Guys I just Cloned my project from a repository.
I am getting this Similar error
The Web Application Project […] is configured to use IIS. The Web server […] could not be found.
I do have IIS Manager on my pc. one of the solution is to set True on my cs.proj file but when i do it auto imports a port number. when i try to run the application with that port number the application hangs(load forever).
What are possible ways to solve this error ?**
Just to register an answer for all getting into the same problem under the same scenario, as we discuss and resolve it from the question's comments:
Ps: as i said this solution works for this particular scenario, maybe anyone else has to apply a different approach!
In this case, try to follow the below link for other solutions!
The Web Application Project [...] is configured to use IIS. The Web server [...] could not be found.
Reset the IIS; (https://learn.microsoft.com/en-us/visualstudio/debugger/error-the-web-server-is-not-configured-correctly?view=vs-2019)
Publish the project;
Add it to IIS Server;
Run it using IIS Local (not the IIS Express)
I'm trying to get to grips with Google Cloud for a University Project.
I have created a .NET Google Cloud project on VS 2019 and I'm trying to deploy it to my Windows 2016 server on Google Cloud Platform.
However I keep getting the error:
D:\Program Files\Microsoft Visual Studio\MSBuild\Microsoft\VisualStudio\v16.0\Web\Microsoft.Web.Publishing.targets(4284,5): msdeploy error ERROR_DESTINATION_NOT_REACHABLE: Web deployment task failed. (Could not connect to the remote computer ("35.235.58.62"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started.
What I've tried so far:
Checking server's firewall is open for inbound 8172
Disabled home PC firewall to make sure that wasn't the issue
Installed Web Platform Installer on the server
Added ISS Management Service through Web Platform Installer
Enabled remote connections on ISS
Any advice or help on the solution would be greatly appreciated.
Have you installed web deploy on your remote server?
Remote deployment also rely on Web deploy Agent service or Web management Service . Please ensure they have been started. Then you could check whether port number has been opened by making test with Tcping.exe from remote server.
The link provide the steps about how to publish with Management service from remote server：
Web Deploy from Visual Studio 2012 to a remote IIS 8 server
Just remember to set firewall rule like this:
Please ensure port 8172 has been enabled in both windows firewall and Google cloud external firewall.
If the management service is not working, you could try remote agent
https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-remote-agent
The second part from Jokies Ding got it to work for me. (I'm unable to leave a comment on his post due to my stackoverflow reputation points not being 50 yet) I feel like I correctly followed google's instructions for getting web deploy to work with visual studio, but I was unsuccessful.
This below worked for me.
If the management service is not working, you could try remote agent
https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-remote-agent
Following the online steps from google instructions to setup web deploy it should be something like this:
install web deploy
add user to IIS Manager Permissions
[skip] check google's firewall rules (VPC network>firewall rules) port 8172 (this won't be necessary since this remote agent route uses port 80)
start using https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-remote-agent
(this is from step 5 instructions) add server name as host name in Site Bindings
(this is from step 5 instructions) ensure "Web Deployment Agent Service" service is running
configure visual studio publish profile using attached screenshot example (I was unable to get "Visual Studio > Build > Publish [Project Name] to Google Cloud..." to work.)
When you install Web Deploy, make sure to select Custom Setup and check all components. This is what solved the issue for me. IIS Deployment Handler wasn't selected
Source: Could not reach the Web Deploy endpoint on the specified virtual machine
i have a piece of C# code and I need to publish that so that I can get an URL which will be passed to another team for integration.
My problem is I have no access to Inetmgr due to some admin access issue.
how can I publish my web app remotely(on to my peer system )?
Using WebDeploy.
It's an IIS add-on which opens a Web service to publish a Web site remotely.
Visual Studio and TFS Build can publish sites using WebDeploy, and you can also deploy using the command-line interface.
I am new in Office Apps. I just want to create a hello world in Outlook Web App (OWA). I've created a new Project in VS2013. File -> New Project -> Apps for Office -> Mail. When I want to debug I get the following exception:
The AutoDiscover service couldn't be located.
Do I have to configure in Visual Studio the IP Address of my Exchange Server?
Can I debug without the AutoDiscover service ?
Yes, you should register with your Exchange server.
When you hit Debug, it will show a screen to you where you specify the Exchange server. You need that since it installs the app in Exchange and executes it from there. Your app won't run without it.
So the bottom-line is: you need a working Exchange server with AutoDiscovery on.
I have a web service project and simple test application. I can debug the web service from Visual Studio 2008. However, there exist a real client application, but it is on another machine. ASP.NET Development Server does not allow connections if they are not from localhost, or so it seems. Is there a way to debug a web service, if client application is on another machine?
Edit
The tool that I used is Trace Utility from Microsoft SOAP Toolkit. Further explanation can be found here (works on XP; see continuation story for Windows 7 solution). There was problem with it though. My remote client fetches the WSDL first, and then creates URL based on values in soap tags found at the end of WSDL. So client gets redirected to localhost, which is not good.
I found my problem though, but I'll leave the question open until I find the time to try debugging via IIS.
Install a virtual directory into the IIS on your local machine. If you don't have IIS, install it. Once IIS is installed and configured on your local machine, you should be able to use either the IP or create a dns alias for that IP to access the web service that way.
I'm using SoapUI basic version to fake the SOAP requests to the web service, which is running in debug mode in Visual Studio, from the local computer.
You can use IIS (or Cassini Web server) - for debugging, attach VS 2008 to correct process (for example w3p.exe(IIS6 or greater) or aspnet_wp.exe(IIS 5)).