Client Error

Hi everybody,

I keep getting sporadically the following exception the only solution I have found so far was to replace the AppID.
Does anyone else have a better idea Does anyone else have this problem (I tried changing the culture info with no luck so far)< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />


System.Web.Services.Protocols.SoapException: Client Error
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at
Nocturnal.com.msn.search.soap.MSNSearchService.Search(SearchRequest Request)
   at
Nocturnal.MSNSearchFilter.Search(String pstrQuery)
 

Thanks,
Coby



Answer this question

Client Error

  • jadelise

    I got the same crptic message with no info in it in my case it was happening consistently.

    I had to create a new AppId and stick it in to make it work. In my case the problem seemed to be with the provisioning system which did not create the Id the first time around.

    The second time when I created it listed my app indicating that it did infact register the app which it did not do the first time.

    You might want to check your APP on the registration site to confirm if you are indeed registered.

  • PeterBrown

    I'm getting a similar problem to this - I dont know if anyone can help me.

    I am developing an entry for the WorldsBestApp competition which uses the MSN Search API, its been working fine up until today. Earlier I opened my application and I was recieving these: "Client: Client Error" errors. I checked the developer area where AppID's are given out and the one I registered before was gone. Do these ID's timeout after a specific period

    I have created a new ID and deployed my application to a new deployment server (the application is almost ready for release), and it now works on there. However, the ID no longer works on the development server on my network, is there a reason for this I would very much like to finish this so I can submit it Smile.

    Thanks.

  • chinarut

    Hello.

    I haven't tried the product, so I am only guessing. Sorry if I am far off.
    Is this under heavy load

    I remeber having errors that looked much like those when trying to invoke web service calls from several threads at the same time on a smartphone. Have you tried to synchronize the access with "lock" or something

    I might be totally wrong though.

  • zx6r

    Am I to take it from reading these post that there is absolutly no way to safe guard this client error. I got the very same problem and could only solve it by getting a new app id.

     

    Does anyone know if this problem is related to how ofter you call the web service and how frequent


  • PrinceThaine

    I have also been getting sporadic faults.  It does appear to be AppID related.  What's strange is that my app is just a loop.  MSN works fine the first few calls, but then starts sporadically croaking.

    The fault states:  InnerText "Invalid value for AppID in request" String

    But since this is a loop and it works half the time, that doesn't seem to be the real problem.  Is there maybe a timer that if you request too quickly this will happen

  • bgo.ugent

    The SOAP response from the server should have more information on the error than the exception thrown by .Net. 

  • Sabrecat

    im not seeing anything at the api namespace
    http://schemas.microsoft.com/MSNSearch/2005/09/fex

     (not sure if this was the case before or not...since I've never looked at the url before)
    ...but it's saying...
    "The system cannot find the path specified."




  • Client Error