WCF service is not getting called after publishing MVC application to IIS

Question

0.00/5 (No votes)

See more:

Hi All,

I have a class library project in which I had added a service reference of a wcf service provided by client.

I am accessing the class library in MVC application.
I have added the bindings and endpoints to web.config of a MVC application.

When I am running application is debug mode service is getting called and I am getting required output.

But when I published the MVC application to IIS and WCF service method is not getting called.

Do we need to add any setting in IIS to make this working. Or Is there any other way to use class library which is having a service reference.

Thanks in advance for your suggestions.

-Avinash

Posted 28-Oct-15 6:01am

Avinash6474

Add a Solution

Comments

F-ES Sitecore 28-Oct-15 12:11pm

Check the end points are correct and use a tool like Fiddler to analyse the network calls to check for errors etc.

Avinash6474 29-Oct-15 2:17am

Thanks , used Fiddler to track network call. It was a firewall issue

1 solution

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)

phil.o · Accepted Answer · 2015-10-28T08:02:00

If I had your issue, I would install the remote debugging tools on the IIS server to be able to attach my debugger to the distant process on the server.
This would allow analyzing and tracking down the problem.

There is an excellent article on CP about remote IIS debugging; there:
Remote IIS Debugging : Debug your ASP.NET Application which is hosted on "Remote IIS Server"[^]

Not exactly a solution, but maybe something on the way to the resolution. Anyway, hope this helps.