Script task in ssis to consume wcf service

Question

0.00/5 (No votes)

See more:

Does anyone succeed in calling wcf service using script task in ssis?
I am getting error

Could not find default endpoint element that references contract 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.

Posted 30-Jan-13 1:08am

chanti143143

Updated 30-Jan-13 2:07am

ZurdoDev

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sandeep Mewara · Answer 1 · 2013-01-30T03:51:00

As mentioned here[^]:
"This error can arise if you are calling the service in a class library and calling the class library from another project."

In this case you will need to include the WS configuration settings into the main projects app.config if its a winapp or web.config if its a web app. This is the way to go even with PRISM and WPF/Silverlight.

Solution suggested: Use contract="IMySOAPWebService" in your config file.

Another thread[^] discussing the same.

gogopa · Answer 2 · 2014-07-02T14:23:00

Solution 2

Message msg = new Message();
sender.Send(msg);

Posted 2-Jul-14 14:23pm

gogopa