The “page cannot be displayed” error occurs due to incorrect IIS installation
Customer has an IIS 6.0 with SMS installed.
When access one of the SMS virtual directory, IE showed “page cannot be displayed” error with a button asking you to troubleshoot connection problem. There was no entries logged in IIS log, however we could found a “connection dropped” error for each request in http error log.
This sounds a SSL handshake issue as this site requires mutual SSL authentication. Requests will be disconnected by HTTP.SYS as long as SSL handshake failed, and never be passed to the work process. We did a quick test on plain html file, and it works. Then, this told us that SSL has no problem. Problem should be due to the SMS extension. Then, we reviewed the SMS logs and there was an error related to network like “network connection was closed”. This didn’t give us too much help. After enabled IIS debug trace, we found something really weird as we could see the request was passed and handled by the SMS extension.
1. SSL handshake succeeded.
00000605 43.71051407 [472] 8072 strmfilt!SSL_STREAM_CONTEXT::DumpCertDebugInfo [\sslcontext.cxx @ 3202]:Client cert key length = 2048 bits
00000606 43.71069336 [472] 8072 strmfilt!SSL_STREAM_CONTEXT::DumpCertDebugInfo [\sslcontext.cxx @ 3240]:Client cert issuer = DC=com, DC=XXX, DC=internal, DC=pc, CN=XXX Group Ltd Issuing
00000607 43.71074677 [472] 8072 strmfilt!SSL_STREAM_CONTEXT::DumpCertDebugInfo [\sslcontext.cxx @ 3283]:Client cert subject = CN=XXX
00000608 43.71078110 [472] 8072 strmfilt!SSL_STREAM_CONTEXT::DumpCertDebugInfo [\sslcontext.cxx @ 3344]:Client cert verification result = 0x0 (SUCCESS)
2. The request was passed to SMS extension.
00000657 43.82388306 [7588] 8184 w3isapi!ISAPI_DLL::Load [\dll_manager.cxx @ 389]:ISAPI_DLL::Load() Loaded extension c:\program files\sms_ccm\getauth.dll, description "MP GetAuth ISAPI Extension"
00000658 43.82393265 [7588] 8184 w3isapi!ProcessIsapiRequest [\w3isapi.cxx @ 572]:
00000659 43.82393265 [7588] Calling into HttpExtensionProc
00000660 43.82393265 [7588] Extension: 'c:\program files\sms_ccm\getauth.dll'
00000661 43.82393265 [7588] pECB: 010D59B8
00000662 43.82393265 [7588] <END>
00000663 43.82393265 [7588]
3. Request was succeeded with 200:
00000678 44.69152832 [7588] HSE_REQ_SEND_RESPONSE_HEADER_EX[010D59B8]: Function Entry
00000679 44.69152832 [7588] Status: '200 OK'
00000680 44.69152832 [7588] Headers: 'Content-Length: 1401
00000681 44.69152832 [7588] Content-Type: text/xml
00000682 44.69152832 [7588] Cache-Control: no-cache
00000683 44.69152832 [7588] Pragma: no-cache
00000684 44.69152832 [7588]
4. SendResponse failed with a network error:
00000687 44.69168472 [7588] 4024 w3core!W3_CONTEXT::SendResponse [\w3context.cxx @ 2338]:SendResponse failed: handler ISAPIHandler, hr 80070057
00000690 44.69181824 [7588] 4024 w3isapi!SSFSendResponseHeaderEx [\server_support.cxx @ 284]:
00000691 44.69181824 [7588] HSE_REQ_SEND_RESPONSE_HEADER_EX[010D59B8]: Failed.
00000692 44.69181824 [7588] Error: 0x80072746
00000693 44.69181824 [7588] <END>
The cause:
Customer’s server is Windows 2003 SP2, however the IIS binaries are RTM. This was an incorrect installation. This was fixed by:
- Reinstall IIS, when installation prompts for Windows 2003 CD, provides a Windows 2003 CD with SP2.
- Or re-apply SP2.
014> lmvm kernel32
start end module name
77e40000 77f42000 kernel32 (private pdb symbols)
Image path: c:\winnt\system32\kernel32.dll
Image name: kernel32.dll
Timestamp: Sun Mar 22 01:08:26 2009 (49C51F0A)
FileVersion: 5.2.3790.4480 (srv03_sp2_gdr.090321-1244)
FileDescription: Windows NT BASE API Client DLL
LegalCopyright: © Microsoft Corporation. All rights reserved.
0:014> lmvm w3core
start end module name
5a390000 5a3e5000 w3core (private pdb symbols)
Image path: c:\winnt\system32\inetsrv\w3core.dll
Image name: w3core.dll
FileVersion: 6.0.3790.0 (srv03_rtm.030324-2048)
FileDescription: IIS Web Server Core
LegalCopyright: © Microsoft Corporation. All rights reserved.
See you next time,
Zhao Wei