"The server committed a protocol violation" calling webservices from .NET

Dears,
I have an Isapi server that publishes a web services using SOAP made in Delphi; so I am using a TROWebBrokerServer and a TROSOAPMessage. I consume the web services with an application made in .NET (C#); It is just adding a Web Reference and using it. I have no problems with version 5.0.23 of Rem Objects SDK but now I’m testing the new version 6.0.57 (in trial mode) and this errors occurs when I call the web services from .NET: “The server committed a protocol violation”.

I found a solution in this link:
http://www.velocityreviews.com/forums/t302174-why-do-i-get-the-server-committed-a-protocol-violation.html

It consists in adding some line in the web.config file of my web application made in .NET to accept “incorrect header protocols”.

How can I fixed my Rem Object application to generate a correct protocol???

Than you

Can you give wsdl and examples of correct and wrong SOAP requests with values of HTTP headers, please?

I’ve created an example. It includes the Delphi project to create a Web Services (Isapi dll) using RemObjects and a .NET solution with to projects: one it is working and the other not. The only difference is to accept “useUnsafeHeaderParsing”. In older versions of Rem Objects this source code works.

The WDSL definition and the .NET error page are included too (TestIsapiWDSL.xml and NETErrorPage.htm).

Best regards,
Mario

Hi.

As I understood problem with HTTP header of server’s response. What version of IIS you are using? Can you give example of server’s http response?

Hi,
I’m testing with IIS 5.1. I can’t test it with IIS 6 or 7 because a modal message of using Trial Version of RemObjects is showed. This message only appears in Windows XP, not in other versions :frowning:
I send you the wdsl and the response of the server (I used Firebug to catch the response). I hope the information is correct.

Best regards,
Mario

Hello Mario.

Sorry for the belated response.
Unfortunately, I can’t reproduce the problem using testcase you have provided. WebError as well as WebOK project shows Server time value as expected. Can you describe environment you are using in details? It will help us to reproduce the problem with original environment.

Thanks in advance.

Hello,
I’m using IIS 5 and Windows XP SP3. I compiled the Isapi dll with a Trial version of RemObjects. When I execute the dll, this modal message is showed:
"Trial Notice. This application…"
I need to accept the message in order to execute the dll. Moreover, to see this message I need to change some Windows Configuration:

  • In the IIS Admin service, I configured the option "Log on->Local System Account->Allow service to interact with desktop"
    Without this configuration it is no possible to execute the dll because the message is not showed, so I can’t accept the Modal Message of the Trial Version.
    I tried to execute the dll on IIS 7 over Windows Server 2008 Standard 32 bits but it is no possible: the Trial Advertisment isn’t showed.

Maybe the problem is with the dll compilation. In that case, you have my compilated dll on the TestIsapi.rar file that I sent.

I hope it’ll be enough to reproduce the error.

Mario

Sorry,
I forget this information:

  • I’m using RemObjects with Delphi 7 Enterprise
  • For .NET, I’m using Microsoft Visual Studio 2008 Professional (9.0.21022.8) with .NET Framework 3.5 SP1

The .NET application was executed in my machine in debbuging mode, using an ASP.NET development server (it is a Windows XP SP3, too). The isapi dll was loaded in another machine.

Mario

Hello Mario.

Sorry for the belated response.
Thank you for the instructions. I have reproduced the problem. Appropriate issue is registered as #55041. Nowadays as workaround please use solution you have provided before.

Thanks.

Dears,
in which review is planned to solve the problem?

Best regards,
Mario

Hello Mario.

The problem is in our issue list now. Unfortunately, I can’t say for sure deadline for this problem.

Sorry for the inconvenience.

Is this issue resolved? I have a similar problem with 7.0.67.1073