I create a service fabric application on my local development machine with 3 statless services, one of the service (Service1) has an endpoint with a static port assigned , Service is a .net core web api hosted using kestrel
After deploying the application to my local cluster , I am not able to acess this service using the following URL
http://localhost:8641/api/values
but I can access it using the reverse proxy url
http://localhost:19081/ServiceFabricApplicationName/Service1/api/values
Any ides why I cannot reach the service with first url ?
Related
I just created a WCF service and deployed in one of the machine's IIS and checked it works fine.
When I deploy the same service on Cloud VM's IIS I am not able to consume that service.
I am getting the error saying that "There is no listener with the endpoint".
Can i deploy normal WCF on cloud or do i need to create WCF cloud service?
Environment(IIS 8.5)
It could be several Things, most probably:
ASP.net not activated on IIS
Also check:
The url you are using
firewall problems
site not started
I am hosting WCF services in a console application and i am trying to use the same endpoint address configured in the service config file in my host application. But when ever i am trying to run the application i am getting AddressAlreadyInUse exception because of WCF Test Client is consuming those ports. So i wanted to disable automatice hosting in the WCF test client while debugging self hosting.
I tried disabling WCFTestClient.exe startup through project property section but still it's not working.
Have a look of the snapshot:
I have an external (public) website developed in Silverlight. The Silverlight app currently calls http based wcf services hosted in IIS.
I am now having to call a wcf service with net.tcp binding hosted in a different app server. I have the net.tcp wcf service hosted in a windows service on port range 4502-4530 and with an interface to expose clientaccesspolicy.xml file as part of the service. I am able to invoke this service from my Silverlight app in the web server. I want the SL app to make direct call to net.tcp, rather than routing the call to it from another http based service.
Question is will this work without any issues when exposed over internet.
Client browser --> IIS webserver with Silverlight website --> App Server with wcf service on net.tcp.
I am assuming in this case, from XAP SL would try to make direct call to the app server service using net.tcp ?
The communication between the web server and app server could be opened up for ports 4502-4535. But I am wondering what about the client. Does this setup require the ports to be available even in the clients machine (with browser)?
Any insight is much helpful.
Thanks.
Take a look at http://support.microsoft.com/kb/2425652; there is sample code included as well! If you setup clientaccesspolicy.xml correctly; it should work as long as clients can access your TCP server.
If your clients are behind some firewall which is blocking your server's ports; they may face connectivity issues!
I have successfully deployed my WCF restful web service to IIS 7. I have verified that my service is working when I call it from a browser in IE via a something like "https://myserver/mservice.svc/postuser/JohnSmith" . The method is a POST and I have verified that my IIS configuration allows for POSTS.
My issue is as follows. We are using a 3rd party Software as a Service application that allows for external web service calls. It allows you to configure the URL "https://myserver/mservice.svc/postuser/" and then you can choose a parameter. When I call the web service from the external application, a 404 error is registered in IIS.
I think there must be some difference between the way I call my webservice "https://myserver/mservice.svc/postuser/JohnSmith" and the way the SAAS application is calling my external web service. The web service is attempting to pass the username, but I cannot detect how it is constructing this.
Do I need to write a web enabled front end for my web service that is hosted in IIS that can handle XML? I'm assuming this is how the SAAS application is trying to pass the username onto my web service.
Thank you all in advance for your ideas and help.
I have created a WCF service which is deployed on my local machine. This service exposes one method which start/stop a windows service on my local machine.
On the remote machine I have created a client that consumes the WCF service. When I try to invoke the method which start/stop service exposed from a WCF service , I get InvalidOperationException . I found that this is the Security issue.
Also when I do the same operation (start/stop windows service) on the local machine it works!!
The WCF service is hosted on IIS 7.0 which is using basichttpBinding. Also Anonnymous access is checked. I have also added <identity Impersonate = true > under the web section in the web config file but still no success.
Please help!!
You set impersonation for ASP.NET. Impersonation in WCF uses its own infrastructure. Moreover in WCF client has to allow service to impersonate his identity. Check this simple example.