.Net 1.1 Web Service on 64-bit IIS 7.5: 'invalid Content-Type setting' error
Hi,
I am trying to run tests for Web Service implemented using .Net 1.1. The tests and service ran fine on W2K3 server previously.
I followed http://blogs.iis.net/bills/archive/2008/06/02/installing-asp-net-1-1-with-iis7-on-vista-and-windows-2008.aspx and was able to run most of the tests using latest TC 8.6 with the service running on 64-bit W2K8 R2 SP1.
I ensured that webs service is running on IIS in the .Net 1.1 3-bit application pool.
The problem is that some tests test if expected exception is thrown if the service is called with incorrect parameters. And all these tests fail now with the 'Received content of invalid Content-Type setting: text/html - SOAP expects "text/xml"' error.
Googling did not result in the relevant solution.
The interesting thing is that if I run Fiddler web debugger/proxy on the IIS side and set TC to use Fiddler as a proxy (TC Tools|Options|Engines|Web Services), then no error occurs, test succeeds and Fiddler shows traffic with expected request and response. But if TC requests Web Service directly, than the error is returned instead of expected exception.
Considering that everything works through the Fiddler, I think that this is a problem with IIS configuration (permissions, threading, etc.).
Wondering if someone have ever seen such a problem and can share some piece of advice...
I am trying to run tests for Web Service implemented using .Net 1.1. The tests and service ran fine on W2K3 server previously.
I followed http://blogs.iis.net/bills/archive/2008/06/02/installing-asp-net-1-1-with-iis7-on-vista-and-windows-2008.aspx and was able to run most of the tests using latest TC 8.6 with the service running on 64-bit W2K8 R2 SP1.
I ensured that webs service is running on IIS in the .Net 1.1 3-bit application pool.
The problem is that some tests test if expected exception is thrown if the service is called with incorrect parameters. And all these tests fail now with the 'Received content of invalid Content-Type setting: text/html - SOAP expects "text/xml"' error.
Googling did not result in the relevant solution.
The interesting thing is that if I run Fiddler web debugger/proxy on the IIS side and set TC to use Fiddler as a proxy (TC Tools|Options|Engines|Web Services), then no error occurs, test succeeds and Fiddler shows traffic with expected request and response. But if TC requests Web Service directly, than the error is returned instead of expected exception.
Considering that everything works through the Fiddler, I think that this is a problem with IIS configuration (permissions, threading, etc.).
Wondering if someone have ever seen such a problem and can share some piece of advice...
