cascadingdropdown error 404

this problem occures sometimes when the data is not correctly popluated from the server, the threads are interappting each other please check the following there are some solutions:

please check all your variables u might be missing something or there could be some ambiguous variable declared.

there is a new version or Ajaxcontrol toolkit check it out it may solve this issue

http://forums.asp.net/t/1138732.aspx

sorry, the link in my previous post is for information this is the link for ajaxcontrol toolkit new version:

http://www.codeplex.com/AtlasControlToolkit/Release/ProjectReleases.aspx?ReleaseId=4941

thanks

Hi Kuangyc,

kuangyc:

I used some cascadingdropdown in a page ,most of the time it runs good!but some times it turns out method error 404! I don't konw how it happens,there are some codes:

Client Error 4xx
The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents SHOULD display any included entity to the user.

If the client is sending data, a server implementation using TCP SHOULD be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted by the HTTP application.

404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.

So I think your issue is caused by the system environment's rather than the WebService. I suggest that you should use a debugging tool(such as WebDevelopment Helper, Fiddler and HttpWatch etc) to watch the posts and feadbacks when the error ocurred.

If it doesn't work, please share more information which is catched by your debugging tool.

Hope this help.

Best regards,

Jonathan