Install/Configuration/Run Errors

Cantor, Scott cantor.2 at
Thu Jan 19 02:54:44 GMT 2012

> >From Native_Warn.log:
> 2012-01-18 18:26:03 ERROR Shibboleth.ISAPI [2764] isapi_shib_extension:
> Error reading request body from browser (2746).
> 2012-01-18 18:26:06 ERROR Shibboleth.Listener [2764]
> isapi_shib_extension: remoted message returned an error: Invalid HTTP
> method (GET).
> 2012-01-18 18:26:06 ERROR Shibboleth.ISAPI [2764] isapi_shib_extension:
> Invalid HTTP method (GET).

The latter two are from your reloading the /SAML2/POST page after IIS returns the initial 500 error, and that turns into a GET, which is invalid for that endpoint. That's why they're three seconds later.  The only important error is the POST failing. Error 0x2746 is a connection reset error which happens because the client has closed the connection to the server by the time the extension asks for the data. That in turn is because something has already read and swallowed the POST, leaving no data for the SP to read, so when it asks for the data, it's gone, and the client has already gone away.

All of that is very clear from the tracing we did. What isn't clear is what's swallowing the POST, or why your IIS installs seem to be consistently doing this.

Something we didn't try, though, was switching to 32-bit. You could try doing an install with the 32-bit version. You would need to tell IIS to use an App Pool that supports 32-bit .NET processes.

-- Scott

More information about the users mailing list