Shibboleth SP3 Problem: xmltooling::IOException setHeader (Header) failed: -2147024809

Cantor, Scott cantor.2 at
Thu Jan 21 21:52:24 UTC 2021

On 1/21/21, 4:39 PM, "users on behalf of Stephen Holland-Chang" <users-bounces at on behalf of stephen at> wrote:

>    Does anyone know if there is a way we can debug the error and figure out which actual attribute is throwing the 
> setHeader Failed error? 

Not mapping the attribute suspected is a simple way to prevent a header from being set for it, and given a separate installation and a trace it is eminently possible to reproduce a test of the processing of a message given other manipulation of security policy to bypass checks for freshness and other factors.

>    We do know that the 2 users having the problem have one attribute “role” which has (71 values)

Then there really isn't any doubt, nor any doubt that IIS is so broken that it apparently doesn't honor the setting you're trying to change, or has some inherent limitation that overrides the setting.

> Thats the only field that looks particularly distinctive.

Assuming the data is all ASCII/non-unusual, then I don't think there's any real doubt, but I would be concerned about there being multi-byte UTF-8 data involved too.

-- Scott

More information about the users mailing list