I am toothily new to server side and I want host a web service in my newly created windows server 2008 r2 virtual machine. however i cannot get it up there. I am getting errors after such as MIME type, sometimes files get downloaded, Permission errors, protocol mapping.
Therefore, I would like to know how to host a WCf Application from the begining. Thanks in advance
Here are excellent guides you can refer to host a WCF service in Windows Server 2008 R2:
http://broomandan.blogspot.in/2011/04/how-to-configure-windows-server-2008-to.html
http://blogs.technet.com/b/meamcs/archive/2014/02/16/wcf-service-manual-deployment-on-windows-server-2008-r2.aspx
Related
I am trying to deploy a simple HTTP API app on an Window Server 2012 and it's not working. The app is accessible internally (I can ping it within the server) but NOT externally. What do I need to do make the API server accessible via network? I disabled the firewall so it's not a firewall issue. I would usually use Linux, but I don't have a choice but use Windows this case. Please help!
I solved it by installing IIS and use it as a reverse proxy. So when a http request comes in from the internet, IIS it takes it and forwards it to my web app.. I am not sure this is the right way or not, but if it is, then it's pretty stupid as my web app should be accessible directly which would have been the case if I were using Linux.
I want my SP 2013 cloud app (office 365) to connect to my on premises WCF services. Visual Studio gives templates to create provider hosted apps for this purpose. However, that requires Windows Azure service bus connector that helps the app connect to WCF. Since I have a static IP, I want to get this done without the connector.
I attempted this by implementing IRemoteEventService in a new WCF with wsHTTPBinding with security as none. This is running on static IP machine with all connections allowed on the port where this service is listening. I was able to call this service from my test WCF client over the internet.
Now in my app, I changed my end point to this WCF service. When app installs it tries to call this end point to deliver the app install event. However, it gives error that end point is not available or there is a soap error.
Please provide pointers on what changes are required in WCF configuration to receive calls from SharePoint. Thanks.
I'm using visual studio 2008 to create custom reports. But I've always getting the same mistake...
The remote certificate is invalid according to the validation
procedure.
---------------------------- The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
---------------------------- Metadata contains a reference that cannot be resolved:
'https://srv-crm/myCompany/XRMServices/2011/Organization.svc?wsdl'.
My site has multiple IIS bindings so I've tried the following. But still nothing and I got a 404 error instead.
CRM2011 is configured on two separate servers (separate sql server + client side) and I'm tring to access to the service from a test server.
What else could I check?
Any help would be welcome !
For those having troubles like these accessing the soap web services and using a https protocol, we managed to solve the issue by configuring the RTM CRM 2011 deployment with Claims based authentication and IFD access thanks to this tutorial.
Hope it will help some of you !
I have a web service and I throw a soap exception. If I host it on Azure I got a different faultstring , if I host on dev fabric I got a different fault string. Why are they different and how can I control them?
The Visual Studio Development Web Server is different from the IIS 7.5 web servers that are used in staging and production, I'm guessing that this may cause your SOAP faultstring to differ in your scenario. More info here http://msdn.microsoft.com/en-us/library/58wxa9w5.aspx
For testing purposes, I'm trying to run a number of client applications connecting to a server all on the same host machine.
The host machine is running Windows 2008 Server Standard 32-bit with Service Pack 2.
On my XP development machine I installed the Microsoft Loopback Adapter in order to run multiple clients connecting from separate IP addresses. My LAN network is 192.168.1.xxx and so I chose 192.168.5.xxx for the loopback adapter addresses.
On my development machine, everything works fine and I am able to see the client applications binding to the loopback adapter using TCPView.
When I try and run the same setup on the Windows 2008 server with the same settings, the client applications are unable to bind to the loopback adapter addresses. There is no activity in TCPView and so I believe there's possibly some configuration setting I'm missing in setting up the loopback adapter.
Can anyone help?
Thanks!
Nick.
Ok, problem solved. I was specifying that the client connect to 127.0.0.1 but when I asked it to connect to a 192.168.5.x address it worked. The server was bound to 0.0.0.0 which suggests that it should still have been bound to 127.0.0.1 anyway but it just didn't seem to work!