As per the view I am getting error “The server committed a protocol violation. Section=ResponseStatusLine”
The StackTrace " at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object] parameters)
at DirectFlightAccessApplication.com.flightaware.DirectFlight.GetLastTrack(String ident) in C:\Vivek\kachara\DirectFlight\DirectFlightAccessApplication\DirectFlightAccessApplication\Web References\com.flightaware\Reference.cs:line 263
at DirectFlightAccessApplication.Form1.button1_Click(Object sender, EventArgs e) in C:\Vivek\kachara\DirectFlight\DirectFlightAccessApplication\DirectFlightAccessApplication\Form1.cs:line 35" string
I am getting following NEW error while Updating/Refreshing the WSDL Reference in my projects with VS 2005 ( dotnet Framework 2.0) and VS 2003 ( dotnet Framework 1.1)
It is not able to create the Web Service Proxy 'caz of wrong schema.
Now also I am getting th same error above at Dotnet 2003 Command Promp when running the command : " wsdl flightaware.com/commercial/flightxml
/data/wsdl1.xml "
I have pasted the ERROR at Dotnet command prompt below,
Setting environment for using Microsoft Visual Studio .NET 2003 tools.
(If you have another version of Visual Studio or Visual C++ installed and wish
to use its tools from the command line, run vcvars32.bat for that version.)
C:\Documents and Settings\vivek>wsdl flightaware.com/commercial/flightxml
/data/wsdl1.xml
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 1.1.4322.573]
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
Fortunately I have found the old proxy I had created some days back when WSDL was working fine. Now I am using that. So the problem related to WSDL has solved for this time.
The other error related to “The server committed a protocol violation.” is still there, So could you please help me in that. Thanks.
I have regenerated the API access key.
It could be the same problem (in another post) you were facing, related to authentication failures.