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

Stephen Holland-Chang stephen at
Thu Jan 14 20:06:07 UTC 2021

Ive looked at the log configuration guide for Shibboleth SP 3 but still cannot see anywhere in logs to show me which SAML2 data that keeps failing. 

Looking in the Windows Event Logger under Shibboleth it doesn’t show any WARN or ERRORS

When Shibboleth errors with that xmltooling::IOException, shouldn’t it be logging that error somewhere? Any guidance to help us so we can track down the data that is throwing the error would be greatly appreciated! 

We have configured our native.logger to DEBUG

# set overall behavior
log4j.rootCategory=DEBUG, native_log

# fairly verbose for DEBUG, so generally leave at WARN/INFO

# raise for low-level tracing of SOAP client HTTP/SSL behavior

# useful categories to tune independently:
# tracing of SAML messages and security policies

log4j.appender.native_log.source=Shibboleth Service Provider
log4j.appender.native_log.layout.ConversionPattern=%c %x: %m


> On Jan 13, 2021, at 6:28 PM, Cantor, Scott <cantor.2 at> wrote:
> On 1/13/21, 9:26 PM, "users on behalf of Stephen Holland-Chang" <users-bounces at on behalf of stephen at> wrote:
>>   Thanks Scott, is there anyway to bypass this error or log the full list i attributes passed so we can see whats wrong? 
> Logging documentation and configuration addresses what categories log SAML messages.
> -- Scott
> -- 
> For Consortium Member technical support, see
> To unsubscribe from this list send an email to users-unsubscribe at

More information about the users mailing list