Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

861 lines
22 KiB

  1. /***************************************************************************
  2. * *
  3. * bitsmsg.h -- error code definitions for the background file copier *
  4. * *
  5. * Copyright (c) 2000, Microsoft Corp. All rights reserved. *
  6. * *
  7. ***************************************************************************/
  8. #ifndef _BGCPYMSG_
  9. #define _BGCPYMSG_
  10. #if defined (_MSC_VER) && (_MSC_VER >= 1020) && !defined(__midl)
  11. #pragma once
  12. #endif
  13. //
  14. // Values are 32 bit values layed out as follows:
  15. //
  16. // 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
  17. // 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
  18. // +---+-+-+-----------------------+-------------------------------+
  19. // |Sev|C|R| Facility | Code |
  20. // +---+-+-+-----------------------+-------------------------------+
  21. //
  22. // where
  23. //
  24. // Sev - is the severity code
  25. //
  26. // 00 - Success
  27. // 01 - Informational
  28. // 10 - Warning
  29. // 11 - Error
  30. //
  31. // C - is the Customer code flag
  32. //
  33. // R - is a reserved bit
  34. //
  35. // Facility - is the facility code
  36. //
  37. // Code - is the facility's status code
  38. //
  39. //
  40. // Define the facility codes
  41. //
  42. //
  43. // Define the severity codes
  44. //
  45. //
  46. // MessageId: BG_E_NOT_FOUND
  47. //
  48. // MessageText:
  49. //
  50. // The requested job was not found.
  51. //
  52. #define BG_E_NOT_FOUND 0x80200001L
  53. //
  54. // MessageId: BG_E_INVALID_STATE
  55. //
  56. // MessageText:
  57. //
  58. // The requested action is not allowed in the current job state. The job might have been canceled or completed transferring. It is in a read-only state now.
  59. //
  60. #define BG_E_INVALID_STATE 0x80200002L
  61. //
  62. // MessageId: BG_E_EMPTY
  63. //
  64. // MessageText:
  65. //
  66. // There are no files attached to this job. Attach files to the job, and then try again.
  67. //
  68. #define BG_E_EMPTY 0x80200003L
  69. //
  70. // MessageId: BG_E_FILE_NOT_AVAILABLE
  71. //
  72. // MessageText:
  73. //
  74. // No file is available because no URL generated an error.
  75. //
  76. #define BG_E_FILE_NOT_AVAILABLE 0x80200004L
  77. //
  78. // MessageId: BG_E_PROTOCOL_NOT_AVAILABLE
  79. //
  80. // MessageText:
  81. //
  82. // No protocol is available because no URL generated an error.
  83. //
  84. #define BG_E_PROTOCOL_NOT_AVAILABLE 0x80200005L
  85. //
  86. // MessageId: BG_S_ERROR_CONTEXT_NONE
  87. //
  88. // MessageText:
  89. //
  90. // No errors have occurred.
  91. //
  92. #define BG_S_ERROR_CONTEXT_NONE 0x00200006L
  93. //
  94. // MessageId: BG_E_ERROR_CONTEXT_UNKNOWN
  95. //
  96. // MessageText:
  97. //
  98. // The error occurred in an unknown location.
  99. //
  100. #define BG_E_ERROR_CONTEXT_UNKNOWN 0x80200007L
  101. //
  102. // MessageId: BG_E_ERROR_CONTEXT_GENERAL_QUEUE_MANAGER
  103. //
  104. // MessageText:
  105. //
  106. // The error occurred in the Background Intelligent Transfer Service (BITS) queue manager.
  107. //
  108. #define BG_E_ERROR_CONTEXT_GENERAL_QUEUE_MANAGER 0x80200008L
  109. //
  110. // MessageId: BG_E_ERROR_CONTEXT_LOCAL_FILE
  111. //
  112. // MessageText:
  113. //
  114. // The error occurred while the local file was being processed. Verify that the file is not in use, and then try again.
  115. //
  116. #define BG_E_ERROR_CONTEXT_LOCAL_FILE 0x80200009L
  117. //
  118. // MessageId: BG_E_ERROR_CONTEXT_REMOTE_FILE
  119. //
  120. // MessageText:
  121. //
  122. // The error occurred while the remote file was being processed.
  123. //
  124. #define BG_E_ERROR_CONTEXT_REMOTE_FILE 0x8020000AL
  125. //
  126. // MessageId: BG_E_ERROR_CONTEXT_GENERAL_TRANSPORT
  127. //
  128. // MessageText:
  129. //
  130. // The error occurred in the transport layer. The client could not connect to the server.
  131. //
  132. #define BG_E_ERROR_CONTEXT_GENERAL_TRANSPORT 0x8020000BL
  133. //
  134. // MessageId: BG_E_ERROR_CONTEXT_QUEUE_MANAGER_NOTIFICATION
  135. //
  136. // MessageText:
  137. //
  138. // The error occurred while the notification callback was being processed. Background Intelligent Transfer Service (BITS) will try again later.
  139. //
  140. #define BG_E_ERROR_CONTEXT_QUEUE_MANAGER_NOTIFICATION 0x8020000CL
  141. //
  142. // MessageId: BG_E_DESTINATION_LOCKED
  143. //
  144. // MessageText:
  145. //
  146. // The destination file system volume is not available. Verify that another program, such as CheckDisk, is not running, which would lock the volume. When the volume is available, Background Intelligent Transfer Service (BITS) will try again.
  147. //
  148. #define BG_E_DESTINATION_LOCKED 0x8020000DL
  149. //
  150. // MessageId: BG_E_VOLUME_CHANGED
  151. //
  152. // MessageText:
  153. //
  154. // The destination volume has changed. If the disk is removable, it might have been replaced with a different disk. Reinsert the original disk and resume the job.
  155. //
  156. #define BG_E_VOLUME_CHANGED 0x8020000EL
  157. //
  158. // MessageId: BG_E_ERROR_INFORMATION_UNAVAILABLE
  159. //
  160. // MessageText:
  161. //
  162. // No errors have occurred.
  163. //
  164. #define BG_E_ERROR_INFORMATION_UNAVAILABLE 0x8020000FL
  165. //
  166. // MessageId: BG_E_NETWORK_DISCONNECTED
  167. //
  168. // MessageText:
  169. //
  170. // There are currently no active network connections. Background Intelligent Transfer Service (BITS) will try again when an adapter is connected.
  171. //
  172. #define BG_E_NETWORK_DISCONNECTED 0x80200010L
  173. //
  174. // MessageId: BG_E_MISSING_FILE_SIZE
  175. //
  176. // MessageText:
  177. //
  178. // The server did not return the file size. The URL might point to dynamic content. The Content-Length header is not available in the server's HTTP reply.
  179. //
  180. #define BG_E_MISSING_FILE_SIZE 0x80200011L
  181. //
  182. // MessageId: BG_E_INSUFFICIENT_HTTP_SUPPORT
  183. //
  184. // MessageText:
  185. //
  186. // The server does not support HTTP 1.1.
  187. //
  188. #define BG_E_INSUFFICIENT_HTTP_SUPPORT 0x80200012L
  189. //
  190. // MessageId: BG_E_INSUFFICIENT_RANGE_SUPPORT
  191. //
  192. // MessageText:
  193. //
  194. // The server does not support the necessary HTTP protocol. Background Intelligent Transfer Service (BITS) requires that the server support the Range protocol header.
  195. //
  196. #define BG_E_INSUFFICIENT_RANGE_SUPPORT 0x80200013L
  197. //
  198. // MessageId: BG_E_REMOTE_NOT_SUPPORTED
  199. //
  200. // MessageText:
  201. //
  202. // Background Intelligent Transfer Service (BITS) cannot be used remotely.
  203. //
  204. #define BG_E_REMOTE_NOT_SUPPORTED 0x80200014L
  205. //
  206. // MessageId: BG_E_NEW_OWNER_DIFF_MAPPING
  207. //
  208. // MessageText:
  209. //
  210. // The drive mapping for the job is different for the current owner than for the previous owner. Use a UNC path instead.
  211. //
  212. #define BG_E_NEW_OWNER_DIFF_MAPPING 0x80200015L
  213. //
  214. // MessageId: BG_E_NEW_OWNER_NO_FILE_ACCESS
  215. //
  216. // MessageText:
  217. //
  218. // The new owner has insufficient access to the local files for the job. The new owner might not have permissions to access the job files. Verify that the new owner has sufficient permissions, and then try again.
  219. //
  220. #define BG_E_NEW_OWNER_NO_FILE_ACCESS 0x80200016L
  221. //
  222. // MessageId: BG_S_PARTIAL_COMPLETE
  223. //
  224. // MessageText:
  225. //
  226. // Some of the transferred files were deleted because they were incomplete.
  227. //
  228. #define BG_S_PARTIAL_COMPLETE 0x00200017L
  229. //
  230. // MessageId: BG_E_PROXY_LIST_TOO_LARGE
  231. //
  232. // MessageText:
  233. //
  234. // The HTTP proxy list cannot be longer than 32,000 characters. Try again with a shorter proxy list.
  235. //
  236. #define BG_E_PROXY_LIST_TOO_LARGE 0x80200018L
  237. //
  238. // MessageId: BG_E_PROXY_BYPASS_LIST_TOO_LARGE
  239. //
  240. // MessageText:
  241. //
  242. // The HTTP proxy bypass list cannot be longer than 32,000 characters. Try again with a shorter bypass proxy list.
  243. //
  244. #define BG_E_PROXY_BYPASS_LIST_TOO_LARGE 0x80200019L
  245. //
  246. // MessageId: BG_S_UNABLE_TO_DELETE_FILES
  247. //
  248. // MessageText:
  249. //
  250. // Some of the temporary files could not be deleted. Check the system event log for the complete list of files that could not be deleted.
  251. //
  252. #define BG_S_UNABLE_TO_DELETE_FILES 0x0020001AL
  253. //
  254. // MessageId: BG_E_INVALID_SERVER_RESPONSE
  255. //
  256. // MessageText:
  257. //
  258. // 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.
  259. //
  260. #define BG_E_INVALID_SERVER_RESPONSE 0x8020001BL
  261. //
  262. // MessageId: BG_E_TOO_MANY_FILES
  263. //
  264. // MessageText:
  265. //
  266. // No more files can be added to this job.
  267. //
  268. #define BG_E_TOO_MANY_FILES 0x8020001CL
  269. //
  270. // MessageId: BG_E_LOCAL_FILE_CHANGED
  271. //
  272. // MessageText:
  273. //
  274. // The local file was changed during the transfer. Recreate the job, and then try to transfer it again.
  275. //
  276. #define BG_E_LOCAL_FILE_CHANGED 0x8020001DL
  277. //
  278. // MessageId: BG_E_ERROR_CONTEXT_REMOTE_APPLICATION
  279. //
  280. // MessageText:
  281. //
  282. // The program on the remote server reported the error.
  283. //
  284. #define BG_E_ERROR_CONTEXT_REMOTE_APPLICATION 0x8020001EL
  285. //
  286. // MessageId: BG_E_SESSION_NOT_FOUND
  287. //
  288. // MessageText:
  289. //
  290. // The specified session could not be found on the server. Background Intelligent Transfer Service (BITS) will try again.
  291. //
  292. #define BG_E_SESSION_NOT_FOUND 0x8020001FL
  293. //
  294. // MessageId: BG_E_TOO_LARGE
  295. //
  296. // MessageText:
  297. //
  298. // The job is too large for the server to accept. This job might exceed a job size limit set by the server administrator. Reduce the size of the job, and then try again.
  299. //
  300. #define BG_E_TOO_LARGE 0x80200020L
  301. //
  302. // MessageId: BG_E_STRING_TOO_LONG
  303. //
  304. // MessageText:
  305. //
  306. // The specified string is too long.
  307. //
  308. #define BG_E_STRING_TOO_LONG 0x80200021L
  309. //
  310. // MessageId: BG_E_CLIENT_SERVER_PROTOCOL_MISMATCH
  311. //
  312. // MessageText:
  313. //
  314. // The client and server versions of Background Intelligent Transfer Service (BITS) are incompatible.
  315. //
  316. #define BG_E_CLIENT_SERVER_PROTOCOL_MISMATCH 0x80200022L
  317. //
  318. // MessageId: BG_E_SERVER_EXECUTE_ENABLE
  319. //
  320. // MessageText:
  321. //
  322. // Scripting OR execute permissions are enabled on the IIS virtual directory associated with the job. To upload files to the virtual directory, disable the scripting and execute permissions on the virtual directory.
  323. //
  324. #define BG_E_SERVER_EXECUTE_ENABLE 0x80200023L
  325. //
  326. // MessageId: BG_E_NO_PROGRESS
  327. //
  328. // MessageText:
  329. //
  330. // The job is not making headway. The server may be misconfigured. Background Intelligent Transfer Service (BITS) will try again later.
  331. //
  332. #define BG_E_NO_PROGRESS 0x80200024L
  333. //
  334. // MessageId: BG_E_USERNAME_TOO_LARGE
  335. //
  336. // MessageText:
  337. //
  338. // The user name cannot be longer than 300 characters. Try again with a shorter name.
  339. //
  340. #define BG_E_USERNAME_TOO_LARGE 0x80200025L
  341. //
  342. // MessageId: BG_E_PASSWORD_TOO_LARGE
  343. //
  344. // MessageText:
  345. //
  346. // The password cannot be longer than 300 characters. Try again with a shorter password.
  347. //
  348. #define BG_E_PASSWORD_TOO_LARGE 0x80200026L
  349. //
  350. // MessageId: BG_E_INVALID_AUTH_TARGET
  351. //
  352. // MessageText:
  353. //
  354. // The authentication target specified in the credentials is not defined.
  355. //
  356. #define BG_E_INVALID_AUTH_TARGET 0x80200027L
  357. //
  358. // MessageId: BG_E_INVALID_AUTH_SCHEME
  359. //
  360. // MessageText:
  361. //
  362. // The authentication scheme specified in the credentials is not defined.
  363. //
  364. #define BG_E_INVALID_AUTH_SCHEME 0x80200028L
  365. //
  366. // MessageId: BG_E_HTTP_ERROR_100
  367. //
  368. // MessageText:
  369. //
  370. // The request can be continued.
  371. //
  372. #define BG_E_HTTP_ERROR_100 0x80190064L
  373. //
  374. // MessageId: BG_E_HTTP_ERROR_101
  375. //
  376. // MessageText:
  377. //
  378. // The server switched protocols in an upgrade header.
  379. //
  380. #define BG_E_HTTP_ERROR_101 0x80190065L
  381. //
  382. // MessageId: BG_E_HTTP_ERROR_200
  383. //
  384. // MessageText:
  385. //
  386. // 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.
  387. //
  388. #define BG_E_HTTP_ERROR_200 0x801900C8L
  389. //
  390. // MessageId: BG_E_HTTP_ERROR_201
  391. //
  392. // MessageText:
  393. //
  394. // The request was fulfilled and resulted in the creation of a new resource.
  395. //
  396. #define BG_E_HTTP_ERROR_201 0x801900C9L
  397. //
  398. // MessageId: BG_E_HTTP_ERROR_202
  399. //
  400. // MessageText:
  401. //
  402. // The request was accepted for processing, but the processing has not been completed yet.
  403. //
  404. #define BG_E_HTTP_ERROR_202 0x801900CAL
  405. //
  406. // MessageId: BG_E_HTTP_ERROR_203
  407. //
  408. // MessageText:
  409. //
  410. // The returned metadata in the entity-header is not the definitive set available from the server of origin.
  411. //
  412. #define BG_E_HTTP_ERROR_203 0x801900CBL
  413. //
  414. // MessageId: BG_E_HTTP_ERROR_204
  415. //
  416. // MessageText:
  417. //
  418. // The server has fulfilled the request, but there is no new information to send back.
  419. //
  420. #define BG_E_HTTP_ERROR_204 0x801900CCL
  421. //
  422. // MessageId: BG_E_HTTP_ERROR_205
  423. //
  424. // MessageText:
  425. //
  426. // 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.
  427. //
  428. #define BG_E_HTTP_ERROR_205 0x801900CDL
  429. //
  430. // MessageId: BG_E_HTTP_ERROR_206
  431. //
  432. // MessageText:
  433. //
  434. // The server fulfilled the partial GET request for the resource.
  435. //
  436. #define BG_E_HTTP_ERROR_206 0x801900CEL
  437. //
  438. // MessageId: BG_E_HTTP_ERROR_300
  439. //
  440. // MessageText:
  441. //
  442. // The server could not return the requested data.
  443. //
  444. #define BG_E_HTTP_ERROR_300 0x8019012CL
  445. //
  446. // MessageId: BG_E_HTTP_ERROR_301
  447. //
  448. // MessageText:
  449. //
  450. // 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.
  451. //
  452. #define BG_E_HTTP_ERROR_301 0x8019012DL
  453. //
  454. // MessageId: BG_E_HTTP_ERROR_302
  455. //
  456. // MessageText:
  457. //
  458. // The requested resource was assigned a different Uniform Resource Identifier (URI). This change is temporary.
  459. //
  460. #define BG_E_HTTP_ERROR_302 0x8019012EL
  461. //
  462. // MessageId: BG_E_HTTP_ERROR_303
  463. //
  464. // MessageText:
  465. //
  466. // The response to the request is under a different Uniform Resource Identifier (URI) and must be retrieved using a GET method on that resource.
  467. //
  468. #define BG_E_HTTP_ERROR_303 0x8019012FL
  469. //
  470. // MessageId: BG_E_HTTP_ERROR_304
  471. //
  472. // MessageText:
  473. //
  474. // 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.
  475. //
  476. #define BG_E_HTTP_ERROR_304 0x80190130L
  477. //
  478. // MessageId: BG_E_HTTP_ERROR_305
  479. //
  480. // MessageText:
  481. //
  482. // The requested resource must be accessed through the proxy given by the location field.
  483. //
  484. #define BG_E_HTTP_ERROR_305 0x80190131L
  485. //
  486. // MessageId: BG_E_HTTP_ERROR_307
  487. //
  488. // MessageText:
  489. //
  490. // The URL has been temporarily relocated. Try again later.
  491. //
  492. #define BG_E_HTTP_ERROR_307 0x80190133L
  493. //
  494. // MessageId: BG_E_HTTP_ERROR_400
  495. //
  496. // MessageText:
  497. //
  498. // The server cannot process the request because the syntax is not valid.
  499. //
  500. #define BG_E_HTTP_ERROR_400 0x80190190L
  501. //
  502. // MessageId: BG_E_HTTP_ERROR_401
  503. //
  504. // MessageText:
  505. //
  506. // The requested resource requires user authentication.
  507. //
  508. #define BG_E_HTTP_ERROR_401 0x80190191L
  509. //
  510. // MessageId: BG_E_HTTP_ERROR_402
  511. //
  512. // MessageText:
  513. //
  514. // 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.
  515. //
  516. #define BG_E_HTTP_ERROR_402 0x80190192L
  517. //
  518. // MessageId: BG_E_HTTP_ERROR_403
  519. //
  520. // MessageText:
  521. //
  522. // The client does not have sufficient access rights to the requested server object.
  523. //
  524. #define BG_E_HTTP_ERROR_403 0x80190193L
  525. //
  526. // MessageId: BG_E_HTTP_ERROR_404
  527. //
  528. // MessageText:
  529. //
  530. // The requested URL does not exist on the server.
  531. //
  532. #define BG_E_HTTP_ERROR_404 0x80190194L
  533. //
  534. // MessageId: BG_E_HTTP_ERROR_405
  535. //
  536. // MessageText:
  537. //
  538. // The method used is not allowed.
  539. //
  540. #define BG_E_HTTP_ERROR_405 0x80190195L
  541. //
  542. // MessageId: BG_E_HTTP_ERROR_406
  543. //
  544. // MessageText:
  545. //
  546. // No responses acceptable to the client were found.
  547. //
  548. #define BG_E_HTTP_ERROR_406 0x80190196L
  549. //
  550. // MessageId: BG_E_HTTP_ERROR_407
  551. //
  552. // MessageText:
  553. //
  554. // Proxy authentication is required.
  555. //
  556. #define BG_E_HTTP_ERROR_407 0x80190197L
  557. //
  558. // MessageId: BG_E_HTTP_ERROR_408
  559. //
  560. // MessageText:
  561. //
  562. // The server timed out waiting for the request.
  563. //
  564. #define BG_E_HTTP_ERROR_408 0x80190198L
  565. //
  566. // MessageId: BG_E_HTTP_ERROR_409
  567. //
  568. // MessageText:
  569. //
  570. // 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.
  571. //
  572. #define BG_E_HTTP_ERROR_409 0x80190199L
  573. //
  574. // MessageId: BG_E_HTTP_ERROR_410
  575. //
  576. // MessageText:
  577. //
  578. // The requested resource is not currently available at the server, and no forwarding address is known.
  579. //
  580. #define BG_E_HTTP_ERROR_410 0x8019019AL
  581. //
  582. // MessageId: BG_E_HTTP_ERROR_411
  583. //
  584. // MessageText:
  585. //
  586. // The server cannot accept the request without a defined content length.
  587. //
  588. #define BG_E_HTTP_ERROR_411 0x8019019BL
  589. //
  590. // MessageId: BG_E_HTTP_ERROR_412
  591. //
  592. // MessageText:
  593. //
  594. // The precondition given in one or more of the request header fields evaluated to false when it was tested on the server.
  595. //
  596. #define BG_E_HTTP_ERROR_412 0x8019019CL
  597. //
  598. // MessageId: BG_E_HTTP_ERROR_413
  599. //
  600. // MessageText:
  601. //
  602. // The server cannot process the request because the request entity is too large.
  603. //
  604. #define BG_E_HTTP_ERROR_413 0x8019019DL
  605. //
  606. // MessageId: BG_E_HTTP_ERROR_414
  607. //
  608. // MessageText:
  609. //
  610. // The server cannot process the request because the request Uniform Resource Identifier (URI) is longer than the server can interpret.
  611. //
  612. #define BG_E_HTTP_ERROR_414 0x8019019EL
  613. //
  614. // MessageId: BG_E_HTTP_ERROR_415
  615. //
  616. // MessageText:
  617. //
  618. // 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.
  619. //
  620. #define BG_E_HTTP_ERROR_415 0x8019019FL
  621. //
  622. // MessageId: BG_E_HTTP_ERROR_416
  623. //
  624. // MessageText:
  625. //
  626. // The server could not satisfy the range request.
  627. //
  628. #define BG_E_HTTP_ERROR_416 0x801901A0L
  629. //
  630. // MessageId: BG_E_HTTP_ERROR_417
  631. //
  632. // MessageText:
  633. //
  634. // The server could not meet the expectation given in an Expect request-header field.
  635. //
  636. #define BG_E_HTTP_ERROR_417 0x801901A1L
  637. //
  638. // MessageId: BG_E_HTTP_ERROR_449
  639. //
  640. // MessageText:
  641. //
  642. // 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.
  643. //
  644. #define BG_E_HTTP_ERROR_449 0x801901C1L
  645. //
  646. // MessageId: BG_E_HTTP_ERROR_500
  647. //
  648. // MessageText:
  649. //
  650. // An unexpected condition prevented the server from fulfilling the request.
  651. //
  652. #define BG_E_HTTP_ERROR_500 0x801901F4L
  653. //
  654. // MessageId: BG_E_HTTP_ERROR_501
  655. //
  656. // MessageText:
  657. //
  658. // The server does not support the functionality required to fulfill the request.
  659. //
  660. #define BG_E_HTTP_ERROR_501 0x801901F5L
  661. //
  662. // MessageId: BG_E_HTTP_ERROR_502
  663. //
  664. // MessageText:
  665. //
  666. // The server, while acting as a gateway or proxy to fulfill the request, received an invalid response from the upstream server it accessed.
  667. //
  668. #define BG_E_HTTP_ERROR_502 0x801901F6L
  669. //
  670. // MessageId: BG_E_HTTP_ERROR_503
  671. //
  672. // MessageText:
  673. //
  674. // The service is temporarily overloaded.
  675. //
  676. #define BG_E_HTTP_ERROR_503 0x801901F7L
  677. //
  678. // MessageId: BG_E_HTTP_ERROR_504
  679. //
  680. // MessageText:
  681. //
  682. // The request was timed out waiting for a gateway.
  683. //
  684. #define BG_E_HTTP_ERROR_504 0x801901F8L
  685. //
  686. // MessageId: BG_E_HTTP_ERROR_505
  687. //
  688. // MessageText:
  689. //
  690. // The server does not support the HTTP protocol version that was used in the request message.
  691. //
  692. #define BG_E_HTTP_ERROR_505 0x801901F9L
  693. //
  694. // MessageId: MC_JOB_CANCELLED
  695. //
  696. // MessageText:
  697. //
  698. // The administrator %4 canceled job "%2" on behalf of %3. The job ID was %1.
  699. //
  700. #define MC_JOB_CANCELLED 0x80194000L
  701. //
  702. // MessageId: MC_FILE_DELETION_FAILED
  703. //
  704. // MessageText:
  705. //
  706. // While canceling job "%2", BITS was not able to remove the temporary files listed below.
  707. // If you can delete them, then you will regain some disk space. The job ID was %1.%\
  708. //
  709. // %3
  710. //
  711. #define MC_FILE_DELETION_FAILED 0x80194001L
  712. //
  713. // MessageId: MC_FILE_DELETION_FAILED_MORE
  714. //
  715. // MessageText:
  716. //
  717. // While canceling job "%2", BITS was not able to remove the temporary files listed below.
  718. // If you can delete them, then you will regain some disk space. The job ID was %1. %\
  719. //
  720. // %3
  721. // %\
  722. // Due to space limitations, not all files are listed here. Check for additional files of the form BITxxx.TMP in the same directory.
  723. //
  724. #define MC_FILE_DELETION_FAILED_MORE 0x80194002L
  725. //
  726. // MessageId: MC_JOB_PROPERTY_CHANGE
  727. //
  728. // MessageText:
  729. //
  730. // The administrator %3 modified the %4 property of job "%2". The job ID was %1.
  731. //
  732. #define MC_JOB_PROPERTY_CHANGE 0x80194003L
  733. //
  734. // MessageId: MC_JOB_TAKE_OWNERSHIP
  735. //
  736. // MessageText:
  737. //
  738. // The administrator %4 took ownership of job "%2" from %3. The job ID was %1.
  739. //
  740. #define MC_JOB_TAKE_OWNERSHIP 0x80194004L
  741. //
  742. // MessageId: MC_JOB_SCAVENGED
  743. //
  744. // MessageText:
  745. //
  746. // Job "%2" owned by %3 was canceled after being inactive for more than %4 days. The job ID was %1.
  747. //
  748. #define MC_JOB_SCAVENGED 0x80194005L
  749. //
  750. // MessageId: MC_JOB_NOTIFICATION_FAILURE
  751. //
  752. // MessageText:
  753. //
  754. // Job "%2" owned by %3 failed to notify its associated application. BITS will retry in %4 minutes. The job ID was %1.
  755. //
  756. #define MC_JOB_NOTIFICATION_FAILURE 0x80194006L
  757. //
  758. // MessageId: MC_STATE_FILE_CORRUPT
  759. //
  760. // MessageText:
  761. //
  762. // 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.
  763. //
  764. #define MC_STATE_FILE_CORRUPT 0x80194007L
  765. #endif //_BGCPYMSG_