In VS 2013 I have my first WCF web service, the web service is functioning correctly as a Class Library, when I attempt to ready the application to deploy as a managed windows service I modify the output type to Windows Application. Running the application in the test client provides the error:
Error: Cannot obtain Metadata from [SERVICE URL OMITTED] If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. For help enabling metadata publishing
I think that is about the endpoint of your service.
Check this answer and maybe you will be able to find the answer here:
Error: Cannot obtain Metadata from WCF service
I hope this helps
Related
I am revising .NET and web services and attempting to test calling the web service I created with a WPF desktop application. The web service builds and runs fine and when I start without debugging in VS Community 2017 it works as expected and I can see the web service end points in the browser along with the WSDL. But when I attempt to add a WPF desktop application and start without debugging to the browser does NOT have the .asmx file in the URL anymore and states -
HTTP Error 403.14 Forbidden
the web server is configured to not list the contents of this directory
I have googled this error and tried several of the suggested fixes but none of them have resolved the issue. Can this be done at all or do I have to publish the web service to IIS Express on its own and have the WPF desktop application on its own? Its just that it would be very useful to have a desktop application within the same solution to code and test
I am new to IIS and Silverlight. I followed this tutorial to create a web application using Visual C#2010 and IIS 7.
The application is working perfectly when in visual studio using IIS express. When I deploy to Local IIS it shows this error:
CommunicationException was unhandled by user code. An error occurred
while trying to make a request to URI
'http://localhost:55826/WebService1.asmx'
This could be due to attempting to access a service in a cross-domain
way without a proper cross-domain policy in place, or a policy that is
unsuitable for SOAP services. You may need to contact the owner of the
service to publish a cross-domain policy file and to ensure it allows
SOAP-related HTTP headers to be sent. This error may also be caused by
using internal types in the web service proxy without using the
InternalsVisibleToAttribute attribute. Please see the inner exception
for more details.
How can I deploy a web app based on MySQL to IIS without encountering this error?
You need to make the service available across domains when deployed. For this, you need to add a crossdomain.xml and a clientaccesspolicy.xml files to your web project. You can find more details here : https://msdn.microsoft.com/en-us/library/cc197955(VS.95).aspx
I am currently trying to set up a WCF Data Service Client using Visual Studio 2013 Desktop. The following guide shows how to set it up as a console application, but every-single-time I try to add a Service Reference VS says:
Unable to add a service reference to the specified OData feed because
WCF Data Services is not installed for this target framework. To install
a supported version of WCF Data Services, see
http://go.microsoft.com/fwlink/?LinkId=253653.
Is there something I am missing or is it even possible? I've added and tried multiple different different References for the WCF data to no avail. Suggestions?
Though op question has been resolved, I am adding this answer so that it can help any other with the same problem.
The solution is to to download and install WCF Data Service RTM Tools as suggested in link provided by Microsoft in error itself.
More more details refer:
http://www.microsoft.com/en-us/download/details.aspx?id=39373
http://msdn.microsoft.com/en-us/jj658961
I am trying to access a windows application (which uses the .NET 2.0 framework) from the share folder. The application connects to a web service.
There is no proxy between the application and the web service (on either the remote machine or on the local machine).
When application tries to access any web method I am getting following error:
Insufficient permissions for setting the configuration section 'defaultProxy'.
I heard there was a hot fix from Microsoft but didn't find anything on the site.
Please suggest how to resolve the problem.
Can i consume WCF service inside windows mobile 6 project??
I spend many days to solve my problem of adding web reference of WCF to smartdevice project
but the smae error appears.
There was an error downloading 'http://localhost:8731/Design_Time_Addresses/WcfServiceLibrary1/Service1/mex'.
Unable to connect to the remote server
No connection could be made because the target machine actively refused it 127.0.0.1:8731
There was an error downloading 'http://localhost:8731/Desi
So i ask is it possible to consume WCF from windows mobile 6 project??
I create WCF and windows mobile projects in visual studio 2008 and when i "add web reference" to the mobile project to add the WCF and put the URL i get this error
"There was an error downloading 'http://localhost:8731/Design_Time_Addresses/WcfServiceLibrary1/Service1/mex'.
Unable to connect to the remote server
No connection could be made because the target machine actively refused it 127.0.0.1:8731
There was an error downloading 'http://localhost:8731/Desi"
however i change the "localhost" to my computer IP address the same error appeared.
How can i write the URL that will be put in the client application.
The important part of the error is "Unable to connect"
This means that the add service reference has tried to make a call to the service, but the call failed.
The most likely reasons for this are:
The service is not running
The metadata exchange (mex endpoint) is not enabled
It looks like you're trying to get the Mex, but the service isn't running on the dev machine:
Try going to this url in your browser
http://localhost:8731/Design_Time_Addresses/WcfServiceLibrary1/Service1/mex
you'll probably get the same error (machine actively refused it)
Make sure the service is started.