Last post Nov 18, 2015 09:22 AM by chris.obrien9
Apr 30, 2015 04:14 AM|GTHvidsten|LINK
We have a .NET 2.0 webservice which intermittently produce this error on a server
Request format is unrecognized for URL unexpectedly ending in /methodname
All solutions I have found for this error gives the same answer, which is what is to include the following in the web.config file.
<add name="HttpGet" />
<add name="HttpPost" />
The big problem for me here is that my web.config file already includes this information.
And it obviously works as the webservice can be called just fine, until it suddenly fails for no apparent reason. Restarting the webservice (by forcing a web.config change) or even restarting the computer most of the times (sometimes multiple reboots must
be done) brings the service back up, until it fails again a few hours, or a few days later.
We have been suggested to run aspnet_regiis.exe. However, because we're only using .NET 2.0 on the server there shouldn't be any conflicting versions. Also I believe that had this been the case we should experience the error all the time instead of in infrequent
intervals as we do.
In any case, we have other webservices running on this computer and we have never experienced this kind of error with any of those.
I did find this hotfix from Microsoft (https://support.microsoft.com/en-us/kb/2783777) which might be related, but this is only for .NET 3.5 (I also found a similar hotfix for .NET
4.0), and since we're using .NET 2.0 it's no use for us. Upgrading to .NET 3.5 is not an option in this case.
Can it be that we're experiencing the issue the hotfix supposedly fixes, or is this something else entirely? In either case, how can we fix it?
May 05, 2015 05:25 AM|gtscdsi|LINK
I have done a quick research according to your description and got similar results as yours.
This thread discussed about the similar issue.
This article metioned to modify the web.config file.
Regarding the hotfix, I don't find the one for .NET2.0.
In addition, you may check if middle ware, such as proxy or NLB between client and server which may cause the issue.
Hope the above information useful to you!
Nov 18, 2015 09:22 AM|chris.obrien9|LINK
Were you ever able to find a resolution to this issue? We are seeing the same behavior with one of our several asmx web services and are wondering if there is a solution outside of upgraded .net on our servers. The issue occurs randomly after an IIS recycle,
producing the "Request format is unrecognized" error. An app recycle (or several) will eventually resolve the issue temporarily.