Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Error referencing a WCF Service from custom moduleError referencing a WCF Service from custom module
Previous
 
Next
New Post
7/28/2009 7:22 PM
 

I have a custom developed module/user control, that uses a service reference from the business controller layer.

I created a customer module definition, and when I go to add the module to a page I am getting the following error:

Could not find default endpoint element that references contract 'NetService.INetService' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element.

I placed the system.servicemodel section in the webconfig, but not quite sure if anything else is missing. I was also wondering that is the ascx files are placed under "Desktop Modules" and the dlls are placed in the "bin", where exactly should it be looking for the client configuration section?

Please advise, as this issue has consumed my entire day. Thank you!

 
New Post
7/30/2009 10:12 AM
 

I think it might be helpful to state that it is DNN version 4.9.1.

I just want to verify that the system.servicemodel section should be in the web.config, or if there are additional config modifications that need to be done.

 
New Post
1/10/2011 7:44 AM
 
I am facing the nearly same error

An error occurred while receiving the HTTP response to http://www.mysite.com/service.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
 
New Post
1/10/2011 8:39 AM
 
Have you seen Steve Fabian's blog serries on WCF services and DotNetNuke?

http://www.gooddogs.com/Blog/tabid/97...

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Error referencing a WCF Service from custom moduleError referencing a WCF Service from custom module


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out