Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Request format is unrecognized

0 views
Skip to first unread message

Andrew Filev

unread,
Apr 22, 2004, 5:04:35 PM4/22/04
to
I've got an error trying to open
http://[myservername]/BAMQueryWebSvc/QueryWebService.asmx or
http://[myservername]/BAMQueryWebSvc/QueryWebService.asmx?wsdl in browser.
Should it be so? The error is:
Server Error in '/BAMQueryWebSvc' Application.
--------------------------------------------------------------------------------

Request format is unrecognized.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: Request format is
unrecognized.

Source Error:

An unhandled exception was generated during the execution of the current
web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.

Stack Trace:


[InvalidOperationException: Request format is unrecognized.]
System.Web.Services.Protocols.WebServiceHandlerFactory.CoreGetHandler(Type
type, HttpContext context, HttpRequest request, HttpResponse response) +386
System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler(HttpContext
context, String verb, String url, String filePath) +92
System.Web.HttpApplication.MapHttpHandler(HttpContext context, String
requestType, String path, String pathTranslated, Boolean useAppConfig) +698
System.Web.MapHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
+96
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +173


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.985;
ASP.NET Version:1.1.4322.968

Matt Milner

unread,
Apr 22, 2004, 11:15:08 PM4/22/04
to
If you look in the web.config for the service you will see that the web
services section has some protocols disabled. Comment this section out of
the web.config and it should work fine. essentially, MS setup these
services to be consumed, not to be browsed.

Matt


"Andrew Filev" <[NOSPAM]> wrote in message
news:opr6vl5x...@msnews.microsoft.com...

0 new messages