I have a WCF application which was working perfectly fine until recently when we introduced some SSL related settings and certificate requirements into our application. As soon as we turned out the SSL following started happening:
When I launch the service using my Visual studio it launches fine without any errors and With Https in the URL
As soon as I click on WCF URL to see the WSDL, it fails with SSL connection error.
Browser does not provide any more information on this. I have also installed WCF Trace utility and it traces most of the errors correctly BUT not this one(probably because it does launch the application fine but fails when we try to launch the WSDL)
Any suggestions on a good tool that can help me debug SSL errors any better?
One thing I found very very helpful while working with WCF in general is using Idiagnostic module. It does not relate to any specific SSL related issues but it helps debug issues in general
Related
I'm using the automated help files and when I build and debug locally they work fine.
When I do a publish to a remote IIS server, instead of the working full api documentation, I get this:
Introduction
Provide a general description of your APIs here.
GETPOSTPOSTPOSTDELETEGETGETPOSTGETGETGETGETGETPOSTDELETEPOSTDELETEGETGETPOSTDELETEGETGETGETPOSTGETGETGETGETGETGETPOSTDELETEGETGET
When I started the project, the remote deployed help files worked fine, and I have no idea how they broke. Any tips on where to look would be really appreciated.
Note: The rest of the webservice works exactly the same, all of the api calls work locally and deployed. it's only the help that is broken.
I was trying to create azure mobile service from VS 2013, 2 issues I am facing.
Host in cloud option is disabled.
Getting error on click of Validate connection while publishing the project. error thrown there is "Destination is unreachable".
Log I have extracted from output window is :
Error ERROR_DESTINATION_NOT_REACHABLE: Web deployment task failed. (Could not connect to the remote computer ("****.scm.azure-mobile.net"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.)
I have attached screenshot you reference. Please check.
gone through similar question : Not able to publish website on Windows Azure using publish through VS2010
didnt helped though.
Can anyone help me to resolve these issues..? Appreciate the help.
Regards
Ravi Bhat
I encounter this error as well.
I tried changed two things and it works, yet now I don't remember which one is the root cause:
use https instead of http for the server address and destination URL
My company has proxy settings for all internet access, I change to the other WIFI without any proxy. So check your internet connection.
You could try this, but I'm not sure if it works.
I've read numerous posts on this, but none help at all...
My situation is actually very similar to others, however, it only affects me when I'm trying to debug locally. When using my actual PROD service, the Reference.cs file gets generated fine.
I also tried running the client under the VS development server and on Local IIS Web Server using IIS Express.
No errors occur during generation of the proxy and I have triple verified that my DEV client matches up to my DEV service.
If anyone has any solid ideas on how to resolve this, I would appreciate it since it is preventing me from debugging locally with my service.
I created a WCF service. It uses MySQL Connector to connect to a MySQL Database. The consumer of the service is a Windows Phone app.
On my computer everything works great. But if I publish the WCF Service (on the web or on localhost), and try to use it from the phone application, it generates an error
"The server was unable to process the request due to an internal
error."
By testing I found out that the error comes at the line connection = new MySqlConnection(ConnectionString); On my laptop everything worked (when I debugged the project), I tested my WCF Service and it perfectly accessed the database and did everything well. Again, when I publish at localhost or on web, accessing the service causes an error.
I published the log file here.
What is wrong? What can cause this problem?
Finally, I found what was the problem.
This question helped a lot. It turned out that the problem was with MySql.Data.dll. It must be copied locally (by default that property is set to false). Without that, the program doesn't find the library and throws an exception. So I needed to change the setting to 'Copy To Local = true'
I have a C# web service that I am trying to debug in Visual Studio 2008, and when I try to run it, Internet Explorer pops-up as expected, but it just displays 'waiting for response from localhost...' in the status bar. I have left it running for a few minutes and it never responds.
I have other web services that I am able to debug fine, is VS2005 and 2008. The problem web service is impersonating a different identity in the web.config file, but I have no problems with this same user on a different web service (in VS2005).
Does anybody have any ideas on what might be preventing it from starting up? Interestingly, a colleague has the same problem with a web service that IS working on my machine, even though we are working with identical code. Something must be configured differently...
By the way, I've noticed that the 'Temporary ASP.NET Files' folder is missing from both
C:\Windows\Microsoft.NET\Framework and C:\Windows\Microsoft.NET\Framework64... I certainly haven't deleted them, and other web services debug okay, so is this just a red herring?
We are also on a domain which has its own firewall (outside of the developers' control) - could this be blocking it?
EDIT: I have just removed the user impersonation for a quick test, and it worked. So there must be something about Visual Studio 2008 that does not want to run when impersonating THIS particular user. Any ideas what configuration I would need to change to correct this?
I have had the same issues with impersonation; I don't know if Cassini (the built-in VS web server) supports this properly. About the best advice I can give is to either use Local IIS with an app pool running as your impersonated user or to attach your debugger using remote debugging to a remote IIS server.
I believe using Local IIS will attach correctly & automatically if configured as much in the Web tab of Project Properties. You'll have to run VS as an admin to get the virtual directories setup automatically by VS in IIS.