Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Windows Internet Status

Updated: January 7, 2009

Applies To: Windows Server 2008 R2

Windows Internet (WinINet) Status relates to the success or failure of application programming interface (API) calls to the WinINet API. No user action is required.

Events

Event ID Source Message

101

Microsoft-Windows-WinINet

Session handle %1 created: UserAgent=%3, AccessType=%5, ProxyList=%7, ProxyBypassList=%9, Flags=%10

102

Microsoft-Windows-WinINet

Handle %1 created by InternetOpenURL: SessionHandle=%2,URL=%4, Headers=%6, Flags=%7

103

Microsoft-Windows-WinINet

Handle %1 created by InternetConnect: SessionHandle=%2, Server=%4:%5, %7, Flags=%8

104

Microsoft-Windows-WinINet

Request handle %1 created by HttpOpenRequest: ConnectionHandle=%2, %4, Target=%6, Ver=%8, Referrer=%10, Media types=%12, Flags=%13

105

Microsoft-Windows-WinINet

Handle %1 closed successfully

106

Microsoft-Windows-WinINet

Failed to create handle: ParentHandle=%1, Error=%2

107

Microsoft-Windows-WinINet

Handle %1 failed to close: Error=%2

200

Microsoft-Windows-WinINet

HTTP request was received from API: RequestHandle=%1

201

Microsoft-Windows-WinINet

HTTP request was sent successfully: RequestHandle=%1, SocketHandle=%2, %4, CookieSent= %5

202

Microsoft-Windows-WinINet

HTTP request send failed: Handle=%1, Error=%2

203

Microsoft-Windows-WinINet

HTTP response (%1) received: RequestHandle=%2, SocketHandle=%3, %5, ContentLength=%7

204

Microsoft-Windows-WinINet

HTTP response failed: Handle=%1, Error=%2

205

Microsoft-Windows-WinINet

HTTP connection (Handle=%1, SocketHandle=%2) closed due to the following reason: %4

206

Microsoft-Windows-WinINet

Keep-alive connection is re-used: ConnectionHandle=%1, SocketHandle=%2

207

Microsoft-Windows-WinINet

Connection is returned to keep-alive pool: ConnectionHandle=%1, SocketHandle=%2

208

Microsoft-Windows-WinINet

Keep-alive connection is closed: ConnectionHandle=%1, SocketHandle=%2

301

Microsoft-Windows-WinINet

TCP connection to server %2 established: ConnectionHandle=%3, SocketHandle=%4, LocalPort=%5

302

Microsoft-Windows-WinINet

TCP connection to %2 for connection handle %3 failed: Error=%4

303

Microsoft-Windows-WinINet

TCP connection closed successfully: SocketHandle=%1

304

Microsoft-Windows-WinINet

DNS query for %2 hostname is sent: Handle=%3

305

Microsoft-Windows-WinINet

DNS query for %2 hostname is complete: Handle=%3, Addresses=%5

306

Microsoft-Windows-WinINet

DNS query for %2 hostname failed: Handle=%3 Error=%4

307

Microsoft-Windows-WinINet

Re-used DNS cache, query for %2 hostname is complete: Handle=%3, Addresses=%5

308

Microsoft-Windows-WinINet

A network change was detected: Handle=%1

601

Microsoft-Windows-WinINet

Auth response received: RequestHandle=%1, Scheme=%3, IsProxy=%4

602

Microsoft-Windows-WinINet

Client sets user name: RequestHandle=%1, IsProxy=%2

603

Microsoft-Windows-WinINet

Client sets password: RequestHandle=%1, IsProxy=%2

604

Microsoft-Windows-WinINet

Using cached credentials: RequestHandle=%1, IsProxy=%2

605

Microsoft-Windows-WinINet

Using default credentials: RequestHandle=%1, IsProxy=%2

606

Microsoft-Windows-WinINet

Client adds authorization headers to an HTTP request: RequestHandle=%1, Scheme=%3, IsProxy=%4

1000

Microsoft-Windows-WinINet

 

Related Management Information

Windows Internet API

Networking

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.