This is page contains raw error codes. It is meant as a software developer reference, not a customer support site.
| Code | HRESULT | Description | #define |
|---|---|---|---|
| 100 | 0x80190064 | HTTP status 100: The request can be continued. | BG_E_HTTP_ERROR_100 |
| 101 | 0x80190065 | HTTP status 101: The server switched protocols in an upgrade header. | BG_E_HTTP_ERROR_101 |
| 200 | 0x801900C8 | HTTP status 200: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again. | BG_E_HTTP_ERROR_200 |
| 201 | 0x801900C9 | HTTP status 201: The request was fulfilled and resulted in the creation of a new resource. | BG_E_HTTP_ERROR_201 |
| 202 | 0x801900CA | HTTP status 202: The request was accepted for processing, but the processing has not been completed yet. | BG_E_HTTP_ERROR_202 |
| 203 | 0x801900CB | HTTP status 203: The returned metadata in the entity-header is not the definitive set available from the server of origin. | BG_E_HTTP_ERROR_203 |
| 204 | 0x801900CC | HTTP status 204: The server has fulfilled the request, but there is no new information to send back. | BG_E_HTTP_ERROR_204 |
| 205 | 0x801900CD | HTTP status 205: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again. | BG_E_HTTP_ERROR_205 |
| 206 | 0x801900CE | HTTP status 206: The server fulfilled the partial GET request for the resource. | BG_E_HTTP_ERROR_206 |
| 300 | 0x8019012C | HTTP status 300: The server could not return the requested data. | BG_E_HTTP_ERROR_300 |
| 301 | 0x8019012D | HTTP status 301: The requested resource was assigned to a new permanent Uniform Resource Identifier (URI), and any future references to this resource should use one of the returned URIs. | BG_E_HTTP_ERROR_301 |
| 302 | 0x8019012E | HTTP status 302: The requested resource was assigned a different Uniform Resource Identifier (URI). This change is temporary. | BG_E_HTTP_ERROR_302 |
| 303 | 0x8019012F | HTTP status 303: The response to the request is under a different Uniform Resource Identifier (URI) and must be retrieved using a GET method on that resource. | BG_E_HTTP_ERROR_303 |
| 304 | 0x80190130 | HTTP status 304: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again. | BG_E_HTTP_ERROR_304 |
| 305 | 0x80190131 | HTTP status 305: The requested resource must be accessed through the proxy given by the location field. | BG_E_HTTP_ERROR_305 |
| 307 | 0x80190133 | HTTP status 307: The URL has been temporarily relocated. Try again later. | BG_E_HTTP_ERROR_307 |
| 400 | 0x80190190 | HTTP status 400: The server cannot process the request because the syntax is not valid. | BG_E_HTTP_ERROR_400 |
| 401 | 0x80190191 | HTTP status 401: The requested resource requires user authentication. | BG_E_HTTP_ERROR_401 |
| 402 | 0x80190192 | HTTP status 402: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again. | BG_E_HTTP_ERROR_402 |
| 403 | 0x80190193 | HTTP status 403: The client does not have sufficient access rights to the requested server object. | BG_E_HTTP_ERROR_403 |
| 404 | 0x80190194 | HTTP status 404: The requested URL does not exist on the server. | BG_E_HTTP_ERROR_404 |
| 405 | 0x80190195 | HTTP status 405: The method used is not allowed. | BG_E_HTTP_ERROR_405 |
| 406 | 0x80190196 | HTTP status 406: No responses acceptable to the client were found. | BG_E_HTTP_ERROR_406 |
| 407 | 0x80190197 | HTTP status 407: Proxy authentication is required. | BG_E_HTTP_ERROR_407 |
| 408 | 0x80190198 | HTTP status 408: The server timed out waiting for the request. | BG_E_HTTP_ERROR_408 |
| 409 | 0x80190199 | HTTP status 409: The request could not be completed because of a conflict with the current state of the resource. The user should resubmit the request with more information. | BG_E_HTTP_ERROR_409 |
| 410 | 0x8019019A | HTTP status 410: The requested resource is not currently available at the server, and no forwarding address is known. | BG_E_HTTP_ERROR_410 |
| 411 | 0x8019019B | HTTP status 411: The server cannot accept the request without a defined content length. | BG_E_HTTP_ERROR_411 |
| 412 | 0x8019019C | HTTP status 412: The precondition given in one or more of the request header fields evaluated to false when it was tested on the server. | BG_E_HTTP_ERROR_412 |
| 413 | 0x8019019D | HTTP status 413: The server cannot process the request because the request entity is too large. | BG_E_HTTP_ERROR_413 |
| 414 | 0x8019019E | HTTP status 414: The server cannot process the request because the request Uniform Resource Identifier (URI) is longer than the server can interpret. | BG_E_HTTP_ERROR_414 |
| 415 | 0x8019019F | HTTP status 415: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again. | BG_E_HTTP_ERROR_415 |
| 416 | 0x801901A0 | HTTP status 416: The server could not satisfy the range request. | BG_E_HTTP_ERROR_416 |
| 417 | 0x801901A1 | HTTP status 417: The server could not meet the expectation given in an Expect request-header field. | BG_E_HTTP_ERROR_417 |
| 449 | 0x801901C1 | HTTP status 449: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again. | BG_E_HTTP_ERROR_449 |
| 500 | 0x801901F4 | HTTP status 500: An unexpected condition prevented the server from fulfilling the request. | BG_E_HTTP_ERROR_500 |
| 501 | 0x801901F5 | HTTP status 501: The server does not support the functionality required to fulfill the request. | BG_E_HTTP_ERROR_501 |
| 502 | 0x801901F6 | HTTP status 502: The server, while acting as a gateway or proxy to fulfill the request, received an invalid response from the upstream server it accessed. | BG_E_HTTP_ERROR_502 |
| 503 | 0x801901F7 | HTTP status 503: The service is temporarily overloaded. | BG_E_HTTP_ERROR_503 |
| 504 | 0x801901F8 | HTTP status 504: The request was timed out waiting for a gateway. | BG_E_HTTP_ERROR_504 |
| 505 | 0x801901F9 | HTTP status 505: The server does not support the HTTP protocol version that was used in the request message. | BG_E_HTTP_ERROR_505 |
| 16384 | 0x80194000 | The administrator %4 canceled job "%2" on behalf of %3. The job ID was %1. | BITS_MC_JOB_CANCELLED |
| 16385 | 0x80194001 | While canceling job "%2", BITS was not able to remove the temporary files listed below. If you can delete them, then you will regain some disk space. The job ID was %1. %3 | BITS_MC_FILE_DELETION_FAILED |
| 16386 | 0x80194002 | While canceling job "%2", BITS was not able to remove the temporary files listed below. If you can delete them, then you will regain some disk space. The job ID was %1. %3 Due to space limitations, not all files are listed here. Check for additional files of the form BITxxx.TMP in the same directory. | BITS_MC_FILE_DELETION_FAILED_MORE |
| 16387 | 0x80194003 | The administrator %3 modified the %4 property of job "%2". The job ID was %1. | BITS_MC_JOB_PROPERTY_CHANGE |
| 16388 | 0x80194004 | The administrator %4 took ownership of job "%2" from %3. The job ID was %1. | BITS_MC_JOB_TAKE_OWNERSHIP |
| 16389 | 0x80194005 | Job "%2" owned by %3 was canceled after being inactive for more than %4 days. The job ID was %1. | BITS_MC_JOB_SCAVENGED |
| 16390 | 0x80194006 | Job "%2" owned by %3 failed to notify its associated application. BITS will retry in %4 minutes. The job ID was %1. | BITS_MC_JOB_NOTIFICATION_FAILURE |
| 16391 | 0x80194007 | The BITS job list is not in a recognized format. It may have been created by a different version of BITS. The job list has been cleared. | BITS_MC_STATE_FILE_CORRUPT |
| 16392 | 0x80194008 | The BITS service failed to start. Try restarting the service at a later time. | BITS_MC_FAILED_TO_START |
| 16393 | 0x80194009 | BITS has hit a fatal error communicating with an Internet Gateway Device. Please check that the device is functioning properly. BITS will not attempt to use this device until the next system reboot. | BITS_MC_FATAL_IGD_ERROR |
| 16394 | 0x8019400A | BITS Peer-caching protocol | BITS_MC_PEERCACHING_PORT |
| 16395 | 0x8019400B | Web Services-Discovery protocol | BITS_MC_WSD_PORT |
No comments:
Post a Comment