I have one old wcf developed with .Net Framework 4.0 and was hosted on Windows Sever 2012 R2.
It was working fine but after server upgrade to Windows Sever 2019, it is throwing following error:
An error occurred while making the HTTP request to
https://prod1-a1:8086/MainAuthService/Authentication.svc. This could be due to the fact that the
server certificate is not configured properly with HTTP.SYS in the
HTTPS case. This could also be caused by a mismatch of the security
binding between the client and the server.
IIS version is 10.
It is first time I am working with web service and I don't have clue. I don't have access to code but any help would be appreciable.
Finally I was able to resolve it by using full domain name with URL which has https.
https://prod1-a1:8086.pisc.com/MainAuthService/Authentication.svc.
Related
I am getting a ProtocolException when using a WCF Service targeting .NET framework 4.5 on IIS7.5 on a Windows Server 2012 box.
The remote server returned an unexpected response: (405) Method Not Allowed.
Any pointers to the problem would help as it works okay in Development env.
I can browse to the service's svc file in the browser but when invoked from a website on the same box, it gives this error.
I've been trying to install and configure dynamics AX mobile solution by following the instructions mentioned in the Whitepaper here
On page 12 where you can validate if your service is set up correctly by opnening the url: https://localhost/adfs/fs/federationserverservice.asmx
i get the HTTP error 503 saying that the service is unavailable. I even tried to open these URL: https://localhost/adfs/services/trust/13/usernamemixed, https://localhost/FederationMetadata/2007-06/FederationMetadata.xml but it gave me the same error message. The IIS application pool for the ADFS is running. The ADFS Windows Server is running.
The funny thing is that the "Workflow approval via email" is working.
The ADFS is installed/added through Server Manger on Windows Server 2012 R2.
Any idea how to solve this?
You should check the event viewer logs. You see the 503 error when there is a port conflict. Some other service is most likely using the same port, so even though ADFS says it has started, there is still a port conflict that you need to resolve. This is a great way to fix it:
http://social.technet.microsoft.com/wiki/contents/articles/2009.ad-fs-2-0-how-to-change-the-net-tcp-ports-for-services-and-administration.aspx
Hope this helps!
I have hosted a WCF service in my local machine(XP SP3) lets name as PushService, I am consuming this service in PushServiceClient. When I keep PushService project in running mode and try to push data from PushServiceClient I am able to Push the Data(DB is in another machine). When I stop PushService project in VS 2010 and Consume PushService hosted through IIS then I am not able to Push the Data.I am facing Authentication error during connect to DB. I am not getting where its going wrong.
IIS Version: 5.0
Permission in IIS : Anonymous Acess
Binding: WSHttpBinding(Tried Basic http also)
Security mode: None
Thanks in advance,
Manjunath
Does IIS worker process have permission for database access? Impersonating the host would solve your problem.
This is due to lack of Permisswion to acess the DB, If using IIS 5.1 then in coding set it to take Default credentials if its in IIS 6.0 (Windows server 2003) set it to take local Identity in IIS AppPool. I will get back with full details on it.
Thanks Guys for your reply.
Manjunath
I have developed a WCF Data service using VS 2010, I am able to run it and get the data as feed by running using VS 2010.
I published the service on IIS 5.1 but I m getting http: 404 error.
Can anyone help to deploy the service on IIS 5.1 step by step?
I found a bit on it here.
I am unable to browser the service which is hosted on IIS 7 Windows Server 2008.
When I hit the url http://myservice/service1.svc it throws an error.
Check to make sure you have framework 3.5 sp1 installed, after this go to Programs, add remove windows features, then make sure you have:
Microsoft .net framework 3.5.1
under that make sure both options are checked:
WCF HTTP activation, and WCF Non HTTP Activation....
If this still doesn't work update post a comment here....