When troubleshooting ISA Server 2004 one of the first places you are going to go to is the Logging page to see what is happening with your traffic.
For additional information you might want to add the following two columns to the logging page to get additional information regarding ISA’s behavior displayed on the Logging page:
For information on the Result Code column see, Error Codes on MSDN Web site.
For more information on the Error Information column, search product help for “Error information log values”.
ISA Server Product Team
Thanks for participating in this blog. The more info we can get from the ISA team the better.
The MSDN error page could be very useful information if the information were complete. Half the codes have no explanation at all and the rest only have a sentence at most. Maybe someone could get that error page updated with more complete info. That would be great!
Also I'm getting an HTTP Status Code of 0x80090317 ... any idea what that means or where I can find a list of those codes?
The Result Code and Error Information columns on the ISA Server 2004 logging page only include some typical examples. The number of possibilities is very large, and the information is usually available elsewhere in the MSDN Library. For example, information
on system error codes can be found at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/system_error_codes.asp?frame=true, information on Winsock error codes can be found at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/winsock/windows_sockets_error_codes_2.asp, and information on the error codes defined in Winerror.h can be found at
The specific error 0x80090317 is defined in Wiknerror.h. Its symbolic name is SEC_E_CONTEXT_EXPIRED, and its message text is The context has expired and can no longer be used.
Had these errors occur for some users after 10-25 seconds of using bridged HTTPS connection to an apache webserver.
It turned out the maxkeepalive setting on apache was set to 100, and request 101 failed, causing the connection to fail and showing this error in ISA logs.
Might save somone some time.
PingBack from http://www.hilpers.com/150200-ms-isa-2004-ergebniscodes
Thanks for the recognition and the community support!