Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7178797
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T16:59:35+00:00 2026-05-28T16:59:35+00:00

I have been working on this issue for a few days now and can’t

  • 0

I have been working on this issue for a few days now and can’t seem to find a solution 🙁

I have an Asynchronous call to a WCF service which will work sometimes and on other occassions will do absolutely nothing – no call, no error, nothing. It will just stop after the execution of my calling method (main thread).
Breakpoints have been added to both the service method and in the auto-generated proxy class. If I am debugging on a failed call, these breakpoints will never be hit. Other times (when it happens to work) all break points will be hit.

I have completely removed the service and added it again, but still no luck.
I have even added a new service method and request message object in the hope that it was a freak problem with the original, however I am experiencing the same issue with the newly inserted method as well.

Just to note – This issue happens more often when I publish my application to a Virtual Machine. It doesn’t happen so much on my local machine, however it still happens.

Here is an example of my code:-

This is the async call to the service;

ValidateUpdatesMessageRequest request = new ValidateUpdatesMessageRequest();
_serviceClient.ProcessUpdatesAsync(Request)

The service method looks like this;

public ValidateUpdatesMessageResponse ProcessUpdates(ValidateUpdatesMessageRequest request){ 
//method body 
}

I also have an interface for the service which looks like this;

[OperationContract]
ValidateUpdatesMessageResponse ProcessUpdates(ValidateUpdatesMessageRequest request);

I would appreaciate ANY feedback whatsoever that may help steer me in the direction of a solution.

If you require any further info, please just let me know.

Many thanks in advance!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-28T16:59:36+00:00Added an answer on May 28, 2026 at 4:59 pm

    I have actually now resolved my issue.

    I thought I would post my solution for anyone else who might be experiencing the same problem.

    At the end of my method which calls the async method:-

    _serviceClient.ProcessUpdatesAsync(request);
    

    I had a

    CleanUp()
    

    which made a call to

    _serviceClient.CloseAsync();
    

    So this was being closed before the service method could be run.

    I simply took the

    CleanUp() 
    

    out of the orginial method call to the service and placed it in the event completed method, this way the async thread is closed on completion.
    Seems so obvious now!

    Thank you for all of your suggestions and input, it is much appreciated!

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

So I have been working on this for a few days now, and I
I've been searching for a solution to this issue for a few days now.
I have been working on this frustrating bug for a few days now and
I have been searching for a solution to this issue for a few days
I have been working on this problem for 2 days now and it's an
I have been struggling with this problem for a few days now and I
I've been working on this for a few days now, and I've found several
I have been working on this for days but I don't get it so
I have been working on this problem for a while now. I am trying
I have been working on this for 24 hours now, trying to optimize it.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.