.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

WCF discovery (AdHoc)

Posted By:      Posted Date: May 22, 2011    Points: 0   Category :SharePoint


I set up the discovery pattern for my service but it discovers only the service on the same computer. We are in a domain in the same subnet and the discovery is not working if the service is host on another computer than mine.

Is the AdHoc discovery working with such configuration? Computers have no firewall activated and if I test with the WCF Test Client, I can invoke any methods of the service.



Adrien Pellegrini.

View Complete Post

More Related Resource Links

Foundations: Discover a New WCF with Discovery


Juval Lowy explains how the industry-standard discovery solution enables clients to discover available addresses for WCF calls at runtime, and he provides tools and helper classes to simplify the process.

Juval Lowy

MSDN Magazine January 2010

WS-Discovery match probe response with uuid

Hello, I am trying to make a service beeing discovered by a client which is not .NET based. I could configure the server based on .NET 4 to receive the probe message properly, but the probe match reply is not as the client expect it to be. The reply look like this: <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <s:Header><a:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/04/discovery/ProbeMatches </a:Action><h:AppSequence InstanceId="1175946188" MessageNumber="5" xmlns:h="http://schemas.xmlsoap.org/ws/2005/04/discovery"/> <a:To s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</a:To> <a:RelatesTo>uuid:1f969bbc-4d9e-4151-ad7e-60bd7fa15a9a</a:RelatesTo><a:MessageID>urn:uuid:43fefd16-83ec-4f5a-a8ef-ad65f8e9cce4</a:MessageID> </s:Header><s:Body><ProbeMatches xmlns="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> <ProbeMatch><a:EndpointReference><a:Address></a:Address> </a:EndpointReference><d:Types xmlns:d="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns

WCF Discovery/Announcement using TCP and app.config problems

All, I have been using managed discovery for a while now doing all of the configuration in code.  I have been trying to port this to use app.config for the additional flexibility it provides.  I am having serious issues when it comes to discovery / announcement.  As can be seen from my code below, I am creating an Address and Binding and handing it to the DiscoveryEndpoint / AnnouncementEndpoint.  I am not quite sure how to do this in code.  All of the examples use some form of UDP broadcasting, and I'm just curious how I go about doing this using TCP. Here is the code:  private MyDiscoveryProxy _discoveryProxy;         private ServiceHost _discoveryProxyHost;         public void Start(IServiceController serviceController)         {             // Host the DiscoveryProxy service             _discoveryProxy = new MyDiscoveryProxy(serviceController);             _discoveryProxy.OnlineServiceAnnounced += new Action<IAmsServiceInfo>(_discoveryProxy_OnlineServiceAnnounced);             _discoveryProxy.OfflineServiceAnno

AppFabric + WS-Discovery

Hello I would not present a problem and if this forum is the right place. If not I would support to address coorectament. I am currently developing a new system, along with the team to work. Rather use existing technologies, SQL Server 2008 R2, ADFS2.0, II7.5 AppFabric Windows 2008 R2 Visual Studio 2010, etc.. The solution divides the business through WCF services are hosted in IIS 7.5 and managed to AppFabric. The services are enabled to start automatically. Have discovery protocol (udpDyscovery) and its extreme enabled. We created a mini application to test the service discovery and the results are the following: If the run on the host, works fine, the service responds to UDP port 3702 packets. If the client does not run a station responds. We did not know if UDP packets from reaching the server. To check this, we created an application that captures the packages with the library PCAP.Net (Pcapdotnet.codeplex.com) and we run on the server. And yes, the packages arrive. But also when the application is running, the service also responds to requests for discovery (probeMatch) that makes the client station. What makes the application acting as sniffer plate is put in promiscuous mode network card. The server is virtualized with vmware 4.0 (vsphere). Can anyone find the answer to this? Thanks.

Service Registry, UDDI, WS-Discovery ... slippery slope ?

Hi, i work for a retail company, we are starting to make some internal software in. NET and of course using WCF to 'connect' applications, we have still a very long way to a SOA architecture but i am doing some deep researching on the path to SOA.   One thing i dont see a good solution is in how to implement some service registry, for human and software access, at this point of my research im not looking for a ESB or some robust and powerfull (and complex) middleware for services architecture, currently i want to publish services with associated documents for human acess and of course for client access, my initial requirement would be given a contract (Interface) determine a service endpoint based on parameters such as network response, debug/production, service quality, transaction support, etc. with this i start looking and of course first go to see UDDI, i use for research Windows Server 2003 and Windows Server 2008 and both gives me UDDI as a component of the OS, so i was happy to there, but i start read some microsoft documentation i began to doubt, the docs are poor for msdn standar, refers some requirements in terms of Netscape navigator... supports API v2.0 of UDDI and frm 2005 there is v3....   plus trying to use the UDDI wasnt very easy for an IT manager people, i have some gap between WCF services and the UDDI model, not easy to close... doing some more research i

WCF discovery finds the endpoint but the address is localhost

Hi,   I have a wcf discoverable service called "GetNameService" which is hosted on a PC @ It is hosted with wsHttpBinding and is discoverable thru' UdpEndpoint. I also have a client @ which discovers for such services in the same network. When I ran the client, I am able to discover the service but the end point of the service discovered is having localhost in it. How can this happen, please help me out in this.   Some more information,   App.config used <?xml version="1.0" encoding="utf-8" ?> <configuration> <system.web> <compilation debug="true" /> </system.web> <!-- When deploying the service library project, the content of the config file must be added to the host's app.config file. System.Configuration does not support config files for libraries. --> <system.serviceModel> <services> <service name="NameService.GetNameService"> <host> <baseAddresses> <add baseAddress = "" /> </baseAddresses> </host> <!-- Service Endpoints --> <!-- Unless fully qualified, address is relative to base address supplied above --> <endpoint address ="" binding="ws

Error in Adhoc report MDX query


Hi Experts,          

Now i have another issue the Following MDX query is working fine in MDX query analyzer.


call SQLQuery.ExecuteSql(
    "Provider=SQLNCLI10.1;Data Source=TMDEVDWHSRV01;Integrated Security=SSPI;Initial Catalog=BankingDWHStg"
    ,"Exec DecryptPANKey 1")


SQLQuery  means Assemblyname



but in Adhoc report i want to use with select statment for the above MDX query.


In Adhoc report MDX is not supporting the above query


call SQLQuery.ExecuteSql(
    "Provider=SQLNCLI10.1;Data Source=TMDEVDWHSRV01;Integrated Security=SSPI;Initial Catalog=BankingDWHStg"
    ,"Exec DecryptPANKey 1")


Please help to use the above query in ADHOC report MDX.



adhoc reporting - data doesn't refresh on date range change


I created an adhoc report model using SQL Server 2008 reporting services. I am using data from a SQL 2000 database sitting on a SQL 2000 server. I created reports with start date and end date parameters, everything worked fine.


Now my ad hoc report model uses a SQL 2000 database (this database is a replication of the database I was using)  sitting on a SQL 2008 server. When I change parameters like start date and end dates, data doesn’t refresh. It shows the same data for any date range.


Has anyone seen this problem? What could be done to fix the issue. Is there any setting on the SQL server to fix this?



Showing #Error in SSRS adhoc report


Hi ,

Im facing one issues by using Varbinary data type field in ssrs adhoc report.

While running it is showing as #Error in the adhoc report.

Pls help me how to solve.







WS-Discovery and encryption


I would like to encrypt the WS-Discovery information that is being sent out.

I am currently only using NetTcp for the protocol on the service, and have all the clients connecting up to it.

For the security on the service, I use client certificates.

Each client also has a our top level certificate installed so chain certificates work.


what I would like to do is encrypt the WS-Discovery info using the top level certifcate.

I would like to do this so anyone sniffing on our private network can not just see the info and be able to try and connect.

how to use parameter in SSRS adhoc report



 Im using the following statement in Adhoc report data set

call SQLQuery.ExecuteSql(
    "Provider=SQLNCLI10.1;Data Source=DevSRV01;Integrated Security=SSPI;Initial Catalog=BankingDWHStg"
    ,"Exec PANKey 1")


SQLQuery - SSAS Assembly name

PANKey- Sp name


When i use the above statment in SSRS adhoc report data set. Here i was not able to use the parameter binding with the above statement.

Any one pls help me how to use the parameter value in  above statement.






WCF Architecture: AppFabric Service Bus Discovery


Learn how to roll your own discovery mechanism as we walk you through a small framework the author wrote to support discovery over the service bus, bringing it on par with the built-in support for discovery in WCF.

Juval Lowy

MSDN Magazine October 2010

Providing multiple Managed Discovery Proxies... Avoiding single point of failure


I have created a service with multiple discovery proxies, hoping that if one of them is offline the other one will do the job.


     Uri announcementEndpointAddress = new Uri("net.tcp://app1/Discovery.ServiceActivation/DiscoveryService.svc");
     AnnouncementEndpoint announcementEndpoint = new AnnouncementEndpoint(netTcpBinding, new EndpointAddress(announcementEndpointAddress));

     Uri announcementEndpointAddress2 = new Uri("net.tcp://app2/Discovery.ServiceActivation/DiscoveryService.svc");
     AnnouncementEndpoint announcementEndpoint2 = new AnnouncementEndpoint(netTcpBinding, new EndpointAddress(announcementEndpointAddress2));

     ServiceDiscoveryBehavior serviceDiscoveryBehavior = new ServiceDiscoveryBehavior();

     // add the discovery behavior at the service with the proxy address 

However I noticed the service will not host unless both Discovery Proxies services are running. Is this normal? how can do that multiple registry proxies can be susbcribed, and if one of them is down the other takes over.

I don't want to start using an NLB for this...

what is the best approch

SSRS AdHoc model project: Entity Name - lable problem



I have created AdHoc model project. I have few entities, designed as parent-child (to handle one to many and many to many relation)

Parent1 has Child_Entity11, Child_Entity12, Child_Entity13 and

Parent2 has Child_Entity21, Child_Entity22, Child_Entity23 and

Parent3 has Child_Entity31, Child_Entity32, Child_Entity33.

Parent1, Parent2 and Parent3 are connected to each other but not the other parent's child directly.


Now, when I deploy this model to report server and access in Report Builder 2.0, it looks good when nothing is on report design. but when I drag one field and when it will filter entity list and show only related entity only. then it's Child name label are not populating correctly. It is showing Child2, Child3 instead of ChildEntity11 or ChildEntity12.

Any help would be appreciated!

Discovery on IIS hosted WCF service no endpoints found untill site is visited


I have a problem which makes the whole discovery (.net 4) idea useless.
I got self-hosted wcf services with discovey working so I now at least something about it, however, when I create a website with a .svc file, configure the web.config well and host it in IIS something goes wrong.

I have my windows forms client program to test the discovery and it doesn't return any endpoints, not after iisreset, not after checking twice, tree-times with long timeouts. I have to manually "visit" my .svc file in the website by browser to kind of activate it and than my client recogizes it immediately.

Because you have to visit the service first, you already have to know what the url is and makes discovery pointless in this case (and I need it so much)

What can I do about this?

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend