Assets/messages.xml
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 4738 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753 4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4776 4777 4778 4779 4780 4781 4782 4783 4784 4785 4786 4787 4788 4789 4790 4791 4792 4793 4794 4795 4796 4797 4798 4799 4800 4801 4802 4803 4804 4805 4806 4807 4808 4809 4810 4811 4812 4813 4814 4815 4816 4817 4818 4819 4820 4821 4822 4823 4824 4825 4826 4827 4828 4829 4830 4831 4832 4833 4834 4835 4836 4837 4838 4839 4840 4841 4842 4843 4844 4845 4846 4847 4848 4849 4850 4851 4852 4853 4854 4855 4856 4857 4858 4859 4860 4861 4862 4863 4864 4865 4866 4867 4868 4869 4870 4871 4872 4873 4874 4875 4876 4877 4878 4879 4880 4881 4882 4883 4884 4885 4886 4887 4888 4889 4890 4891 4892 4893 4894 4895 4896 4897 4898 4899 4900 4901 4902 4903 4904 4905 4906 4907 4908 4909 4910 4911 4912 4913 4914 4915 4916 4917 4918 4919 4920 4921 4922 4923 4924 4925 4926 4927 4928 4929 4930 4931 4932 4933 4934 4935 4936 4937 4938 4939 4940 4941 4942 4943 4944 4945 4946 4947 4948 4949 4950 4951 4952 4953 4954 4955 4956 4957 4958 4959 4960 4961 4962 4963 4964 4965 4966 4967 4968 4969 4970 4971 4972 4973 4974 4975 4976 4977 4978 4979 4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 4990 4991 4992 4993 4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062 5063 5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 5078 5079 5080 5081 5082 5083 5084 5085 5086 5087 5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 5099 5100 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110 5111 5112 5113 5114 5115 5116 5117 5118 5119 5120 5121 5122 5123 5124 5125 5126 5127 5128 5129 5130 5131 5132 5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 5186 5187 5188 5189 5190 5191 5192 5193 5194 5195 5196 5197 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5209 5210 5211 5212 5213 5214 5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225 5226 5227 5228 5229 5230 5231 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 5243 5244 5245 5246 5247 5248 5249 5250 5251 5252 5253 5254 5255 5256 5257 5258 5259 5260 5261 5262 5263 5264 5265 5266 5267 5268 5269 5270 5271 5272 5273 5274 5275 5276 5277 5278 5279 5280 5281 5282 5283 5284 5285 5286 5287 5288 5289 5290 5291 5292 5293 5294 5295 5296 5297 5298 5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5314 5315 5316 5317 5318 5319 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5330 5331 5332 5333 5334 5335 5336 5337 5338 5339 5340 5341 5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365 5366 5367 5368 5369 5370 5371 5372 5373 5374 5375 5376 5377 5378 5379 5380 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395 5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5420 5421 5422 5423 5424 5425 5426 5427 5428 5429 5430 5431 5432 5433 5434 5435 5436 5437 5438 5439 5440 5441 5442 5443 5444 5445 5446 5447 5448 5449 5450 5451 5452 5453 5454 5455 5456 5457 5458 5459 5460 5461 5462 5463 5464 5465 5466 5467 5468 5469 5470 5471 5472 5473 5474 5475 5476 5477 5478 5479 5480 5481 5482 5483 5484 5485 5486 5487 5488 5489 5490 5491 5492 5493 5494 5495 5496 5497 5498 5499 5500 5501 5502 5503 5504 5505 5506 5507 5508 5509 5510 5511 5512 5513 5514 5515 5516 5517 5518 5519 5520 5521 5522 5523 5524 5525 5526 5527 5528 5529 5530 5531 5532 5533 5534 5535 5536 5537 5538 5539 5540 5541 5542 5543 5544 5545 5546 5547 5548 5549 5550 5551 5552 5553 5554 5555 5556 5557 5558 5559 5560 5561 5562 5563 5564 5565 5566 5567 5568 5569 5570 5571 5572 5573 5574 5575 5576 5577 5578 5579 5580 5581 5582 5583 5584 5585 5586 5587 5588 5589 5590 5591 5592 5593 5594 5595 5596 5597 5598 5599 5600 5601 5602 5603 5604 5605 5606 5607 5608 5609 5610 5611 5612 5613 5614 5615 5616 5617 5618 5619 5620 5621 5622 5623 5624 5625 5626 5627 5628 5629 5630 5631 5632 5633 5634 5635 5636 5637 5638 5639 5640 5641 5642 5643 5644 5645 5646 5647 5648 5649 5650 5651 5652 5653 5654 5655 5656 5657 5658 5659 5660 5661 5662 5663 5664 5665 5666 5667 5668 5669 5670 5671 5672 5673 5674 5675 5676 5677 5678 5679 5680 5681 5682 5683 5684 5685 5686 5687 5688 5689 5690 5691 5692 5693 5694 5695 5696 5697 5698 5699 5700 5701 5702 5703 5704 5705 5706 5707 5708 5709 5710 5711 5712 5713 5714 5715 5716 5717 5718 5719 5720 5721 5722 5723 5724 5725 5726 5727 5728 5729 5730 5731 5732 5733 5734 5735 5736 5737 5738 5739 5740 5741 5742 5743 5744 5745 5746 5747 5748 5749 5750 5751 5752 5753 5754 5755 5756 5757 5758 5759 5760 5761 5762 5763 5764 5765 5766 5767 5768 5769 5770 5771 5772 5773 5774 5775 5776 5777 5778 5779 5780 5781 5782 5783 5784 5785 5786 5787 5788 5789 5790 5791 5792 5793 5794 5795 5796 5797 5798 5799 5800 5801 5802 5803 5804 5805 5806 5807 5808 5809 5810 5811 5812 5813 5814 5815 5816 5817 5818 5819 5820 5821 5822 5823 5824 5825 5826 5827 5828 5829 5830 5831 5832 5833 5834 5835 5836 5837 5838 5839 5840 5841 5842 5843 5844 5845 5846 5847 5848 5849 5850 5851 5852 5853 5854 5855 5856 5857 5858 5859 5860 5861 5862 5863 5864 5865 5866 5867 5868 5869 5870 5871 5872 5873 5874 5875 5876 5877 5878 5879 5880 5881 5882 5883 5884 5885 5886 5887 5888 5889 5890 5891 5892 5893 5894 5895 5896 5897 5898 5899 5900 5901 5902 5903 5904 5905 5906 5907 5908 5909 5910 5911 5912 5913 5914 5915 5916 5917 5918 5919 5920 5921 5922 5923 5924 5925 5926 5927 5928 5929 5930 5931 5932 5933 5934 5935 5936 5937 5938 5939 5940 5941 5942 5943 5944 5945 5946 5947 5948 5949 5950 5951 5952 5953 5954 5955 5956 5957 5958 5959 5960 5961 5962 5963 5964 5965 5966 5967 5968 5969 5970 5971 5972 5973 5974 5975 5976 5977 5978 5979 5980 5981 5982 5983 5984 5985 5986 5987 5988 5989 5990 5991 5992 5993 5994 5995 5996 5997 5998 5999 6000 6001 6002 6003 6004 6005 6006 6007 6008 6009 6010 6011 6012 6013 6014 6015 6016 6017 6018 6019 6020 6021 6022 6023 6024 6025 6026 6027 6028 6029 6030 6031 6032 6033 6034 6035 6036 6037 6038 6039 6040 6041 6042 6043 6044 6045 6046 6047 6048 6049 6050 6051 6052 6053 6054 6055 6056 6057 6058 6059 6060 6061 6062 6063 6064 6065 6066 6067 6068 6069 6070 6071 6072 6073 6074 6075 6076 6077 6078 6079 6080 6081 6082 6083 6084 6085 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095 6096 6097 6098 6099 6100 6101 6102 6103 6104 6105 6106 6107 6108 6109 6110 6111 6112 6113 6114 6115 6116 6117 6118 6119 6120 6121 6122 6123 6124 6125 6126 6127 6128 6129 6130 6131 6132 6133 6134 6135 6136 6137 6138 6139 6140 6141 6142 6143 6144 6145 6146 6147 6148 6149 6150 6151 6152 6153 6154 6155 6156 6157 6158 6159 6160 6161 6162 6163 6164 6165 6166 6167 6168 6169 6170 6171 6172 6173 6174 6175 6176 6177 6178 6179 6180 6181 6182 6183 6184 6185 6186 6187 6188 6189 6190 6191 6192 6193 6194 6195 6196 6197 6198 6199 6200 6201 6202 6203 6204 6205 6206 6207 6208 6209 6210 6211 6212 6213 6214 6215 6216 6217 6218 6219 6220 6221 6222 6223 6224 6225 6226 6227 6228 6229 6230 6231 6232 6233 6234 6235 6236 6237 6238 6239 6240 6241 6242 6243 6244 6245 6246 6247 6248 6249 6250 6251 6252 6253 6254 6255 6256 6257 6258 6259 6260 6261 6262 6263 6264 6265 6266 6267 6268 6269 6270 6271 6272 6273 6274 6275 6276 6277 6278 6279 6280 6281 6282 6283 6284 6285 6286 6287 6288 6289 6290 6291 6292 6293 6294 6295 6296 6297 6298 6299 6300 6301 6302 6303 6304 6305 6306 6307 6308 6309 6310 6311 6312 6313 6314 6315 6316 6317 6318 6319 6320 6321 6322 6323 6324 6325 6326 6327 6328 6329 6330 6331 6332 6333 6334 6335 6336 6337 6338 6339 6340 6341 6342 6343 6344 6345 6346 6347 6348 6349 6350 6351 6352 6353 6354 6355 6356 6357 6358 6359 6360 6361 6362 6363 6364 6365 6366 6367 6368 6369 6370 6371 6372 6373 6374 6375 6376 6377 6378 6379 6380 6381 6382 6383 6384 6385 6386 6387 6388 6389 6390 6391 6392 6393 6394 6395 6396 6397 6398 6399 6400 6401 6402 6403 6404 6405 6406 6407 6408 6409 6410 6411 6412 6413 6414 6415 6416 6417 6418 6419 6420 6421 6422 6423 6424 6425 6426 6427 6428 6429 6430 6431 6432 6433 6434 6435 6436 6437 6438 6439 6440 6441 6442 6443 6444 6445 6446 6447 6448 6449 6450 6451 6452 6453 6454 6455 6456 6457 6458 6459 6460 6461 6462 6463 6464 6465 6466 6467 6468 6469 6470 6471 6472 6473 6474 6475 6476 6477 6478 6479 6480 6481 6482 6483 6484 6485 6486 6487 6488 6489 6490 6491 6492 6493 6494 6495 6496 6497 6498 6499 6500 6501 6502 6503 6504 6505 6506 6507 6508 6509 6510 6511 6512 6513 6514 6515 6516 6517 6518 6519 6520 6521 6522 6523 6524 6525 6526 6527 6528 6529 6530 6531 6532 6533 6534 6535 6536 6537 6538 6539 6540 6541 6542 6543 6544 6545 6546 6547 6548 6549 6550 6551 6552 6553 6554 6555 6556 6557 6558 6559 6560 6561 6562 6563 6564 6565 6566 6567 6568 6569 6570 6571 6572 6573 6574 6575 6576 6577 6578 6579 6580 6581 6582 6583 6584 6585 6586 6587 6588 6589 6590 6591 6592 6593 6594 6595 6596 6597 6598 6599 6600 6601 6602 6603 6604 6605 6606 6607 6608 6609 6610 6611 6612 6613 6614 6615 6616 6617 6618 6619 6620 6621 6622 6623 6624 6625 6626 6627 6628 6629 6630 6631 6632 6633 6634 6635 6636 6637 6638 6639 6640 6641 6642 6643 6644 6645 6646 6647 6648 6649 6650 6651 6652 6653 6654 6655 6656 6657 6658 6659 6660 6661 6662 6663 6664 6665 6666 6667 6668 6669 6670 6671 6672 6673 6674 6675 6676 6677 6678 6679 6680 6681 6682 6683 6684 6685 6686 6687 6688 6689 6690 6691 6692 6693 6694 6695 6696 6697 6698 6699 6700 6701 6702 6703 6704 6705 6706 6707 6708 6709 6710 6711 6712 6713 6714 6715 6716 6717 6718 6719 6720 6721 6722 6723 6724 6725 6726 6727 6728 6729 6730 6731 6732 6733 6734 6735 6736 6737 6738 6739 6740 6741 6742 6743 6744 6745 6746 6747 6748 6749 6750 6751 6752 6753 6754 6755 6756 6757 6758 6759 6760 6761 6762 6763 6764 6765 6766 6767 6768 6769 6770 6771 6772 6773 6774 6775 6776 6777 6778 6779 6780 6781 6782 6783 6784 6785 6786 6787 6788 6789 6790 6791 6792 6793 6794 6795 6796 6797 6798 6799 6800 6801 6802 6803 6804 6805 6806 6807 6808 6809 6810 6811 6812 6813 6814 6815 6816 6817 6818 6819 6820 6821 6822 6823 6824 6825 6826 6827 6828 6829 6830 6831 6832 6833 6834 6835 6836 6837 6838 6839 6840 6841 6842 6843 6844 6845 6846 6847 6848 6849 6850 6851 6852 6853 6854 6855 6856 6857 6858 6859 6860 6861 6862 6863 6864 6865 6866 6867 6868 6869 6870 6871 6872 6873 6874 6875 6876 6877 6878 6879 6880 6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6901 6902 6903 6904 6905 6906 6907 6908 6909 6910 6911 6912 6913 6914 6915 6916 6917 6918 6919 6920 6921 6922 6923 6924 6925 6926 6927 6928 6929 6930 6931 6932 6933 6934 6935 6936 6937 6938 6939 6940 6941 6942 6943 6944 6945 6946 6947 6948 6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6959 6960 6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 6978 6979 6980 6981 6982 6983 6984 6985 6986 6987 6988 6989 6990 6991 6992 6993 6994 6995 6996 6997 6998 6999 7000 7001 7002 7003 7004 7005 7006 7007 7008 7009 7010 7011 7012 7013 7014 7015 7016 7017 7018 7019 7020 7021 7022 7023 7024 7025 7026 7027 7028 7029 7030 7031 7032 7033 7034 7035 7036 7037 7038 7039 7040 7041 7042 7043 7044 7045 7046 7047 7048 7049 7050 7051 7052 7053 7054 7055 7056 7057 7058 7059 7060 7061 7062 7063 7064 7065 7066 7067 7068 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7079 7080 7081 7082 7083 7084 7085 7086 7087 7088 7089 7090 7091 7092 7093 7094 7095 7096 7097 7098 7099 7100 7101 7102 7103 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7119 7120 7121 7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7271 7272 7273 7274 7275 7276 7277 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8193 8194 8195 8196 8197 8198 8199 8200 8201 8202 8203 8204 8205 8206 8207 8208 8209 8210 8211 8212 8213 8214 8215 8216 8217 8218 8219 8220 8221 8222 8223 8224 8225 8226 8227 8228 8229 8230 8231 8232 8233 8234 8235 8236 8237 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8252 8253 8254 8255 8256 8257 8258 8259 8260 8261 8262 8263 8264 8265 8266 8267 8268 8269 8270 8271 8272 8273 8274 8275 8276 8277 8278 8279 8280 8281 8282 8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294 8295 8296 8297 8298 8299 8300 8301 8302 8303 8304 8305 8306 8307 8308 8309 8310 8311 8312 8313 8314 8315 8316 8317 8318 8319 8320 8321 8322 8323 8324 8325 8326 8327 8328 8329 8330 8331 8332 8333 8334 8335 8336 8337 8338 8339 8340 8341 8342 8343 8344 8345 8346 8347 8348 8349 8350 8351 8352 8353 8354 8355 8356 8357 8358 8359 8360 8361 8362 8363 8364 8365 8366 8367 8368 8369 8370 8371 8372 8373 8374 8375 8376 8377 8378 8379 8380 8381 8382 8383 8384 8385 8386 8387 8388 8389 8390 8391 8392 8393 8394 8395 8396 8397 8398 8399 8400 8401 8402 8403 8404 8405 8406 8407 8408 8409 8410 8411 8412 8413 8414 8415 8416 8417 8418 8419 8420 8421 8422 8423 8424 8425 8426 8427 8428 8429 8430 8431 8432 8433 8434 8435 8436 8437 8438 8439 8440 8441 8442 8443 8444 8445 8446 8447 8448 8449 8450 8451 8452 8453 8454 8455 8456 8457 8458 8459 8460 8461 8462 8463 8464 8465 8466 8467 8468 8469 8470 8471 8472 8473 8474 8475 8476 8477 8478 8479 8480 8481 8482 8483 8484 8485 8486 8487 8488 8489 8490 8491 8492 8493 8494 8495 8496 8497 8498 8499 8500 8501 8502 8503 8504 8505 8506 8507 8508 8509 8510 8511 8512 8513 8514 8515 8516 8517 8518 8519 8520 8521 8522 8523 8524 8525 8526 8527 8528 8529 8530 8531 8532 8533 8534 8535 8536 8537 8538 8539 8540 8541 8542 8543 8544 8545 8546 8547 8548 8549 8550 8551 8552 8553 8554 8555 8556 8557 8558 8559 8560 8561 8562 8563 8564 8565 8566 8567 8568 8569 8570 8571 8572 8573 8574 8575 8576 8577 8578 8579 8580 8581 8582 8583 8584 8585 8586 8587 8588 8589 8590 8591 8592 8593 8594 8595 8596 8597 8598 8599 8600 8601 8602 8603 8604 8605 8606 8607 8608 8609 8610 8611 8612 8613 8614 8615 8616 8617 8618 8619 8620 8621 8622 8623 8624 8625 8626 8627 8628 8629 8630 8631 8632 8633 8634 8635 8636 8637 8638 8639 8640 8641 8642 8643 8644 8645 8646 8647 8648 8649 8650 8651 8652 8653 8654 8655 8656 8657 8658 8659 8660 8661 8662 8663 8664 8665 8666 8667 8668 8669 8670 8671 8672 8673 8674 8675 8676 8677 8678 8679 8680 8681 8682 8683 8684 8685 8686 8687 8688 8689 8690 8691 8692 8693 8694 8695 8696 8697 8698 8699 8700 8701 8702 8703 8704 8705 8706 8707 8708 8709 8710 8711 8712 8713 8714 8715 8716 8717 8718 8719 8720 8721 8722 8723 8724 8725 8726 8727 8728 8729 8730 8731 8732 8733 8734 8735 8736 8737 8738 8739 8740 8741 8742 8743 8744 8745 8746 8747 8748 8749 8750 8751 8752 8753 8754 8755 8756 8757 8758 8759 8760 8761 8762 8763 8764 8765 8766 8767 8768 8769 8770 8771 8772 8773 8774 8775 8776 8777 8778 8779 8780 8781 8782 8783 8784 8785 8786 8787 8788 8789 8790 8791 8792 8793 8794 8795 8796 8797 8798 8799 8800 8801 8802 8803 8804 8805 8806 8807 8808 8809 8810 8811 8812 8813 8814 8815 8816 8817 8818 8819 8820 8821 8822 8823 8824 8825 8826 8827 8828 8829 8830 8831 8832 8833 8834 8835 8836 8837 8838 8839 8840 8841 8842 8843 8844 8845 8846 8847 8848 8849 8850 8851 8852 8853 8854 8855 8856 8857 8858 8859 8860 8861 8862 8863 8864 8865 8866 8867 8868 8869 8870 8871 8872 8873 8874 8875 8876 8877 8878 8879 8880 8881 8882 8883 8884 8885 8886 8887 8888 8889 8890 8891 8892 8893 8894 8895 8896 8897 8898 8899 8900 8901 8902 8903 8904 8905 8906 8907 8908 8909 8910 8911 8912 8913 8914 8915 8916 8917 8918 8919 8920 8921 8922 8923 8924 8925 8926 8927 8928 8929 8930 8931 8932 8933 8934 8935 8936 8937 8938 8939 8940 8941 8942 8943 8944 8945 8946 8947 8948 8949 8950 8951 8952 8953 8954 8955 8956 8957 8958 8959 8960 8961 8962 8963 8964 8965 8966 8967 8968 8969 8970 8971 8972 8973 8974 8975 8976 8977 8978 8979 8980 8981 8982 8983 8984 8985 8986 8987 8988 8989 8990 8991 8992 8993 8994 8995 8996 8997 8998 8999 9000 9001 9002 9003 9004 9005 9006 9007 9008 9009 9010 9011 9012 9013 9014 9015 9016 9017 9018 9019 9020 9021 9022 9023 9024 9025 9026 9027 9028 9029 9030 9031 9032 9033 9034 9035 9036 9037 9038 9039 9040 9041 9042 9043 9044 9045 9046 9047 9048 9049 9050 9051 9052 9053 9054 9055 9056 9057 9058 9059 9060 9061 9062 9063 9064 9065 9066 9067 9068 9069 9070 9071 9072 9073 9074 9075 9076 9077 9078 9079 9080 9081 9082 9083 9084 9085 9086 9087 9088 9089 9090 9091 9092 9093 9094 9095 9096 9097 9098 9099 9100 9101 9102 9103 9104 9105 9106 9107 9108 9109 9110 9111 9112 9113 9114 9115 9116 9117 9118 9119 9120 9121 9122 9123 9124 9125 9126 9127 9128 9129 9130 9131 9132 9133 9134 9135 9136 9137 9138 9139 9140 9141 9142 9143 9144 9145 9146 9147 9148 9149 9150 9151 9152 9153 9154 9155 9156 9157 9158 9159 9160 9161 9162 9163 9164 9165 9166 9167 9168 9169 9170 9171 9172 9173 9174 9175 9176 9177 9178 9179 9180 9181 9182 9183 9184 9185 9186 9187 9188 9189 9190 9191 9192 9193 9194 9195 9196 9197 9198 9199 9200 9201 9202 9203 9204 9205 9206 9207 9208 9209 9210 9211 9212 9213 9214 9215 9216 9217 9218 9219 9220 9221 9222 9223 9224 9225 9226 9227 9228 9229 9230 9231 9232 9233 9234 9235 9236 9237 9238 9239 9240 9241 9242 9243 9244 9245 9246 9247 9248 9249 9250 9251 9252 9253 9254 9255 9256 9257 9258 9259 9260 9261 9262 9263 9264 9265 9266 9267 9268 9269 9270 9271 9272 9273 9274 9275 9276 9277 9278 9279 9280 9281 9282 9283 9284 9285 9286 9287 9288 9289 9290 9291 9292 9293 9294 9295 9296 9297 9298 9299 9300 9301 9302 9303 9304 9305 9306 9307 9308 9309 9310 9311 9312 9313 9314 9315 9316 9317 9318 9319 9320 9321 9322 9323 9324 9325 9326 9327 9328 9329 9330 9331 9332 9333 9334 9335 9336 9337 9338 9339 9340 9341 9342 9343 9344 9345 9346 9347 9348 9349 9350 9351 9352 9353 9354 9355 9356 9357 9358 9359 9360 9361 9362 9363 9364 9365 9366 9367 9368 9369 9370 9371 9372 9373 9374 9375 9376 9377 9378 9379 9380 9381 9382 9383 9384 9385 9386 9387 9388 9389 9390 9391 9392 9393 9394 9395 9396 9397 9398 9399 9400 9401 9402 9403 9404 9405 9406 9407 9408 9409 9410 9411 9412 9413 9414 9415 9416 9417 9418 9419 9420 9421 9422 9423 9424 9425 9426 9427 9428 9429 9430 9431 9432 9433 9434 9435 9436 9437 9438 9439 9440 9441 9442 9443 9444 9445 9446 9447 9448 9449 9450 9451 9452 9453 9454 9455 9456 9457 9458 9459 9460 9461 9462 9463 9464 9465 9466 9467 9468 9469 9470 9471 9472 9473 9474 9475 9476 9477 9478 9479 9480 9481 9482 9483 9484 9485 9486 9487 9488 9489 9490 9491 9492 9493 9494 9495 9496 9497 9498 9499 9500 9501 9502 9503 9504 9505 9506 9507 9508 9509 9510 9511 9512 9513 9514 9515 9516 9517 9518 9519 9520 9521 9522 9523 9524 9525 9526 9527 9528 9529 9530 9531 9532 9533 9534 9535 9536 9537 9538 9539 9540 9541 9542 9543 9544 9545 9546 9547 9548 9549 9550 9551 9552 9553 9554 9555 9556 9557 9558 9559 9560 9561 9562 9563 9564 9565 9566 9567 9568 9569 9570 9571 9572 9573 9574 9575 9576 9577 9578 9579 9580 9581 9582 9583 9584 9585 9586 9587 9588 9589 9590 9591 9592 9593 9594 9595 9596 9597 9598 9599 9600 9601 9602 9603 9604 9605 9606 9607 9608 9609 9610 9611 9612 9613 9614 9615 9616 9617 9618 9619 9620 9621 9622 9623 9624 9625 9626 9627 9628 9629 9630 9631 9632 9633 9634 9635 9636 9637 9638 9639 9640 9641 9642 9643 9644 9645 9646 9647 9648 9649 9650 9651 9652 9653 9654 9655 9656 9657 9658 9659 9660 9661 9662 9663 9664 9665 9666 9667 9668 9669 9670 9671 9672 9673 9674 9675 9676 9677 9678 9679 9680 9681 9682 9683 9684 9685 9686 9687 9688 9689 9690 9691 9692 9693 9694 9695 9696 9697 9698 9699 9700 9701 9702 9703 9704 9705 9706 9707 9708 9709 9710 9711 9712 9713 9714 9715 9716 9717 9718 9719 9720 9721 9722 9723 9724 9725 9726 9727 9728 9729 9730 9731 9732 9733 9734 9735 9736 9737 9738 9739 9740 9741 9742 9743 9744 9745 9746 9747 9748 9749 9750 9751 9752 9753 9754 9755 9756 9757 9758 9759 9760 9761 9762 9763 9764 9765 9766 9767 9768 9769 9770 9771 9772 9773 9774 9775 9776 9777 9778 9779 9780 9781 9782 9783 9784 9785 9786 9787 9788 9789 9790 9791 9792 9793 9794 9795 9796 9797 9798 9799 9800 9801 9802 9803 9804 9805 9806 9807 9808 9809 9810 9811 9812 9813 9814 9815 9816 9817 9818 9819 9820 9821 9822 9823 9824 9825 9826 9827 9828 9829 9830 9831 9832 9833 9834 9835 9836 9837 9838 9839 9840 9841 9842 9843 9844 9845 9846 9847 9848 9849 9850 9851 9852 9853 9854 9855 9856 9857 9858 9859 9860 9861 9862 9863 9864 9865 9866 9867 9868 9869 9870 9871 9872 9873 9874 9875 9876 9877 9878 9879 9880 9881 9882 9883 9884 9885 9886 9887 9888 9889 9890 9891 9892 9893 9894 9895 9896 9897 9898 9899 9900 9901 9902 9903 9904 9905 9906 9907 9908 9909 9910 9911 9912 9913 9914 9915 9916 9917 9918 9919 9920 9921 9922 9923 9924 9925 9926 9927 9928 9929 9930 9931 9932 9933 9934 9935 9936 9937 9938 9939 9940 9941 9942 9943 9944 9945 9946 9947 9948 9949 9950 9951 9952 9953 9954 9955 9956 9957 9958 9959 9960 9961 9962 9963 9964 9965 9966 9967 9968 9969 9970 9971 9972 9973 9974 9975 9976 9977 9978 9979 9980 9981 9982 9983 9984 9985 9986 9987 9988 9989 9990 9991 9992 9993 9994 9995 9996 9997 9998 9999 10000 10001 10002 10003 10004 10005 10006 10007 10008 10009 10010 10011 10012 10013 10014 10015 10016 10017 10018 10019 10020 10021 10022 10023 10024 10025 10026 10027 10028 10029 10030 10031 10032 10033 10034 10035 10036 10037 10038 10039 10040 10041 10042 10043 10044 10045 10046 10047 10048 10049 10050 10051 10052 10053 10054 10055 10056 10057 10058 10059 10060 10061 10062 10063 10064 10065 10066 10067 10068 10069 10070 10071 10072 10073 10074 10075 10076 10077 10078 10079 10080 10081 10082 10083 10084 10085 10086 10087 10088 10089 10090 10091 10092 10093 10094 10095 10096 10097 10098 10099 10100 10101 10102 10103 10104 10105 10106 10107 10108 10109 10110 10111 10112 10113 10114 10115 10116 10117 10118 10119 10120 10121 10122 10123 10124 10125 10126 10127 10128 10129 10130 10131 10132 10133 10134 10135 10136 10137 10138 10139 10140 10141 10142 10143 10144 10145 10146 10147 10148 10149 10150 10151 10152 10153 10154 10155 10156 10157 10158 10159 10160 10161 10162 10163 10164 10165 10166 10167 10168 10169 10170 10171 10172 10173 10174 10175 10176 10177 10178 10179 10180 10181 10182 10183 10184 10185 10186 10187 10188 10189 10190 10191 10192 10193 10194 10195 10196 10197 10198 10199 10200 10201 10202 10203 10204 10205 10206 10207 10208 10209 10210 10211 10212 10213 10214 10215 10216 10217 10218 10219 10220 10221 10222 10223 10224 10225 10226 10227 10228 10229 10230 10231 10232 10233 10234 10235 10236 10237 10238 10239 10240 10241 10242 10243 10244 10245 10246 10247 10248 10249 10250 10251 10252 10253 10254 10255 10256 10257 10258 10259 10260 10261 10262 10263 10264 10265 10266 10267 10268 10269 10270 10271 10272 10273 10274 10275 10276 10277 10278 10279 10280 10281 10282 10283 10284 10285 10286 10287 10288 10289 10290 10291 10292 10293 10294 10295 10296 10297 10298 10299 10300 10301 10302 10303 10304 10305 10306 10307 10308 10309 10310 10311 10312 10313 10314 10315 10316 10317 10318 10319 10320 10321 10322 10323 10324 10325 10326 10327 10328 10329 10330 10331 10332 10333 10334 10335 10336 10337 10338 10339 10340 10341 10342 10343 10344 10345 10346 10347 10348 10349 10350 10351 10352 10353 10354 10355 10356 10357 10358 10359 10360 10361 10362 10363 10364 10365 10366 10367 10368 10369 10370 10371 10372 10373 10374 10375 10376 10377 10378 10379 10380 10381 10382 10383 10384 10385 10386 10387 10388 10389 10390 10391 10392 10393 10394 10395 10396 10397 10398 10399 10400 10401 10402 10403 10404 10405 10406 10407 10408 10409 10410 10411 10412 10413 10414 10415 10416 10417 10418 10419 10420 10421 10422 10423 10424 10425 10426 10427 10428 10429 10430 10431 10432 10433 10434 10435 10436 10437 10438 10439 10440 10441 10442 10443 10444 10445 10446 10447 10448 10449 10450 10451 10452 10453 10454 10455 10456 10457 10458 10459 10460 10461 10462 10463 10464 10465 10466 10467 10468 10469 10470 10471 10472 10473 10474 10475 10476 10477 10478 10479 10480 10481 10482 10483 10484 10485 10486 10487 10488 10489 10490 10491 10492 10493 10494 10495 10496 10497 10498 10499 10500 10501 10502 10503 10504 10505 10506 10507 10508 10509 10510 10511 10512 10513 10514 10515 10516 10517 10518 10519 10520 10521 10522 10523 10524 10525 10526 10527 10528 10529 10530 10531 10532 10533 10534 10535 10536 10537 10538 10539 10540 10541 10542 10543 10544 10545 10546 10547 10548 10549 10550 10551 10552 10553 10554 10555 10556 10557 10558 10559 10560 10561 10562 10563 10564 10565 10566 10567 10568 10569 10570 10571 10572 10573 10574 10575 10576 10577 10578 10579 10580 10581 10582 10583 10584 10585 10586 10587 10588 10589 10590 10591 10592 10593 10594 10595 10596 10597 10598 10599 10600 10601 10602 10603 10604 10605 10606 10607 10608 10609 10610 10611 10612 10613 10614 10615 10616 10617 10618 10619 10620 10621 10622 10623 10624 10625 10626 10627 10628 10629 10630 10631 10632 10633 10634 10635 10636 10637 10638 10639 10640 10641 10642 10643 10644 10645 10646 10647 10648 10649 10650 10651 10652 10653 10654 10655 10656 10657 10658 10659 10660 10661 10662 10663 10664 10665 10666 10667 10668 10669 10670 10671 10672 10673 10674 10675 10676 10677 10678 10679 10680 10681 10682 10683 10684 10685 10686 10687 10688 10689 10690 10691 10692 10693 10694 10695 10696 10697 10698 10699 10700 10701 10702 10703 10704 10705 10706 10707 10708 10709 10710 10711 10712 10713 10714 10715 10716 10717 10718 10719 10720 10721 10722 10723 10724 10725 10726 10727 10728 10729 10730 10731 10732 10733 10734 10735 10736 10737 10738 10739 10740 10741 10742 10743 10744 10745 10746 10747 10748 10749 10750 10751 10752 10753 10754 10755 10756 10757 10758 10759 10760 10761 10762 10763 10764 10765 10766 10767 10768 10769 10770 10771 10772 10773 10774 10775 10776 10777 10778 10779 10780 10781 10782 10783 10784 10785 10786 10787 10788 10789 10790 10791 10792 10793 10794 10795 10796 10797 10798 10799 10800 10801 10802 10803 10804 10805 10806 10807 10808 10809 10810 10811 10812 10813 10814 10815 10816 10817 10818 10819 10820 10821 10822 10823 10824 10825 10826 10827 10828 10829 10830 10831 10832 10833 10834 10835 10836 10837 10838 10839 10840 10841 10842 10843 10844 10845 10846 10847 10848 10849 10850 10851 10852 10853 10854 10855 10856 10857 10858 10859 10860 10861 10862 10863 10864 10865 10866 10867 10868 10869 10870 10871 10872 10873 10874 10875 10876 10877 10878 10879 10880 10881 10882 10883 10884 10885 10886 10887 10888 10889 10890 10891 10892 10893 10894 10895 10896 10897 10898 10899 10900 10901 10902 10903 10904 10905 10906 10907 10908 10909 10910 10911 10912 10913 10914 10915 10916 10917 10918 10919 10920 10921 10922 10923 10924 10925 10926 10927 10928 10929 10930 10931 10932 10933 10934 10935 10936 10937 10938 10939 10940 10941 10942 10943 10944 10945 10946 10947 10948 10949 10950 10951 10952 10953 10954 10955 10956 10957 10958 10959 10960 10961 10962 10963 10964 10965 10966 10967 10968 10969 10970 10971 10972 10973 10974 10975 10976 10977 10978 10979 10980 10981 10982 10983 10984 10985 10986 10987 10988 10989 10990 10991 10992 10993 10994 10995 10996 10997 10998 10999 11000 11001 11002 11003 11004 11005 11006 11007 11008 11009 11010 11011 11012 11013 11014 11015 11016 11017 11018 11019 11020 11021 11022 11023 11024 11025 11026 11027 11028 11029 11030 11031 11032 11033 11034 11035 11036 11037 11038 11039 11040 11041 11042 11043 11044 11045 11046 11047 11048 11049 11050 11051 11052 11053 11054 11055 11056 11057 11058 11059 11060 11061 11062 11063 11064 11065 11066 11067 11068 11069 11070 11071 11072 11073 11074 11075 11076 11077 11078 11079 11080 11081 11082 11083 11084 11085 11086 11087 11088 11089 11090 11091 11092 11093 11094 11095 11096 11097 11098 11099 11100 11101 11102 11103 11104 11105 11106 11107 11108 11109 11110 11111 11112 11113 11114 11115 11116 11117 11118 11119 11120 11121 11122 11123 11124 11125 11126 11127 11128 11129 11130 11131 11132 11133 11134 11135 11136 11137 11138 11139 11140 11141 11142 11143 11144 11145 11146 11147 11148 11149 11150 11151 11152 11153 11154 11155 11156 11157 11158 11159 11160 11161 11162 11163 11164 11165 11166 11167 11168 11169 11170 11171 11172 11173 11174 11175 11176 11177 11178 11179 11180 11181 11182 11183 11184 11185 11186 11187 11188 11189 11190 11191 11192 11193 11194 11195 11196 11197 11198 11199 11200 11201 11202 11203 11204 11205 11206 11207 11208 11209 11210 11211 11212 11213 11214 11215 11216 11217 11218 11219 11220 11221 11222 11223 11224 11225 11226 11227 11228 11229 11230 11231 11232 11233 11234 11235 11236 11237 11238 11239 11240 11241 11242 11243 11244 11245 11246 11247 11248 11249 11250 11251 11252 11253 11254 11255 11256 11257 11258 11259 11260 11261 11262 11263 11264 11265 11266 11267 11268 11269 11270 11271 11272 11273 11274 11275 11276 11277 11278 11279 11280 11281 11282 11283 11284 11285 11286 11287 11288 11289 11290 11291 11292 11293 11294 11295 11296 11297 11298 11299 11300 11301 11302 11303 11304 11305 11306 11307 11308 11309 11310 11311 11312 11313 11314 11315 11316 11317 11318 11319 11320 11321 11322 11323 11324 11325 11326 11327 11328 11329 11330 11331 11332 11333 11334 11335 11336 11337 11338 11339 11340 11341 11342 11343 11344 11345 11346 11347 11348 11349 11350 11351 11352 11353 11354 11355 11356 11357 11358 11359 11360 11361 11362 11363 11364 11365 11366 11367 11368 11369 11370 11371 11372 11373 11374 11375 11376 11377 11378 11379 11380 11381 11382 11383 11384 11385 11386 11387 11388 11389 11390 11391 11392 11393 11394 11395 11396 11397 11398 11399 11400 11401 11402 11403 11404 11405 11406 11407 11408 11409 11410 11411 11412 11413 11414 11415 11416 11417 11418 11419 11420 11421 11422 11423 11424 11425 11426 11427 11428 11429 11430 11431 11432 11433 11434 11435 11436 11437 11438 11439 11440 11441 11442 11443 11444 11445 11446 11447 11448 11449 11450 11451 11452 11453 11454 11455 11456 11457 11458 11459 11460 11461 11462 11463 11464 11465 11466 11467 11468 11469 11470 11471 11472 11473 11474 11475 11476 11477 11478 11479 11480 11481 11482 11483 11484 11485 11486 11487 11488 11489 11490 11491 11492 11493 11494 11495 11496 11497 11498 11499 11500 11501 11502 11503 11504 11505 11506 11507 11508 11509 11510 11511 11512 11513 11514 11515 11516 11517 11518 11519 11520 11521 11522 11523 11524 11525 11526 11527 11528 11529 11530 11531 11532 11533 11534 11535 11536 11537 11538 11539 11540 11541 11542 11543 11544 11545 11546 11547 11548 11549 11550 11551 11552 11553 11554 11555 11556 11557 11558 11559 11560 11561 11562 11563 11564 11565 11566 11567 11568 11569 11570 11571 11572 11573 11574 11575 11576 11577 11578 11579 11580 11581 11582 11583 11584 11585 11586 11587 11588 11589 11590 11591 11592 11593 11594 11595 11596 11597 11598 11599 11600 11601 11602 11603 11604 11605 11606 11607 11608 11609 11610 11611 11612 11613 11614 11615 11616 11617 11618 11619 11620 11621 11622 11623 11624 11625 11626 11627 11628 11629 11630 11631 11632 11633 11634 11635 11636 11637 11638 11639 11640 11641 11642 11643 11644 11645 11646 11647 11648 11649 11650 11651 11652 11653 11654 11655 11656 11657 11658 11659 11660 11661 11662 11663 11664 11665 11666 11667 11668 11669 11670 11671 11672 11673 11674 11675 11676 11677 11678 11679 11680 11681 11682 11683 11684 11685 11686 11687 11688 11689 11690 11691 11692 11693 11694 11695 11696 11697 11698 11699 11700 11701 11702 11703 11704 11705 11706 11707 11708 11709 11710 11711 11712 11713 11714 11715 11716 11717 11718 11719 11720 11721 11722 11723 11724 11725 11726 11727 11728 11729 11730 11731 11732 11733 11734 11735 11736 11737 11738 11739 11740 11741 11742 11743 11744 11745 11746 11747 11748 11749 11750 11751 11752 11753 11754 11755 11756 11757 11758 11759 11760 11761 11762 11763 11764 11765 11766 11767 11768 11769 11770 11771 11772 11773 11774 11775 11776 11777 11778 11779 11780 11781 11782 11783 11784 11785 11786 11787 11788 11789 11790 11791 11792 11793 11794 11795 11796 11797 11798 11799 11800 11801 11802 11803 11804 11805 11806 11807 11808 11809 11810 11811 11812 11813 11814 11815 11816 11817 11818 11819 11820 11821 11822 11823 11824 11825 11826 11827 11828 11829 11830 11831 11832 11833 11834 11835 11836 11837 11838 11839 11840 11841 11842 11843 11844 11845 11846 11847 11848 11849 11850 11851 11852 11853 11854 11855 11856 11857 11858 11859 11860 11861 11862 11863 11864 11865 11866 11867 11868 11869 11870 11871 11872 11873 11874 11875 11876 11877 11878 11879 11880 11881 11882 11883 11884 11885 11886 11887 11888 11889 11890 11891 11892 11893 11894 11895 11896 11897 11898 11899 11900 11901 11902 11903 11904 11905 11906 11907 11908 11909 11910 11911 11912 11913 11914 11915 11916 11917 11918 11919 11920 11921 11922 11923 11924 11925 11926 11927 11928 11929 11930 11931 11932 11933 11934 11935 11936 11937 11938 11939 11940 11941 11942 11943 11944 11945 11946 11947 11948 11949 11950 11951 11952 11953 11954 11955 11956 11957 11958 11959 11960 11961 11962 11963 11964 11965 11966 11967 11968 11969 11970 11971 11972 11973 11974 11975 11976 11977 11978 11979 11980 11981 11982 11983 11984 11985 11986 11987 11988 11989 11990 11991 11992 11993 11994 11995 11996 11997 11998 11999 12000 12001 12002 12003 12004 12005 12006 12007 12008 12009 12010 12011 12012 12013 12014 12015 12016 12017 12018 12019 12020 12021 12022 12023 12024 12025 12026 12027 12028 12029 12030 12031 12032 12033 12034 12035 12036 12037 12038 12039 12040 12041 12042 12043 12044 12045 12046 12047 12048 12049 12050 12051 12052 12053 12054 12055 12056 12057 12058 12059 12060 12061 12062 12063 12064 12065 12066 12067 12068 12069 12070 12071 12072 12073 12074 12075 12076 12077 12078 12079 12080 12081 12082 12083 12084 12085 12086 12087 12088 12089 12090 12091 12092 12093 12094 12095 12096 12097 12098 12099 12100 12101 12102 12103 12104 12105 12106 12107 12108 12109 12110 12111 12112 12113 12114 12115 12116 12117 12118 12119 12120 12121 12122 12123 12124 12125 12126 12127 12128 12129 12130 12131 12132 12133 12134 12135 12136 12137 12138 12139 12140 12141 12142 12143 12144 12145 12146 12147 12148 12149 12150 12151 12152 12153 12154 12155 12156 12157 12158 12159 12160 12161 12162 12163 12164 12165 12166 12167 12168 12169 12170 12171 12172 12173 12174 12175 12176 12177 12178 12179 12180 12181 12182 12183 12184 12185 12186 12187 12188 12189 12190 12191 12192 12193 12194 12195 12196 12197 12198 12199 12200 12201 12202 12203 12204 12205 12206 12207 12208 12209 12210 12211 12212 12213 12214 12215 12216 12217 12218 12219 12220 12221 12222 12223 12224 12225 12226 12227 12228 12229 12230 12231 12232 12233 12234 12235 12236 12237 12238 12239 12240 12241 12242 12243 12244 12245 12246 12247 12248 12249 12250 12251 12252 12253 12254 12255 12256 12257 12258 12259 12260 12261 12262 12263 12264 12265 12266 12267 12268 12269 12270 12271 12272 12273 12274 12275 12276 12277 12278 12279 12280 12281 12282 12283 12284 12285 12286 12287 12288 12289 12290 12291 12292 12293 12294 12295 12296 12297 12298 12299 12300 12301 12302 12303 12304 12305 12306 12307 12308 12309 12310 12311 12312 12313 12314 12315 12316 12317 12318 12319 12320 12321 12322 12323 12324 12325 12326 12327 12328 12329 12330 12331 12332 12333 12334 12335 12336 12337 12338 12339 12340 12341 12342 12343 12344 12345 12346 12347 12348 12349 12350 12351 12352 12353 12354 12355 12356 12357 12358 12359 12360 12361 12362 12363 12364 12365 12366 12367 12368 12369 12370 12371 12372 12373 12374 12375 12376 12377 12378 12379 12380 12381 12382 12383 12384 12385 12386 12387 12388 12389 12390 12391 12392 12393 12394 12395 12396 12397 12398 12399 12400 12401 12402 12403 12404 12405 12406 12407 12408 12409 12410 12411 12412 12413 12414 12415 12416 12417 12418 12419 12420 12421 12422 12423 12424 12425 12426 12427 12428 12429 12430 12431 12432 12433 12434 12435 12436 12437 12438 12439 12440 12441 12442 12443 12444 12445 12446 12447 12448 12449 12450 12451 12452 12453 12454 12455 12456 12457 12458 12459 12460 12461 12462 12463 12464 12465 12466 12467 12468 12469 12470 12471 12472 12473 12474 12475 12476 12477 12478 12479 12480 12481 12482 12483 12484 12485 12486 12487 12488 12489 12490 12491 12492 12493 12494 12495 12496 12497 12498 12499 12500 12501 12502 12503 12504 12505 12506 12507 12508 12509 12510 12511 12512 12513 12514 12515 12516 12517 12518 12519 12520 12521 12522 12523 12524 12525 12526 12527 12528 12529 12530 12531 12532 12533 12534 12535 12536 12537 12538 12539 12540 12541 12542 12543 12544 12545 12546 12547 12548 12549 12550 12551 12552 12553 12554 12555 12556 12557 12558 12559 12560 12561 12562 12563 12564 12565 12566 12567 12568 12569 12570 12571 12572 12573 12574 12575 12576 12577 12578 12579 12580 12581 12582 12583 12584 12585 12586 12587 12588 12589 12590 12591 12592 12593 12594 12595 12596 12597 12598 12599 12600 12601 12602 12603 12604 12605 12606 12607 12608 12609 12610 12611 12612 12613 12614 12615 12616 12617 12618 12619 12620 12621 12622 12623 12624 12625 12626 12627 12628 12629 12630 12631 12632 12633 12634 12635 12636 12637 12638 12639 12640 12641 12642 12643 12644 12645 12646 12647 12648 12649 12650 12651 12652 12653 12654 12655 12656 12657 12658 12659 12660 12661 12662 12663 12664 12665 12666 12667 12668 12669 12670 12671 12672 12673 12674 12675 12676 12677 12678 12679 12680 12681 12682 12683 12684 12685 12686 12687 12688 12689 12690 12691 12692 12693 12694 12695 12696 12697 12698 12699 12700 12701 12702 12703 12704 12705 12706 12707 12708 12709 12710 12711 12712 12713 12714 12715 12716 12717 12718 12719 12720 12721 12722 12723 12724 12725 12726 12727 12728 12729 12730 12731 12732 12733 12734 12735 12736 12737 12738 12739 12740 12741 12742 12743 12744 12745 12746 12747 12748 12749 12750 12751 12752 12753 12754 12755 12756 12757 12758 12759 12760 12761 12762 12763 12764 12765 12766 12767 12768 12769 12770 12771 12772 12773 12774 12775 12776 12777 12778 12779 12780 12781 12782 12783 12784 12785 12786 12787 12788 12789 12790 12791 12792 12793 12794 12795 12796 12797 12798 12799 12800 12801 12802 12803 12804 12805 12806 12807 12808 12809 12810 12811 12812 12813 12814 12815 12816 12817 12818 12819 12820 12821 12822 12823 12824 12825 12826 12827 12828 12829 12830 12831 12832 12833 12834 12835 12836 12837 12838 12839 12840 12841 12842 12843 12844 12845 12846 12847 12848 12849 12850 12851 12852 12853 12854 12855 12856 12857 12858 12859 12860 12861 12862 12863 12864 12865 12866 12867 12868 12869 12870 12871 12872 12873 12874 12875 12876 12877 12878 12879 12880 12881 12882 12883 12884 12885 12886 12887 12888 12889 12890 12891 12892 12893 12894 12895 12896 12897 12898 12899 12900 12901 12902 12903 12904 12905 12906 12907 12908 12909 12910 12911 12912 12913 12914 12915 12916 12917 12918 12919 12920 12921 12922 12923 12924 12925 12926 12927 12928 12929 12930 12931 12932 12933 12934 12935 12936 12937 12938 12939 12940 12941 12942 12943 12944 12945 12946 12947 12948 12949 12950 12951 12952 12953 12954 12955 12956 12957 12958 12959 12960 12961 12962 12963 12964 12965 12966 12967 12968 12969 12970 12971 12972 12973 12974 12975 12976 12977 12978 12979 12980 12981 12982 12983 12984 12985 12986 12987 12988 12989 12990 12991 12992 12993 12994 12995 12996 12997 12998 12999 13000 13001 13002 13003 13004 13005 13006 13007 13008 13009 13010 13011 13012 13013 13014 13015 13016 13017 13018 13019 13020 13021 13022 13023 13024 13025 13026 13027 13028 13029 13030 13031 13032 13033 13034 13035 13036 13037 13038 13039 13040 13041 13042 13043 13044 13045 13046 13047 13048 13049 13050 13051 13052 13053 13054 13055 13056 13057 13058 13059 13060 13061 13062 13063 13064 13065 13066 13067 13068 13069 13070 13071 13072 13073 13074 13075 13076 13077 13078 13079 13080 13081 13082 13083 13084 13085 13086 13087 13088 13089 13090 13091 13092 13093 13094 13095 13096 13097 13098 13099 13100 13101 13102 13103 13104 13105 13106 13107 13108 13109 13110 13111 13112 13113 13114 13115 13116 13117 13118 13119 13120 13121 13122 13123 13124 13125 13126 13127 13128 13129 13130 13131 13132 13133 13134 13135 13136 13137 13138 13139 13140 13141 13142 13143 13144 13145 13146 13147 13148 13149 13150 13151 13152 13153 13154 13155 13156 13157 13158 13159 13160 13161 13162 13163 13164 13165 13166 13167 13168 13169 13170 13171 13172 13173 13174 13175 13176 13177 13178 13179 13180 13181 13182 13183 13184 13185 13186 13187 13188 13189 13190 13191 13192 13193 13194 13195 13196 13197 13198 13199 13200 13201 13202 13203 13204 13205 13206 13207 13208 13209 13210 13211 13212 13213 13214 13215 13216 13217 13218 13219 13220 13221 13222 13223 13224 13225 13226 13227 13228 13229 13230 13231 13232 13233 13234 13235 13236 13237 13238 13239 13240 13241 13242 13243 13244 13245 13246 13247 13248 13249 13250 13251 13252 13253 13254 13255 13256 13257 13258 13259 13260 13261 13262 13263 13264 13265 13266 13267 13268 13269 13270 13271 13272 13273 13274 13275 13276 13277 13278 13279 13280 13281 13282 13283 13284 13285 13286 13287 13288 13289 13290 13291 13292 13293 13294 13295 13296 13297 13298 13299 13300 13301 13302 13303 13304 13305 13306 13307 13308 13309 13310 13311 13312 13313 13314 13315 13316 13317 13318 13319 13320 13321 13322 13323 13324 13325 13326 13327 13328 13329 13330 13331 13332 13333 13334 13335 13336 13337 13338 13339 13340 13341 13342 13343 13344 13345 13346 13347 13348 13349 13350 13351 13352 13353 13354 13355 13356 13357 13358 13359 13360 13361 13362 13363 13364 13365 13366 13367 13368 13369 13370 13371 13372 13373 13374 13375 13376 13377 13378 13379 13380 13381 13382 13383 13384 13385 13386 13387 13388 13389 13390 13391 13392 13393 13394 13395 13396 13397 13398 13399 13400 13401 13402 13403 13404 13405 13406 13407 13408 13409 13410 13411 13412 13413 13414 13415 13416 13417 13418 13419 13420 13421 13422 13423 13424 13425 13426 13427 13428 13429 13430 13431 13432 13433 13434 13435 13436 13437 13438 13439 13440 13441 13442 13443 13444 13445 13446 13447 13448 13449 13450 13451 13452 13453 13454 13455 13456 13457 13458 13459 13460 13461 13462 13463 13464 13465 13466 13467 13468 13469 13470 13471 13472 13473 13474 13475 13476 13477 13478 13479 13480 13481 13482 13483 13484 13485 13486 13487 13488 13489 13490 13491 13492 13493 13494 13495 13496 13497 13498 13499 13500 13501 13502 13503 13504 13505 13506 13507 13508 13509 13510 13511 13512 13513 13514 13515 13516 13517 13518 13519 13520 13521 13522 13523 13524 13525 13526 13527 13528 13529 13530 13531 13532 13533 13534 13535 13536 13537 13538 13539 13540 13541 13542 13543 13544 13545 13546 13547 13548 13549 13550 13551 13552 13553 13554 13555 13556 13557 13558 13559 13560 13561 13562 13563 13564 13565 13566 13567 13568 13569 13570 13571 13572 13573 13574 13575 13576 13577 13578 13579 13580 13581 13582 13583 13584 13585 13586 13587 13588 13589 13590 13591 13592 13593 13594 13595 13596 13597 13598 13599 13600 13601 13602 13603 13604 13605 13606 13607 13608 13609 13610 13611 13612 13613 13614 13615 13616 13617 13618 13619 13620 13621 13622 13623 13624 13625 13626 13627 13628 13629 13630 13631 13632 13633 13634 13635 13636 13637 13638 13639 13640 13641 13642 13643 13644 13645 13646 13647 13648 13649 13650 13651 13652 13653 13654 13655 13656 13657 13658 13659 13660 13661 13662 13663 13664 13665 13666 13667 13668 13669 13670 13671 13672 13673 13674 13675 13676 13677 13678 13679 13680 13681 13682 13683 13684 13685 13686 13687 13688 13689 13690 13691 13692 13693 13694 13695 13696 13697 13698 13699 13700 13701 13702 13703 13704 13705 13706 13707 13708 13709 13710 13711 13712 13713 13714 13715 13716 13717 13718 13719 13720 13721 13722 13723 13724 13725 13726 13727 13728 13729 13730 13731 13732 13733 13734 13735 13736 13737 13738 13739 13740 13741 13742 13743 13744 13745 13746 13747 13748 13749 13750 13751 13752 13753 13754 13755 13756 13757 13758 13759 13760 13761 13762 13763 13764 13765 13766 13767 13768 13769 13770 13771 13772 13773 13774 13775 13776 13777 13778 13779 13780 13781 13782 13783 13784 13785 13786 13787 13788 13789 13790 13791 13792 13793 13794 13795 13796 13797 13798 13799 13800 13801 13802 13803 13804 13805 13806 13807 13808 13809 13810 13811 13812 13813 13814 13815 13816 13817 13818 13819 13820 13821 13822 13823 13824 13825 13826 13827 13828 13829 13830 13831 13832 13833 13834 13835 13836 13837 13838 13839 13840 13841 13842 13843 13844 13845 13846 13847 13848 13849 13850 13851 13852 13853 13854 13855 13856 13857 13858 13859 13860 13861 13862 13863 13864 13865 13866 13867 13868 13869 13870 13871 13872 13873 13874 13875 13876 13877 13878 13879 13880 13881 13882 13883 13884 13885 13886 13887 13888 13889 13890 13891 13892 13893 13894 13895 13896 13897 13898 13899 13900 13901 13902 13903 13904 13905 13906 13907 13908 13909 13910 13911 13912 13913 13914 13915 13916 13917 13918 13919 13920 13921 13922 13923 13924 13925 13926 13927 13928 13929 13930 13931 13932 13933 13934 13935 13936 13937 13938 13939 13940 13941 13942 13943 13944 13945 13946 13947 13948 13949 13950 13951 13952 13953 13954 13955 13956 13957 13958 13959 13960 13961 13962 13963 13964 13965 13966 13967 13968 13969 13970 13971 13972 13973 13974 13975 13976 13977 13978 13979 13980 13981 13982 13983 13984 13985 13986 13987 13988 13989 13990 13991 13992 13993 13994 13995 13996 13997 13998 13999 14000 14001 14002 14003 14004 14005 14006 14007 14008 14009 14010 14011 14012 14013 14014 14015 14016 14017 14018 14019 14020 14021 14022 14023 14024 14025 14026 14027 14028 14029 14030 14031 14032 14033 14034 14035 14036 14037 14038 14039 14040 14041 14042 14043 14044 14045 14046 14047 14048 14049 14050 14051 14052 14053 14054 14055 14056 14057 14058 14059 14060 14061 14062 14063 14064 14065 14066 14067 14068 14069 14070 14071 14072 14073 14074 14075 14076 14077 14078 14079 14080 14081 14082 14083 14084 14085 14086 14087 14088 14089 14090 14091 14092 14093 14094 14095 14096 14097 14098 14099 14100 14101 14102 14103 14104 14105 14106 14107 14108 14109 14110 14111 14112 14113 14114 14115 14116 14117 14118 14119 14120 14121 14122 14123 14124 14125 14126 14127 14128 14129 14130 14131 14132 14133 14134 14135 14136 14137 14138 14139 14140 14141 14142 14143 14144 14145 14146 14147 14148 14149 14150 14151 14152 14153 14154 14155 14156 14157 14158 14159 14160 14161 14162 14163 14164 14165 14166 14167 14168 14169 14170 14171 14172 14173 14174 14175 14176 14177 14178 14179 14180 14181 14182 14183 14184 14185 14186 14187 14188 14189 14190 14191 14192 14193 14194 14195 14196 14197 14198 14199 14200 14201 14202 14203 14204 14205 14206 14207 14208 14209 14210 14211 14212 14213 14214 14215 14216 14217 14218 14219 14220 14221 14222 14223 14224 14225 14226 14227 14228 14229 14230 14231 14232 14233 14234 14235 14236 14237 14238 14239 14240 14241 14242 14243 14244 14245 14246 14247 14248 14249 14250 14251 14252 14253 14254 14255 14256 14257 14258 14259 14260 14261 14262 14263 14264 14265 14266 14267 14268 14269 14270 14271 14272 14273 14274 14275 14276 14277 14278 14279 14280 14281 14282 14283 14284 14285 14286 14287 14288 14289 14290 14291 14292 14293 14294 14295 14296 14297 14298 14299 14300 14301 14302 14303 14304 14305 14306 14307 14308 14309 14310 14311 14312 14313 14314 14315 14316 14317 14318 14319 14320 14321 14322 14323 14324 14325 14326 14327 14328 14329 14330 14331 14332 14333 14334 14335 14336 14337 14338 14339 14340 14341 14342 14343 14344 14345 14346 14347 14348 14349 14350 14351 14352 14353 14354 14355 14356 14357 14358 14359 14360 14361 14362 14363 14364 14365 14366 14367 14368 14369 14370 14371 14372 14373 14374 14375 14376 14377 14378 14379 14380 14381 14382 14383 14384 14385 14386 14387 14388 14389 14390 14391 14392 14393 14394 14395 14396 14397 14398 14399 14400 14401 14402 14403 14404 14405 14406 14407 14408 14409 14410 14411 14412 14413 14414 14415 14416 14417 14418 14419 14420 14421 14422 14423 14424 14425 14426 14427 14428 14429 14430 14431 14432 14433 14434 14435 14436 14437 14438 14439 14440 14441 14442 14443 14444 14445 14446 14447 14448 14449 14450 14451 14452 14453 14454 14455 14456 14457 14458 14459 14460 14461 14462 14463 14464 14465 14466 14467 14468 14469 14470 14471 14472 14473 14474 14475 14476 14477 14478 14479 14480 14481 14482 14483 14484 14485 14486 14487 14488 14489 14490 14491 14492 14493 14494 14495 14496 14497 14498 14499 14500 14501 14502 14503 14504 14505 14506 14507 14508 14509 14510 14511 14512 14513 14514 14515 14516 14517 14518 14519 14520 14521 14522 14523 14524 14525 14526 14527 14528 14529 14530 14531 14532 14533 14534 14535 14536 14537 14538 14539 14540 14541 14542 14543 14544 14545 14546 14547 14548 14549 14550 14551 14552 14553 14554 14555 14556 14557 14558 14559 14560 14561 14562 14563 14564 14565 14566 14567 14568 14569 14570 14571 14572 14573 14574 14575 14576 14577 14578 14579 14580 14581 14582 14583 14584 14585 14586 14587 14588 14589 14590 14591 14592 14593 14594 14595 14596 14597 14598 14599 14600 14601 14602 14603 14604 14605 14606 14607 14608 14609 14610 14611 14612 14613 14614 14615 14616 14617 14618 14619 14620 14621 14622 14623 14624 14625 14626 14627 14628 14629 14630 14631 14632 14633 14634 14635 14636 14637 14638 14639 14640 14641 14642 14643 14644 14645 14646 14647 14648 14649 14650 14651 14652 14653 14654 14655 14656 14657 14658 14659 14660 14661 14662 14663 14664 14665 14666 14667 14668 14669 14670 14671 14672 14673 14674 14675 14676 14677 14678 14679 14680 14681 14682 14683 14684 14685 14686 14687 14688 14689 14690 14691 14692 14693 14694 14695 14696 14697 14698 14699 14700 14701 14702 14703 14704 14705 14706 14707 14708 14709 14710 14711 14712 14713 14714 14715 14716 14717 14718 14719 14720 14721 14722 14723 14724 14725 14726 14727 14728 14729 14730 14731 14732 14733 14734 14735 14736 14737 14738 14739 14740 14741 14742 14743 14744 14745 14746 14747 14748 14749 14750 14751 14752 14753 14754 14755 14756 14757 14758 14759 14760 14761 14762 14763 14764 14765 14766 14767 14768 14769 14770 14771 14772 14773 14774 14775 14776 14777 14778 14779 14780 14781 14782 14783 14784 14785 14786 14787 14788 14789 14790 14791 14792 14793 14794 14795 14796 14797 14798 14799 14800 14801 14802 14803 14804 14805 14806 14807 14808 14809 14810 14811 14812 14813 14814 14815 14816 14817 14818 14819 14820 14821 14822 14823 14824 14825 14826 14827 14828 14829 14830 14831 14832 14833 14834 14835 14836 14837 14838 14839 14840 14841 14842 14843 14844 14845 14846 14847 14848 14849 14850 14851 14852 14853 14854 14855 14856 14857 14858 14859 14860 14861 14862 14863 14864 14865 14866 14867 14868 14869 14870 14871 14872 14873 14874 14875 14876 14877 14878 14879 14880 14881 14882 14883 14884 14885 14886 14887 14888 14889 14890 14891 14892 14893 14894 14895 14896 14897 14898 14899 14900 14901 14902 14903 14904 14905 14906 14907 14908 14909 14910 14911 14912 14913 14914 14915 14916 14917 14918 14919 14920 14921 14922 14923 14924 14925 14926 14927 14928 14929 14930 14931 14932 14933 14934 14935 14936 14937 14938 14939 14940 14941 14942 14943 14944 14945 14946 14947 14948 14949 14950 14951 14952 14953 14954 14955 14956 14957 14958 14959 14960 14961 14962 14963 14964 14965 14966 14967 14968 14969 14970 14971 14972 14973 14974 14975 14976 14977 14978 14979 14980 14981 14982 14983 14984 14985 14986 14987 14988 14989 14990 14991 14992 14993 14994 14995 14996 14997 14998 14999 15000 15001 15002 15003 15004 15005 15006 15007 15008 15009 15010 15011 15012 15013 15014 15015 15016 15017 15018 15019 15020 15021 15022 15023 15024 15025 15026 15027 15028 15029 15030 15031 15032 15033 15034 15035 15036 15037 15038 15039 15040 15041 15042 15043 15044 15045 15046 15047 15048 15049 15050 15051 15052 15053 15054 15055 15056 15057 15058 15059 15060 15061 15062 15063 15064 15065 15066 15067 15068 15069 15070 15071 15072 15073 15074 15075 15076 15077 15078 15079 15080 15081 15082 15083 15084 15085 15086 15087 15088 15089 15090 15091 15092 15093 15094 15095 15096 15097 15098 15099 15100 15101 15102 15103 15104 15105 15106 15107 15108 15109 15110 15111 15112 15113 15114 15115 15116 15117 15118 15119 15120 15121 15122 15123 15124 15125 15126 15127 15128 15129 15130 15131 15132 15133 15134 15135 15136 15137 15138 15139 15140 15141 15142 15143 15144 15145 15146 15147 15148 15149 15150 15151 15152 15153 15154 15155 15156 15157 15158 15159 15160 15161 15162 15163 15164 15165 15166 15167 15168 15169 15170 15171 15172 15173 15174 15175 15176 15177 15178 15179 15180 15181 15182 15183 15184 15185 15186 15187 15188 15189 15190 15191 15192 15193 15194 15195 15196 15197 15198 15199 15200 15201 15202 15203 15204 15205 15206 15207 15208 15209 15210 15211 15212 15213 15214 15215 15216 15217 15218 15219 15220 15221 15222 15223 15224 15225 15226 15227 15228 15229 15230 15231 15232 15233 15234 15235 15236 15237 15238 15239 15240 15241 15242 15243 15244 15245 15246 15247 15248 15249 15250 15251 15252 15253 15254 15255 15256 15257 15258 15259 15260 15261 15262 15263 15264 15265 15266 15267 15268 15269 15270 15271 15272 15273 15274 15275 15276 15277 15278 15279 15280 15281 15282 15283 15284 15285 15286 15287 15288 15289 15290 15291 15292 15293 15294 15295 15296 15297 15298 15299 15300 15301 15302 15303 15304 15305 15306 15307 15308 15309 15310 15311 15312 15313 15314 15315 15316 15317 15318 15319 15320 15321 15322 15323 15324 15325 15326 15327 15328 15329 15330 15331 15332 15333 15334 15335 15336 15337 15338 15339 15340 15341 15342 15343 15344 15345 15346 15347 15348 15349 15350 15351 15352 15353 15354 15355 15356 15357 15358 15359 15360 15361 15362 15363 15364 15365 15366 15367 15368 15369 15370 15371 15372 15373 15374 15375 15376 15377 15378 15379 15380 15381 15382 15383 15384 15385 15386 15387 15388 15389 15390 15391 15392 15393 15394 15395 15396 15397 15398 15399 15400 15401 15402 15403 15404 15405 15406 15407 15408 15409 15410 15411 15412 15413 15414 15415 15416 15417 15418 15419 15420 15421 15422 15423 15424 15425 15426 15427 15428 15429 15430 15431 15432 15433 15434 15435 15436 15437 15438 15439 15440 15441 15442 15443 15444 15445 15446 15447 15448 15449 15450 15451 15452 15453 15454 15455 15456 15457 15458 15459 15460 15461 15462 15463 15464 15465 15466 15467 15468 15469 15470 15471 15472 15473 15474 15475 15476 15477 15478 15479 15480 15481 15482 15483 15484 15485 15486 15487 15488 15489 15490 15491 15492 15493 15494 15495 15496 15497 15498 15499 15500 15501 15502 15503 15504 15505 15506 15507 15508 15509 15510 15511 15512 15513 15514 15515 15516 15517 15518 15519 15520 15521 15522 15523 15524 15525 15526 15527 15528 15529 15530 15531 15532 15533 15534 15535 15536 15537 15538 15539 15540 15541 15542 15543 15544 15545 15546 15547 15548 15549 15550 15551 15552 15553 15554 15555 15556 15557 15558 15559 15560 15561 15562 15563 15564 15565 15566 15567 15568 15569 15570 15571 15572 15573 15574 15575 15576 15577 15578 15579 15580 15581 15582 15583 15584 15585 15586 15587 15588 15589 15590 15591 15592 15593 15594 15595 15596 15597 15598 15599 15600 15601 15602 15603 15604 15605 |
<?xml version="1.0" standalone="yes"?>
<dtsHealthCheck xmlns="http://tempuri.org/HealthCheckDataSet.xsd"> <Message> <MessageID>500</MessageID> <Description>This component started.</Description> </Message> <Message> <MessageID>501</MessageID> <Description>This component was signalled to stop by an administrator or the operating system. The component will complete any processing it is doing and stop at a safe point in time. If the component or this computer is very busy, it may take several minutes for the component to stop.</Description> </Message> <Message> <MessageID>502</MessageID> <Description>This component stopped.</Description> </Message> <Message> <MessageID>503</MessageID> <Description>This component was signalled to pause by an administrator. The component will complete any processing it is doing and pause at a safe point in time. If the component or this computer is very busy, it may take several minutes for the component to pause. Once the component has paused, it will not do any more processing until the administrator signals it to resume processing.</Description> </Message> <Message> <MessageID>504</MessageID> <Description>This component was signalled to resume processing by an administrator.</Description> </Message> <Message> <MessageID>505</MessageID> <Description>Server %1 is unreachable or down.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>506</MessageID> <Description>Copied file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>507</MessageID> <Description>Moved file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>508</MessageID> <Description>Deleted file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>509</MessageID> <Description>Locked file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>510</MessageID> <Description>Unlocked file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>511</MessageID> <Description>Created directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>512</MessageID> <Description>Removed directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>513</MessageID> <Description>Set the current directory for this process to "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>514</MessageID> <Description>Opened a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>515</MessageID> <Description>Could not open a change notification handle for directory "%1" because the directory is on a remote computer.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>516</MessageID> <Description>Closed the change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>517</MessageID> <Description>Could not open file "%1" for reading.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>518</MessageID> <Description>Could not open file "%1" for reading and writing.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>519</MessageID> <Description>Could not read from file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>520</MessageID> <Description>Could not write to file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>521</MessageID> <Description>Could not copy file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>522</MessageID> <Description>Could not move file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>523</MessageID> <Description>Could not delete file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>524</MessageID> <Description>Could not lock file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>525</MessageID> <Description>Could not create directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>526</MessageID> <Description>Could not remove directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>527</MessageID> <Description>Could not set the current directory for this process to "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>528</MessageID> <Description>Could not open a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>529</MessageID> <Description>Could not wait on a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>530</MessageID> <Description>Could not open file "%1" for reading.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>531</MessageID> <Description>Could not open file "%1" for reading and writing.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>532</MessageID> <Description>Could not read from file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>533</MessageID> <Description>Could not write to file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>534</MessageID> <Description>Could not copy file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>535</MessageID> <Description>Could not move file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>536</MessageID> <Description>Could not delete file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>537</MessageID> <Description>Could not lock file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>538</MessageID> <Description>Could not create directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>539</MessageID> <Description>Could not remove directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>540</MessageID> <Description>Could not set the current directory for this process to "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>541</MessageID> <Description>Could not open a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>542</MessageID> <Description>Could not wait on a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>543</MessageID> <Description>Parsed site control file "%1", serial number %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>544</MessageID> <Description>Wrote delta site control file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>545</MessageID> <Description>Could not read site control file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>546</MessageID> <Description>Could not parse site control file "%1", the file contains a syntax error or it is improperly formatted or corrupt.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>547</MessageID> <Description>Could not parse site control file "%1", the file does not contain an end-of-file (EOF) marker.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>548</MessageID> <Description>Site control file "%1" does not contain a "File Definition" item.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>549</MessageID> <Description>Could not write delta site control file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>550</MessageID> <Description>Parsed installation map "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>551</MessageID> <Description>Could not read installation map "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>552</MessageID> <Description>Could not parse installation map "%1", the file contains a syntax error or it is improperly formatted or corrupt.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>553</MessageID> <Description>Read registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>554</MessageID> <Description>Wrote registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>555</MessageID> <Description>Deleted registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>556</MessageID> <Description>Read registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>557</MessageID> <Description>Wrote registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>558</MessageID> <Description>Deleted registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>559</MessageID> <Description>Opened a change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>560</MessageID> <Description>Closed the change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>561</MessageID> <Description>Could not connect to registry hive %1 on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>562</MessageID> <Description>Could not open registry key "%1" on computer %2 for reading.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>563</MessageID> <Description>Could not create or open registry key "%1" on computer %2 for reading and writing.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>564</MessageID> <Description>Could not read registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>565</MessageID> <Description>Could not write registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>566</MessageID> <Description>Could not delete the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>567</MessageID> <Description>Could not enumerate the subkeys of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>568</MessageID> <Description>Could not open a change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>569</MessageID> <Description>The registry key "%1" on computer %2 is missing a required subkey or value, or contains one or more values that contain invalid data.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>570</MessageID> <Description>Could not read the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>571</MessageID> <Description>Could not write the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>572</MessageID> <Description>Could not delete the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>573</MessageID> <Description>Could not enumerate the values of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>574</MessageID> <Description>The registry value "%1" on computer %2 contains invalid data.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>575</MessageID> <Description>Could not connect to registry hive %1 on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>576</MessageID> <Description>Could not open registry key "%1" on computer %2 for reading.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>577</MessageID> <Description>Could not create or open registry key "%1" on computer %2 for reading and writing.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>578</MessageID> <Description>Could not read registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>579</MessageID> <Description>Could not write registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>580</MessageID> <Description>Could not delete the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>581</MessageID> <Description>Could not enumerate the subkeys of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>582</MessageID> <Description>Could not open a change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>583</MessageID> <Description>The registry key "%1" on computer %2 is missing a required subkey or value, or contains one or more values that contain invalid data.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>584</MessageID> <Description>Could not read the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>585</MessageID> <Description>Could not write the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>586</MessageID> <Description>Could not delete the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>587</MessageID> <Description>Could not enumerate the values of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>588</MessageID> <Description>The registry value "%1" on computer %2 contains invalid data.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>589</MessageID> <Description>Creating "%1" trigger for "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>590</MessageID> <Description>Dropping trigger "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>591</MessageID> <Description>Creating table "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>592</MessageID> <Description>Dropping table "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>593</MessageID> <Description>Creating index "%1" on table "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>594</MessageID> <Description>Dropping index "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>595</MessageID> <Description>Creating stored procedure "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>596</MessageID> <Description>Dropping stored procedure "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>597</MessageID> <Description>Creating view "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>598</MessageID> <Description>Dropping view "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>599</MessageID> <Description>SQL Login data is incomplete.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>600</MessageID> <Description>Failed to get a SQL Server connection. Either the SQL Server is not running, or all connections have been used.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>601</MessageID> <Description>Failed to execute SQL command: "%1". Check messages from SQL Server.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>602</MessageID> <Description>The following SQL operation has timed out: "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>603</MessageID> <Description>Failed to get new table name.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>604</MessageID> <Description>Failed to create table "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>605</MessageID> <Description>Failed to rename table "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>606</MessageID> <Description>Failed to add columns to table "%1".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>607</MessageID> <Description>Failed to drop table "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>608</MessageID> <Description>Failed to create index "%1" on table "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>609</MessageID> <Description>Failed to create procedure "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>610</MessageID> <Description>Failed to create view "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>611</MessageID> <Description>Failed to create trigger "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>612</MessageID> <Description>Failed to drop procedure "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>613</MessageID> <Description>Failed to drop view "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>614</MessageID> <Description>Failed to drop trigger "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>615</MessageID> <Description>Microsoft SQL Server reported SQL error %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>616</MessageID> <Description>Microsoft SQL Server reported SQL error %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>617</MessageID> <Description>Microsoft SQL Server reported SQL error %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>618</MessageID> <Description>Microsoft SQL Server reported SQL message %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>619</MessageID> <Description>Microsoft SQL Server reported SQL message %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>620</MessageID> <Description>Microsoft SQL Server reported SQL message %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>621</MessageID> <Description>Created the "%1" inbox definition. The inbox will exist on the Site Server with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>622</MessageID> <Description>Created the "%1" inbox definition. The inbox will exist on the SQL Server with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>623</MessageID> <Description>Created the "%1" inbox definition. The inbox will exist on the Client Access Point with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>624</MessageID> <Description>Created the "%1" inbox definition. The inbox will exist on the named export "%2" with the relative path "%3".%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>625</MessageID> <Description>Read the existing "%1" inbox definition. The inbox should exist on the Site Server with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>626</MessageID> <Description>Read the existing "%1" inbox definition. The inbox should exist on the SQL Server with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>627</MessageID> <Description>Read the existing "%1" inbox definition. The inbox should exist on the Client Access Point with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>628</MessageID> <Description>Read the existing "%1" inbox definition. The inbox should exist on the named export "%2" with the relative path "%3".%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>629</MessageID> <Description>Deleted the "%1" inbox definition.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>630</MessageID> <Description>Created an inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>631</MessageID> <Description>Created an inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>632</MessageID> <Description>Created an inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>633</MessageID> <Description>Created an inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>634</MessageID> <Description>Created an inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%12%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>635</MessageID> <Description>Created an inbox rule to mirror "%1" directories that match the template "%1" from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%12%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>636</MessageID> <Description>Read the existing inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>637</MessageID> <Description>Read the existing inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>638</MessageID> <Description>Read the existing inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>639</MessageID> <Description>Read the existing inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>640</MessageID> <Description>Read the existing inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%12%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>641</MessageID> <Description>Read the existing inbox rule to mirror "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%12%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>642</MessageID> <Description>Deleted the inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>643</MessageID> <Description>Deleted the inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>644</MessageID> <Description>Deleted the inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>645</MessageID> <Description>Deleted the inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>646</MessageID> <Description>Deleted the inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>647</MessageID> <Description>Deleted the inbox rule to mirror "%1" directories from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>648</MessageID> <Description>Resolved the "%1" inbox to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>649</MessageID> <Description>Waiting for the "%1" inbox to be defined.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>650</MessageID> <Description>Waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>651</MessageID> <Description>Still waiting for the "%1" inbox to be defined.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>652</MessageID> <Description>Still waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>653</MessageID> <Description>Still waiting for the "%1" inbox to be defined.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>654</MessageID> <Description>Still waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>655</MessageID> <Description>Could not connect to the "%1" inbox source on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>656</MessageID> <Description>Could not create the "%1" inbox definition. (Could not insert the inbox definition into the "%2" inbox source on computer %3.)%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>657</MessageID> <Description>Could not create an inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>658</MessageID> <Description>Could not create an inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>659</MessageID> <Description>Could not create an inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>660</MessageID> <Description>Could not create an inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>661</MessageID> <Description>Could not create an inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>662</MessageID> <Description>Could not create an inbox rule to mirror "%1" directories from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>663</MessageID> <Description>Instructed SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3. The replication will be scheduled as low priority.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>664</MessageID> <Description>Instructed SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3. The replication will be scheduled as normal priority.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>665</MessageID> <Description>Instructed SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3. The replication will be scheduled as high priority.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>666</MessageID> <Description>Could not instruct SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>667</MessageID> <Description>Could not instruct SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>668</MessageID> <Description>The system is low on virtual memory and the component failed a memory allocation. The component will retry the allocation until it succeeds.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>669</MessageID> <Description>The component raised an exception but failed to handle it and will be stopped immediately. Component name: %1 Executable: %2 Process ID: %3 Thread ID: %4 Instruction address: %5 Exception code: %6 Client version: %8 Additional information: %7%12%9%10</Description> </Message> <Message> <MessageID>670</MessageID> <Description>Failed to update the site control file.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>671</MessageID> <Description>Failed to read the site control file.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>672</MessageID> <Description>Failed to read registry.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>673</MessageID> <Description>Failed to copy file %1 to %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>674</MessageID> <Description>Failed to open file %1.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>675</MessageID> <Description>Failed to connect to the inbox source..%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>676</MessageID> <Description>Inbox %1 has not been created.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>677</MessageID> <Description>Required registry value %1 is empty.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>678</MessageID> <Description>Failed to update registry.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>679</MessageID> <Description>This component failed to retrieve the list of SMS sites from the site database.%12</Description> </Message> <Message> <MessageID>680</MessageID> <Description>Failed to delete file %1.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>681</MessageID> <Description>Failed to move file %1 to %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>682</MessageID> <Description>The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed but the authentication key did not match the recorded key for this client.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>683</MessageID> <Description>The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was not signed and an authentication key was required.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>684</MessageID> <Description>The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed and this client does not require authentication.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>686</MessageID> <Description>Component %1 on %2 is %3.</Description> </Message> <Message> <MessageID>1001</MessageID> <Description>The Active Directory forest designed to store the Configuration Manager health state references has not been extended with the Configuration Manager 2007 schema extensions. The error encountered was %1.</Description> </Message> <Message> <MessageID>1002</MessageID> <Description>The Active Directory (AD) Cache Client failed to search the AD Forest for NAP-related Configuration Manager Health Information. The error encountered was %1.</Description> </Message> <Message> <MessageID>1003</MessageID> <Description>The file cache store in the System Health Validator point failed to initialize properly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1004</MessageID> <Description>The File Cache Store update failed. This will potentially cause the Configuration Manager System Health Validator to not validate the incoming NAP statement of health requests correctly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1005</MessageID> <Description>The File Cache Store could not be persisted to disk properly. This will potentially cause the Configuration Manager System Health Validator to not validate the incoming NAP statement of health requests correctly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1006</MessageID> <Description>The Configuration Manager System Health Validator Registry Settings failed to get loaded properly. This will prevent the Configuration Manager System Health Validator Service from functioning properly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1007</MessageID> <Description>Changes to Configuration Manager System Health Validator Registry Settings failed to get processed properly. This might prevent the Configuration Manager System Health Validator Service from functioning as desired. The error encountered was %1.</Description> </Message> <Message> <MessageID>1008</MessageID> <Description>The Configuration Manager System Health Validator Service failed to initialize properly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1009</MessageID> <Description>The AD Cache Client failed to initialize properly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1013</MessageID> <Description>Site Component Manager detected that this component should be installed on this site system. Site Component Manager will attempt to install the component every %1 minutes until the installation succeeds.</Description> </Message> <Message> <MessageID>1014</MessageID> <Description>Site Component Manager is installing this component on this site system.</Description> </Message> <Message> <MessageID>1015</MessageID> <Description>Site Component Manager successfully installed this component on this site system.</Description> </Message> <Message> <MessageID>1016</MessageID> <Description>Site Component Manager failed to install this component on this site system.</Description> </Message> <Message> <MessageID>1017</MessageID> <Description>Site Component Manager detected that this component should be reinstalled on this site system. Site Component Manager will attempt to install the component every %1 minutes until the installation succeeds.</Description> </Message> <Message> <MessageID>1018</MessageID> <Description>Site Component Manager is reinstalling this component on this site system.</Description> </Message> <Message> <MessageID>1019</MessageID> <Description>Site Component Manager successfully reinstalled this component on this site system.</Description> </Message> <Message> <MessageID>1020</MessageID> <Description>Site Component Manager failed to reinstall this component on this site system.</Description> </Message> <Message> <MessageID>1021</MessageID> <Description>Site Component Manager detected that this component should be deinstalled from this site system. Site Component Manager will attempt to deinstall the component every %1 minutes. Site Component Manager will abort the deinstallation if it fails to succeed after %2 minutes.</Description> </Message> <Message> <MessageID>1022</MessageID> <Description>Site Component Manager is deinstalling this component from this site system.</Description> </Message> <Message> <MessageID>1023</MessageID> <Description>Site Component Manager successfully deinstalled this component from this site system.</Description> </Message> <Message> <MessageID>1024</MessageID> <Description>Site Component Manager failed to deinstall this component from this site system.</Description> </Message> <Message> <MessageID>1025</MessageID> <Description>Site Component Manager failed to deinstall this component from this site system.</Description> </Message> <Message> <MessageID>1026</MessageID> <Description>Site Component Manager is configuring site system "%1" to receive Configuration Manager Server Components.</Description> </Message> <Message> <MessageID>1027</MessageID> <Description>Site Component Manager successfully configured site system "%1" to receive Configuration Manager Server Components. Site Component Manager will now begin installing the components on the site system.</Description> </Message> <Message> <MessageID>1028</MessageID> <Description>Site Component Manager failed to configure site system "%1" to receive Configuration Manager Server Components.</Description> </Message> <Message> <MessageID>1029</MessageID> <Description>Site Component Manager is reconfiguring site system "%1" to receive Configuration Manager Server Components.</Description> </Message> <Message> <MessageID>1030</MessageID> <Description>Site Component Manager successfully reconfigured site system "%1" to receive Configuration Manager Server Components. Site Component Manager will now begin reinstalling the components on the site system.</Description> </Message> <Message> <MessageID>1031</MessageID> <Description>Site Component Manager failed to reconfigure site system "%1" to receive Configuration Manager Server Components.</Description> </Message> <Message> <MessageID>1032</MessageID> <Description>Site Component Manager detected that all Configuration Manager Server Components have been deinstalled from site system "%1". Site Component Manager is removing remaining accounts, files, and registry keys associated with the Configuration Manager Server Components from the site system.</Description> </Message> <Message> <MessageID>1033</MessageID> <Description>Site Component Manager successfully removed all accounts, files, and registry keys associated with the Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>1034</MessageID> <Description>Site Component Manager failed to remove all accounts, files, and registry keys associated with the Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>1035</MessageID> <Description>Site Component Manager failed to remove all accounts, files, and registry keys associated with the Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>1036</MessageID> <Description>Site Component Manager could not access site system "%1" due to an unexpected failure within the network abstraction layer (NAL).%12</Description> </Message> <Message> <MessageID>1037</MessageID> <Description>Site Component Manager could not access site system "%1".%12</Description> </Message> <Message> <MessageID>1038</MessageID> <Description>Site Component Manager detected that site system "%1" is not running the Microsoft Windows Server operating system.%12</Description> </Message> <Message> <MessageID>1039</MessageID> <Description>Site Component Manager detected that the site server does not contain the binary files for the platform (processor architecture) of site system "%1".%12</Description> </Message> <Message> <MessageID>1040</MessageID> <Description>Site Component Manager detected that site system "%1" is based on an Intel x86 or compatible platform (processor architecture).</Description> </Message> <Message> <MessageID>1041</MessageID> <Description>Site Component Manager detected that site system "%1" is based on the Alpha platform (processor architecture).</Description> </Message> <Message> <MessageID>1042</MessageID> <Description>Site Component Manager could not detect which version of the Microsoft Windows Server operating system is running on site system "%1".%12</Description> </Message> <Message> <MessageID>1043</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2, which is not a supported operating system for this version of SMS.</Description> </Message> <Message> <MessageID>1044</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2 service pack %3, which is not a supported operating system for this version of Configuration Manager.</Description> </Message> <Message> <MessageID>1045</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Workstation operating system, which is not a supported operating system for this version of SMS.</Description> </Message> <Message> <MessageID>1046</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2.</Description> </Message> <Message> <MessageID>1047</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2 service pack %3.</Description> </Message> <Message> <MessageID>1048</MessageID> <Description>Site Component Manager detected that site system "%1" is currently in use by ConfigMgr site %2.</Description> </Message> <Message> <MessageID>1049</MessageID> <Description>Site Component Manager could not find an NTFS partition on site system "%1" to hold the Configuration Manager Server Components' files.%12</Description> </Message> <Message> <MessageID>1050</MessageID> <Description>Site Component Manager could not create the Configuration Manager Server Components' installation directory "%2" on site system "%1" or set the correct permissions on the directory.%12</Description> </Message> <Message> <MessageID>1051</MessageID> <Description>Site Component Manager created the Configuration Manager Server Components' installation directory "%2" on site system "%1". Site Component Manager selected this partition because it was the NTFS partition with the most free space.</Description> </Message> <Message> <MessageID>1052</MessageID> <Description>Site Component Manager could not create the "%2" account on site system "%1".%12</Description> </Message> <Message> <MessageID>1053</MessageID> <Description>Site Component Manager created the "%2" account on site system "%1". When Site Component Manager installs services on the site system, it will configure them to log in using this account. If the site system is a stand-alone server, the account is a local machine account with full administrative rights. If the site system is a domain controller, the account is a domain account with domain user rights and full administrative rights only to the site system.</Description> </Message> <Message> <MessageID>1054</MessageID> <Description>Site Component Manager could not verify that the "%2" account exists on site system "%1".%12</Description> </Message> <Message> <MessageID>1055</MessageID> <Description>Site Component Manager could not read the Network Connection account data, which is stored in the installation directory on the site server.%12</Description> </Message> <Message> <MessageID>1056</MessageID> <Description>Site Component Manager could not write Network Connection account data to the installation directory "%2" on site system "%1".%12</Description> </Message> <Message> <MessageID>1057</MessageID> <Description>Because site system "%1" might have malfunctioned, as a safety measure Site Component Manager will attempt to reconfigure it to receive Configuration Manager Server Components and reinstall all of the Configuration Manager Server Components on it. This attempt will occur in %2 minutes.</Description> </Message> <Message> <MessageID>1058</MessageID> <Description>Site Component Manager could not remove the "%2" account from site system "%1".%12</Description> </Message> <Message> <MessageID>1059</MessageID> <Description>Site Component Manager removed the "%2" account from site system "%1".</Description> </Message> <Message> <MessageID>1060</MessageID> <Description>Site Component Manager could not remove the Configuration Manager installation directory "%2" on site system "%1".%12</Description> </Message> <Message> <MessageID>1061</MessageID> <Description>Site Component Manager removed the Configuration Manager Server Components' installation directory "%2" on site system "%1".</Description> </Message> <Message> <MessageID>1062</MessageID> <Description>Site Component Manager detected that the service account has changed, and will now reinstall all of the Configuration Manager Server Components that are installed on the site server.</Description> </Message> <Message> <MessageID>1063</MessageID> <Description>Site Component Manager was instructed by Configuration Manager Setup to shut down the site in preparation for a site upgrade, modification, or reset operation. Site Component Manager will now stop all of the Configuration Manager Server Components on all of the site systems, mark all of these components for reinstallation, and then stop itself. Site Component Manager will reinstall all of the components when it is restarted by Configuration Manager Setup at the end of the site upgrade, modification, or reset operation.</Description> </Message> <Message> <MessageID>1064</MessageID> <Description>Site Component Manager is stopping all of the Configuration Manager Server Components on site system "%1".</Description> </Message> <Message> <MessageID>1065</MessageID> <Description>Site Component Manager will not stop any Configuration Manager Server Components on site system "%1" because no Configuration Manager Server Components are installed on the site system.</Description> </Message> <Message> <MessageID>1066</MessageID> <Description>Site Component Manager will now try again to stop all of the Configuration Manager Server Components on site system "%1", as requested by Configuration Manager Setup.</Description> </Message> <Message> <MessageID>1067</MessageID> <Description>Site Component Manager will now cease trying to stop all of the Configuration Manager Server Components on site system "%1", as requested by Configuration Manager Setup. The Configuration Manager Server Components were not properly deinstalled from the site system.</Description> </Message> <Message> <MessageID>1068</MessageID> <Description>Site Component Manager was instructed by Configuration Manager Setup to deinstall the site. Site Component Manager will now deinstall all of the Configuration Manager Server Components from all of the site systems.</Description> </Message> <Message> <MessageID>1069</MessageID> <Description>Site Component Manager is deinstalling all of the Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>1070</MessageID> <Description>Site Component Manager will not deinstall any Configuration Manager Server Components from site system "%1" because no Configuration Manager Server Components are installed on the site system.</Description> </Message> <Message> <MessageID>1071</MessageID> <Description>Site Component Manager will now try again to deinstall all of the Configuration Manager Server Components from site system "%1", as requested by Configuration Manager Setup.</Description> </Message> <Message> <MessageID>1072</MessageID> <Description>Site Component Manager will now cease trying to deinstall all of the Configuration Manager Server Components from site system "%1", as requested by Configuration Manager Setup. The Configuration Manager Server Components were not properly deinstalled from the site system.</Description> </Message> <Message> <MessageID>1073</MessageID> <Description>Site Component Manager could not detect how much disk space was available in the "%1" directory on this site system.%12</Description> </Message> <Message> <MessageID>1074</MessageID> <Description>Site Component Manager cannot install this component on this site system because %1 bytes are required on the drive containing the "%2" directory, but only %3 bytes are available.</Description> </Message> <Message> <MessageID>1075</MessageID> <Description>Site Component Manager detected that %1 bytes are required by this component on the drive containing the "%2" directory, and that %3 bytes are available. Site Component Manager will proceed with the installation of this component.</Description> </Message> <Message> <MessageID>1076</MessageID> <Description>Site Component Manager could not copy file "%1" to "%2".%12 Site Component Manager reports this error when it fails to: 1. Create the destination directory, if it does not already exist. 2. Assign the proper directory permissions to the destination directory. 3. Copy the source file to the destination directory.</Description> </Message> <Message> <MessageID>1077</MessageID> <Description>Site Component Manager could not copy file "%1" to "%2".%12 Site Component Manager reports this error when it fails to: 1. Create the destination directory, if it does not already exist. 2. Copy the source file to the destination directory.</Description> </Message> <Message> <MessageID>1078</MessageID> <Description>Site Component Manager copied file "%1" to "%2".</Description> </Message> <Message> <MessageID>1079</MessageID> <Description>Site Component Manager did not copy file "%1" to "%2", because the source file is not a newer version than the destination file.</Description> </Message> <Message> <MessageID>1080</MessageID> <Description>Site Component Manager detected that the %1 service was installed on site system "%2", but Site Component Manager could not deinstall the service.%12</Description> </Message> <Message> <MessageID>1081</MessageID> <Description>Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1082</MessageID> <Description>Site Component Manager could not start the %1 service on site system "%2" to install component %4 with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1083</MessageID> <Description>Site Component Manager successfully used the %1 service to run the following program on site system "%2": %3 %4 %5 The program failed for the following reason: %6</Description> </Message> <Message> <MessageID>1084</MessageID> <Description>Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1085</MessageID> <Description>Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1086</MessageID> <Description>Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1087</MessageID> <Description>Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1088</MessageID> <Description>Site Component Manager installed the %1 service on site system "%2". The service will log on as account "%3".</Description> </Message> <Message> <MessageID>1089</MessageID> <Description>Site Component Manager started the %1 service on site system "%2".</Description> </Message> <Message> <MessageID>1090</MessageID> <Description>Site Component Manager could not stop the %1 service on site system "%2".%12</Description> </Message> <Message> <MessageID>1091</MessageID> <Description>Site Component Manager could not deinstall the %1 service from site system "%2".%12</Description> </Message> <Message> <MessageID>1092</MessageID> <Description>Site Component Manager stopped the %1 service on site system "%2".</Description> </Message> <Message> <MessageID>1093</MessageID> <Description>Site Component Manager deinstalled the %1 service from site system "%2".</Description> </Message> <Message> <MessageID>1094</MessageID> <Description>Site Component Manager installed this component as a thread of the SMS Executive service on this site system.</Description> </Message> <Message> <MessageID>1095</MessageID> <Description>Site Component Manager started this component on this site system.</Description> </Message> <Message> <MessageID>1096</MessageID> <Description>Site Component Manager stopped this component on this site system.</Description> </Message> <Message> <MessageID>1097</MessageID> <Description>Site Component Manager deinstalled this component as a thread of SMS Executive on this site system.</Description> </Message> <Message> <MessageID>1098</MessageID> <Description>Site Component Manager could not start this component on this site system because the SMS Executive service is not running.</Description> </Message> <Message> <MessageID>1099</MessageID> <Description>Site Component Manager signaled this component on this site system to stop, but it did not stop after 60 seconds.</Description> </Message> <Message> <MessageID>1104</MessageID> <Description>SMS Executive detected that this component stopped unexpectedly.%12</Description> </Message> <Message> <MessageID>1105</MessageID> <Description>SMS Executive is next scheduled to start this component on "%1".</Description> </Message> <Message> <MessageID>1106</MessageID> <Description>SMS Executive will never start this component because it is never scheduled to run. If you want SMS Executive to start the component, enable the component in the Configuration Manager Console and adjust its schedule to an appropriate setting.</Description> </Message> <Message> <MessageID>1107</MessageID> <Description>SMS Executive is scheduled to start this component now, but cannot because it is already running.</Description> </Message> <Message> <MessageID>1108</MessageID> <Description>SMS Executive could not start this component because it could not load \"%1\" using the MFC AfxLoadLibrary() function.%12</Description> </Message> <Message> <MessageID>1109</MessageID> <Description>SMS Executive could not start this component because it could not determine the address of the ThreadMain() function exported by \"%1\" using the Win32 GetProcAddress() function.%12</Description> </Message> <Message> <MessageID>1200</MessageID> <Description>In the last %1 hours, Status Manager processed %2 status messages. Of these, %3 were written to the site database, %4 were replicated to the parent site, %5 were reported as Windows Events on the site server, and %6 were passed as command-line parameters to external programs. During this time, Status Manager received %7 corrupt files that contained one or more status messages that could not be processed. Also during this time, Status Manager used %8 hours of CPU time, which represents a %9 percent utilization of the total CPU time available for the period. Status Manager periodically reports this message for your convenience; you can ignore it if your not interested in monitoring Status Manager's processing performance. Status Manager will report this message again in %10 hours.%12</Description> </Message> <Message> <MessageID>1201</MessageID> <Description>Status Manager successfully initialized the "SMS Status Messages" performance object. Every time Status Manager receives a status message it will update the performance counters contained by this performance object. You can measure Status Manager's processing performance by monitoring this performance object with the Windows Performance Monitor. For example, you can monitor the total number of status messages written to the site database by Status Manager by monitoring the "_Total" instance of the "Written To SMS Database" counter. Status Manager resets all of the counts when it is restarted, and the counts cannot be viewed when Status Manager is not running.%12</Description> </Message> <Message> <MessageID>1202</MessageID> <Description>Due to an internal error, Status Manager could not initialize the "SMS Status Messages" performance object. You can measure Status Manager's processing performance by monitoring this performance object with the Windows Performance Monitor. This problem will not affect Status Manager's ability to process status messages, but it will prevent you from viewing this performance object. You can ignore this problem if you do not need to view this performance object. Please refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.%12</Description> </Message> <Message> <MessageID>1203</MessageID> <Description>Status Manager successfully initialized an in-memory queue to forward status messages to the summarizer component %1. The summarizer distills the stream of status messages into a high-level summary, which you can view under the System Status node of the Configuration Manager Console. You can monitor the performance of the in-memory queue in the Windows Performance Monitor by selecting the "SMS In-Memory Queues" performance object, and then selecting the instance for this summarizer. For example, the "Total Objects Enqueued" counter tells you how many status messages Status Manager has forwarded to the summarizer. The counts are reset when both Status Manager and the summarizer are restarted, which typically occurs when SMS Executive is restarted. The counts cannot be viewed when Status Manager and the summarizer are both not running.%12</Description> </Message> <Message> <MessageID>1204</MessageID> <Description>Status Manager will no longer forward status messages to the summarizer component %1 because the summarizer was disabled. The summarizer distills a stream of status messages into a high-level summary, which you can view under the System Status node of the Configuration Manager Console. If you reenable the summarizer in the Configuration Manager Console, Status Manager will resume forwarding messages to the summarizer.%12</Description> </Message> <Message> <MessageID>1205</MessageID> <Description>Due to an internal error, Status Manager could not initialize an in-memory queue to forward status messages to the summarizer component %1. The summarizer distills the stream of status messages into a high-level summary, which you can view under the System Status node of the Configuration Manager Console. Until this problem is fixed, the high-level summary will be inaccurate or not available. Please refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.%12</Description> </Message> <Message> <MessageID>1209</MessageID> <Description>Status Manager has created %1 instances of the "SMS Status Messages" performance object, which is the maximum allowed number of instances. Every time Status Manager receives a status message it will update the performance counters contained by this performance object. You can measure Status Manager's processing performance by monitoring this performance object with the Windows Performance Monitor. Because the maximum limit was reached, Status Manager will not create any more instances of this performance object. Status Manager builds the list of instances as it receives status messages. You can reset the list by restarting Status Manager.%12</Description> </Message> <Message> <MessageID>1210</MessageID> <Description>Status Manager was instructed by a Status Filter Rule to execute program and command-line arguments "%1" upon receipt of a status message that satisfied the criteria specified by the Status Filter Rule, but the program and command-line arguments are invalid. (Note that for display purposes, the program and command-line arguments were truncated to %2 characters in this message.)</Description> </Message> <Message> <MessageID>1211</MessageID> <Description>Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt of a status message that satisfied the criteria specified by the Status Filter Rule. (Note that for display purposes, the program and command-line arguments were truncated to %3 characters in this message.) Status Manager failed to execute the program.%12</Description> </Message> <Message> <MessageID>1212</MessageID> <Description>Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt of a status message that satisfied the criteria specified by the Status Filter Rule. (Note that for display purposes, the program and command-line arguments were truncated to %3 characters in this message.) Status Manager successfully started the program, but the program was still running after 60 seconds.</Description> </Message> <Message> <MessageID>1213</MessageID> <Description>Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the message is more recent than the current system time on the site server.</Description> </Message> <Message> <MessageID>1214</MessageID> <Description>Status Manager received a status message with an invalid time stamp. The status message was reported by component "%1" running on computer "%2".</Description> </Message> <Message> <MessageID>1215</MessageID> <Description>Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the message is more recent than the current system time on the site server.</Description> </Message> <Message> <MessageID>1300</MessageID> <Description>Network Discovery is starting.%12</Description> </Message> <Message> <MessageID>1301</MessageID> <Description>Network Discovery is retrieving information about previously discovered devices and networks from CIM Object Manager.%12 This process can take a long time when many devices are being discovered.</Description> </Message> <Message> <MessageID>1302</MessageID> <Description>Network Discovery protocol modules are initializing.%12</Description> </Message> <Message> <MessageID>1303</MessageID> <Description>Network Discovery is starting protocol operations. Network Discovery is querying network devices to discover devices related to the specified configuration.%12</Description> </Message> <Message> <MessageID>1304</MessageID> <Description>Network Discovery is stopping protocol operations.%12</Description> </Message> <Message> <MessageID>1305</MessageID> <Description>Network Discovery is stopping the Network Discovery protocol modules.%12</Description> </Message> <Message> <MessageID>1306</MessageID> <Description>Network Discovery is storing currently discovered devices and networks in CIM Object Manager, which can take a long time when many devices are being discovered.%12</Description> </Message> <Message> <MessageID>1307</MessageID> <Description>Network Discovery is exporting devices and networks to the Discovery Data Manager. This process can take a long time when many devices are being discovered.%12</Description> </Message> <Message> <MessageID>1308</MessageID> <Description>Network Discovery has stopped.%12</Description> </Message> <Message> <MessageID>1309</MessageID> <Description>Network Discovery failed to connect to a DHCP server due to insufficient access.%12 This error message means that fewer clients and networks will be found than otherwise. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs.</Description> </Message> <Message> <MessageID>1310</MessageID> <Description>Network Discovery failed to connect to a DHCP server due to a connection error. (Network Discovery can communicate only with Microsoft DHCP servers; if you do not use these servers, you can ignore this error.)%12</Description> </Message> <Message> <MessageID>1311</MessageID> <Description>Network Discovery failed to perform a WinSock operation.%12</Description> </Message> <Message> <MessageID>1312</MessageID> <Description>Network Discovery failed to perform a WinSock operation relating to multicast membership. Network Discovery will not discover other routers on your local subnet by listening for OSPF packets. However, if Network Discovery can detect your default gateway using SNMP, it will find those routers anyway.%12</Description> </Message> <Message> <MessageID>1313</MessageID> <Description>Network Discovery did not have time to finish. Therefore, the information in the site database is not as complete as it should be.%12</Description> </Message> <Message> <MessageID>1314</MessageID> <Description>Network Discovery failed to connect to CIM Object Manager. Network Discovery cannot continue because all its configuration information is retrieved from CIM Object Manager.%12</Description> </Message> <Message> <MessageID>1315</MessageID> <Description>Network Discovery detected CIM Object Manager, but could not establish a connection to it. Network Discovery cannot continue because all its configuration information is retrieved from CIM Object Manager.%12</Description> </Message> <Message> <MessageID>1316</MessageID> <Description>Network Discovery failed to read information from CIM Object Manager. Network Discovery cannot continue.%12</Description> </Message> <Message> <MessageID>1317</MessageID> <Description>Network Discovery failed to read information from CIM Object Manager. Network Discovery will continue, but slowly.%12</Description> </Message> <Message> <MessageID>1318</MessageID> <Description>Network Discovery failed to write information to CIM Object Manager. Network Discovery cannot continue.%12</Description> </Message> <Message> <MessageID>1319</MessageID> <Description>Network Discovery failed to write information to CIM Object Manager. Network discovery will continue, but slowly.%12</Description> </Message> <Message> <MessageID>1320</MessageID> <Description>Network Discovery failed to execute a query from CIM Object Manager. Network discovery will continue, but slowly.%12</Description> </Message> <Message> <MessageID>1321</MessageID> <Description>Network Discovery failed to communicate with some SNMP devices because of an internal problem with SNMP resources. Network Discovery will continue, but slowly. The discovery duration might have to elapse before discovery can finish fully.%12</Description> </Message> <Message> <MessageID>1322</MessageID> <Description>Network Discovery failed to export a device to the Discovery Data Manager. Therefore, discovered devices will not appear in the site database.%12</Description> </Message> <Message> <MessageID>1323</MessageID> <Description>Network Discovery failed to export a network to the Discovery Data Manager. Therefore, discovered devices will not appear in the site database.%12</Description> </Message> <Message> <MessageID>1324</MessageID> <Description>Network Discovery failed to enumerate the computers on one or more domains.%12</Description> </Message> <Message> <MessageID>2300</MessageID> <Description>Distribution Manager is beginning to process package "%1" (package ID = %2).%12</Description> </Message> <Message> <MessageID>2301</MessageID> <Description>Distribution Manager successfully processed package "%1" (package ID = %2).%12</Description> </Message> <Message> <MessageID>2302</MessageID> <Description>Distribution Manager failed to process package "%1" (package ID = %2).%12</Description> </Message> <Message> <MessageID>2303</MessageID> <Description>Distribution Manager refreshed package "%1" on distribution point "%2".%12</Description> </Message> <Message> <MessageID>2304</MessageID> <Description>Distribution Manager is retrying to distribute package "%1".%12 Wait to see if the package is successfully distributed on the retry.</Description> </Message> <Message> <MessageID>2305</MessageID> <Description>Distribution Manager failed to process package "%1" without a source directory.%12</Description> </Message> <Message> <MessageID>2306</MessageID> <Description>The source directory "%1" for package "%2" does not exist.%12</Description> </Message> <Message> <MessageID>2307</MessageID> <Description>Distribution Manager failed to access the source directory "%1" for package "%2".%12</Description> </Message> <Message> <MessageID>2308</MessageID> <Description>Distribution Manager failed to remove the previously compressed copy for package "%1" located at "%2".%12</Description> </Message> <Message> <MessageID>2309</MessageID> <Description>Distribution Manager failed to compress package "%1" from "%2" to "%4". The file that failed the compression is "%3".%12</Description> </Message> <Message> <MessageID>2310</MessageID> <Description>Distribution Manager compressed package "%1" from "%2" to "%3".%12</Description> </Message> <Message> <MessageID>2311</MessageID> <Description>Distribution Manager successfully created or updated package "%1".%12</Description> </Message> <Message> <MessageID>2312</MessageID> <Description>Distribution Manager failed to update the distribution source for package "%1".%12</Description> </Message> <Message> <MessageID>2313</MessageID> <Description>Distribution Manager failed to remove package "%1" from "%2".%12</Description> </Message> <Message> <MessageID>2314</MessageID> <Description>Distribution Manager removed package "%1" from "%2" due to changes in the share type or the share name.%12</Description> </Message> <Message> <MessageID>2315</MessageID> <Description>Distribution Manager deleted the compressed image of package "%1" at "%2".%12</Description> </Message> <Message> <MessageID>2316</MessageID> <Description>Distribution Manager failed to delete the compressed image of package "%1" at "%2".%12</Description> </Message> <Message> <MessageID>2317</MessageID> <Description>Distribution Manager is refreshing package "%1" on distribution point "%2".%12</Description> </Message> <Message> <MessageID>2318</MessageID> <Description>Distribution Manager failed to distribute package "%1".%12</Description> </Message> <Message> <MessageID>2319</MessageID> <Description>Distribution Manager failed to decompress package "%1" from "%2".%12</Description> </Message> <Message> <MessageID>2320</MessageID> <Description>There is not enough free disk space on the site server to decompress package "%1".%12</Description> </Message> <Message> <MessageID>2321</MessageID> <Description>Distribution Manager failed to decompress package "%1" from "%2" to "%3". The file that failed to decompress is "%4".%12</Description> </Message> <Message> <MessageID>2322</MessageID> <Description>Distribution Manager decompressed package "%1" from "%2" to "%3".%12</Description> </Message> <Message> <MessageID>2323</MessageID> <Description>Distribution Manager failed to connect to the distribution point.%12</Description> </Message> <Message> <MessageID>2324</MessageID> <Description>Distribution Manager failed to find or create the defined share or folder (%3) on distribution point "%1" for distributing package "%2".%12</Description> </Message> <Message> <MessageID>2325</MessageID> <Description>Distribution Manager failed to create subdirectories on distribution point "%1" for distributing package "%2".%12</Description> </Message> <Message> <MessageID>2326</MessageID> <Description>Distribution Manager failed to save package status for package "%1" to the site database.%12</Description> </Message> <Message> <MessageID>2327</MessageID> <Description>Distribution Manager failed to update the package properties on distribution points for package "%1".%12</Description> </Message> <Message> <MessageID>2328</MessageID> <Description>Distribution Manager failed to copy package "%1" from "%2" to "%3".%12</Description> </Message> <Message> <MessageID>2329</MessageID> <Description>Distribution Manager copied package "%1" from "%2" to "%3".%12</Description> </Message> <Message> <MessageID>2330</MessageID> <Description>Distribution Manager successfully distributed package "%1" to distribution point "%2".%12</Description> </Message> <Message> <MessageID>2331</MessageID> <Description>Distribution Manager successfully removed package "%1" from distribution point "%2".%12</Description> </Message> <Message> <MessageID>2332</MessageID> <Description>Distribution Manager failed to remove package "%1" from distribution path "%2".%12</Description> </Message> <Message> <MessageID>2333</MessageID> <Description>Distribution Manager is preparing to send the compressed image of package "%1" to child site "%2".%12</Description> </Message> <Message> <MessageID>2334</MessageID> <Description>Distribution Manager created a 1.x style instruction to send package "%1" to 1.x child site "%2".%12</Description> </Message> <Message> <MessageID>2335</MessageID> <Description>Distribution Manager instructed Scheduler and Sender to send package "%1" to child site "%2".%12</Description> </Message> <Message> <MessageID>2336</MessageID> <Description>Distribution Manager failed to create a 1.x style instruction to send package "%1" to 1.x child site "%2".%12</Description> </Message> <Message> <MessageID>2337</MessageID> <Description>Distribution Manager failed to instruct Scheduler to send package "%1" to child site "%2".%12</Description> </Message> <Message> <MessageID>2338</MessageID> <Description>Distribution Manager created a 1.x style instruction to send package definition for package "%1" to 1.x child site "%2".%12</Description> </Message> <Message> <MessageID>2339</MessageID> <Description>Distribution Manager instructed Scheduler and Sender to send the package information for package "%1" to child site "%2".%12</Description> </Message> <Message> <MessageID>2340</MessageID> <Description>Distribution Manager failed to create a 1.x style instruction to send the package definition for package "%1" to 1.x child site "%2".%12</Description> </Message> <Message> <MessageID>2341</MessageID> <Description>Distribution Manager failed to send the package information for package "%1" to child site "%2".%12</Description> </Message> <Message> <MessageID>2342</MessageID> <Description>Distribution Manager is starting to distribute package "%1" to distribution point "%2".%12</Description> </Message> <Message> <MessageID>2343</MessageID> <Description>There is not enough free disk space to copy package "%1" to "%2".%12</Description> </Message> <Message> <MessageID>2344</MessageID> <Description>Failed to create virtual directory on the defined share or volume on distribution point "%1".%12</Description> </Message> <Message> <MessageID>2345</MessageID> <Description>Failed to delete virtual directory on the defined share or volume on distribution point "%1".%12</Description> </Message> <Message> <MessageID>2346</MessageID> <Description>Distribution Manager failed to distribute package "%1".%12</Description> </Message> <Message> <MessageID>2347</MessageID> <Description>Distribution Manager upgraded the hidden file ISAPI on the distribution point but was unable to load the file because the original ISAPI was in use. To load the new ISAPI please restart IIS on computer "%1".%12</Description> </Message> <Message> <MessageID>2348</MessageID> <Description>Distribution Manager failed to decompress package "%1" from "%2".%12</Description> </Message> <Message> <MessageID>2349</MessageID> <Description>The WebDAV server extensions are disabled on the distribution point "%1".%12 As a result, clients will not be able to use BITS support on the distribution point. To enable BITS support, enable the WebDAV server extension from the Web Service Extensions node in the Internet Information Services (IIS) administrative tool.</Description> </Message> <Message> <MessageID>2350</MessageID> <Description>Distribution Manager instructed Scheduler and Sender to send a forwarding request to site "%2", requesting that site to forward package "%1" to site "%3".%12</Description> </Message> <Message> <MessageID>2351</MessageID> <Description>Distribution Manager is unable to forward package "%1" to site(s) "%2" because the local version of the package ("%3") is greater than the version requested ("%4").%12</Description> </Message> <Message> <MessageID>2352</MessageID> <Description>Distribution Manager is unable to forward package "%1" to site(s) "%2" because the local version of the package ("%3") is lower than the version requested ("%4").%12</Description> </Message> <Message> <MessageID>2353</MessageID> <Description>Failed to configure ports in IIS on the defined share or volume on distribution point "%1".%12</Description> </Message> <Message> <MessageID>2354</MessageID> <Description>Failed to validate package status file "%1" received from Distribution Point %2 for package %3.%12</Description> </Message> <Message> <MessageID>2355</MessageID> <Description>Package "%1" is not assigned to any standard distribution points for site "%2". Branch distribution points require the package to be assigned to at least one standard distribution point .%12 The branch distribution point downloads package content from a standard distribution point from the site where the branch distribution point client is assigned.</Description> </Message> <Message> <MessageID>2356</MessageID> <Description>Distribution Manager failed to instruct Package Transfer manager to send package "%1" to distribution point "%2".%12</Description> </Message> <Message> <MessageID>2357</MessageID> <Description>Distribution Manager instructed Package Transfer manager to send package "%1" to distribution point "%2".%12</Description> </Message> <Message> <MessageID>2358</MessageID> <Description>"%1" server ("%2") is a 32-bit system. Multicast or File Streaming are not supported distribution point features on 32-bit system.%12 These features can not be enabled on this distribution point.</Description> </Message> <Message> <MessageID>2359</MessageID> <Description>Distribution Manager failed to find a drive on distribution point "%1" on system "%2" which has characteristics appropriate for storing shared folders used by distribution point.%12</Description> </Message> <Message> <MessageID>2360</MessageID> <Description>Distribution Manager failed to verify drive specified by user on distribution point "%1" on system "%2".%12</Description> </Message> <Message> <MessageID>2361</MessageID> <Description>Distribution Manager failed to access the source directory "%1" for content "%2" (content ID = %3).%12</Description> </Message> <Message> <MessageID>2362</MessageID> <Description>Distribution Manager successfully installed IIS component of operating system to distribution point "%1".%12</Description> </Message> <Message> <MessageID>2363</MessageID> <Description>Distribution Manager has not tried to install IIS component of operating system to distribution point "%1" because its operating system is older than Windows Server 2008. Manual installation of IIS component of operating system to distribution point might be needed. Please ensure RDC is also enabled.%12</Description> </Message> <Message> <MessageID>2364</MessageID> <Description>Distribution Manager installed IIS component of operating system to distribution point "%1". Installation process ended with an exit code of %2. Reboot of machine "%1" is needed to complete the configuration of IIS component of operating system. Also please ensure that the http(s) traffic is not blocked on this machine by firewall settings.%12</Description> </Message> <Message> <MessageID>2365</MessageID> <Description>Distribution Manager attempted to run a tool to install IIS component of operating system to distribution point "%1". The tool returned non-zero error code %2. Reboot or manual installation of IIS might be required to complete the configuration of IIS component of operating system. Also please ensure that the http(s) traffic is not blocked on this machine by firewall settings and RDC is enabled.%12</Description> </Message> <Message> <MessageID>2366</MessageID> <Description>Distribution Manager attempted to run a tool to install IIS component of operating system to distribution point "%1". Reboot or manual installation of IIS might be required to complete the configuration of IIS component of operating system. Also please ensure that the http(s) traffic is not blocked on this machine by firewall settings.%12</Description> </Message> <Message> <MessageID>2367</MessageID> <Description>Package "%1" content was successfully imported from a prestaged content file to distribution points on site server "%2" (%3).%12</Description> </Message> <Message> <MessageID>2368</MessageID> <Description>An error occurred during the import of content from a prestaged content file to distribution points on site server "%1" (%2).%12</Description> </Message> <Message> <MessageID>2369</MessageID> <Description>WDS is not installed on distribution point "%1".The PXE service point will not be available.%12</Description> </Message> <Message> <MessageID>2370</MessageID> <Description>Distribution Manager failed to install distribution point %1 on computer %2.%12</Description> </Message> <Message> <MessageID>2371</MessageID> <Description>Distribution Manager is waiting for package %1 content to be prestaged on the distribution point %2. You must manually prestage the package %1 on the distribution point before the content will be available.</Description> </Message> <Message> <MessageID>2372</MessageID> <Description>The content files for package %1 have not yet arrived from the source site %2. Distribution Manager will try again later to distribute the content.</Description> </Message> <Message> <MessageID>2373</MessageID> <Description>PXE is %1 on distribution point %2</Description> </Message> <Message> <MessageID>2374</MessageID> <Description>Multicast is %1 on distribution point %2</Description> </Message> <Message> <MessageID>2375</MessageID> <Description>Created virtual directories on the defined share or volume on distribution point "%1" successfully.</Description> </Message> <Message> <MessageID>2376</MessageID> <Description>Distribution Manager created a snapshot for content %1 successfully.</Description> </Message> <Message> <MessageID>2380</MessageID> <Description>Start to evaluate package "%1" on distribution point "%2".</Description> </Message> <Message> <MessageID>2381</MessageID> <Description>An evaluation task is running. Put package "%1" to wait queue on distribution point "%2".</Description> </Message> <Message> <MessageID>2382</MessageID> <Description>The hash of package "%1" is invalid on distribution point "%2". Please redistribute the package.</Description> </Message> <Message> <MessageID>2383</MessageID> <Description>Failed to validate package "%1" on distribution point "%2". The package may not be present or may be corrupt. Please redistribute it.</Description> </Message> <Message> <MessageID>2384</MessageID> <Description>Package "%1" on distribution point "%2" has been verified successfully.</Description> </Message> <Message> <MessageID>2385</MessageID> <Description>Following file(s) of package "%1" on distribution point "%2" are missing. %3</Description> </Message> <Message> <MessageID>2386</MessageID> <Description>All content on distribution point "%1" has been verified.</Description> </Message> <Message> <MessageID>2387</MessageID> <Description>The hash of the migrated package "%1" is incorrect in the database. Please update the package on the Configuration Manager 2007 site and then migrate the package again.</Description> </Message> <Message> <MessageID>2388</MessageID> <Description>Failed to retrieve the package list on the distribution point %1. Or the package list in content library doesn't match the one in WMI. Review smsdpmon.log for more information about this failure.</Description> </Message> <Message> <MessageID>2389</MessageID> <Description>Failed to copy the package "%1" from "%2" into the content library on the distribution point server "%3".</Description> </Message> <Message> <MessageID>2390</MessageID> <Description>The migrated packages on the distribution point server "%1" have been successfully copied into the content library on the server.</Description> </Message> <Message> <MessageID>2391</MessageID> <Description>Distribution Manager failed to connect to the distribution point %1. Check your network and firewall settings.</Description> </Message> <Message> <MessageID>2392</MessageID> <Description>Distribution Manager has not tried to install IIS component of operating system to distribution point "%1". You should install and configure IIS manually. Please ensure RDC is also enabled.%12</Description> </Message> <Message> <MessageID>2393</MessageID> <Description>Successfully retrieved and validated the package list from the distribution point %1.</Description> </Message> <Message> <MessageID>2394</MessageID> <Description>A reboot is required on the distribution point %1.</Description> </Message> <Message> <MessageID>2397</MessageID> <Description>Detail will be available after the server finishes processing the messages.</Description> </Message> <Message> <MessageID>2398</MessageID> <Description>Starting to process content</Description> </Message> <Message> <MessageID>2399</MessageID> <Description>Successfully completed the installation or upgrade of the distribution point on computer "%1".</Description> </Message> <Message> <MessageID>2400</MessageID> <Description>Database Notification Monitor failed to copy file smsxp.dll from the \SMS\bin\i386 directory to its required place in the\Windows\system32 directory. Smsxp.dll must exist in the system32 directory for all triggering operations to function, such as notification to the server components of a new package or collection.%12</Description> </Message> <Message> <MessageID>2401</MessageID> <Description>Database Notification Monitor failed to execute database maintenance task "%1".%12</Description> </Message> <Message> <MessageID>2402</MessageID> <Description>Database Notification Monitor failed to execute database maintenance SQL Server command "%1".%12</Description> </Message> <Message> <MessageID>2404</MessageID> <Description>The database maintenance SQL Server task "%1" completed successfully. The task deleted %2 items from the site database.</Description> </Message> <Message> <MessageID>2405</MessageID> <Description>Database Notification Monitor is installing trigger "%1" for table "%2" and actions "%3" in the site database. Server components such as Hierarchy Manager, Collection Evaluator, and Discovery Data Manager instruct Database Notification Monitor to install SQL Server triggers. Then, when certain kinds of data are added to, changed in, or removed from the site database, the SQL Server triggers notify Database Notification Monitor. In turn, Database Notification Monitor notifies the appropriate server components.</Description> </Message> <Message> <MessageID>2406</MessageID> <Description>Database Notification Monitor is removing trigger "%1" from the site database. Server components such as Hierarchy Manager, Collection Evaluator, and Discovery Data Manager instruct Database Notification Monitor to install SQL triggers. Then, when certain kinds of data are added to, changed in, or removed from the site database, the SQL Server triggers notify Database Notification Monitor. In turn, Database Notification Monitor notifies the appropriate server components. This trigger is being removed because it is no longer needed.</Description> </Message> <Message> <MessageID>2407</MessageID> <Description>Database Notification Monitor failed to install trigger "%1" in the site database.%12</Description> </Message> <Message> <MessageID>2408</MessageID> <Description>Database Notification Monitor is executing database maintenance SQL Server command/task "%1". You can configure the execution schedule for this SQL Server command/task in the Configuration Manager console under Administration / Overview / Site Configuration / Sites -> Site Maintenance.</Description> </Message> <Message> <MessageID>2409</MessageID> <Description>The Delete Aged Collected Files database maintenance task completed successfully. The task deleted %1 collected files and %2 directories.</Description> </Message> <Message> <MessageID>2410</MessageID> <Description>The Rebuild Indexes database maintenance task successfully recreated index "%1" on table "%2" in the site database. The Rebuild Indexes task periodically recreates the indexes in the site database to provide optimal query performance.</Description> </Message> <Message> <MessageID>2411</MessageID> <Description>The Rebuild Indexes task has dropped index "%1" on table "%2" in the site database. The Rebuild Indexes task periodically recreates the indexes in the site database to provide optimal query performance. The task will drop an index when the index has a density of less than 0.50, which indicates that it is not selective enough to improve query performance.</Description> </Message> <Message> <MessageID>2412</MessageID> <Description>The Monitor Keys and Recreate Views database maintenance task has detected less than 100 values left for key "%1" and has rolled it over to "%2".%12</Description> </Message> <Message> <MessageID>2413</MessageID> <Description>The Software Metering File Usage Summarization task has completed, %1 rows have been added to the summary tables.%12</Description> </Message> <Message> <MessageID>2414</MessageID> <Description>The Software Metering Data Monthly Usage Summarization task has completed, %1 rows have been added or updated in the summary tables.%12</Description> </Message> <Message> <MessageID>2415</MessageID> <Description>The Clear Install Flag for Undiscovered Clients task has completed, %1 rows have been updated in system discovery tables.%12</Description> </Message> <Message> <MessageID>2416</MessageID> <Description>Database Notification Monitor could not start the SMS Backup service on server %1.%12</Description> </Message> <Message> <MessageID>2417</MessageID> <Description>The Delete Inactive Client Discovery Data task has completed, %1 inactive clients have been removed from the database.%12</Description> </Message> <Message> <MessageID>2418</MessageID> <Description>The Delete Obsolete Client Discovery Data task has completed, %1 obsolete clients have been removed from the database.%12</Description> </Message> <Message> <MessageID>2419</MessageID> <Description>The Client Access License Usage Data Summarization task has completed, %1 rows have been added or updated in the summary table.%12</Description> </Message> <Message> <MessageID>2420</MessageID> <Description>The task "%1" is configured to run today, but it could not run within the scheduled time. %12</Description> </Message> <Message> <MessageID>2421</MessageID> <Description>Database Notification Monitor succeed to start task Reset AMT Computer Passwords.%12</Description> </Message> <Message> <MessageID>2422</MessageID> <Description>Database Notification Monitor succeed to start task Evaluate Provisioned AMT Computer Certificates.%12</Description> </Message> <Message> <MessageID>2423</MessageID> <Description>Database Notification Monitor succeed to run task 'Delete Expired Bookmarks'. %1 bookmarks have been removed.%12</Description> </Message> <Message> <MessageID>2424</MessageID> <Description>Database Notification Monitor succeed to run task 'Delete Expired Activities'. %1 activities have been removed.%12</Description> </Message> <Message> <MessageID>2425</MessageID> <Description>Database Notification Monitor succeed to run task 'Delete Expired Activity Facts'. %1 activity facts have been removed.%12</Description> </Message> <Message> <MessageID>2426</MessageID> <Description>Database Notification Monitor successfully ran task 'Delete Obsolete Alerts'. %1 alerts have been removed.%12</Description> </Message> <Message> <MessageID>2427</MessageID> <Description>The database maintenance SQL Server task "%1" completed successfully. %2 catalog rows have been added.</Description> </Message> <Message> <MessageID>2428</MessageID> <Description>The database maintenance SQL Server task "%1" completed successfully. %2 Software rows have been added to summary table.</Description> </Message> <Message> <MessageID>2500</MessageID> <Description>Collection Evaluator failed to enumerate collections.%12</Description> </Message> <Message> <MessageID>2504</MessageID> <Description>Collection Evaluator failed to find collection "%1". Collection Evaluator received a .udc (update collection) or .adc (create collection) file for a collection that does not exist.%12</Description> </Message> <Message> <MessageID>2507</MessageID> <Description>Collection Evaluator failed to delete collection "%1".%12</Description> </Message> <Message> <MessageID>2511</MessageID> <Description>Collection Evaluator failed to update the membership of collection "%1".%12</Description> </Message> <Message> <MessageID>2519</MessageID> <Description>Collection Evaluator failed to enumerate members of collection "%1" at site "%2".%12</Description> </Message> <Message> <MessageID>2521</MessageID> <Description>Collection Evaluator failed to retrieve collection "%1" from the collection source. (On primary sites, the collection source is the site database. On secondary sites, it is \Sms\inboxes\colleval.box.)%12</Description> </Message> <Message> <MessageID>2523</MessageID> <Description>Collection Evaluator failed to enumerate membership rules for collection "%1".%12</Description> </Message> <Message> <MessageID>2524</MessageID> <Description>Collection Evaluator failed to write to file "%1".%12</Description> </Message> <Message> <MessageID>2530</MessageID> <Description>Collection Evaluator failed to update collection "%1" in the collection source. (On primary sites, this is the site database. On secondary sites, this is \Sms\inboxes\colleval.box.)%12</Description> </Message> <Message> <MessageID>2531</MessageID> <Description>Collection Evaluator failed to retrieve a SQL Server command from the collection membership rule.%12</Description> </Message> <Message> <MessageID>2532</MessageID> <Description>Collection Evaluator failed to connect to the site database.%12</Description> </Message> <Message> <MessageID>2533</MessageID> <Description>Collection Evaluator failed to enumerate discovery architectures because it cannot retrieve the discovery architecture list from the database.%12</Description> </Message> <Message> <MessageID>2535</MessageID> <Description>Collection "%1" has no name. Collection Evaluator cannot continue processing the collection without a name.%12</Description> </Message> <Message> <MessageID>2542</MessageID> <Description>Collection Evaluator failed to update the query rule "%1" of collection "%2" (%3).%12</Description> </Message> <Message> <MessageID>2543</MessageID> <Description>Collection Evaluator failed to evalute some of the query rules for collection "%1" (%2).%12</Description> </Message> <Message> <MessageID>2545</MessageID> <Description>Collection Evaluator successfully processed new Collection Settings %1.%12</Description> </Message> <Message> <MessageID>2546</MessageID> <Description>Collection Evaluator successfully processed Update to Collection Settings %1.%12</Description> </Message> <Message> <MessageID>2547</MessageID> <Description>Collection Evaluator successfully removed Collection Settings Policy for Collection %1.%12</Description> </Message> <Message> <MessageID>2548</MessageID> <Description>Collection Evaluator failed to process Collection Settings changes. These changes will be retried on next processing cycle.%12</Description> </Message> <Message> <MessageID>2549</MessageID> <Description>Collection Evaluator failed to process Collection Settings for Collection %1. This Collection Settings will be retried %2 times on the next processing cycles.%12</Description> </Message> <Message> <MessageID>2550</MessageID> <Description>Collection Evaluator failed to process Collection Settings for Collection %1. This Collection Settings has been retried %2 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>2551</MessageID> <Description>Collection Evaluator failed to process Collection Settings Replication File %1 as Collection %2 referenced object of type %3 does not exists. This Collection Settings Replication file has been retried %4 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>2552</MessageID> <Description>Collection Evaluator failed to process Collection Settings Replication File %1. This Collection Settings Replication file has been retried %2 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>2553</MessageID> <Description>Policy Provider failed to process Machine Settings for Machine %1. This Machine Settings will be retried on the next processing cycles.%12</Description> </Message> <Message> <MessageID>2554</MessageID> <Description>Policy Provider failed to process Machine Settings changes. These changes will be retried on next processing cycle.%12</Description> </Message> <Message> <MessageID>2555</MessageID> <Description>Collection Evaluator successfully processed %1 client updates for collection %2. Original clients number: %3, added: %4, deleted: %5.</Description> </Message> <Message> <MessageID>2556</MessageID> <Description>The query rule for the collection "%1" generated a high number of records (%2).%12</Description> </Message> <Message> <MessageID>2557</MessageID> <Description>Policy Provider failed to process User Settings changes. These changes will be retried on next processing cycle.%12</Description> </Message> <Message> <MessageID>2600</MessageID> <Description>Discovery Data Manager failed to synchronize this site's deletions with all secondary site databases. When discovery data is deleted, the deletion must be propagated to all secondary sites. In addition, any licenses associated with the deleted resources must be revoked. Because secondary site data is not synchronized, more licenses will be used than is necessary.%12</Description> </Message> <Message> <MessageID>2601</MessageID> <Description>Discovery Data Manager failed to connect to the discovery database.%12</Description> </Message> <Message> <MessageID>2602</MessageID> <Description>Discovery Data Manager is removing references from deleted site "%1".%12</Description> </Message> <Message> <MessageID>2603</MessageID> <Description>Discovery Data Manager is beginning the process of sending discovery data to the new parent site. (This happens whenever a site attaches to a new parent site.)%12</Description> </Message> <Message> <MessageID>2604</MessageID> <Description>Discovery Data Manager failed to send discovery data to the new parent site. Discovery Data Manager will retry, resuming where it left off.%12</Description> </Message> <Message> <MessageID>2605</MessageID> <Description>Discovery Data Manager failed to move the new parent site notification file to the Data Loader inbox.%12</Description> </Message> <Message> <MessageID>2606</MessageID> <Description>Discovery Data Manager has tried ten times to send the discovery database to the new parent site, and Discovery Data Manager has been unsuccessful each time. Discovery Data Manager is giving up.%12</Description> </Message> <Message> <MessageID>2607</MessageID> <Description>Discovery Data Manager has successfully sent the discovery database to the parent site.%12</Description> </Message> <Message> <MessageID>2608</MessageID> <Description>Discovery Data Manager failed to send file "%1" to site "%2".%12</Description> </Message> <Message> <MessageID>2609</MessageID> <Description>Discovery Data Manager failed to enumerate discovery architectures.%12</Description> </Message> <Message> <MessageID>2610</MessageID> <Description>Discovery Data Manager failed to create the discovery data record (DDR) to send to the new parent site.%12</Description> </Message> <Message> <MessageID>2611</MessageID> <Description>Discovery Data Manager has detected a change in assignment rules. Discovery Data Manager will not process discovery data records (DDRs) until it completes the rule refresh operation.%12</Description> </Message> <Message> <MessageID>2612</MessageID> <Description>Discovery Data Manager failed to complete the rule refresh process.%12</Description> </Message> <Message> <MessageID>2613</MessageID> <Description>Discovery Data Manager failed to read the serial number from the parsed discovery data record (DDR) "%1".%12</Description> </Message> <Message> <MessageID>2614</MessageID> <Description>Discovery Data Manager failed to read the new discovery item from the parsed discovery data record (DDR) "%1".%12</Description> </Message> <Message> <MessageID>2615</MessageID> <Description>Discovery Data Manager failed to parse the new discovery item data from the parsed discovery data record (DDR) %1.%12</Description> </Message> <Message> <MessageID>2616</MessageID> <Description>Discovery Data Manager failed to insert the new item from file "%1" into the data source.%12</Description> </Message> <Message> <MessageID>2617</MessageID> <Description>Discovery Data Manager failed to write the serial number record to file "%1".%12</Description> </Message> <Message> <MessageID>2618</MessageID> <Description>Discovery Data Manager failed to write the item key record to file "%1".%12</Description> </Message> <Message> <MessageID>2619</MessageID> <Description>Discovery Data Manager failed to write item buffer to file "%1". Discovery Data Manager is attempting to send a discovery data record (DDR) to another site or registered consumer, but is unable to write the data for the new item.%12</Description> </Message> <Message> <MessageID>2620</MessageID> <Description>Discovery Data Manager failed to format discovery data into file "%1".%12</Description> </Message> <Message> <MessageID>2621</MessageID> <Description>Discovery Data Manager failed to enumerate properties for architecture "%1".%12</Description> </Message> <Message> <MessageID>2622</MessageID> <Description>Discovery Data Manager failed to process file "%1" because it cannot detect any Name properties. Discovery Data Manager requires that all discovery data records (DDRs) report at least one field that is defined as a Name candidate. The three default architectures--User, User Group, and System--all have one or more defined Name fields. Either this DDR is not of one of those three architectures, or it is an invalid DDR.%12</Description> </Message> <Message> <MessageID>2623</MessageID> <Description>Discovery Data Manager failed to insert discovery data because the site is out of client access licenses.%12</Description> </Message> <Message> <MessageID>2624</MessageID> <Description>Discovery Data Manager failed to read the current site's .ncf (assignment rule) file.%12</Description> </Message> <Message> <MessageID>2625</MessageID> <Description>Discovery Data Manager failed to read the .ncf (assignment rule) file for site "%1".%12</Description> </Message> <Message> <MessageID>2626</MessageID> <Description>Discovery Data Manager failed to open the .ncf (assignment rule) file for site "%1".%12</Description> </Message> <Message> <MessageID>2627</MessageID> <Description>Discovery Data Manager failed to read the site control file for site "%1". Because the site database maintains the site control files for this site and all sites beneath it, Discovery Data Manager reads site control files only from the site database.%12</Description> </Message> <Message> <MessageID>2628</MessageID> <Description>Discovery Data Manager failed to write the .ncf (assignment rule) file "%1". Discovery Data Manager will retry writing this file during its next processing cycle.%12</Description> </Message> <Message> <MessageID>2629</MessageID> <Description>Discovery Data Manager failed to copy the .ncf (assignment rule) file "%1" to Asstdata.box, the point of replication to client access points (CAPs). Discovery Data Manager will retry copying this file during its next processing cycle.%12</Description> </Message> <Message> <MessageID>2630</MessageID> <Description>During a refresh, Discovery Data Manager detected that assignment rules had changed. Therefore, Discovery Data Manager is stopping the refresh now, but will perform it later.%12</Description> </Message> <Message> <MessageID>2631</MessageID> <Description>Discovery Data Manager failed to create a full refresh file to send to the secondary site.%12</Description> </Message> <Message> <MessageID>2632</MessageID> <Description>Discovery Data Manager failed to notify all consumers that a full refresh has occurred and that users need to refresh their data store.%12</Description> </Message> <Message> <MessageID>2633</MessageID> <Description>Discovery Data Manager failed to send file "%1" to site "%2".%12</Description> </Message> <Message> <MessageID>2634</MessageID> <Description>Discovery Data Manager will resume processing because it has successfully completed assignment-rule processing.%12</Description> </Message> <Message> <MessageID>2635</MessageID> <Description>While parsing discovery data record (DDR) "%1", Discovery Data Manager found a blank Architecture field, which makes "%1" a bad DDR.%12</Description> </Message> <Message> <MessageID>2636</MessageID> <Description>Discovery Data Manager failed to process the discovery data record (DDR) "%1", because it cannot update the data source.%12</Description> </Message> <Message> <MessageID>2637</MessageID> <Description>Discovery Data Manager is updating statistics in all tables in the site database, which helps ensure optimal performance of SQL Server 6.5.%12</Description> </Message> <Message> <MessageID>2638</MessageID> <Description>Discovery Data Manager has interpreted discovery data record (DDR) "%1" as a delete request. Therefore, Discovery Data Manager is deleting item "%2" of architecture "%3". DDR "%1" contains an old item, but not a new item.%12</Description> </Message> <Message> <MessageID>2639</MessageID> <Description>Discovery Data Manager has processed a discovery data record (DDR) for computer "%1" with the SMS identifier of "%3" which has reported a new hardware identifier of "%2". %4 existing records sharing this hardware identifier have been marked as obsolete. The data in these records has been superseded by the data in the new record.</Description> </Message> <Message> <MessageID>2640</MessageID> <Description>Discovery Data Manager has processed a discovery data record (DDR) for computer "%1" with the SMS identifier of "%2" which has reported a new SMS ID of "%3". An existing record with the previous SMS identifier has been marked as obsolete. The data in this record has been superseded by the data in the new record.</Description> </Message> <Message> <MessageID>2641</MessageID> <Description>Discovery Data Manager failed to process a client registration request for computer with the identity "%1" and with the SMS identifier "%2" because the SMS identifier has already been registered for another client.%12</Description> </Message> <Message> <MessageID>2642</MessageID> <Description>Configuration Manager has detected a record that might be conflicting with the following client record in the site database: %1.%12</Description> </Message> <Message> <MessageID>2700</MessageID> <Description>Inventory Data Loader failed to read the delta MIF file "%1" and will move the file to the BADMIFs directory.%12</Description> </Message> <Message> <MessageID>2701</MessageID> <Description>Inventory Data Loader encountered a SQL Server problem and is stopping the MIF processing thread.%12</Description> </Message> <Message> <MessageID>2702</MessageID> <Description>Inventory Data Loader failed to process the delta MIF file "%1" because the file does not have a corresponding discovery record. Inventory Data Loader has moved this file to the Orphans directory as file "%2" and will retry processing it within 10 minutes.%12</Description> </Message> <Message> <MessageID>2703</MessageID> <Description>Inventory Data Loader failed to process the delta MIF file "%1" and has moved it to "%2."%12</Description> </Message> <Message> <MessageID>2704</MessageID> <Description>Inventory Data Loader is updating database statistics for all inventory-related tables. By default, statistics are updated to optimize database performance after a certain number of MIF files have been processed. This message indicates that this milestone has been achieved. You can edit this value in the Configuration Manager Console, under Component Configuration, Data Processing and Storage Properties.%12</Description> </Message> <Message> <MessageID>2705</MessageID> <Description>Inventory Data Loader has finished processing %1 MIF files and is terminating the MIF file processing thread.%12 Each time the processing cycle completes, Inventory Data Loader generates this message to report the number of MIF files it has processed.</Description> </Message> <Message> <MessageID>2706</MessageID> <Description>Inventory Data Loader has quit trying to update inventory after failing 10 times. Inventory Data Loader detected that the parent site was changed to a new site, and then Inventory Data Loader tried to send all inventory to the new parent through the inventory update process. However, Inventory Data Loader tried this process 10 times and failed each time.%12</Description> </Message> <Message> <MessageID>2707</MessageID> <Description>Inventory Data Loader failed to send inventory to the new parent site, but it will retry %1 more times before quitting.%12 If you want more information, review the immediately preceding status messages from this component, or look in dadaldr.log. If you ignore this problem, ConfigMgr will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>2708</MessageID> <Description>Inventory Data Loader detected that the parent site has changed to a new site, and now Inventory Data Loader is trying to send all inventory to the new parent through the inventory update process.%12</Description> </Message> <Message> <MessageID>2709</MessageID> <Description>The Inventory Data Loader inventory update process has initialized the inventory update status file, which controls the inventory update process's ability to restart.%12</Description> </Message> <Message> <MessageID>2710</MessageID> <Description>The Inventory Data Loader has detected that the inventory update process has already been completed. Therefore, Inventory Data Loader is not starting the inventory update process. If this information is incorrect, delete the status file Inv_stat.dat to force the inventory update process to restart.%12</Description> </Message> <Message> <MessageID>2711</MessageID> <Description>The Inventory Data Loader inventory update process will use the directory %1. Inventory Data Loader will create delta MIF files in this folder to send to the parent site.%12</Description> </Message> <Message> <MessageID>2712</MessageID> <Description>The Inventory Data Loader inventory update process failed to write the MIF file for machine %1 of architecture %2.%12</Description> </Message> <Message> <MessageID>2713</MessageID> <Description>The Inventory Data Loader inventory update process has finished successfully. All inventory has been sent to the parent site.%12</Description> </Message> <Message> <MessageID>2714</MessageID> <Description>Inventory Data Loader has requested a resynchronization for site %1. Inventory Data Loader requests resynchronization when it receives an Update or Delete request for a nonexistent group.%12</Description> </Message> <Message> <MessageID>2715</MessageID> <Description>Inventory Data Loader has detected a resynchronization request for agent %1. When an agent is specified, the resynchronization is planned only for items reported by that agent. A resynchronization indicates that the current MIF file represents all inventory for the current machine. If any inventory is present in the database that does not occur in the MIF file, Inventory Data Loader deletes it (unless, as with an agent resynchronization, it was reported by a different agent). If many resynchronizations occur, it indicates that inventory was lost at some point.%12</Description> </Message> <Message> <MessageID>2716</MessageID> <Description>Inventory Data Loader is going to widen attribute %2 of group %1 from %3 to %4. Inventory Data Loader has received a MIF file that contains a referenced attribute that exceeds the current maximum length. Inventory Data Loader will attempt to widen the column before it inserts the data.%12</Description> </Message> <Message> <MessageID>2717</MessageID> <Description>Inventory Data Loader has added group %1 to architecture %2. Inventory Data Loader found a group that it had not found before and successfully added the group to the inventory database.%12</Description> </Message> <Message> <MessageID>2718</MessageID> <Description>Inventory Data Loader has added the architecture %1. Inventory Data Loader found an architecture that it had not found before and successfully added it to the inventory database. A custom MIF file, either from this site or from one beneath it, caused this action.%12</Description> </Message> <Message> <MessageID>2719</MessageID> <Description>Inventory Data Loader failed to process the file %1 because it is larger than the defined maximum allowable size of %2.%12</Description> </Message> <Message> <MessageID>2720</MessageID> <Description>Inventory Data Loader has detected that a resource with GUID %1 needs to be resynchronized, but the resource will not be resynchronized because the registry key HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Resynchronize Clients on the resource computer has been turned off. Data will not be processed for this resource until it has been resynchronized.%12</Description> </Message> <Message> <MessageID>2721</MessageID> <Description>Inventory Data Loader failed to compile %1. The failing MOF file has been moved to %2, and the last successfully compiled version has been restored.%12</Description> </Message> <Message> <MessageID>2722</MessageID> <Description>Inventory Data Loader has requested a resynchronization for machine %1. Inventory Data Loader requests resynchronization when it receives an Update or Delete request for a nonexistent group.%12</Description> </Message> <Message> <MessageID>2723</MessageID> <Description>Inventory Data Loader requested a resynchronization for machine "%1" because a hardware inventory file was sent without a public key information.%12</Description> </Message> <Message> <MessageID>2724</MessageID> <Description>Inventory Data Loader detected more than %1 class redefinitions in %2 minutes. Will switch to single-threaded operation after exceeding %3.%12</Description> </Message> <Message> <MessageID>2725</MessageID> <Description>Inventory Data Loader detected more than %1 class redefinitions in %2 minutes. Switching to single-threaded operation for the next %3 minutes.%12</Description> </Message> <Message> <MessageID>2800</MessageID> <Description>Site Control Manager is beginning to process delta site control file "%1".%12 Configuration Manager Server Components and SMS Provider clients (such as the Configuration Manager Console) submit delta site control files to change the configuration of the site. A delta site control file contains one or more required changes to the actual site control file ("%2" at this site). The actual site control file contains the site configuration currently in use. The site is successfully reconfigured only after Site Control Manager receives and processes a delta site control file and then updates the actual site control file with the new configuration data.</Description> </Message> <Message> <MessageID>2801</MessageID> <Description>Site Control Manager successfully processed delta site control file %1.</Description> </Message> <Message> <MessageID>2802</MessageID> <Description>Site Control Manager could not completely process delta site control file %1.%12</Description> </Message> <Message> <MessageID>2803</MessageID> <Description>A non-critical problem occurred while Site Control Manager was processing delta site control file %1.%12</Description> </Message> <Message> <MessageID>2804</MessageID> <Description>Site Control Manager aborted the processing of delta site control file %1.%12</Description> </Message> <Message> <MessageID>2805</MessageID> <Description>The delta site control file %1 contains a corrupt site configuration change request. This site configuration change request and the remaining site configuration change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2806</MessageID> <Description>The delta site control file %1 contains a site configuration change request that is missing a "%2" item, or that item is corrupt or invalid. The site configuration change request cannot be processed without this item.%12</Description> </Message> <Message> <MessageID>2807</MessageID> <Description>The delta site control file %1 contains a site configuration change request submitted by the "%2" SMS Provider client running as user "%3" on computer "%4" at site "%5" at "%6".%12 The site configuration change request was assigned the serial number %7 at site "%5". Site Control Manager uses this serial number to ensure that it does not process the same site configuration change request from an SMS Provider client (such as the Configuration Manager Console) more than once. When an SMS Provider client submits a delta site control file containing a site configuration change request, Hierarchy Manager at the site submitting the file will report status message 3307. You can track the time on message 3307 and this one to determine when the site configuration change request was submitted and when it actually went into effect.</Description> </Message> <Message> <MessageID>2808</MessageID> <Description>The delta site control file %1 contains a site configuration change request submitted by the server component "%2" running as user "%3" on computer "%4" at "%5".%12</Description> </Message> <Message> <MessageID>2809</MessageID> <Description>Site Control Manager will ignore this site configuration change request ("%1" from site "%2").%12 This change request was already processed as part of an older delta site control file. Hierarchy Manager at site "%2" will continue to submit this site configuration change request until it receives a copy of the new actual site control file from site "%3" that confirms the change was successfully processed. If you find that Hierarchy Manager continues to submit this site configuration change request for an extraordinarily long time, there might be a problem with Hierarchy Manager at any of the sites between and including sites "%2" and "%3". Or, if "%2" and "%3" are different sites, there might be a communication problem between them or any sites between them. If you suspect this is happening, check for Warning and Error status messages from Hierarchy Manager, Replication Manager, Scheduler, and the Sender components at these sites.</Description> </Message> <Message> <MessageID>2810</MessageID> <Description>Site Control Manager created the temporary file "%1".%12 In a moment, Site Control Manager will rename this file to %2, and it will become the new actual site control file.%12</Description> </Message> <Message> <MessageID>2811</MessageID> <Description>Site Control Manager created serial number %2 of the actual site control file %1.%12 This creation occurred in response to a site configuration change request contained in delta site control file %3. The other Configuration Manager Server Components will detect that a new actual site control file is available, read it, and reconfigure themselves accordingly.</Description> </Message> <Message> <MessageID>2812</MessageID> <Description>Site Control Manager created serial number %2 of the actual site control file %1 as a result of processing delta site control file %3.%12 No changes were made to the site configuration.</Description> </Message> <Message> <MessageID>2813</MessageID> <Description>Site Control Manager added a "%1" item named "%2" to the actual site control file %5.%12 This addition occurred as a result of a site configuration change request in delta site control file %4. The change will take effect in serial number %3 of the actual site control file.</Description> </Message> <Message> <MessageID>2814</MessageID> <Description>Site Control Manager modified the properties of the "%1" item named "%2" in the actual site control file %7.%12 This modification occurred as a result of a site configuration change request in delta site control file %6. The change will take effect in serial number %5 of the actual site control file. You can compare the file %3 with the file %4 to determine which properties changed.</Description> </Message> <Message> <MessageID>2815</MessageID> <Description>Site Control Manager deleted the "%1" item named "%2" from the actual site control file %5.%12 This deletion occurred as a result of a site configuration change request contained in delta site control file %4. The change will take effect in serial number %3 of the actual site control file.</Description> </Message> <Message> <MessageID>2816</MessageID> <Description>The actual site control file %1 does not exist.%12</Description> </Message> <Message> <MessageID>2817</MessageID> <Description>This computer "%1" is not the site server (%2).%12</Description> </Message> <Message> <MessageID>2818</MessageID> <Description>The actual site control file %1 does not contain a "%2" item.%12</Description> </Message> <Message> <MessageID>2819</MessageID> <Description>Site Control Manager will maintain copies of the %1 most recent actual site control files in the directory "%2".%12 The actual site control file %3 contains the configuration currently in use at this site. You can compare the files in the "%2" directory with each other to determine how the site configuration has changed over time. Each file is named ????????.ct0, where ???????? is the actual site control file serial number in hexadecimal format. For example, actual site control file 20 would be named 00000014.ct0. Also, if the current actual site control file %3 ever becomes corrupted or is ever accidentally deleted, you can restore it from one of the versions in the "%2" directory. Contact Microsoft for help before attempting to restore "%3" from one of these versions.</Description> </Message> <Message> <MessageID>2820</MessageID> <Description>Site Control Manager wrote a copy of the actual site control file %1 to %2.%12 In a moment, Site Control Manager will move this file into the Hierarchy Manager inbox ("%3") for processing.</Description> </Message> <Message> <MessageID>2821</MessageID> <Description>Site Control Manager could not write a copy of the actual site control file %1 to %2. Consequently, Hierarchy Manager will not be notified that the site configuration has changed, and it might appear that the site has not been fully reconfigured.%12</Description> </Message> <Message> <MessageID>2822</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not identify the change request as being valid. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2823</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify which site should receive the change request. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2824</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies that the change request should be submitted to site "%3" instead of this site ("%4"). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2825</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify which site submitted the change request. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2826</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify which computer submitted the change request. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2827</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify which user submitted the change request. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2828</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify which component submitted the change request. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2829</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 was submitted by a server component at site "%3", instead of this site ("%4"). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2830</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site type that does not match the current site's type. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2831</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify a site code. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2832</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site code (%3) that does not match the current site's code (%4). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2833</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify a site name. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2834</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site name ("%3") that does not match the current site's name ("%4"). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2835</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site server. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2836</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site server name ("%3") that does not match the name of the current site server ("%4"). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2837</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the domain of the site server. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2838</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site server domain (%3) that does not match the site server's domain (%4). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2839</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server's platform. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2840</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server installation directory. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2841</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site server installation directory ("%3") that does not match the current site's installation directory ("%4"). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2842</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2does not specify the domain of the service account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2843</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the service account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2844</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the plain text name of the service account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2845</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the service account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2846</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting the service account and password. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2847</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies an invalid public key for decrypting the service account and password. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2848</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies an service account name and/or password that cannot be decrypted with the specified public key. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2849</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the public key for decrypting the address accounts and passwords. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2850</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL Server in use at this site. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2851</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site database. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2852</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL administrator account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2853</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the SQL administrator account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2854</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting the SQL administrator account and password. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2855</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a SQL administrator account name and/or password that cannot be decrypted with the specified public key. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2864</MessageID> <Description>The "%1" item in the actual site control file %2 does not contain a "%3" item named "%4", or that item is corrupt. As a result, the Configuration Manager Server Components might not be using the site system connection accounts you created in the Configuration Manager Console and might be unable to access some site systems.%12</Description> </Message> <Message> <MessageID>2865</MessageID> <Description>Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager.%12 This is the new actual site control file that contains the current configuration of this site. If this is a primary site, Hierarchy Manager will update this site's database with the copy. If this is a child site of another site, Hierarchy Manager will replicate the copy up the site hierarchy, updating each parent site's database.</Description> </Message> <Message> <MessageID>2866</MessageID> <Description>Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager as a heartbeat site control file.%12 Site Control Manager periodically submits heartbeat site control files to Hierarchy Manager to ensure that this site and all of its parent sites contain an up-to-date copy of this site's configuration. If this is a primary site, Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, Hierarchy Manager will replicate the copy up the site hierarchy and ensure that each parent site's database contains the up-to-date configuration. Site Control Manager will then submit a heartbeat site control file to Hierarchy Manager at "%3".</Description> </Message> <Message> <MessageID>2867</MessageID> <Description>Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager as a heartbeat site control file.%12 Site Control Manager periodically submits heartbeat site control files to Hierarchy Manager to ensure that this site and all of its parent sites contain an up-to-date copy of this site's configuration. If this is a primary site, Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, Hierarchy Manager will replicate the copy up the site hierarchy and ensure that each parent site's database contains the up-to-date configuration.</Description> </Message> <Message> <MessageID>2868</MessageID> <Description>Site Control Manager is configured so that no more heartbeat site control files will be submitted to Hierarchy Manager.%12</Description> </Message> <Message> <MessageID>2869</MessageID> <Description>The schedule at which Site Control Manager submits heartbeat site control files to Hierarchy Manager has changed.%12 The next heartbeat site control file will be submitted at "%1". Site Control Manager periodically submits heartbeat site control files to Hierarchy Manager to ensure that this site and all of its parent sites contain an up-to-date copy of this site's configuration. If this is a primary site, Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, Hierarchy Manager will replicate the heartbeat site control file up the site hierarchy and ensure that each parent site's database contains the up-to-date configuration.</Description> </Message> <Message> <MessageID>2870</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2contains a full version that's older than the current full version. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>3000</MessageID> <Description>Client Configuration Manager failed to read the site control file for site "%1."%12</Description> </Message> <Message> <MessageID>3001</MessageID> <Description>Client Configuration Manager failed to read the site identification values from the registry in \HKLM\Software\Microsoft\SMS\Identification key.%12</Description> </Message> <Message> <MessageID>3002</MessageID> <Description>Client Configuration Manager failed to connect to the registry of site server %1.%12</Description> </Message> <Message> <MessageID>3003</MessageID> <Description>Client Configuration Manager failed to read the account information for site %1.%12</Description> </Message> <Message> <MessageID>3004</MessageID> <Description>Client Configuration Manager failed to read the component item "%1" from the site control file on the server "%2".%12</Description> </Message> <Message> <MessageID>3005</MessageID> <Description>Client Configuration Manager failed to create a thread.%12</Description> </Message> <Message> <MessageID>3006</MessageID> <Description>Client Configuration Manager failed to establish inbox "%1" on the site server.%12</Description> </Message> <Message> <MessageID>3008</MessageID> <Description>Client Configuration Manager failed to create an inbox rule to copy files "%1" from inbox "%2" to inbox "%3."%12</Description> </Message> <Message> <MessageID>3009</MessageID> <Description>Client Configuration Manager reports that queue "%1" contains %2 Client Configuration Requests (CCRs), which exceeds the queue's threshold.%12</Description> </Message> <Message> <MessageID>3010</MessageID> <Description>In the past %3 hours, Client Configuration Manager has made %1 unsuccessful attempts to install the ConfigMgr client "%2". CCM will continue to attempt to install this client.%12</Description> </Message> <Message> <MessageID>3011</MessageID> <Description>Client Configuration Manager failed to complete the ConfigMgr installation on client "%1". In the past %3 hours, CCM has made %2 unsuccessful attempts.%12</Description> </Message> <Message> <MessageID>3012</MessageID> <Description>Client Configuration Manager failed to complete its periodic account maintenance cycle.%12</Description> </Message> <Message> <MessageID>3013</MessageID> <Description>The Client Push Installation account list has been reset to a single account.%12</Description> </Message> <Message> <MessageID>3014</MessageID> <Description>Client Configuration Manager cannot connect to the machine "%1".%12</Description> </Message> <Message> <MessageID>3015</MessageID> <Description>Client Configuration Manager cannot find machine "%1" on the network.%12</Description> </Message> <Message> <MessageID>3016</MessageID> <Description>Client Configuration Manager cannot install a client to machine "%1", because it is not a supported platform for this action. Refer to the ConfigMgr documentation for the list of supported platforms.</Description> </Message> <Message> <MessageID>3017</MessageID> <Description>Client Configuration Manager cannot install a client to machine "%1", because it is a domain controler. CCM is currently configured to not install to domain controllers.</Description> </Message> <Message> <MessageID>3019</MessageID> <Description>Client Configuration Manager cannot install the client to machine "%1". This platform is not supported. Refer to the ConfigMgr documentation for the list of supported platforms.</Description> </Message> <Message> <MessageID>3200</MessageID> <Description>Inventory Processor failed to process MIF file %1.%12</Description> </Message> <Message> <MessageID>3201</MessageID> <Description>Inventory Processor failed to process inventory RAW file %1.%12</Description> </Message> <Message> <MessageID>3300</MessageID> <Description>Site "%1" (%2) is trying to report to a site that already reports to site "%1". This configuration is illegal because it creates a "loop" in the site hierarchy.</Description> </Message> <Message> <MessageID>3301</MessageID> <Description>Site "%1" (%2) has the same site code as another site.</Description> </Message> <Message> <MessageID>3302</MessageID> <Description>The parent site for this site cannot be changed from site "%1" (%2).</Description> </Message> <Message> <MessageID>3303</MessageID> <Description>Hierarchy Manager cannot connect to the site database.%12</Description> </Message> <Message> <MessageID>3304</MessageID> <Description>Hierarchy Manager cannot save site information to the site database for site "%1". %12</Description> </Message> <Message> <MessageID>3305</MessageID> <Description>Hierarchy Manager detected that site code "%1" is already in use by existing site "%2".%12</Description> </Message> <Message> <MessageID>3306</MessageID> <Description>Hierarchy Manager successfully processed "%1", which represented the site control file for site "%2" (%3). If this site is a primary site, Hierarchy Manager stored this site control file in the site database. If this site reports to a parent site, Hierarchy Manager instructed Replication Manager to replicate this file to the parent site at high priority.</Description> </Message> <Message> <MessageID>3307</MessageID> <Description>Hierarchy Manager detected that a change was requested by this site to the configuration of site "%1". Hierarchy Manager created a delta site control file for this request. If this site is site "%1", Hierarchy Manager submitted this file to Site Control Manager at this site. If site "%1" is a child site, Hierarchy Manager instructed Replication Manager to deliver the file to Site Control Manager at site "%1" at high priority.</Description> </Message> <Message> <MessageID>3308</MessageID> <Description>Hierarchy Manager cannot reinstall the Site Component Manager.</Description> </Message> <Message> <MessageID>3309</MessageID> <Description>Hierarchy Manager reinstalled Site Component Manager. Site Component Manager will now reinstall all of the other server components at this site.</Description> </Message> <Message> <MessageID>3310</MessageID> <Description>Hierarchy Manager has initiated remote installation of secondary site "%1". To track the progress of this operation, you should also monitor the messages reported by the Sender components.</Description> </Message> <Message> <MessageID>3311</MessageID> <Description>Hierarchy Manager has initiated remote upgrade of secondary site "%1". To track the progress of this operation, you should also monitor the messages reported by the Sender components.</Description> </Message> <Message> <MessageID>3312</MessageID> <Description>Hierarchy Manager has initiated remote deinstallation of secondary site "%1". To track the progress of this operation, you should also monitor the messages reported by the Sender components.</Description> </Message> <Message> <MessageID>3313</MessageID> <Description>Hierarchy Manager failed to execute site maintenance task "%1".%12</Description> </Message> <Message> <MessageID>3317</MessageID> <Description>Hierarchy Manager cannot add machine account %1 for secondary site %2 to the address group %3, this must be done manually.</Description> </Message> <Message> <MessageID>3318</MessageID> <Description>Hierarchy Manager cannot add address account %1 for secondary site %2 to the address group %3, this must be done manually.</Description> </Message> <Message> <MessageID>3320</MessageID> <Description>The secondary site upgrade failed because either the prerequisite checker has not been run without errors on secondary site %1 in the past seven days or it has not been run at all. Follow the corrective steps that are required for the failed prerequisite rules to pass. You must restart the secondary site upgrade after the prerequisite checker has been re-run and passed without errors.</Description> </Message> <Message> <MessageID>3321</MessageID> <Description>Hierarchy Manager detected that this site's client computer communication method is set to allow HTTPS only.</Description> </Message> <Message> <MessageID>3322</MessageID> <Description>Hierarchy Manager cannot remove the computer account of site system %1 from database role %2. This needs to be done manually.</Description> </Message> <Message> <MessageID>3323</MessageID> <Description>Hierarchy Manager detected that this site's client computer communication method is set to allow either HTTPS or HTTP.</Description> </Message> <Message> <MessageID>3324</MessageID> <Description>Hierarchy Manager detected that the public key of this site in the site control file is no longer valid and has updated it with the new public key. %12 The password of all the accounts need to be reset through the Configuration Manager Console. The bootmedia CDs created on the site may also need to be recreated. Please refer to your Configuration Manager documentation or the Microsoft Knowledge Base for further information.</Description> </Message> <Message> <MessageID>3330</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 machine certificate is still valid.</Description> </Message> <Message> <MessageID>3331</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 machine certificate has missed.</Description> </Message> <Message> <MessageID>3332</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 machine certificate has missed. It is failed to remediate with Error %2.</Description> </Message> <Message> <MessageID>3333</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 machine certificate has been remediated.</Description> </Message> <Message> <MessageID>3334</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate is still valid.</Description> </Message> <Message> <MessageID>3335</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has missed.</Description> </Message> <Message> <MessageID>3336</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has been expired.</Description> </Message> <Message> <MessageID>3337</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has missed or is expired, and failed to remediate with Error %2.</Description> </Message> <Message> <MessageID>3338</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has been remediated.</Description> </Message> <Message> <MessageID>3339</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Port %2 still valid.</Description> </Message> <Message> <MessageID>3340</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Port %2 has been changed to %3.</Description> </Message> <Message> <MessageID>3341</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Port %2 has been changed to %3, and failed to remediate with Error %4.</Description> </Message> <Message> <MessageID>3342</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Port %2 has been remediated from %3.</Description> </Message> <Message> <MessageID>3343</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 still valid.</Description> </Message> <Message> <MessageID>3344</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 has been changed to %3.</Description> </Message> <Message> <MessageID>3345</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 has been changed to %3, and failed to remediate with Error %4.</Description> </Message> <Message> <MessageID>3346</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 has been remediated from %3.</Description> </Message> <Message> <MessageID>3347</MessageID> <Description>Hierarchy Monitoring detected that all ConfigMgr SQL Server Roles are still valid.</Description> </Message> <Message> <MessageID>3348</MessageID> <Description>Hierarchy Monitoring detected that the following ConfigMgr SQL Server Roles [%1] are missing.</Description> </Message> <Message> <MessageID>3349</MessageID> <Description>Hierarchy Monitoring detected that the following ConfigMgr SQL Server Roles [%1] are missing.</Description> </Message> <Message> <MessageID>3350</MessageID> <Description>The following missing ConfigMgr SQL Server Roles [%1] have been added back.</Description> </Message> <Message> <MessageID>3351</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr SQL Server ports %1 are still active on Firewall exception.</Description> </Message> <Message> <MessageID>3352</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr SQL Server ports %1 are not active on Firewall exception.</Description> </Message> <Message> <MessageID>3353</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr SQL Server %2 ports %1 are not active on Firewall exception.</Description> </Message> <Message> <MessageID>3354</MessageID> <Description>Hierarchy Monitoring has added the ConfigMgr SQL Server ports %1 into the Firewall exception.</Description> </Message> <Message> <MessageID>3355</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 still valid.</Description> </Message> <Message> <MessageID>3356</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 is missing.</Description> </Message> <Message> <MessageID>3357</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 is missing.</Description> </Message> <Message> <MessageID>3358</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 is valid after remediation.</Description> </Message> <Message> <MessageID>3359</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Database file location is still valid.</Description> </Message> <Message> <MessageID>3360</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Database file location is invalid.</Description> </Message> <Message> <MessageID>3361</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Database file location is invalid.</Description> </Message> <Message> <MessageID>3362</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Database File Disk still has enough free space.</Description> </Message> <Message> <MessageID>3363</MessageID> <Description>Hierarchy Monitoring detected that the Database File Disk (%1) is short of space.</Description> </Message> <Message> <MessageID>3364</MessageID> <Description>Hierarchy Monitoring detected that the Database File Disk (%1) is running out of space.</Description> </Message> <Message> <MessageID>3365</MessageID> <Description>Hierarchy Monitoring detected that the Database File Disk still has enough free space. But there is no alert configured. Please use Site System properties to configure alerts.</Description> </Message> <Message> <MessageID>3366</MessageID> <Description>Hierarchy Manager cannot search the Active Directory.%12</Description> </Message> <Message> <MessageID>3400</MessageID> <Description>Scheduler does not have an address defined at site "%2" for site "%1". Files cannot be sent from site "%2" to site "%1" until an address is defined.%12</Description> </Message> <Message> <MessageID>3401</MessageID> <Description>Scheduler has data to send to site "%1", and addresses defined at site "%2" for site "%1", but none of them are available for sending at this time.</Description> </Message> <Message> <MessageID>3402</MessageID> <Description>Scheduler at site %1 has received package %2 version %3 and has instructed the Sender to send the package to the following sites: %4.%12</Description> </Message> <Message> <MessageID>3500</MessageID> <Description>The sender cannot connect to remote site "%1" over the LAN.%12</Description> </Message> <Message> <MessageID>3501</MessageID> <Description>The sender cannot connect to site "%1" over RAS.%12</Description> </Message> <Message> <MessageID>3502</MessageID> <Description>The address to site "%1" is invalid.%12</Description> </Message> <Message> <MessageID>3503</MessageID> <Description>The address to site "%1" is invalid.%12</Description> </Message> <Message> <MessageID>3504</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2".%12</Description> </Message> <Message> <MessageID>3505</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because the sender cannot create the Bootstrap initialization file "%3".%12</Description> </Message> <Message> <MessageID>3506</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because it cannot retrieve the encryption public key.%12 Please refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>3507</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because it cannot query the status of the Configuration Manager Bootstrap service on server "%2".%12</Description> </Message> <Message> <MessageID>3508</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because it cannot stop the Configuration Manager Bootstrap service on server "%2".%12</Description> </Message> <Message> <MessageID>3509</MessageID> <Description>The sender cannot install, upgrade, or deinstall secondary site "%1" on server "%2".%12</Description> </Message> <Message> <MessageID>3510</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2".%12</Description> </Message> <Message> <MessageID>3511</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because the sender could not copy the Configuration Manager Bootstrap service file from "%3" to "%4".%12</Description> </Message> <Message> <MessageID>3512</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because the sender failed to install the Configuration Manager Bootstrap service.%12</Description> </Message> <Message> <MessageID>3513</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because the sender cannot start the Configuration Manager Bootstrap service.%12</Description> </Message> <Message> <MessageID>3514</MessageID> <Description>The sender has installed the Configuration Manager Bootstrap service on server "%1". The Configuration Manager Bootstrap service will finish the installation of secondary site "%2" by running Configuration Manager Setup with a script that specifies the installation parameters for site "%2". You can track the progress of Configuration Manager Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of Configuration Manager Setup by monitoring "smssetup.log" on server "%1".</Description> </Message> <Message> <MessageID>3515</MessageID> <Description>The sender has installed the Configuration Manager Bootstrap service on server "%1". The Configuration Manager Bootstrap service will finish the upgrade of secondary site "%2" by running Configuration Manager Setup with a script that specifies the upgrade parameters for site "%2". You can track the progress of Configuration Manager Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of Configuration Manager Setup by monitoring "smssetup.log" on server "%1".</Description> </Message> <Message> <MessageID>3516</MessageID> <Description>The sender has installed the Configuration Manager Bootstrap service on server "%1". The Configuration Manager Bootstrap service will finish the deinstallation of secondary site "%2" by running Configuration Manager Setup with a script that specifies the deinstallation parameters for site "%2". You can track the progress of Configuration Manager Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of Configuration Manager Setup by monitoring "smssetup.log" on server "%1".</Description> </Message> <Message> <MessageID>3517</MessageID> <Description>Sender failed to send files to destination site %1. Make sure the address account has full access to directory "%2" on the destination site server and the destination site server has sufficient free disk space on the ConfigMgr installation drive.%12</Description> </Message> <Message> <MessageID>3518</MessageID> <Description>%1 failed to start.%12</Description> </Message> <Message> <MessageID>3522</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because some fatal error occured in Configuration Manager Bootstrap service running on secondary site server. Please review smssetup.log on the secondary site server for troubleshooting the problem. The smssetup.log is located at the root of the system drive. Once the problem is resolved, delete the secondary site object in the Configuration Manager Administrator's Console and rerun the secondary site creation wizard.%12</Description> </Message> <Message> <MessageID>3523</MessageID> <Description>The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", started Configuration Manager Setup successfully.%12</Description> </Message> <Message> <MessageID>3524</MessageID> <Description>The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", failed to start Configuration Manager Setup. Please check the logs on secondary site.%12</Description> </Message> <Message> <MessageID>3525</MessageID> <Description>The Configuration Manager Setup running on secondary site "%1" on server "%2" has completed.%12</Description> </Message> <Message> <MessageID>3526</MessageID> <Description>The Configuration Manager Setup running on secondary site "%1" on server "%2", failed. Please check the logs on secondary site.%12</Description> </Message> <Message> <MessageID>3527</MessageID> <Description>The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", started package decompression.%12</Description> </Message> <Message> <MessageID>3528</MessageID> <Description>The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", completed successfully.%12</Description> </Message> <Message> <MessageID>3529</MessageID> <Description>The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", failed to connect to parent site.%12</Description> </Message> <Message> <MessageID>3530</MessageID> <Description>The sender cannot connect to remote site "%1" over the LAN.%12</Description> </Message> <Message> <MessageID>3531</MessageID> <Description>Sender is currently sending software distribution package %1 version %2 to site %3, %4 percent of the sending has already completed.</Description> </Message> <Message> <MessageID>3532</MessageID> <Description>Sender encountered errors while sending software distribution package %1 version %2 to site %3, %4 percent of the sending has already completed.</Description> </Message> <Message> <MessageID>3533</MessageID> <Description>Sender has successfully sent software distribution package %1 version %2 to site %3.</Description> </Message> <Message> <MessageID>3600</MessageID> <Description>Inbox Manager cannot copy files from "%1" to "%2".%12</Description> </Message> <Message> <MessageID>3601</MessageID> <Description>Inbox Manager cannot create directory "%1" with the desired security rights on server "%2".%12</Description> </Message> <Message> <MessageID>3603</MessageID> <Description>Inbox Manager cannot create directory "%1" with the desired security rights on site system "%2". (The site system is shown here as a network abstraction layer (NAL) path.)%12</Description> </Message> <Message> <MessageID>3604</MessageID> <Description>Inbox Manager Assistant running on the client access point "%1" cannot connect to site server "%2".%12</Description> </Message> <Message> <MessageID>3605</MessageID> <Description>Inbox Manager cannot create the client access point on site system "%1".%12</Description> </Message> <Message> <MessageID>3606</MessageID> <Description>SMS Inbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12</Description> </Message> <Message> <MessageID>3607</MessageID> <Description>SMS Outbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12</Description> </Message> <Message> <MessageID>3700</MessageID> <Description>Software Inventory Processor successfully processed %1 software inventory files.%12</Description> </Message> <Message> <MessageID>3701</MessageID> <Description>Software Inventory Processor failed to process software inventory file "%1," and has moved it to "%2."%12</Description> </Message> <Message> <MessageID>3702</MessageID> <Description>Software Inventory Processor is terminating its processing cycle due to a SQL Server problem.%12</Description> </Message> <Message> <MessageID>3703</MessageID> <Description>Software Inventory Processor requested a resynchronization for machine "%1" because an attempt was made to update inventory information in the site database that does not already exist.%12</Description> </Message> <Message> <MessageID>3704</MessageID> <Description>Software Inventory Processor has removed the oldest revision of collected file "%1" for resource "%2". The maximum revision number for a collected file has been reached, so the oldest copy has been replaced by the most recent copy.%12</Description> </Message> <Message> <MessageID>3705</MessageID> <Description>Software Inventory Processor is updating database statistics.%12 By default, statistics are updated to optimize SQL Server database performance after every 500 software inventory files have been processed. You can edit this value in the Configuration Manager Console, under Component Configuration, Data Processing and Storage Properties.</Description> </Message> <Message> <MessageID>3706</MessageID> <Description>Software Inventory Processor was unable to store collected file "%1" for resource "%2".%12</Description> </Message> <Message> <MessageID>3707</MessageID> <Description>Software Inventory Processor failed to process software inventory file "%1" because the file does not have a corresponding discovery record. Software Inventory Processor has moved this file to the Orphans directory as file "%2" and will retry processing it later.%12 When Software Inventory Processor receives a software inventory file, it acquires the unique numeric ID for the file it is processing from the discovery data in the site database. If this cannot be found, a discovery data record (DDR) is generated, and the software inventory file is temporarily moved to the Orphans directory, where Software Inventory Processor retries the file every 10 minutes.</Description> </Message> <Message> <MessageID>3708</MessageID> <Description>Software Inventory Processor failed to process the file %1 because it is larger than the defined maximum allowable size of %2.%12</Description> </Message> <Message> <MessageID>3709</MessageID> <Description>Software Inventory Processor requested a resynchronization for machine "%1" because a software inventory file was sent without a public key information.%12</Description> </Message> <Message> <MessageID>3800</MessageID> <Description>Received more than 10 NULL status message pointers from the Offer Status Queue.%12</Description> </Message> <Message> <MessageID>3801</MessageID> <Description>Unable to create a file to store the replication data at %1.%12</Description> </Message> <Message> <MessageID>3802</MessageID> <Description>Unable to open the incoming %1 replication file.%12</Description> </Message> <Message> <MessageID>3803</MessageID> <Description>While initializing, no records of the proper type were found in the data store.%12</Description> </Message> <Message> <MessageID>3804</MessageID> <Description>Received a status message from site %1, but this is site %2. Ignoring message.%12</Description> </Message> <Message> <MessageID>3805</MessageID> <Description>The Offer summary %1,%2 has not been heard from for %3 days. This summary has been marked for deletion.%12</Description> </Message> <Message> <MessageID>3806</MessageID> <Description>Failed to send the replication file. Will try again later.%12</Description> </Message> <Message> <MessageID>3807</MessageID> <Description>Interval %1 not found in OfferSummaryDetail record.%12</Description> </Message> <Message> <MessageID>3808</MessageID> <Description>No data store was found at %1 to initialize from.%12</Description> </Message> <Message> <MessageID>3809</MessageID> <Description>The file %1 is not the correct type of replication file for this summarizer, deleting the file.%12</Description> </Message> <Message> <MessageID>3810</MessageID> <Description>Unable to create a file to store the summary data. Will try again in %1 seconds.%12</Description> </Message> <Message> <MessageID>3811</MessageID> <Description>Unable to send changed records to the data store. Will try again in %1 seconds.%12</Description> </Message> <Message> <MessageID>3812</MessageID> <Description>Offer Status Summarizer cannot process a status message because it has an invalid message ID %1. The message ID must be within the range 10000 to 10099. As a result, the deployment Status summary data in the Configuration Manager Console may be inaccurate. The message was reported by component "%2" on computer "%3" at site %4 on %5. Please refer to the Microsoft Knowledge Base for more information.</Description> </Message> <Message> <MessageID>3813</MessageID> <Description>Offer Status Summarizer cannot process a status message because it does not contain a deployment ID. As a result, the deployment Status summary data in the Configuration Manager Console may be inaccurate. The message (ID %1) was reported by component "%2" on computer "%3" at site %4 on %5. Please refer to the Microsoft Knowledge Base for more information.</Description> </Message> <Message> <MessageID>3814</MessageID> <Description>Offer Status Summarizer cannot process a status message because it contains the invalid deployment ID "%6". As a result, the deployment Status summary data in the Configuration Manager Console may be inaccurate. The message (ID %1) was reported by component "%2" on computer "%3" at site %4 on %5. Please refer to the Microsoft Knowledge Base for more information.</Description> </Message> <Message> <MessageID>3900</MessageID> <Description>SMS Offer Manager successfully processed new deployment %1.%12</Description> </Message> <Message> <MessageID>3901</MessageID> <Description>SMS Offer Manager successfully removed deployment %1.%12</Description> </Message> <Message> <MessageID>4000</MessageID> <Description>Replication Manager successfully instructed Scheduler to send files to site "%1".</Description> </Message> <Message> <MessageID>4001</MessageID> <Description>Replication Manager received files from the "%1" component at a child site, but that component is not enabled at the current site. Replication Manager will throw away these files.</Description> </Message> <Message> <MessageID>4200</MessageID> <Description>Server Discovery Agent failed to read the necessary registry information.%12</Description> </Message> <Message> <MessageID>4201</MessageID> <Description>Server Discovery Agent failed to read the location of the outbox.%12</Description> </Message> <Message> <MessageID>4202</MessageID> <Description>Server Discovery Agent read the system roles and found %1 server role entries in the site control file. Windows NT Server Discovery Agent identified %2 unique servers in the server roles and generated %3 discovery data records (DDRs) and %4 errors while attempting to create DDRs.%12</Description> </Message> <Message> <MessageID>4400</MessageID> <Description>Despooler successfully stored the compressed binaries for package "%1" at "%2".%12</Description> </Message> <Message> <MessageID>4401</MessageID> <Description>Despooler failed to decompress package "%1" from "%2".%12</Description> </Message> <Message> <MessageID>4402</MessageID> <Description>Despooler failed to merge delta to the compressed package "%1".%12</Description> </Message> <Message> <MessageID>4403</MessageID> <Description>Obsolete.</Description> </Message> <Message> <MessageID>4404</MessageID> <Description>Despooler received an instruction and package file from site %1 that contains that site's public key, however the despooler cannot find a valid public key to verify the signature of the package. Because this site does not allow unsigned key exchange between sites, the instruction cannot be processed and will be retried.</Description> </Message> <Message> <MessageID>4405</MessageID> <Description>Despooler received an instruction and package file from site %1 that contains either software distribution data or inter-site replication data, however the despooler does not have the public key to verify the signature of the package. The instruction cannot be processed and will be retried.</Description> </Message> <Message> <MessageID>4406</MessageID> <Description>Despooler received an instruction and package file from site %1 that contains either software distribution data or inter-site replication data, however either the signature on the package or the hash algorithm ID used for the signature is not valid, the despooler will delete the instruction and the package file.</Description> </Message> <Message> <MessageID>4407</MessageID> <Description>Despooler successfully received the compressed image for package %1 version %2.%12</Description> </Message> <Message> <MessageID>4500</MessageID> <Description>Sent a replication file to %1.%12</Description> </Message> <Message> <MessageID>4501</MessageID> <Description>A replication file has been created, the replication file is %1.%12</Description> </Message> <Message> <MessageID>4502</MessageID> <Description>Processing the incoming replication file %1.%12</Description> </Message> <Message> <MessageID>4503</MessageID> <Description>The file %1 is not a replication file for this summarizer, deleting the file.%12</Description> </Message> <Message> <MessageID>4504</MessageID> <Description>Unable to decrypt the SQL Server login user name and/or password.%12</Description> </Message> <Message> <MessageID>4505</MessageID> <Description>Unable to find this summarizer's component section in the site control file.%12</Description> </Message> <Message> <MessageID>4506</MessageID> <Description>Unable to open the site control file.%12</Description> </Message> <Message> <MessageID>4507</MessageID> <Description>Unable to read the site configuration.%12</Description> </Message> <Message> <MessageID>4508</MessageID> <Description>An error occurred while setting or resetting a change notification for the site control file.%12</Description> </Message> <Message> <MessageID>4509</MessageID> <Description>An error occurred while setting or resetting a change notification for the summarizer's inbox.%12</Description> </Message> <Message> <MessageID>4510</MessageID> <Description>Unable to create the status message queue.%12</Description> </Message> <Message> <MessageID>4511</MessageID> <Description>Failed to send a replication file to site %1.%12</Description> </Message> <Message> <MessageID>4512</MessageID> <Description>The data store %1 was not found.%12</Description> </Message> <Message> <MessageID>4513</MessageID> <Description>.Could not read all of the records in the file %1. The error code is %2.%12</Description> </Message> <Message> <MessageID>4514</MessageID> <Description>Unable to write changed records to the data store.%12</Description> </Message> <Message> <MessageID>4515</MessageID> <Description>Unable to initialize the summarizer. The returned error code is %1.%12</Description> </Message> <Message> <MessageID>4516</MessageID> <Description>The site properties are not set in the registry.%12</Description> </Message> <Message> <MessageID>4517</MessageID> <Description>The error %1 has occurred while initializing the status message queue.%12</Description> </Message> <Message> <MessageID>4518</MessageID> <Description>The summarizer cannot continue and is stopping. The exit code is %1.%12</Description> </Message> <Message> <MessageID>4519</MessageID> <Description>The reset request list %1 is too old. It was sent on %2 from %3, by user %4, on system %5, at site %6.%12</Description> </Message> <Message> <MessageID>4520</MessageID> <Description>Reset specific tally intervals as requested from %1, by user %2, on system %3, at site %4.%12</Description> </Message> <Message> <MessageID>4600</MessageID> <Description>Component Status Summarizer detected that the list of Component Status Display Intervals specified in the site control file has changed.%12 Component Status Summarizer will reconfigure itself to use the new set of Display Intervals.</Description> </Message> <Message> <MessageID>4601</MessageID> <Description>Component Status Summarizer detected that entry "%1" of the Component Thresholds property list in the site control file is corrupt.%12</Description> </Message> <Message> <MessageID>4602</MessageID> <Description>Component Status Summarizer received a status message from component "%1", running on computer "%2", but there is no record of this component in the site control file.%12</Description> </Message> <Message> <MessageID>4603</MessageID> <Description>Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Informational status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4604</MessageID> <Description>Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Warning status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4605</MessageID> <Description>Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4606</MessageID> <Description>Component Status Summarizer detected that component "%1" running on computer "%2" has reported %3 or more Informational status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4607</MessageID> <Description>Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Warning status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4608</MessageID> <Description>Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4609</MessageID> <Description>Component Status Summarizer set the status of component "%1", running on computer "%2", to Critical.%12</Description> </Message> <Message> <MessageID>4610</MessageID> <Description>Component Status Summarizer set the status of component "%1" running on computer "%2" to Warning.%12</Description> </Message> <Message> <MessageID>4611</MessageID> <Description>Component Status Summarizer reset the status of component "%1", running on computer "%2", to OK.%12 Component Status Summarizer will automatically reset a component's status to OK every time the Component Status Threshold Period elapses and a new Threshold Period begins. For example, if the Threshold Period is "Since 12:00:00 AM", Component Status Summarizer will reset the component's status to OK every 24 hours at midnight. At this time, the counts of status messages reported by the component for the Threshold Period will be reset to zero.</Description> </Message> <Message> <MessageID>4612</MessageID> <Description>Component Status Summarizer has not received a status message from component "%1", running on computer "%2", in %3 hours.%12</Description> </Message> <Message> <MessageID>4613</MessageID> <Description>Component Status Summarizer received a status message that was reported by component "%1", running on computer "%2" at site "%3", which is not the site where Component Status Summarizer is running.%12</Description> </Message> <Message> <MessageID>4614</MessageID> <Description>Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (%9 is a 24-hour interval).%12 The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".</Description> </Message> <Message> <MessageID>4615</MessageID> <Description>Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (1 is Sunday, 2 is Monday, and so on).%12 The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".</Description> </Message> <Message> <MessageID>4616</MessageID> <Description>Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since Day %9 of the Month" Display Interval.%12 The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".</Description> </Message> <Message> <MessageID>4617</MessageID> <Description>Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since Site Installation" Display Interval.%12 The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".</Description> </Message> <Message> <MessageID>4618</MessageID> <Description>Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "%9" Display Interval.%12 The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".</Description> </Message> <Message> <MessageID>4619</MessageID> <Description>Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (%9 is a 24-hour interval). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4620</MessageID> <Description>Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (1 is Sunday, 2 is Monday, and so on). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4621</MessageID> <Description>Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since Day %9 of the Month" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4622</MessageID> <Description>Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since Site Installation" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4623</MessageID> <Description>Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "%9" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". "%9" is an encrypted version of the custom Display Interval you configured the Component Status Summarizer to use. Component Status Summarizer cannot display an unencrypted version of "%9" in a status message.%12</Description> </Message> <Message> <MessageID>4624</MessageID> <Description>Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (%9 is a 24-hour interval). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4625</MessageID> <Description>Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (1 is Sunday, 2 is Monday, and so on). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4626</MessageID> <Description>Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since Day %9 of the Month" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4627</MessageID> <Description>Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since Site Installation" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4628</MessageID> <Description>Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "%9" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". "%9" is an encrypted version of the custom Display Interval that you configured the Component Status Summarizer to use. Component Status Summarizer cannot display an unencrypted version of "%9" in a status message.%12</Description> </Message> <Message> <MessageID>4629</MessageID> <Description>Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Online.</Description> </Message> <Message> <MessageID>4630</MessageID> <Description>Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Failed.%12</Description> </Message> <Message> <MessageID>4631</MessageID> <Description>Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Degraded.%12</Description> </Message> <Message> <MessageID>4632</MessageID> <Description>Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Offline.%12</Description> </Message> <Message> <MessageID>4633</MessageID> <Description>Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Unknown.%12</Description> </Message> <Message> <MessageID>4700</MessageID> <Description>Site System Status Summarizer could not access storage object "%1" on site system "%2".%12</Description> </Message> <Message> <MessageID>4701</MessageID> <Description>Site System Status Summarizer still cannot access storage object "%1" on site system "%2".%12</Description> </Message> <Message> <MessageID>4702</MessageID> <Description>Site System Status Summarizer successfully accessed storage object "%1" on site system "%2".%12</Description> </Message> <Message> <MessageID>4703</MessageID> <Description>Site System Status Summarizer could not access the "%1" database on site database Server "%2".</Description> </Message> <Message> <MessageID>4704</MessageID> <Description>Site System Status Summarizer still cannot access the "%1" database on site database Server "%2".%12</Description> </Message> <Message> <MessageID>4705</MessageID> <Description>Site System Status Summarizer successfully accessed the "%1" database on SQL Server "%2".%12</Description> </Message> <Message> <MessageID>4706</MessageID> <Description>Site System Status Summarizer could not access the transaction log for the "%1" database on SQL Server "%2".%12</Description> </Message> <Message> <MessageID>4707</MessageID> <Description>Site System Status Summarizer still cannot access the transaction log for the "%1" database on SQL Server "%2".%12</Description> </Message> <Message> <MessageID>4708</MessageID> <Description>Site System Status Summarizer successfully accessed the transaction log for the "%1" database on SQL Server "%2". The transaction log had been inaccessible since %3. Providing that the transaction log has sufficient free space, Site System Status Summarizer will now restore the status of the transaction log to OK in the Site System Status summary in the Configuration Manager Console.</Description> </Message> <Message> <MessageID>4709</MessageID> <Description>Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, which is above the Free Space Thresholds for this storage object. Site System Status Summarizer will now set the status of the storage object to OK in the Site System Status summary in the Configuration Manager Console.</Description> </Message> <Message> <MessageID>4710</MessageID> <Description>Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, which is less than or equal to the Warning Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4711</MessageID> <Description>Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, which is less than or equal to the Critical Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4712</MessageID> <Description>Site System Status Summarizer detected that the "%1" database on site database server "%2" has %3 KB of free space, which is above the Free Space Thresholds for the database. Site System Status Summarizer will now set the status of the database to OK in the Site System Status summary in the Configuration Manager Console.</Description> </Message> <Message> <MessageID>4713</MessageID> <Description>Site System Status Summarizer detected that the "%1" database on site database server "%2" has %3 KB of free space, which is less than or equal to the Warning Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4714</MessageID> <Description>Site System Status Summarizer detected that the database "%1" on site database server "%2" has %3 KB of free space, which is less than or equal to the Critical Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4715</MessageID> <Description>Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 KB of free space, which is above the Free Space Thresholds for the transaction log. Site System Status Summarizer will now set the status of the transaction log to OK in the Site System Status summary in the Configuration Manager Console.</Description> </Message> <Message> <MessageID>4716</MessageID> <Description>Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 KB of free space, which is less than or equal to the Warning Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4717</MessageID> <Description>Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 KB of free space, which is less than or equal to the Critical Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4718</MessageID> <Description>Site System Status Summarizer has not been able to access the storage object "%1" on Site Object "%2" for %3 hours. Site System Status Summarizer will now assume that you no longer intend to use the storage object and will no longer monitor the storage object.</Description> </Message> <Message> <MessageID>4719</MessageID> <Description>Site System Status Summarizer detected that the storage object "%1" on Branch Distribution Point site system "%2" has %3 KB of free storage space, which is less than or equal to the Critical Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4720</MessageID> <Description>Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Online.</Description> </Message> <Message> <MessageID>4721</MessageID> <Description>Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Failed.%12</Description> </Message> <Message> <MessageID>4722</MessageID> <Description>Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Degraded.%12</Description> </Message> <Message> <MessageID>4723</MessageID> <Description>Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Offline.%12</Description> </Message> <Message> <MessageID>4724</MessageID> <Description>Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Unknown.%12</Description> </Message> <Message> <MessageID>4900</MessageID> <Description>Site Component Manager is deinstalling all Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>4901</MessageID> <Description>Site Component Manager successfully deinstalled all Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>4902</MessageID> <Description>Site Component Manager failed to deinstall all Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>4903</MessageID> <Description>Site Component Manager failed to deinstall all Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>4904</MessageID> <Description>Site Component Manager successfully installed the performance counters for this component on this site system.</Description> </Message> <Message> <MessageID>4905</MessageID> <Description>Site Component Manager failed to install the performance counters for this component on this site system.</Description> </Message> <Message> <MessageID>4906</MessageID> <Description>Site Component Manager successfully removed the performance counters for this component from this site system.</Description> </Message> <Message> <MessageID>4907</MessageID> <Description>Site Component Manager failed to remove the performance counters for this component from this site system.</Description> </Message> <Message> <MessageID>4908</MessageID> <Description>Site Component Manager could not add machine account "%1" to the SQL Access Group "%2" on the SQL Server machine "%3".</Description> </Message> <Message> <MessageID>4909</MessageID> <Description>Configuration Manager could not locate the "System Management" container in Active Directory (%1). Nor could it create a default container. This will prevent Site Component Manager and Hierarchy Manager from updating or adding any objects to Active Directory.</Description> </Message> <Message> <MessageID>4910</MessageID> <Description>Configuration Manager created a default "System Management" container in Active Directory (%1). This will be used to publish all necessary Active Directory objects for this site.</Description> </Message> <Message> <MessageID>4911</MessageID> <Description>Configuration Manager successfully created the object "%1" in Active Directory (%2).</Description> </Message> <Message> <MessageID>4912</MessageID> <Description>Configuration Manager cannot update the already existing object "%1" in Active Directory (%2).</Description> </Message> <Message> <MessageID>4913</MessageID> <Description>Configuration Manager cannot create the object "%1" in Active Directory (%2).</Description> </Message> <Message> <MessageID>4914</MessageID> <Description>Configuration Manager successfully deleted the object "%1" from Active Directory (%2).</Description> </Message> <Message> <MessageID>4915</MessageID> <Description>Configuration Manager cannot delete the object "%1" in Active Directory (%2).</Description> </Message> <Message> <MessageID>4918</MessageID> <Description>Configuration Manager cannot update the dNSHostName property for the existing object "%1" in Active Directory (%2). This property is used to publish fully qualified host names in Active Directory.</Description> </Message> <Message> <MessageID>4919</MessageID> <Description>Site Component Manager successfully installed the COM access registry keys for this component on this site system.</Description> </Message> <Message> <MessageID>4920</MessageID> <Description>Site Component Manager failed to install the COM access registry keys for this component on this site system.</Description> </Message> <Message> <MessageID>4921</MessageID> <Description>Site Component Manager successfully removed the COM access registry keys for this component from this site system.</Description> </Message> <Message> <MessageID>4922</MessageID> <Description>Site Component Manager failed to remove the COM access registry for this component from this site system.</Description> </Message> <Message> <MessageID>4923</MessageID> <Description>SMS System Health Validator %1 encountered an error. ErrorCode = %2.%12</Description> </Message> <Message> <MessageID>4924</MessageID> <Description>Site Component Manager failed to add machine account %1 to the user group %2, this must be done manually.</Description> </Message> <Message> <MessageID>4950</MessageID> <Description>Site Component Manager failed to install this component, because it can't configure Microsoft Internet Information Services (IIS).</Description> </Message> <Message> <MessageID>4951</MessageID> <Description>Site Component Manager failed to install this component, because the Microsoft Installer File for this component (%1) could not install. Refer to the %2, the %3, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.</Description> </Message> <Message> <MessageID>4952</MessageID> <Description>Site Component Manager failed to install this component because at least one file necessary for installation is missing. Refer to the component's installation log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.</Description> </Message> <Message> <MessageID>4956</MessageID> <Description>Site Component Manager successfully installed this component, However a reboot is required to complete the installation.</Description> </Message> <Message> <MessageID>4957</MessageID> <Description>Site Component Manager failed to install this component, because it either can't find or configure Internet Information Services Background Intelligent Transfer Service (BITS) Server Extensions.</Description> </Message> <Message> <MessageID>4958</MessageID> <Description>Site Component Manager failed to install this component, because it couldn't determine the the name of the IIS anonymous user account.</Description> </Message> <Message> <MessageID>4959</MessageID> <Description>Site Component Manager successfully installed this component. However the SQL Server Principal Name (SPN) could not be validated in Active Directory.</Description> </Message> <Message> <MessageID>4960</MessageID> <Description>Site Component Manager failed to install this component, because the designated Web Site of Internet Information Services is not running or started.</Description> </Message> <Message> <MessageID>4961</MessageID> <Description>Site Component Manager failed to install this component. The Distributed Transaction Coordinater Service (DTC) is not running. This service is needed to complete the Management Point installation. Please start the service, and try again.</Description> </Message> <Message> <MessageID>4962</MessageID> <Description>Site Component Manager failed to install this component. The Task Scheduler Service is not running. This service is needed to complete the Management Point installation. Please start the service, and try again.</Description> </Message> <Message> <MessageID>4963</MessageID> <Description>MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.%12</Description> </Message> <Message> <MessageID>4964</MessageID> <Description>Site Component Manager failed to install this component, because Secure Sockets Layer (SSL) is not configured properly on the Internet Information Server.</Description> </Message> <Message> <MessageID>4965</MessageID> <Description>Site Component Manager failed to install this component, because it can't configure Microsoft Network Policy Server (NPS).</Description> </Message> <Message> <MessageID>4966</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2 service pack %3, which is not a supported operating system for System Health Validator point.</Description> </Message> <Message> <MessageID>4967</MessageID> <Description>Site Component Manager failed to install this component, because it can't configure Microsoft Windows Deployement Services (WDS).</Description> </Message> <Message> <MessageID>4968</MessageID> <Description>Site Component Manager failed to install this component, because it either can't find or configure WSUS.</Description> </Message> <Message> <MessageID>4969</MessageID> <Description>Site Component Manager failed to install WSUS role on server %1. Refer to the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.</Description> </Message> <Message> <MessageID>4970</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The WebDAV server extension is either not installed or not configured properly.</Description> </Message> <Message> <MessageID>4971</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The WCF is not activated.</Description> </Message> <Message> <MessageID>4972</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The IIS Windows Authentication component is not installed.</Description> </Message> <Message> <MessageID>4973</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The IIS ASP.NET component is not installed.</Description> </Message> <Message> <MessageID>4974</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The IIS ASP.NET is not registered correctly.</Description> </Message> <Message> <MessageID>4975</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The .NET Framework 3.5 is not installed.</Description> </Message> <Message> <MessageID>4976</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The .NET Framework 4.0 Full Profile is not installed.</Description> </Message> <Message> <MessageID>4977</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. SCEPInstall.exe returns error %3.%12</Description> </Message> <Message> <MessageID>5000</MessageID> <Description>Site Backup was unable to open control file "%1". Site backup did not occur.%12</Description> </Message> <Message> <MessageID>5001</MessageID> <Description>Site Backup stopped the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>5002</MessageID> <Description>Site Backup could not stop the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>5003</MessageID> <Description>Site Backup started the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>5004</MessageID> <Description>Site Backup could not start the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>5005</MessageID> <Description>Site Backup stopped the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>5006</MessageID> <Description>Site Backup could not stop the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>5007</MessageID> <Description>Site Backup started the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>5008</MessageID> <Description>Site Backup could not start the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>5009</MessageID> <Description>Site Backup successfully backed up file system object %1 to %2.%12</Description> </Message> <Message> <MessageID>5010</MessageID> <Description>Site Backup was unable to back up file system object %1 to %2.%12</Description> </Message> <Message> <MessageID>5011</MessageID> <Description>Site Backup successfully backed up registry key %1 to %2.%12</Description> </Message> <Message> <MessageID>5012</MessageID> <Description>Site Backup was unable to back up registry key %1 to %2.%12</Description> </Message> <Message> <MessageID>5013</MessageID> <Description>Site Backup successfully backed up %1 database %2 to %3.%12</Description> </Message> <Message> <MessageID>5014</MessageID> <Description>Site Backup was unable to back up %1 database %2 to %3.%12</Description> </Message> <Message> <MessageID>5015</MessageID> <Description>Site Backup successfully ran command line "%1", which completed with exit status %2.%12</Description> </Message> <Message> <MessageID>5016</MessageID> <Description>Site Backup was unable to run command line "%1" (error #%2).%12</Description> </Message> <Message> <MessageID>5017</MessageID> <Description>Site Backup reported that the backup control data ended unexpectedly at line %1. This problem might cause part of the site backup to be skipped.%12</Description> </Message> <Message> <MessageID>5018</MessageID> <Description>Site Backup is ignoring the invalid definition on line %1 of the backup control file. This problem may cause part of the site backup to be skipped.%12</Description> </Message> <Message> <MessageID>5019</MessageID> <Description>Site Backup is ignoring the invalid section starting on line %1 of the backup control file. This problem might cause part of the site backup to be skipped.%12</Description> </Message> <Message> <MessageID>5020</MessageID> <Description>Site Backup stopped the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>5021</MessageID> <Description>The %1 ConfigMgr client application on the local computer did not respond to Site Backup's stop request.%12</Description> </Message> <Message> <MessageID>5022</MessageID> <Description>Site Backup could not stop the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>5023</MessageID> <Description>Site Backup started the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>5024</MessageID> <Description>Site Backup could not start the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>5025</MessageID> <Description>Site Backup was run, but the %1 token had no value. Site backup did not occur.%12</Description> </Message> <Message> <MessageID>5026</MessageID> <Description>Site Backup was run, but the backup destination directory ( %1 ) is invalid. Site backup did not occur.%12</Description> </Message> <Message> <MessageID>5027</MessageID> <Description>Site Backup found syntax errors on the following lines:%1 in backup control file. Site backup did not occur.%12</Description> </Message> <Message> <MessageID>5028</MessageID> <Description>The following utility tools were not available to be run: %1 Their output is not provided so you might miss some configuration information.%12</Description> </Message> <Message> <MessageID>5029</MessageID> <Description>Unable to verify the installation of the service : %1 This service will not be stopped or restarted.%12</Description> </Message> <Message> <MessageID>5030</MessageID> <Description>Maximum sleep time is 15 minutes. Time given in Backup Control File exceeds this limit so it is being reset to this maximum limit.%12</Description> </Message> <Message> <MessageID>5031</MessageID> <Description>Token Symbol (%1) already defined. First value (%2) will be used.%12</Description> </Message> <Message> <MessageID>5032</MessageID> <Description>Site Backup was unable to back up registry key %1 to %2.%12</Description> </Message> <Message> <MessageID>5033</MessageID> <Description>Site Backup was unable to back up %1 database %2 to %3.%12</Description> </Message> <Message> <MessageID>5034</MessageID> <Description>Site Backup could not start the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>5035</MessageID> <Description>Site Backup completed successfully with zero errors but still there could be some warnings.%12</Description> </Message> <Message> <MessageID>5036</MessageID> <Description>Site Backup tried to stop the %1 service on site system %2. This service is already stopped.%12</Description> </Message> <Message> <MessageID>5037</MessageID> <Description>Site Backup tried to stop the %1 executable. This executable is already stopped.%12</Description> </Message> <Message> <MessageID>5038</MessageID> <Description>Site Backup service was stopped manually. Backup operation is not completed.%12</Description> </Message> <Message> <MessageID>5039</MessageID> <Description>%1 utility initiated by Site Backup did not complete in timely fashion. Terminating this utility. You may need to get its generated information manually.%12</Description> </Message> <Message> <MessageID>5040</MessageID> <Description>Site Backup successfully initiated command file "%1".%12</Description> </Message> <Message> <MessageID>5041</MessageID> <Description>Site Backup was unable to initiate command file "%1" .%12</Description> </Message> <Message> <MessageID>5042</MessageID> <Description>Site Backup did not find command file "%1" at its predefined location. Command file "%1" not launched.%12</Description> </Message> <Message> <MessageID>5043</MessageID> <Description>Site Backup was unable to back up file system object %1 to %2.%12</Description> </Message> <Message> <MessageID>5044</MessageID> <Description>Site Backup failed to initialize the VSS services. Aborting the backup operation. Please verify that the VSS services are up and running.%12</Description> </Message> <Message> <MessageID>5045</MessageID> <Description>Site Backup could not find the SMS Writer in the list of writers provided by the VSS. Aborting the backup operation. Please verify that the SMS Writer service is up and running.%12</Description> </Message> <Message> <MessageID>5046</MessageID> <Description>Site Backup failed while reading the VSS writers meta data. Aborting the backup operation.%12</Description> </Message> <Message> <MessageID>5047</MessageID> <Description>Site Backup failed while creating the snapshot using the VSS services. Aborting the backup operation.%12</Description> </Message> <Message> <MessageID>5048</MessageID> <Description>Site Backup failed while trying to copy the files to the destination. Backup operation is not completed.</Description> </Message> <Message> <MessageID>5049</MessageID> <Description>Site Backup could not connect to the registry on the SQL Server machine. Aborting the backup operation. Verify that the site server computer accounthas administrative rights on the SQL Server .%12</Description> </Message> <Message> <MessageID>5050</MessageID> <Description>Site Backup could not find the registry entries on the SQL Server machine. SMS SQL Backup service might not be running on the SQL Server machine.%12</Description> </Message> <Message> <MessageID>5051</MessageID> <Description>Site Backup found that the SMS SQL Backup service on the SQL machine is currently backing up the site database. It cannot start the new backup until the previous backup task is completed.%12</Description> </Message> <Message> <MessageID>5052</MessageID> <Description>SMS SQL Backup service on the SQL Server %1 failed to backup the site database %2. The error reported by the service is %3. Backup operation is not completed.%12</Description> </Message> <Message> <MessageID>5053</MessageID> <Description>SMS SQL Backup service on the SQL Server %1 did not start the database backup. SMS SQL Backup service might not be running on the SQL Server machine.%12</Description> </Message> <Message> <MessageID>5054</MessageID> <Description>SMS SQL Backup service on the SQL Server %1 successfully backed up the site database.%12</Description> </Message> <Message> <MessageID>5055</MessageID> <Description>Site Backup task is starting. This task will interact with the windows VSS services and the appropriate writers to create a volume snapshot and then back up the required files to the specified destination.%12</Description> </Message> <Message> <MessageID>5056</MessageID> <Description>Site Backup is starting to copy the files from the snapshot.%12</Description> </Message> <Message> <MessageID>5057</MessageID> <Description>Site Backup has successfully completed copying the files from the snapshot.%12</Description> </Message> <Message> <MessageID>5058</MessageID> <Description>SQL Server Backup path is empty or invalid. For remote SQL Server scenarios you should provide either a UNC path for entire backup or provide a local path on the site server for site backup and a local path on the SQL Server for the SQL backup. For the site database backup to succeed, you must update the SQL Server backup location in the Backup Configuration Manager maintenance task properties in the Configuration Manager Console.%12</Description> </Message> <Message> <MessageID>5059</MessageID> <Description>Site Backup failed to copy the files from the snapshot.%12</Description> </Message> <Message> <MessageID>5060</MessageID> <Description>Site Backup failed. The error reported by the service is %1. Backup operation is not completed. Please see smsbkup.log for more information.%12</Description> </Message> <Message> <MessageID>5100</MessageID> <Description>Policy Provider successfully created a policy and a policy assignment based on package %1 (%2), program %3 and deployment %4 (%5).%12</Description> </Message> <Message> <MessageID>5101</MessageID> <Description>Policy Provider successfully updated the policy and the policy assignment that were created from package %1 (%2), program %3 and deployment %4 (%5).%12</Description> </Message> <Message> <MessageID>5102</MessageID> <Description>Policy Provider successfully removed policy %1 and the related policy assignment.%12</Description> </Message> <Message> <MessageID>5103</MessageID> <Description>Policy Provider successfully created a settings policy and a settings policy assignment.%12</Description> </Message> <Message> <MessageID>5104</MessageID> <Description>Policy Provider successfully updated a settings policy and a settings policy assignment.%12</Description> </Message> <Message> <MessageID>5105</MessageID> <Description>Policy Provider successfully created a metering policy and a metering policy assignment.%12</Description> </Message> <Message> <MessageID>5106</MessageID> <Description>Policy Provider successfully updated a metering policy and a metering policy assignment.%12</Description> </Message> <Message> <MessageID>5107</MessageID> <Description>Policy Provider successfully created a policy and a policy assignment based on Distribution Point %1 (%2).%12</Description> </Message> <Message> <MessageID>5108</MessageID> <Description>Policy Provider successfully updated the policy and the policy assignment that were created from Distribution Point %1 (%2).%12</Description> </Message> <Message> <MessageID>5109</MessageID> <Description>Policy Provider successfully created a policy and a policy assignment based on package %1.%12</Description> </Message> <Message> <MessageID>5110</MessageID> <Description>Policy Provider successfully updated the policy and the policy assignment that were created from package %1.%12</Description> </Message> <Message> <MessageID>5111</MessageID> <Description>The site server signing certificate with hashcode '%1' is missing in the Certificate Store.%12</Description> </Message> <Message> <MessageID>5112</MessageID> <Description>The site server signing certificate will expire in %1 day(s). Please ensure that this certificate is renewed for the proper operation of the ConfigMgr site.%12</Description> </Message> <Message> <MessageID>5113</MessageID> <Description>The site server signing certificate has expired %1 day(s) ago. Please replace/renew the certificate. The Policies at this Site will be re-signed by the Site Server using the new signing certificate.%12</Description> </Message> <Message> <MessageID>5114</MessageID> <Description>The site server signing certificate has changed. The Policy at this Site will be re-signed by the Site Server using the new signing certificate.%12</Description> </Message> <Message> <MessageID>5115</MessageID> <Description>Policy Provider has failed to sign one or more policy assignments. It will retry this operation automatically.%12</Description> </Message> <Message> <MessageID>5116</MessageID> <Description>Policy Provider successfully signed all policy assignments with the new Site Server Signing Certificate.%12</Description> </Message> <Message> <MessageID>5117</MessageID> <Description>The hashing algorithm has changed. The Policy at this Site will be re-signed by the Site Server.%12</Description> </Message> <Message> <MessageID>5118</MessageID> <Description>Policy Provider has noted that the Program: %1 (Package ID: %2) is set to only run on one or more deprecated platforms that are no longer supported. The deployment (ID: %3)will not run on clients until the platform requirements are corrected.%12</Description> </Message> <Message> <MessageID>5119</MessageID> <Description>Policy Provder has detected policy changes for Collection %1. %2 are added. %3 are deleted.</Description> </Message> <Message> <MessageID>5200</MessageID> <Description>Active Directory System Discovery Agent failed to read the necessary registry information.%12</Description> </Message> <Message> <MessageID>5201</MessageID> <Description>Active Directory System Discovery Agent failed to read the location of the outbox.%12</Description> </Message> <Message> <MessageID>5202</MessageID> <Description>Active Directory System Discovery Agent read the AD Containers and found %1 valid AD Container entries in the site control file. Active Directory System Discovery Agent identified %2 systems in the AD Containers and generated %3 system discovery data records (DDRs) and %4 errors while attempting to create DDRs.%12</Description> </Message> <Message> <MessageID>5203</MessageID> <Description>Active Directory System Discovery Agent reported errors for %1 objects. DDRs were generated for %2 objects that had errors while reading non-critical properties. DDRs were not generated for %3 objects that had errors while reading critical properties.%12</Description> </Message> <Message> <MessageID>5204</MessageID> <Description>Active Directory System Discovery Agent failed to bind to container %1. Error: %2.%12</Description> </Message> <Message> <MessageID>5300</MessageID> <Description>Active Directory User Discovery Agent failed to read the necessary registry information.%12</Description> </Message> <Message> <MessageID>5301</MessageID> <Description>Active Directory User Discovery Agent failed to read the location of the outbox.%12</Description> </Message> <Message> <MessageID>5302</MessageID> <Description>Active Directory User Discovery Agent read the AD Containers and found %1 valid AD Container entries in the site control file. Active Directory User Discovery Agent identified %2 users in the AD Containers and generated %3 user discovery data records (DDRs) and %4 errors while attempting to create DDRs.%12</Description> </Message> <Message> <MessageID>5303</MessageID> <Description>Active Directory User Discovery Agent reported errors for %1 objects. DDRs were generated for %2 objects that had errors while reading non-critical properties. DDRs were not generated for %3 objects that had errors while reading critical properties.%12</Description> </Message> <Message> <MessageID>5304</MessageID> <Description>Active Directory User Discovery Agent failed to bind to container %1. Error: %2.%12</Description> </Message> <Message> <MessageID>5350</MessageID> <Description>Active Directory Security Group Discovery Agent failed to read the necessary registry information.%12</Description> </Message> <Message> <MessageID>5351</MessageID> <Description>Active Directory Security Group Discovery Agent failed to read the location of the outbox.%12</Description> </Message> <Message> <MessageID>5352</MessageID> <Description>Active Directory Security Group Discovery Agent read the AD Containers and found %1 valid AD Container entries in the site control file. Active Directory Security Group Discovery Agent identified %2 security group(s) in the AD Containers and generated %3 security group discovery data records (DDRs). %12</Description> </Message> <Message> <MessageID>5353</MessageID> <Description>Active Directory Security Group Discovery Agent reported warnings for %1 object(s). DDRs were generated for %2 object(s) that had warning(s) while reading non-critical properties. DDRs were not generated for %3 object(s) that had warnings while reading critical properties.%12</Description> </Message> <Message> <MessageID>5354</MessageID> <Description>Active Directory Security Group Discovery Agent failed to bind to container %1. Error: %2.%12</Description> </Message> <Message> <MessageID>5400</MessageID> <Description>MP File Dispatch Manager running on the management point "%1" cannot connect to site server "%2".%12</Description> </Message> <Message> <MessageID>5401</MessageID> <Description>MP File Dispatch Manager cannot copy files from "%1" to "%2".%12</Description> </Message> <Message> <MessageID>5410</MessageID> <Description>MP common layer cannot read the registry configuration when processing %1.%12</Description> </Message> <Message> <MessageID>5411</MessageID> <Description>MP has experienced out of memory condition when processing %1.%12</Description> </Message> <Message> <MessageID>5412</MessageID> <Description>MP has incurred an unexpected error when processing %1.%12</Description> </Message> <Message> <MessageID>5413</MessageID> <Description>MP has discarded a report when processing %1.%12</Description> </Message> <Message> <MessageID>5414</MessageID> <Description>MP could not complete a task when processing %1.%12 Check the logs for clues.</Description> </Message> <Message> <MessageID>5415</MessageID> <Description>MP cannot load the hardware inventory class mapping table when processing %1.%12</Description> </Message> <Message> <MessageID>5416</MessageID> <Description>MP needs to reload the hardware inventory class mapping table when processing %1. The MP hardware inventory manager cannot find a WMI class definition in the mapping table when processing a report. This should only happen if new definitions beyond those known to the site are added to the collected classes.%12</Description> </Message> <Message> <MessageID>5417</MessageID> <Description>MP could not process a message itself or spawn a task for message processing and discarded the message when processing %1. This is benign.%12</Description> </Message> <Message> <MessageID>5418</MessageID> <Description>MP could not find some class or property definitions when processing %1 as they are apparently missing in sms_def.mof. Unknown classes and properties have been ignored and a MIF file generated with all the classes and properties that could be found. %12</Description> </Message> <Message> <MessageID>5419</MessageID> <Description>MP retry component gave up on a report when processing %1 and moved it to the bad report directory. %12</Description> </Message> <Message> <MessageID>5420</MessageID> <Description>Management Point encountered an error when connecting to the database %3 on SQL Server %2. The OLEDB error code was %4. %12</Description> </Message> <Message> <MessageID>5421</MessageID> <Description>The Management Point was repaired.%12</Description> </Message> <Message> <MessageID>5430</MessageID> <Description>MP failed to register with the local WINS server.%12</Description> </Message> <Message> <MessageID>5431</MessageID> <Description>MP failed to unregister from the local WINS server.%12</Description> </Message> <Message> <MessageID>5432</MessageID> <Description>MP could not write out CCM setting to WMI.%12</Description> </Message> <Message> <MessageID>5433</MessageID> <Description>MP could not update its settings to the new values.%12</Description> </Message> <Message> <MessageID>5434</MessageID> <Description>Some or all of the MP Component Managers could not be started.%12</Description> </Message> <Message> <MessageID>5435</MessageID> <Description>Some or all of the MP Component Managers could not be stopped.%12</Description> </Message> <Message> <MessageID>5436</MessageID> <Description>MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>5437</MessageID> <Description>MP Control Manager detected NLB MP is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>5438</MessageID> <Description>MP Control Manager detected MP is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>5439</MessageID> <Description>MP Control Manager detected NLB MP is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>5441</MessageID> <Description>The SMS Agent Host (CCMEXEC) was unable to update certificate information in the Active Directory.%12</Description> </Message> <Message> <MessageID>5442</MessageID> <Description>The SMS Agent Host (CCMEXEC) successfuly updated certificate information in the Active Directory. %12</Description> </Message> <Message> <MessageID>5443</MessageID> <Description>MP has rejected a message from client %2 because it was not signed using the hash algorithm that is required by this site.%12</Description> </Message> <Message> <MessageID>5444</MessageID> <Description>MP has rejected policy request from %2 because this SMSID is marked as blocked.%12</Description> </Message> <Message> <MessageID>5445</MessageID> <Description>MP has rejected registration request due to failure in client certificate (Subject Name: %2) chain validation. If this is a valid client, Configuration Manager Administrator needs to place the Root Certification Authority and Intermediate Certificate Authorities in the MPÆs Certificate store or configure Trusted Root Certification Authorities in primary site settings.%12</Description> </Message> <Message> <MessageID>5446</MessageID> <Description>MP has rejected the request because %2 certificate has expired.%12</Description> </Message> <Message> <MessageID>5447</MessageID> <Description>MP has rejected a message from %2 because the signature could not be validated. If this is a valid client, it will attempt to re-register automatically so its signature can be correctly validated.%12</Description> </Message> <Message> <MessageID>5448</MessageID> <Description>MP has rejected a policy request from %2 because this client is not approved.%12</Description> </Message> <Message> <MessageID>5449</MessageID> <Description>MP has rejected a message from Client %2 because it was not signed.%12</Description> </Message> <Message> <MessageID>5450</MessageID> <Description>MP has rejected registration request from %2 because the Client Certificate has insufficient key length.%12</Description> </Message> <Message> <MessageID>5460</MessageID> <Description>MP Control Manager verified that Management Point is responding to HTTP requests.</Description> </Message> <Message> <MessageID>5461</MessageID> <Description>MP Control Manager verified that Device Management Point is responding to HTTP requests.</Description> </Message> <Message> <MessageID>5462</MessageID> <Description>MP Control Manager verified that Device Management Point Proxy is responding to HTTP requests.</Description> </Message> <Message> <MessageID>5480</MessageID> <Description>MP Control Manager detected DMP is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>5481</MessageID> <Description>MP Control Manager detected DMP is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>5482</MessageID> <Description>MP Control Manager detected that this node of the NLB MP is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>5483</MessageID> <Description>MP Control Manager detected that this node of the NLB MP is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>5484</MessageID> <Description>MP Control Manager detected that this node of the NLB MP is online. Node status code is %1 (%2).%12</Description> </Message> <Message> <MessageID>5485</MessageID> <Description>MP Control Manager detected that this node of the NLB MP is degraded. Node status code is %1 (%2).%12</Description> </Message> <Message> <MessageID>5486</MessageID> <Description>MP Control Manager detected that this node of the NLB MP is offline. Node status code is %1 (%2).%12</Description> </Message> <Message> <MessageID>5487</MessageID> <Description>MP Control Manager detected that the SQL Server hosting the database configured for the Management Point has its Common Language Runtime (CLR) disabled. This will cause multiple features of Configuration Manager requiring SQL CLR to fail.%12</Description> </Message> <Message> <MessageID>5488</MessageID> <Description>MP Control Manager detected DMP Proxy is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>5489</MessageID> <Description>MP Control Manager detected DMP Proxy is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>5600</MessageID> <Description>Software Metering Processor failed to read and configure the registry keys necessary for this component.%12</Description> </Message> <Message> <MessageID>5601</MessageID> <Description>Software Metering Processor failed to process the usage file "%1" for client "%2".%12</Description> </Message> <Message> <MessageID>5602</MessageID> <Description>Software Metering Processor was unable to copy the definition for rule %1 to the master rule file for this site. %12</Description> </Message> <Message> <MessageID>5603</MessageID> <Description>Software Metering Processor failed to completely process local rule changes, the rule change log has not been cleared and the changes will be processed again. %12</Description> </Message> <Message> <MessageID>5604</MessageID> <Description>Software Metering Processor failed to replicate the definition for rule %1 to child sites. %12</Description> </Message> <Message> <MessageID>5605</MessageID> <Description>Software Metering Processor failed to process a rule replicated from the parent site. %12</Description> </Message> <Message> <MessageID>5606</MessageID> <Description>Software Metering Processor failed to replicate summary data to the parent site.%12</Description> </Message> <Message> <MessageID>5607</MessageID> <Description>Software Metering Processor could not process replicated summary data from a child site.%12</Description> </Message> <Message> <MessageID>5608</MessageID> <Description>Software Metering Processor failed to process usage data file %1 and moved it to the retry directory. The file will be reprocessed at a later time.%12</Description> </Message> <Message> <MessageID>5609</MessageID> <Description>Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is enabled.</Description> </Message> <Message> <MessageID>5610</MessageID> <Description>Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is disabled.</Description> </Message> <Message> <MessageID>5611</MessageID> <Description>Software Metering Processor maintenance cycle deleted %1 files from directory %2.</Description> </Message> <Message> <MessageID>5612</MessageID> <Description>Software Metering Processor experienced an error while processing and forwarding usage data to the parent site.%12</Description> </Message> <Message> <MessageID>5613</MessageID> <Description>Software Metering Processor has retried the usage data file "%1" the maxumum number of times and has moved it to the discard directory. The file will be deleted when the minimum clean up age has been reached. %12</Description> </Message> <Message> <MessageID>5614</MessageID> <Description>Software Metering Processor failed to process the usage file "%1" for client "%2" because a record contained a bad usage start or end time value. Usage times are rejected if the start time is greater than the end time, the end time is in the future, or the end time is more than 90 days old.%12</Description> </Message> <Message> <MessageID>5615</MessageID> <Description>Software Metering Processor moved file "%1" to the corrupt directory. The file will be deleted when the minimum clean up age has been reached. See the previous and following error status messages for more details.</Description> </Message> <Message> <MessageID>5616</MessageID> <Description>Software Metering Processor could not process a summary file sent from a child site because a referenced computer was not found in the database. The file will be retried later.%12</Description> </Message> <Message> <MessageID>5617</MessageID> <Description>Software Metering Processor could not process a summary file sent from a child site because a referenced computer was not found in the database. The file will not be retried again.%12</Description> </Message> <Message> <MessageID>5700</MessageID> <Description>Device Management Point has encountered an unexpected error when processing %1.%12</Description> </Message> <Message> <MessageID>5701</MessageID> <Description>Device Management Point has experienced out of memory condition when processing %1. %12</Description> </Message> <Message> <MessageID>5702</MessageID> <Description>Device Management Point encountered an error when connecting to its database. %12</Description> </Message> <Message> <MessageID>5703</MessageID> <Description>Device Management Point failed to authenticate the client %1. %12</Description> </Message> <Message> <MessageID>5720</MessageID> <Description>Received an undefined message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5721</MessageID> <Description>Received message from unknown or unauthorized client %1.%12</Description> </Message> <Message> <MessageID>5722</MessageID> <Description>Received an invalid poll message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5723</MessageID> <Description>Received an invalid download instructions request message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5724</MessageID> <Description>Received an invalid package location request message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5725</MessageID> <Description>Received an invalid status message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5726</MessageID> <Description>Received an invalid hardware inventory message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5727</MessageID> <Description>Received an invalid software inventory message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5728</MessageID> <Description>Received an invalid file collection message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5729</MessageID> <Description>Received an invalid registration message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5740</MessageID> <Description>Error generating or sending discovery message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5741</MessageID> <Description>Error generating or sending hardware inventory message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5742</MessageID> <Description>Error generating or sending software inventory message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5743</MessageID> <Description>Error generating or sending file collection message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5744</MessageID> <Description>Error generating or sending status message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5745</MessageID> <Description>Error generating or sending package location request message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5746</MessageID> <Description>Error processing download instructions request message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5747</MessageID> <Description>Error processing registration request message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5748</MessageID> <Description>Device Management Point encountered an error when processing App model policy. %12</Description> </Message> <Message> <MessageID>5749</MessageID> <Description>Device Management Point encountered an error when sending Compliance Report. %12</Description> </Message> <Message> <MessageID>5750</MessageID> <Description>Device Management Point encountered an error when processing DCM CI. %12</Description> </Message> <Message> <MessageID>5751</MessageID> <Description>Device Management Point encountered an error while reading policy xml. %12</Description> </Message> <Message> <MessageID>5752</MessageID> <Description>Device Management Point encountered an error when processing Schedule policy. %12</Description> </Message> <Message> <MessageID>5753</MessageID> <Description>Device Management Point encountered an error when processing Data policy. %12</Description> </Message> <Message> <MessageID>5754</MessageID> <Description>Device Management Point encountered an error when processing prequisite applications policy. %12</Description> </Message> <Message> <MessageID>5755</MessageID> <Description>Device Management Point encountered an error when registering a device. %12</Description> </Message> <Message> <MessageID>5756</MessageID> <Description>Device Management Point encountered an error when processing client certificate. %12</Description> </Message> <Message> <MessageID>5760</MessageID> <Description>Error sending poll response. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5761</MessageID> <Description>Error sending download instructions. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5762</MessageID> <Description>Error sending package location response. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5763</MessageID> <Description>Error sending registration response. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5800</MessageID> <Description>CI Assignment Manager successfully processed new CI Assignment %1.%12</Description> </Message> <Message> <MessageID>5801</MessageID> <Description>CI Assignment Manager successfully processed Update to CI Assignment %1.%12</Description> </Message> <Message> <MessageID>5802</MessageID> <Description>CI Assignment Manager successfully removed CI Assignment %1.%12</Description> </Message> <Message> <MessageID>5803</MessageID> <Description>SMS CI Assignment has been directly deleted from the site Database. Deletion of collection may cause the deletion of all the CI Assignments assigned to that collection. It is not recommended directly deleting CI Assignments from the site database, to verify this deletion was due to Collection delete review the CI Assignment Manager and Collection Evaluator Logs.%12</Description> </Message> <Message> <MessageID>5804</MessageID> <Description>CI Assignment Manager failed to process CI Assignment changes. These changes will be retried on next processing cycle.%12</Description> </Message> <Message> <MessageID>5805</MessageID> <Description>CI Assignment Manager failed to process CI Assignment %1. This CI Assignment will be retried %2 times on the next processing cycles.%12</Description> </Message> <Message> <MessageID>5806</MessageID> <Description>CI Assignment Manager failed to process CI Assignment %1. This CI Assignment has been retried %2 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>5807</MessageID> <Description>CI Assignment Manager failed to process CI Assignment Replication File %1 as CI Assignment %2 referenced object of type %3 does not exists. This CI Assignment Replication file has been retried %4 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>5808</MessageID> <Description>CI Assignment Manager failed to process CI Assignment Replication File %1. This CI Assignment Replication file has been retried %2 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>6000</MessageID> <Description>Object Replication Manager successfully processed Object %1 of Type %2.%12</Description> </Message> <Message> <MessageID>6001</MessageID> <Description>Object Replication Manager successfully processed modification to Object %1 of Type %2.%12</Description> </Message> <Message> <MessageID>6002</MessageID> <Description>Object Replication Manager successfully removed Object %1 of Type %2.%12</Description> </Message> <Message> <MessageID>6003</MessageID> <Description>Object Replication Manager failed to process Object %1 of Type %2. This Object has been retried %3 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>6004</MessageID> <Description>Object Replication Manager failed to process Object changes. These changes will be retried on next processing cycle.%12</Description> </Message> <Message> <MessageID>6005</MessageID> <Description>Object Replication Manager failed to process Object Replication File %1. This Object Replication file has been retried %2 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>6006</MessageID> <Description>Object Replication Manager failed to process Object %1 of Type %2. This Object will be retried %3 times on the next processing cycles.%12</Description> </Message> <Message> <MessageID>6007</MessageID> <Description>Object Replication Manager failed to process Object Replication File %1 as Object %2 of Type %3 referenced object of type %4 does not exists. This Object Replication file has been retried %5 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>6100</MessageID> <Description>The State System failed to read and configure the registry keys necessary for this component.%12</Description> </Message> <Message> <MessageID>6101</MessageID> <Description>The State System message file processing experienced a severe error and suspended file processing. Review the statesys.log file for further details.%12</Description> </Message> <Message> <MessageID>6103</MessageID> <Description>The State System summary task '%1' failed to execute. Review the statesys.log file for further details.%12</Description> </Message> <Message> <MessageID>6104</MessageID> <Description>The State System message file processing could not process file '%1' and moved it to the corrupt directory. Review the statesys.log file for further details.%12</Description> </Message> <Message> <MessageID>6105</MessageID> <Description>The State System message file processing processed one or more files that contained errors or invalid data. Review the statesys.log file for further details.%12</Description> </Message> <Message> <MessageID>6200</MessageID> <Description>The State Migration Point failed to read and configure the registry keys necessary for this component.</Description> </Message> <Message> <MessageID>6201</MessageID> <Description>The State Migration Point reached the minimum disk space threshold on all drives of computer %1.</Description> </Message> <Message> <MessageID>6202</MessageID> <Description>The State Migration Point has reached the maximum client threshold on all drives on computer %1.</Description> </Message> <Message> <MessageID>6203</MessageID> <Description>Client with GUID %1 requested capture request while the store from previous request exists.%12</Description> </Message> <Message> <MessageID>6204</MessageID> <Description>The State Migration Point has reached the minimum disk space threshold of %1 %2 on drive %3 of computer %4. Current free space is %5 %2.%12</Description> </Message> <Message> <MessageID>6205</MessageID> <Description>The State Migration Point has removed the state store %2 on computer %1.%12</Description> </Message> <Message> <MessageID>6206</MessageID> <Description>The State Migration Point can not authenticate the client %1.</Description> </Message> <Message> <MessageID>6207</MessageID> <Description>SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>6208</MessageID> <Description>SMP Control Manager detected SMP is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>6209</MessageID> <Description>State Migration Point cannot access the state store %1 on computer %2.%12</Description> </Message> <Message> <MessageID>6210</MessageID> <Description>State Migration Point failed to read the SignedSerializedSMPKey from the registry on computer %1. Possible reasons are SMP certificate is not yet signed by Site Server. %12</Description> </Message> <Message> <MessageID>6211</MessageID> <Description>There is enough free disk on computer %1.</Description> </Message> <Message> <MessageID>6300</MessageID> <Description>The PXE Service Point failed to read and configure the registry keys necessary for this component.</Description> </Message> <Message> <MessageID>6301</MessageID> <Description>The PXE Service Point failed to initialize the WDS PXE Provider. Check Previous Messages for more error information.</Description> </Message> <Message> <MessageID>6302</MessageID> <Description>The PXE Service Point failed to perform a clean shutdown.</Description> </Message> <Message> <MessageID>6303</MessageID> <Description>The PXE Service Point failed to initialize performance counters.</Description> </Message> <Message> <MessageID>6304</MessageID> <Description>The PXE Service Point failed to initialize worker threads.</Description> </Message> <Message> <MessageID>6305</MessageID> <Description>The PXE Service Point failed to process PXE request.</Description> </Message> <Message> <MessageID>6306</MessageID> <Description>The PXE Service Point is not actively processing PXE messages. Ignoring request from device. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6307</MessageID> <Description>The PXE Service Point failed to Lookup device in the database. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6308</MessageID> <Description>The PXE Service Point failed to get boot action from database for device. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6309</MessageID> <Description>The PXE Service Point failed to find boot image for package %3 while handling device. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6310</MessageID> <Description>The PXE Service Point failed to find boot image for package %3 while handling device. Stalling device until package becomes available. If this situation persists the device might become unmanageable. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6311</MessageID> <Description>The PXE Service Point instructed the device to boot to the bootimage %3 based on deployment %4. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6312</MessageID> <Description>The PXE Service Point encountered an unknown device. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6313</MessageID> <Description>The PXE Service Point intructed device to boot normally since it already had executed deployment %3. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6314</MessageID> <Description>The PXE Service Point intructed device to boot normally since it has no PXE deployment assigned. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6315</MessageID> <Description>The PXE Service Point failed to Initialize the Database Connection.</Description> </Message> <Message> <MessageID>6316</MessageID> <Description>The PXE Certificate used for PXE clients is not valid. Please provide a valid certificate.</Description> </Message> <Message> <MessageID>6317</MessageID> <Description>The PXE Certificate used for PXE clients will expire soon. Please renew the certificate.</Description> </Message> <Message> <MessageID>6318</MessageID> <Description>PXE control manager could not update its settings to the new values.%12</Description> </Message> <Message> <MessageID>6319</MessageID> <Description>PXE Control Manager detected PXE service point is not responding to PXE requests. The error is %1.%12</Description> </Message> <Message> <MessageID>6320</MessageID> <Description>PXE Control Manager detected PXE service point is not responding to PXE requests. The status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>6321</MessageID> <Description>The PXE Service Point does not have a boot image matching the processor architetcure of the PXE booting device. Device MAC Address:%1 SMBIOS GUID:%2. Boot Image Architecture:%3.</Description> </Message> <Message> <MessageID>6322</MessageID> <Description>The PXE Service Point does not have a boot program matching the processor architetcure of the PXE booting device. Device MAC Address:%1 SMBIOS GUID:%2. Boot Program Architecture:%3.</Description> </Message> <Message> <MessageID>6400</MessageID> <Description>Component Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12</Description> </Message> <Message> <MessageID>6500</MessageID> <Description>The Wake On LAN component has failed to read the site control file settings.</Description> </Message> <Message> <MessageID>6501</MessageID> <Description>The Wake On LAN component was enabled by the Configuration Manager Administrator.%12</Description> </Message> <Message> <MessageID>6502</MessageID> <Description>The Wake On LAN component was disabled by the Configuration Manager Administrator.%12</Description> </Message> <Message> <MessageID>6503</MessageID> <Description>The Wake On LAN component settings have been updated by the Configuration Manager Administrator.%12</Description> </Message> <Message> <MessageID>6504</MessageID> <Description>The Wake On LAN component is starting to send wakeup packets for the object id=%1 of type=%2.%12</Description> </Message> <Message> <MessageID>6505</MessageID> <Description>The Wake On LAN component component completed sending wakeup packets for the object id=%1 of type=%2.%12</Description> </Message> <Message> <MessageID>6506</MessageID> <Description>The Wake On LAN component component successfully sent wakeup packets to all clients targeted for the object id=%1 of type=%2.%12</Description> </Message> <Message> <MessageID>6507</MessageID> <Description>The Wake On LAN component component failed to send wakeup packets for some clients targeted by object id=%1 of type=%2.</Description> </Message> <Message> <MessageID>6508</MessageID> <Description>The Wake On LAN component component failed to start sending wakeup packets for object id=%1 of type=%2.</Description> </Message> <Message> <MessageID>6509</MessageID> <Description>The Wake On LAN component failed access the database.</Description> </Message> <Message> <MessageID>6510</MessageID> <Description>The Wake On LAN component successfully processed wakeup information for the object id=%1 of type=%2.%12</Description> </Message> <Message> <MessageID>6511</MessageID> <Description>The Wake On LAN component failed to process wakeup information for the object id=%1 of type=%2.</Description> </Message> <Message> <MessageID>6512</MessageID> <Description>The Wake On LAN component has recovered from an unavailable state. The component is now online.%12</Description> </Message> <Message> <MessageID>6513</MessageID> <Description>The Wake On LAN component has entered an unavailable state due to a high number of failures. The component's services may not be available.%12</Description> </Message> <Message> <MessageID>6600</MessageID> <Description>WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "%1".%12</Description> </Message> <Message> <MessageID>6602</MessageID> <Description>WSUS Configuration Manager failed to get update categories, classifications and locales from WSUS Server "%1".%12</Description> </Message> <Message> <MessageID>6603</MessageID> <Description>WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server "%1".%12</Description> </Message> <Message> <MessageID>6607</MessageID> <Description>WSUS Configuration Manager will not be able to configure WSUS Server "%1" as the WSUS Server remoting API's of version 3.0 SP2 or greater are not installed on this site server.%12</Description> </Message> <Message> <MessageID>6609</MessageID> <Description>WSUS Configuration Manager has configured WSUS Server "%1" to sync from the parent WSUS Server instead of sync from Microsoft Update.%12</Description> </Message> <Message> <MessageID>6610</MessageID> <Description>WSUS Configuration Manager has detected that WSUS Server "%1" cannot sync from the parent WSUS Server as there is no parent WSUS Server. Choose the option from the Configuration Manager Console to sync from either Microsoft Update or Do not Sync.%12</Description> </Message> <Message> <MessageID>6611</MessageID> <Description>WSUS Configuration Manager has detected that Software Updates Point is not configured yet. client boot-strapper packag publishing will be tried later.%12</Description> </Message> <Message> <MessageID>6612</MessageID> <Description>WSUS Configuration Manager failed to get client package info.%12</Description> </Message> <Message> <MessageID>6613</MessageID> <Description>WSUS Configuration Manager failed to publish client boot-strapper package "%1" with version "%2" to the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6614</MessageID> <Description>WSUS Configuration Manager failed to unpublish client boot-strapper package "%1" with version "%2" from the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6615</MessageID> <Description>WSUS Configuration Manager successfully published client boot-strapper package "%1" with version "%2" to the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6616</MessageID> <Description>WSUS Configuration Manager successfully unpublished client boot-strapper package "%1" with version "%2" to the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6617</MessageID> <Description>WSUS Configuration Manager failed to unpublish client boot-strapper package "%1" from the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6618</MessageID> <Description>WSUS Configuration Manager successfully unpublished client boot-strapper package "%1" to the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6700</MessageID> <Description> SMS WSUS Sync Manager error. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>6701</MessageID> <Description> WSUS Synchronization started. %12</Description> </Message> <Message> <MessageID>6702</MessageID> <Description> WSUS Synchronization done. %12</Description> </Message> <Message> <MessageID>6703</MessageID> <Description> WSUS Synchronization failed. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>6704</MessageID> <Description> WSUS Synchronization in progress. Current phase: Synchronizing WSUS Server. %12</Description> </Message> <Message> <MessageID>6705</MessageID> <Description> WSUS Synchronization in progress. Current phase: Synchronizing site database. %12</Description> </Message> <Message> <MessageID>6706</MessageID> <Description> WSUS Synchronization in progress. Current phase: Synchronizing Internet facing WSUS Server. %12</Description> </Message> <Message> <MessageID>6707</MessageID> <Description>Content of WSUS Server %1 is out of sync with upstream server %2.%12</Description> </Message> <Message> <MessageID>6708</MessageID> <Description> WSUS synchronization complete, with pending license terms downloads. %12</Description> </Message> <Message> <MessageID>6800</MessageID> <Description>SMS Writer was unable to open control file "%1". Site backup will fail.%12</Description> </Message> <Message> <MessageID>6801</MessageID> <Description>SMS Writer stopped the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>6802</MessageID> <Description>SMS Writer could not stop the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>6803</MessageID> <Description>SMS Writer started the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>6804</MessageID> <Description>SMS Writer could not start the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>6805</MessageID> <Description>SMS Writer stopped the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>6806</MessageID> <Description>SMS Writer could not stop the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>6807</MessageID> <Description>SMS Writer started the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>6808</MessageID> <Description>SMS Writer could not start the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>6809</MessageID> <Description>SMS Writer stopped the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>6810</MessageID> <Description>The %1 ConfigMgr client application on the local computer did not respond to SMS Writer's stop request.%12</Description> </Message> <Message> <MessageID>6811</MessageID> <Description>SMS Writer could not stop the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>6812</MessageID> <Description>SMS Writer started the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>6813</MessageID> <Description>SMS Writer could not start the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>6814</MessageID> <Description>SMS Writer found syntax errors on the following lines:%1 in backup control file. Site backup will fail.%12</Description> </Message> <Message> <MessageID>6815</MessageID> <Description>The following utility tools were not available to be run: %1 Their output is not provided so you might miss some configuration information.%12</Description> </Message> <Message> <MessageID>6816</MessageID> <Description>Unable to verify the installation of the service : %1 This service will not be stopped or restarted.%12</Description> </Message> <Message> <MessageID>6817</MessageID> <Description>Maximum sleep time is 15 minutes. Time given in Backup Control File exceeds this limit so it is being reset to this maximum limit.%12</Description> </Message> <Message> <MessageID>6818</MessageID> <Description>Token Symbol (%1) already defined. First value (%2) will be used.%12</Description> </Message> <Message> <MessageID>6819</MessageID> <Description>SMS Writer was unable to locate the file system object %1.%12</Description> </Message> <Message> <MessageID>6820</MessageID> <Description>SMS Writer was unable to export the registry key %1 to %2.%12</Description> </Message> <Message> <MessageID>6821</MessageID> <Description>SMS Writer was unable to write the machine info to the temporary backup destination %1.%12</Description> </Message> <Message> <MessageID>6822</MessageID> <Description>SMS Writer tried to stop the %1 service on site system %2. This service is already stopped.%12</Description> </Message> <Message> <MessageID>6823</MessageID> <Description>SMS Writer tried to stop the %1 executable. This executable is already stopped.%12</Description> </Message> <Message> <MessageID>6824</MessageID> <Description>SMS Writer service was stopped manually. All the backup operations will be affected and cannot be completed.%12</Description> </Message> <Message> <MessageID>6825</MessageID> <Description>SMS Writer was unable to initialize the service.%12</Description> </Message> <Message> <MessageID>6826</MessageID> <Description>SMS Writer was unable to subscribe to the VSS services.%12</Description> </Message> <Message> <MessageID>6827</MessageID> <Description>SMS Writer failed to build the metadata. Site Backup tasks will fail.%12</Description> </Message> <Message> <MessageID>6828</MessageID> <Description>The backup application has not included all the required components in the backup list.%12</Description> </Message> <Message> <MessageID>6829</MessageID> <Description>SMS Writer is about to stop the ConfigMgr Services as part of the preparation for the Site backup.%12</Description> </Message> <Message> <MessageID>6830</MessageID> <Description>The snapshots of the volumes required for the Site Backup have been successfully created.%12</Description> </Message> <Message> <MessageID>6831</MessageID> <Description>SMS Writer has started the ConfigMgr Services successfully. %12</Description> </Message> <Message> <MessageID>6832</MessageID> <Description>Site Backup task has been aborted.%12</Description> </Message> <Message> <MessageID>6833</MessageID> <Description>Site Backup task has completed successfully.%12</Description> </Message> <Message> <MessageID>6900</MessageID> <Description>The Fallback Status Point failed to read and configure the registry keys necessary for this component.</Description> </Message> <Message> <MessageID>6901</MessageID> <Description>The Fallback Status Point can not authenticate the client %1.</Description> </Message> <Message> <MessageID>6902</MessageID> <Description>The Fallback Status Point can not process any more messages.</Description> </Message> <Message> <MessageID>6903</MessageID> <Description>The Fallback Status Point could not load valid topics from registry.</Description> </Message> <Message> <MessageID>6904</MessageID> <Description>The Fallback Status Point could not write messages to the staging folder.</Description> </Message> <Message> <MessageID>6905</MessageID> <Description>The Fallback Status Point could not transfer messages from the staging folder to the outbox.</Description> </Message> <Message> <MessageID>7000</MessageID> <Description>WSUS Control Manager failed to configure proxy settings on WSUS Server "%1".%12</Description> </Message> <Message> <MessageID>7001</MessageID> <Description>Failures were reported on WSUS Server "%1" for WSUS components "%2".%12</Description> </Message> <Message> <MessageID>7002</MessageID> <Description>Failures were reported on WSUS Server "%1" while trying to make WSUS database connection with SQL Server Exception error code %2.%12</Description> </Message> <Message> <MessageID>7003</MessageID> <Description>WSUS Control Manager failed to monitor WSUS Server "%1".%12</Description> </Message> <Message> <MessageID>7004</MessageID> <Description>WSUS Control Manager will not be able to configure WSUS Server "%1" as the WSUS Server of version 3.0 SP2 or greater is not installed on this site system.%12</Description> </Message> <Message> <MessageID>7100</MessageID> <Description>The Multicast Service Point failed to open multicast session.</Description> </Message> <Message> <MessageID>7101</MessageID> <Description>MCS Control Manager detected MCS is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>7102</MessageID> <Description>MCS Control Manager detected MCS is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>7103</MessageID> <Description>Multicast Service was unable to create a WDS multicast namaspace for package with UNC "%2" and packageID "%3". The error is %1.%12</Description> </Message> <Message> <MessageID>7104</MessageID> <Description>Multicast Service was unable to initialize multicast service. The error is %1.%12</Description> </Message> <Message> <MessageID>7105</MessageID> <Description>Multicast Service was unable to initialize multicast provider. The error is %1.%12</Description> </Message> <Message> <MessageID>7106</MessageID> <Description>Multicast Service was unable to initialize ISAPI. The error is %1.%12</Description> </Message> <Message> <MessageID>7107</MessageID> <Description>Multicast Service did not grant access to directory %2 for client with account %3. The error is %1.%12</Description> </Message> <Message> <MessageID>7108</MessageID> <Description>Multicast Service failed to read the SignedSerializedMCSKey from the registry on computer %1. Possible reasons are MCS certificate is not yet signed by Site Server. %12</Description> </Message> <Message> <MessageID>7109</MessageID> <Description>Multicast Service has rejected a request from %2 for site %3 because it is not approved.%12</Description> </Message> <Message> <MessageID>7110</MessageID> <Description>Multicast Service has rejected request from %2 because this SMSID is marked as blocked.%12</Description> </Message> <Message> <MessageID>7111</MessageID> <Description>Multicast Service has rejected the request because %2 certificate has expired.%12</Description> </Message> <Message> <MessageID>7112</MessageID> <Description>Multicast Service rejected a request because %2 signature is invalid.%12</Description> </Message> <Message> <MessageID>7150</MessageID> <Description>The Multicast Service failed to initialize properly. The error encountered was %1.</Description> </Message> <Message> <MessageID>7200</MessageID> <Description>The out of band service point failed to read notification registry.</Description> </Message> <Message> <MessageID>7201</MessageID> <Description>The out of band service point failed to initialize the inbox of %1. %</Description> </Message> <Message> <MessageID>7202</MessageID> <Description>The out of band service point is starting to send packets to completion port.</Description> </Message> <Message> <MessageID>7203</MessageID> <Description>The out of band service point completed sending %1 packet(s) to completion port. %2 packet(s) are in pending list. %3 packet(s) are failed to be sent to completion port.</Description> </Message> <Message> <MessageID>7204</MessageID> <Description>WinRM out of band service is not enabled.</Description> </Message> <Message> <MessageID>7205</MessageID> <Description>The port specified for incoming Hello packets is in use by another application.</Description> </Message> <Message> <MessageID>7206</MessageID> <Description>The out of band service point failed to provision %1 with error %2: %3.%12</Description> </Message> <Message> <MessageID>7207</MessageID> <Description>The out of band service point failed to %1 %2 with error %3.%12</Description> </Message> <Message> <MessageID>7208</MessageID> <Description>Provisioning failed because of an unsupported provisioning scenario. 12</Description> </Message> <Message> <MessageID>7209</MessageID> <Description>Provisioning for %1 %2 failed due to an improper or missing provisioning certificate.%12</Description> </Message> <Message> <MessageID>7210</MessageID> <Description>The provisioning certificate with the thumbprint %1 will expire in %2 day(s). Please ensure that this certificate is renewed.%12</Description> </Message> <Message> <MessageID>7211</MessageID> <Description>The provisioning certificate with the thumbprint %1 will expire in %2 day(s). Please ensure that this certificate is renewed.%12</Description> </Message> <Message> <MessageID>7212</MessageID> <Description>The out of band service point failed to provision %1 with error %2: %3.%12</Description> </Message> <Message> <MessageID>7213</MessageID> <Description>Provisioning for %1 %2 failed due to all accounts failed to authentication with target device.%12</Description> </Message> <Message> <MessageID>7214</MessageID> <Description>The provisioning certificate with the thumbprint %1 failed to pass revocation check with error %2.%12</Description> </Message> <Message> <MessageID>7215</MessageID> <Description>The provisioning certificate with the thumbprint %1 is invalid. Please ensure that CN name or OID is correct.</Description> </Message> <Message> <MessageID>7216</MessageID> <Description>The out of band service point failed to run %1 on %2 with error %3.%12</Description> </Message> <Message> <MessageID>7217</MessageID> <Description>The computer is configured to use IPv6 before IPv4. When out of band management uses IPv4 only, this configuration can negatively impact the performance of managing this computer out of band.</Description> </Message> <Message> <MessageID>7218</MessageID> <Description>The out of band service point failed to request a certificate by using the enrollment point.</Description> </Message> <Message> <MessageID>7219</MessageID> <Description>The out of band service point cannot connect to the enrollment point.</Description> </Message> <Message> <MessageID>7220</MessageID> <Description>The out of band service point can connect to the enrollment point.</Description> </Message> <Message> <MessageID>7300</MessageID> <Description>Asset Intelligence Update Service site role failed to install on "%1".%12</Description> </Message> <Message> <MessageID>7400</MessageID> <Description>Reporting Point site role failed to configure SQL Reporting Services on "%1".</Description> </Message> <Message> <MessageID>7401</MessageID> <Description>SQL Reporting Services install is invalid on "%1".</Description> </Message> <Message> <MessageID>7402</MessageID> <Description> Reporting Point failed to monitor SQL Reporting Services Server on "%1".</Description> </Message> <Message> <MessageID>7403</MessageID> <Description>The report server service is not running on Reporting Service Point server "%1"; start the service to enable reporting.</Description> </Message> <Message> <MessageID>7404</MessageID> <Description>SQL Reporting Services is not installed or properly configured on Reporting point server "%1".</Description> </Message> <Message> <MessageID>7405</MessageID> <Description>SQL Reporting Services root folder "%1" is not present or not properly configured on the Reporting point server "%2".</Description> </Message> <Message> <MessageID>7406</MessageID> <Description>The SQL Reporting Services datasource on Reporting point server "%1" is missing or has been changed outside of Configuration Manager. It will be rebuilt based on the RSP configuration.</Description> </Message> <Message> <MessageID>7502</MessageID> <Description>Asset Intelligence KB Manager encountered errors processing file %1 from online service. This file and subsequent data will be deleted, subsequent sync will bring the data again.</Description> </Message> <Message> <MessageID>7600</MessageID> <Description>Failure: The AMT Proxy Manager failed to apply certificate for "%1" from CA at "%2" with error CR_DISP_DENIED: (CERTSRV_E_ENROLL_DENIED(0x80094011L) : The permissions on this certification authority do not allow the current user to enroll for certificates.)%12</Description> </Message> <Message> <MessageID>7601</MessageID> <Description>Failure: The AMT Proxy Manager failed to apply certificate for "%1" from CA at "%2" with certificate trust error.%12</Description> </Message> <Message> <MessageID>7602</MessageID> <Description>Failure: The AMT Proxy Manager failed to add a object into AD. FQDN: %1, ADDN: %2, UUID: %3, AMT Version: %4.%12</Description> </Message> <Message> <MessageID>7603</MessageID> <Description>Failure: The AMT Proxy Manager failed to remove a object into AD. FQDN: %1, ADDN: %2.%12</Description> </Message> <Message> <MessageID>7604</MessageID> <Description>Failure: The AMT Proxy Manager failed to update a object in the AD. FQDN: %1, ADDN: %2.%12</Description> </Message> <Message> <MessageID>7605</MessageID> <Description>Warning: The AMT Proxy Manager failed to apply certificate for "%1" from CA at "%2" with certificate request pending.%12 Please wait for a certification authority administrator to issue the certificate and the AMT Proxy Manager will retrieve it.</Description> </Message> <Message> <MessageID>7606</MessageID> <Description>The out of band service point failed to register the %1 in DNS. The machine's FQDN is %2.%12</Description> </Message> <Message> <MessageID>7607</MessageID> <Description>The out of band service point failed to unregister the %1 in DNS.%12</Description> </Message> <Message> <MessageID>7608</MessageID> <Description>The AMT Proxy Manager failed to replicate file %1 to out of band service point for the %2 time. The file will be re-send again later.</Description> </Message> <Message> <MessageID>7609</MessageID> <Description>The AMT Proxy Manager failed %2 times while replicating file %1 to out of band service point. The file has been moved to the BAD file inbox.</Description> </Message> <Message> <MessageID>7700</MessageID> <Description>The Client Health Manager failed to read and configure the registry keys necessary for this component.%12</Description> </Message> <Message> <MessageID>7800</MessageID> <Description>The RCM Control failed to read and configure the registry keys necessary for this component.%12</Description> </Message> <Message> <MessageID>7801</MessageID> <Description>Site %1 is requesting initialization for replication group %2 from site %3.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7802</MessageID> <Description>Received initialization request from Site %1 for replication group "%2".</Description> </Message> <Message> <MessageID>7803</MessageID> <Description>Snapshot for replication group "%1" for Site %2 created successfully.</Description> </Message> <Message> <MessageID>7804</MessageID> <Description>Failed to create snapshot for replication group "%1" for Site %2.%12 Error: %3 %12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7805</MessageID> <Description>Snapshot for replication group "%1" from Site %2 applied successfully.</Description> </Message> <Message> <MessageID>7806</MessageID> <Description>Snapshot for replication group "%1" from Site %2 failed to be applied successfully.%12 Error: %3 %12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7809</MessageID> <Description>The replication status for this site has changed from "%1" to "%2".</Description> </Message> <Message> <MessageID>7810</MessageID> <Description>Site %1 is ready for replication.</Description> </Message> <Message> <MessageID>7811</MessageID> <Description>A transmission error has been detected for messages going to site %1.%12 Error: %2.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7812</MessageID> <Description>The queue %1 for site %2 is currently disabled.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7815</MessageID> <Description>Unable to determine link status for site %1 at this time. Setting link status to site %1 to unknown.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7816</MessageID> <Description>The link status to site %1 is degraded at this time.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7817</MessageID> <Description>The replication system has experienced an error and is attempting to recover. All synchronizations are currently stopped.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7818</MessageID> <Description>The replication system has experienced an unrecoverable error and all synchronizations are currently stopped.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7819</MessageID> <Description>The replication system has recovered and is synchronizing with other sites again.</Description> </Message> <Message> <MessageID>7820</MessageID> <Description>This site is now in maintenance mode. Replication has been stopped until maintenance is complete.</Description> </Message> <Message> <MessageID>7821</MessageID> <Description>Maintenance is complete and replication has restarted.</Description> </Message> <Message> <MessageID>7822</MessageID> <Description>The link status to site %1 is failed at this time.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7825</MessageID> <Description>Site %1 is detaching.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7826</MessageID> <Description>Site %1 has failed to detach.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7827</MessageID> <Description>Site %1 has successfully detached.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7828</MessageID> <Description>The link status to site %1 has changed to active.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7829</MessageID> <Description>The link status to site %1 is in an error state at this time.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7830</MessageID> <Description>Detected Service Broker is not enabled on site %1. To fix this, put the database in single user mode and execute 'ALTER DATABASE [%2] SET ENABLE_BROKER'.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7831</MessageID> <Description>On site %1, found service broker queue %2 disabled. It has been enabled now.%12 Refer to the SQL view vLogs for more information.</Description> </Message> <Message> <MessageID>7832</MessageID> <Description>An unhandled exception has occurred - %1.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7833</MessageID> <Description>When RCM creates the linked server for %1, an exception has occurred - %2.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7834</MessageID> <Description>When RCM drops the linked server for %1, an exception has occurred - %2.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7835</MessageID> <Description>When RCM configures dview for table table %1, an exception has occurred - %2.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7836</MessageID> <Description>When RCM renames table %1 to %2_RCM for dview, an exception has occurred - %3.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7837</MessageID> <Description>When RCM tries to clean old replicated data on table %1 for dview, an exception has occurred - %2.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7838</MessageID> <Description>RCM has successfully configured dview on CAS for replicationgroup [%1].%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7839</MessageID> <Description>RCM is currently configuring dview on CAS for replicationgroup [%1].%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7840</MessageID> <Description>RCM received resync request for replicationgroup [%1] to version %2.Please refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7841</MessageID> <Description>RCM has finished processing resync for replicationgroup [%1] to version %2.Please refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7900</MessageID> <Description>Offline Image Servicing Manager started processing of schedule with ID %1 and name %2.</Description> </Message> <Message> <MessageID>7901</MessageID> <Description>Offline Image Servicing Manager completed processing of schedule with ID %1 and name %2.</Description> </Message> <Message> <MessageID>7902</MessageID> <Description>Offline Image Servicing Manager cancelled processing of schedule with ID %1 and Name %2.</Description> </Message> <Message> <MessageID>7903</MessageID> <Description>Offline Image Servicing Manager started copying image with ID %1 from image package source to local staging folder.</Description> </Message> <Message> <MessageID>7904</MessageID> <Description>Offline Image Servicing Manager started copying updated image with ID %1 from staging folder to the image package folder.</Description> </Message> <Message> <MessageID>7905</MessageID> <Description>Offline Image Servicing Manager completed copying image with ID %1.</Description> </Message> <Message> <MessageID>7906</MessageID> <Description>Offline Image Servicing Manager started applying updates on image with ID %1.</Description> </Message> <Message> <MessageID>7907</MessageID> <Description>Offline Image Servicing Manager completed installing updates on image with ID %1.</Description> </Message> <Message> <MessageID>7908</MessageID> <Description>Offline Image Servicing Manager successfully installed update with ID %1 on image with ID %2 (image index %3).</Description> </Message> <Message> <MessageID>7909</MessageID> <Description>Offline Image Servicing Manager determined that update with ID %1 is not required on image with ID %2 (image index %3).</Description> </Message> <Message> <MessageID>7910</MessageID> <Description>Offline Image Servicing Manager failed to process schedule with ID %1 and name %2.</Description> </Message> <Message> <MessageID>7911</MessageID> <Description>Offline Image Servicing Manager failed to apply update with ID %1 on image with ID %2 (image index %3).</Description> </Message> <Message> <MessageID>7912</MessageID> <Description>Offline Image Servicing Manager failed to mount image with ID %1 (image index %2) to mount directory %3. Error : %4.</Description> </Message> <Message> <MessageID>7913</MessageID> <Description>Offline Image Servicing Manager failed to unmount image with ID %1 (image index %2) from mount directory %3. Error : %4.</Description> </Message> <Message> <MessageID>7914</MessageID> <Description>Offline Image Servicing Manager failed because there is not enough free disk space left on the staging drive %1. Required disk Space = %2 MB, available free disk space = %3 MB.</Description> </Message> <Message> <MessageID>7915</MessageID> <Description>Offline Image Servicing Manager cannot write to the image package source location for the image with ID %1. Please make sure that the image package source folder can be written to.</Description> </Message> <Message> <MessageID>7916</MessageID> <Description>Offline Image Servicing Manager does not support image with ID %1 (image index %2) and therefore will not process this image.</Description> </Message> <Message> <MessageID>7917</MessageID> <Description>Offline Image Servicing Manager could not determine if binary %1 from an update with ID %2 is supported.</Description> </Message> <Message> <MessageID>7918</MessageID> <Description>Offline Image Servicing Manager: applicability check failed for binary %1 from an update with ID %2.</Description> </Message> <Message> <MessageID>7919</MessageID> <Description>Offline Image Servicing Manager failed to apply one or more updates on image with package ID %1 (image index %2), but continued offline servicing of the image on error per selected by user option.</Description> </Message> <Message> <MessageID>8000</MessageID> <Description>Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>8001</MessageID> <Description>Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>8002</MessageID> <Description>Portal Web Site Control Manager detected PORTALWEB is responding to HTTP requests.</Description> </Message> <Message> <MessageID>8003</MessageID> <Description>Portal Web Site Control Manager detected PORTALWEB is not able to save the Web.config.</Description> </Message> <Message> <MessageID>8004</MessageID> <Description>Portal Web Site Control Manager detected PORTALWEB can update the Web.config file.</Description> </Message> <Message> <MessageID>8005</MessageID> <Description>The application catalog website role did not find an SSL certificate required to communicate with the application catalog web service role.</Description> </Message> <Message> <MessageID>8100</MessageID> <Description>Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>8101</MessageID> <Description>Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>8102</MessageID> <Description>Application Web Service Control Manager detected AWEBSVC is responding to HTTP requests.</Description> </Message> <Message> <MessageID>8103</MessageID> <Description>Application Web Service Control Manager detected AWEBSVC is not able to save the Web.config.</Description> </Message> <Message> <MessageID>8104</MessageID> <Description>Application Web Service Control Manager detected AWEBSVC can update the Web.config file.</Description> </Message> <Message> <MessageID>8200</MessageID> <Description>Package Transfer Manager has successfully sent software distribution package "%1" version %2 to distibution point "%3".</Description> </Message> <Message> <MessageID>8201</MessageID> <Description>The address to distribution point server "%1" is invalid.%12</Description> </Message> <Message> <MessageID>8202</MessageID> <Description>The Package Transfer Manager cannot connect to distribution point server "%1" over the LAN.%12</Description> </Message> <Message> <MessageID>8203</MessageID> <Description>The Package Transfer Manager failed to send files to destination server "%1". Make sure the site server machine account or the site system connection account has full access to directory "%2" on the destination site server and the destination site server has sufficient free disk space.%12</Description> </Message> <Message> <MessageID>8204</MessageID> <Description>Package Transfer Manager is currently sending software distribution package %1 to distribution point server %2, %3 percent of the sending has already completed.</Description> </Message> <Message> <MessageID>8205</MessageID> <Description>Package Transfer Manager encountered errors while sending software distribution package %1 to distribution point server %2, %3 percent of the sending has already completed.</Description> </Message> <Message> <MessageID>8206</MessageID> <Description>Package Transfer Manager is retrying to distribute package "%1" to distribution point %2.%12 Wait to see if the package is successfully distributed on the retry.</Description> </Message> <Message> <MessageID>8207</MessageID> <Description>Package Transfer Manager has failed to distribute package "%1" to distribution point %2.%12 Please try to distribute the package again to this distribution point server.</Description> </Message> <Message> <MessageID>8208</MessageID> <Description>Package Transfer Manager has failed to verify hash for package "%1", Version %2 on distribution point %3.%12 Please try to distribute the package again to this distribution point server. If this package has been marked for prestaging on the distribution points then make sure the package has been correctly copied to the appropriate package folder on the distribution point server.</Description> </Message> <Message> <MessageID>8209</MessageID> <Description>Package Transfer Manager has successfully verified that the package "%1", Version %2 has been prestaged on distribution point %3.</Description> </Message> <Message> <MessageID>8210</MessageID> <Description>Package Transfer Manager has successfully updated the package "%1", Version %2 on distribution point %3.</Description> </Message> <Message> <MessageID>8211</MessageID> <Description>Package Transfer Manager failed to update the package "%1", Version %2 on distribution point %3. Review PkgXferMgr.log for more information about this failure.</Description> </Message> <Message> <MessageID>8212</MessageID> <Description>Package Transfer Manager failed to update the package "%1", Version %2 on pull distribution point %3. This pull distribution point has no sources from which it can download content. We will try again later.</Description> </Message> <Message> <MessageID>8300</MessageID> <Description>Enrollment Point Control Manager detected that the Enrollment Point is not responding to HTTP/HTTPS requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>8301</MessageID> <Description>Enrollment Point Control Manager detected Enrollment Point is not responding to HTTP/HTTPS requests. The http status code is %1.%12</Description> </Message> <Message> <MessageID>8302</MessageID> <Description>Enrollment Server is starting....</Description> </Message> <Message> <MessageID>8303</MessageID> <Description>Enrollment Point fails to connect to SQL server.%12</Description> </Message> <Message> <MessageID>8304</MessageID> <Description>Enrollment Point cannot accomplish tasks on the CA.%12</Description> </Message> <Message> <MessageID>8306</MessageID> <Description>ConfigMgr server cannot accomplish tasks in Active Directory.%12</Description> </Message> <Message> <MessageID>8307</MessageID> <Description>The Enrollment Point failed to revoke the certificate (Cert Serial Number: %1) issued to the device/requester %2 on the Certification Authority %3.%12</Description> </Message> <Message> <MessageID>8400</MessageID> <Description>Enrollment Point AD Service Control failed to read and configure the registry keys necessary for this component.%12</Description> </Message> <Message> <MessageID>8500</MessageID> <Description>Enrollment Proxy Point Control Manager detected that the Enrollment Proxy Point Component is not responding to HTTP/HTTPS requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>8501</MessageID> <Description>Enrollment Proxy Point Control Manager detected that the Enrollment Proxy Point Component is not responding to HTTP/HTTPS requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>8502</MessageID> <Description>Enrollment Proxy Point is starting....</Description> </Message> <Message> <MessageID>8600</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" was able to connect and authenticate successfully to Configuration Manager 2007 site server "%2".</Description> </Message> <Message> <MessageID>8601</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" was unable to connect to Configuration Manager 2007 site server "%2" due to network connection time out. Check the network connection and the firewall configuration between the two servers.</Description> </Message> <Message> <MessageID>8602</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" was unable to connect to Configuration Manager 2007 site server "%2" due to insufficient permissions. Ensure the account specified for the specified source Configuration Manager site is part of the local "SMS Admins" security group and has been granted full permissions to Configuration Manager 2007 site.</Description> </Message> <Message> <MessageID>8603</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" detected the specified site "%2" is not a valid Configuration Manager 2007 top-level site or stand-alone primary site. Please specify the fully qualified domain name of a Configuration Manager 2007 top-level site or stand-alone primary site as the source hierarchy.</Description> </Message> <Message> <MessageID>8604</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" has the same site code as the specified site "%2". Configuration Manager cannot migrate from sites with the same sitecode. Ensure the site codes are unique across both your Configuration Manager 2007 hierarchy and Configuration Manager 2012 hierarchy.</Description> </Message> <Message> <MessageID>8605</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" finished the data gathering process with Configuration Manager 2007 site server "%2".</Description> </Message> <Message> <MessageID>8606</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" started the migration job "%2 (%3)" to migrate "%4" objects from the source hierarchy.</Description> </Message> <Message> <MessageID>8607</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" stopped the migration job "%2 (%3)" per manual request through SDK or Console.</Description> </Message> <Message> <MessageID>8608</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" finished the migration job "%2 (%3)".</Description> </Message> <Message> <MessageID>8609</MessageID> <Description>The source hierarchy "%1" specified is not a valid Configuration Manager 2007 top-level site or stand-alone primary site.</Description> </Message> <Message> <MessageID>8610</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" was unable to complete the SQL operation on the SQL Server "%2" of Configuration Manager 2007 due to error "%3".</Description> </Message> <Message> <MessageID>8611</MessageID> <Description>The value "%1" configured for the parameter "%2" of Migration Manager is invalid.</Description> </Message> <Message> <MessageID>8612</MessageID> <Description>The migration job "%1" failed to copy content for some packages due to error "%2".</Description> </Message> <Message> <MessageID>8613</MessageID> <Description>Object %1 with path %2 have failed to migrate as part of migration job %3 (%4) which ran on site server %5 with error %6.</Description> </Message> <Message> <MessageID>8614</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" encountered a SQL query timeout. Please consider increasing the timeout value for the Migraton Manager by configuring the registry.</Description> </Message> <Message> <MessageID>8615</MessageID> <Description>The object "%1" being migrated is missing a dependency "%2". Confirm the configuration of the object "%1" in the Configuration Manager 2007 environment and initiate the "Gather Data Now" action in the console and recreate the migration job.</Description> </Message> <Message> <MessageID>8616</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" gathered from Configuration Manager 2007 site server "%3" "%2" new source sites.</Description> </Message> <Message> <MessageID>8617</MessageID> <Description>An unexpected error occurred in the Migration Manager on Configuration Manager site server "%1". Please refer to the migmctrl.log file for details.</Description> </Message> <Message> <MessageID>8618</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" encountered an error "%2" while performing SQL operations. Please refer to the migmctrl.log file for details.</Description> </Message> <Message> <MessageID>8619</MessageID> <Description>Updates Assignment "%1" includes Update "%2" (BulletinID "%3", ArticleID "%4", CI_ID "%5") which is not available on the destination site. Please ensure updates have been synchronized at the destination, or remove this Update from the Updates Assignment.</Description> </Message> <Message> <MessageID>8620</MessageID> <Description>The data gathering agent configuration type "%1" is not recognized.</Description> </Message> <Message> <MessageID>8621</MessageID> <Description>When connecting to "%1", the migration data gathering process encountered a source site code ("%2") already being used for mapping "%3" to "%4" (%5).</Description> </Message> <Message> <MessageID>8622</MessageID> <Description>The CI "%1" was made applicable to all platforms during migration.</Description> </Message> <Message> <MessageID>8623</MessageID> <Description>The CI "%1" is not applicable to any platforms after migration.</Description> </Message> <Message> <MessageID>8700</MessageID> <Description> SMS Rule Engine error. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>8701</MessageID> <Description> Rule Evaluation started. %12</Description> </Message> <Message> <MessageID>8702</MessageID> <Description> Rule Evaluation completed. %12</Description> </Message> <Message> <MessageID>8703</MessageID> <Description> Rule Evaluation failed. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>8704</MessageID> <Description> Content download started. %12</Description> </Message> <Message> <MessageID>8705</MessageID> <Description> Content download completed. %12</Description> </Message> <Message> <MessageID>8706</MessageID> <Description> Content download failed. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>8707</MessageID> <Description> Update group creation failed. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>8708</MessageID> <Description> Deployment creation failed. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>8800</MessageID> <Description>Connection to Exchange server %1 failed. Message: %2. %12</Description> </Message> <Message> <MessageID>8801</MessageID> <Description>Connection to Exchange server %1 failed.</Description> </Message> <Message> <MessageID>8802</MessageID> <Description>Connection to Exchange server %1 failed.</Description> </Message> <Message> <MessageID>8803</MessageID> <Description>Connection to Exchange server %1 failed.</Description> </Message> <Message> <MessageID>8810</MessageID> <Description>PowerShell 2.0 is not installed which is required by Exchange Connector component.</Description> </Message> <Message> <MessageID>8811</MessageID> <Description>Configuration is corrupted for %1.</Description> </Message> <Message> <MessageID>8812</MessageID> <Description>Policy setting %1 is invalid.</Description> </Message> <Message> <MessageID>8813</MessageID> <Description>Configured setting name %1 is invalid.</Description> </Message> <Message> <MessageID>8814</MessageID> <Description>Ignore configured on-premise Exchange server %1. The Exchange organization %2 for this server has already been configured on site %3 as server %4. %12</Description> </Message> <Message> <MessageID>8815</MessageID> <Description>Ignore configured hosted Exchange server %1. The Exchange organization %2 for this server has already been configured on site %3 as server %4 with credential %5. %12</Description> </Message> <Message> <MessageID>8816</MessageID> <Description>No default policy for Exchange server %1.</Description> </Message> <Message> <MessageID>8817</MessageID> <Description>Exchange cmdlet call failed. Cmdlet %1. ErrorId: %2 Message: %3 %12</Description> </Message> <Message> <MessageID>8818</MessageID> <Description>Exchange cmdlet %1 is not found.</Description> </Message> <Message> <MessageID>8819</MessageID> <Description>Exchange ActiveSync device %1 is not found in Exchange server %2.</Description> </Message> <Message> <MessageID>8831</MessageID> <Description>Connected to Exchange Server %1. Start full synchronization. %12</Description> </Message> <Message> <MessageID>8832</MessageID> <Description>Successfully ran the full synchronization on Exchange Server %1. %2 mobile devices has been discovered. %12</Description> </Message> <Message> <MessageID>8833</MessageID> <Description>Successfully ran the delta synchronization on Exchange Server %1. %2 mobile devices are updated. %12</Description> </Message> <Message> <MessageID>8834</MessageID> <Description>Global mobile device setting has been successfully synchronized to Exchange Server %1. %12</Description> </Message> <Message> <MessageID>8835</MessageID> <Description>Successfully send wipe request of the device %1 to Exchange Server %2. Waiting for the wipe confirmation. %12</Description> </Message> <Message> <MessageID>8836</MessageID> <Description>Received the wipe confirmation of the device %1. The device has been successfully wiped. %12</Description> </Message> <Message> <MessageID>8837</MessageID> <Description>Connected to Exchange Server %1. Start delta synchronization. %12</Description> </Message> <Message> <MessageID>8838</MessageID> <Description>Allow access request for Device %1 has been successfully sent to Exchange Server %2. %12</Description> </Message> <Message> <MessageID>8839</MessageID> <Description>Block access request for Device %1 has been successfully sent to Exchange Server %2. %12</Description> </Message> <Message> <MessageID>8840</MessageID> <Description>Organization DefaultAccessLevel and AdminEmailRecipients has been successfully synchronized to Exchange Server %1. %12</Description> </Message> <Message> <MessageID>8841</MessageID> <Description>Exchange ActiveSync access rule %1 has been successfully created on Exchange Server %2. %12</Description> </Message> <Message> <MessageID>8842</MessageID> <Description>Exchange ActiveSync access rule %1 has been successfully removed from Exchange Server %2. %12</Description> </Message> <Message> <MessageID>8900</MessageID> <Description>Active Directory Forest Discovery was run for forest %1 and discovered %5 IP subnets and %6 Active Directory sites.</Description> </Message> <Message> <MessageID>8901</MessageID> <Description>Active Directory Forest Discovery was run for forest %1 and it could not complete. The error code returned was %5.</Description> </Message> <Message> <MessageID>8902</MessageID> <Description>Active Directory Forest Discovery was not able to connect to Site Server database. Please see ADForestDisc.log for details. Active Directory Forest Discovery will be attempted on next cycle.</Description> </Message> <Message> <MessageID>8903</MessageID> <Description>Active Directory Forest Discovery was not able to use credentials supplied for account %5 to discover forest %1. Please check if credentials supplied to discovery the forest are valid.</Description> </Message> <Message> <MessageID>8904</MessageID> <Description>Active Directory Forest Discovery was not able to connect to forest %1. Error code returned is: %5. Forest discovery for this forest will be attempted again on next cycle.</Description> </Message> <Message> <MessageID>9100</MessageID> <Description>Alert notification sent notification email for Alert (ID:%1) successfully. %12</Description> </Message> <Message> <MessageID>9101</MessageID> <Description>Alert notification sent notification email failed for Alert (ID:%1), please check the email addresses of the sender(%2) and recipients(%3). %12</Description> </Message> <Message> <MessageID>9102</MessageID> <Description>Alert notification sent notification email failed for Alert (ID:%1), the email could not be delivered to recipients(%2). %12</Description> </Message> <Message> <MessageID>9103</MessageID> <Description>Alert notification sent notification email failed for Alert (ID:%1), an SMTP exception occured. %12</Description> </Message> <Message> <MessageID>9104</MessageID> <Description>Alert notification failed to initialize the SMTP client, please check the credential of user "%1". %12</Description> </Message> <Message> <MessageID>9200</MessageID> <Description>Endpoint Protection Control Manager failed to update malware definition. Verify that the Endpoint Protection client is installed and running on the Endpoint Protection role server. Verify that the Endpoint Protection client on the role server can receive updated definitions. Error code returned is:"%1". %12</Description> </Message> <Message> <MessageID>9201</MessageID> <Description>Endpoint Protection Manager failed to generate malware detection alerts for type:"%1". Verify that the site database is configured correctly. Error code returned is:"%2". %12</Description> </Message> <Message> <MessageID>9300</MessageID> <Description>Cloud Content Manager encountered an internal error [%1] Check logs for details.</Description> </Message> <Message> <MessageID>9301</MessageID> <Description>Cloud Content Manager was unable to encrypt content for the package %1.</Description> </Message> <Message> <MessageID>9302</MessageID> <Description>Cloud Content Manager was unable to connect to the service %1.</Description> </Message> <Message> <MessageID>9303</MessageID> <Description>Cloud Content Manager was unable to determine the upload location for the package %1.</Description> </Message> <Message> <MessageID>9304</MessageID> <Description>Cloud Content Manager was unable to find the content source [%1] for package %2.</Description> </Message> <Message> <MessageID>9305</MessageID> <Description>Cloud Content Manager was unable to encrypt the file %1.</Description> </Message> <Message> <MessageID>9306</MessageID> <Description>Cloud Content Manager was unable to access the storage account for %1.</Description> </Message> <Message> <MessageID>9307</MessageID> <Description>Cloud Content Manager was unable to get content key for content %1.</Description> </Message> <Message> <MessageID>9308</MessageID> <Description>Cloud Content Manager encountered blank content XML for %1.</Description> </Message> <Message> <MessageID>9309</MessageID> <Description>Cloud Content Manager was unable to mark the upload status as completed for %1.</Description> </Message> <Message> <MessageID>9310</MessageID> <Description>Cloud Content Manager encountered an empty download address from content upload for package %1.</Description> </Message> <Message> <MessageID>9311</MessageID> <Description>Cloud Content Manager was unable to connect to the cloud distribution point service when trying to distribute package %1.</Description> </Message> <Message> <MessageID>9400</MessageID> <Description>Cloud Services Manager encountered an internal error, %1.</Description> </Message> <Message> <MessageID>9401</MessageID> <Description>Cloud Services Manager task [%1] has failed, exception %2.</Description> </Message> <Message> <MessageID>9402</MessageID> <Description>Cloud Services Manager task [%1] has been canceled.</Description> </Message> <Message> <MessageID>9403</MessageID> <Description>Cloud Services Manager created service %1 in region %2.</Description> </Message> <Message> <MessageID>9404</MessageID> <Description>Cloud Services Manager created a deployment for service %1 in region %2.</Description> </Message> <Message> <MessageID>9405</MessageID> <Description>Cloud Services Manager has started provisioning service %1 in region %2.</Description> </Message> <Message> <MessageID>9406</MessageID> <Description>Cloud Services Manager has configured storage account %1 for service %2.</Description> </Message> <Message> <MessageID>9407</MessageID> <Description>Cloud Services Manager has uploaded the service package for service %1 to %2.</Description> </Message> <Message> <MessageID>9408</MessageID> <Description>Service %1 in region %2 is ready for use.</Description> </Message> <Message> <MessageID>9409</MessageID> <Description>Cloud Services Manager has successfully provisioned service %1 in region %2.</Description> </Message> <Message> <MessageID>9410</MessageID> <Description>Cloud Services Manager failed to provision service %1 in region %2. Please see cloudmgr.log for more details.</Description> </Message> <Message> <MessageID>9411</MessageID> <Description>Cloud Services Manager is unable to connect to Windows Azure for subscription Id %1. Please check your proxy configuration.</Description> </Message> <Message> <MessageID>9412</MessageID> <Description>Cloud Services Manager is starting to uninstall service %1.</Description> </Message> <Message> <MessageID>9413</MessageID> <Description>Cloud Services Manager has completed the uninstall for service %1.</Description> </Message> <Message> <MessageID>9414</MessageID> <Description>Cloud Services Manager has failed to uninstall service %1. Please delete the deployment using the Windows Azure portal.</Description> </Message> <Message> <MessageID>9415</MessageID> <Description>Cloud Services Manager has failed to authenticate for subscription Id %1. Please check that the management certificate is property configured.</Description> </Message> <Message> <MessageID>9416</MessageID> <Description>Cloud Services Manager has started maintenance for service %1.</Description> </Message> <Message> <MessageID>9417</MessageID> <Description>Cloud Services Manager has completed maintenance for service %1.</Description> </Message> <Message> <MessageID>9418</MessageID> <Description>Cloud Services Manager has failed to complete maintenance for service %1.</Description> </Message> <Message> <MessageID>9419</MessageID> <Description>Cloud Services Manager has requested the deployment to start for service %1.</Description> </Message> <Message> <MessageID>9420</MessageID> <Description>Cloud Services Manager has started the deployment for service %1.</Description> </Message> <Message> <MessageID>9421</MessageID> <Description>Cloud Services Manager has failed to start the deployment for service %1. Exception %2.</Description> </Message> <Message> <MessageID>9422</MessageID> <Description>Cloud Services Manager has requested the deployment to stop for service %1.</Description> </Message> <Message> <MessageID>9423</MessageID> <Description>Cloud Services Manager has stopped the deployment for service %1.</Description> </Message> <Message> <MessageID>9424</MessageID> <Description>Cloud Services Manager has failed to stop the deployment for service %1. Exception %2.</Description> </Message> <Message> <MessageID>9425</MessageID> <Description>The %1 certificate was invalid for cloud service %2. Please check CloudMgr.log for further details.</Description> </Message> <Message> <MessageID>9426</MessageID> <Description>Service Monitor could not find service %1. Please check the status of the service through the azure portal.</Description> </Message> <Message> <MessageID>9427</MessageID> <Description>Service Monitor found that the Deployment %1 is in %2 state. Expected state is 'Running'. Please check the status of the deployment through the azure portal.</Description> </Message> <Message> <MessageID>9428</MessageID> <Description>Service Monitor could not find the Deployment %1. Please check the status of the deployment through the azure portal.</Description> </Message> <Message> <MessageID>9429</MessageID> <Description>Service Monitor received exception while monitoring service %1. Please check CloudMgr.log for further details. Exception: %2.</Description> </Message> <Message> <MessageID>9430</MessageID> <Description>Service Monitor found the deployment in running state for service %1.</Description> </Message> <Message> <MessageID>9431</MessageID> <Description>Storage account was not found for service %1.</Description> </Message> <Message> <MessageID>9500</MessageID> <Description>PXE is enabled on distribution point %1</Description> </Message> <Message> <MessageID>9501</MessageID> <Description>PXE is disabled on distribution point %1</Description> </Message> <Message> <MessageID>9502</MessageID> <Description>Multicast is enabled on distribution point %1</Description> </Message> <Message> <MessageID>9503</MessageID> <Description>Multicast is disabled on distribution point %1</Description> </Message> <Message> <MessageID>9504</MessageID> <Description>Distribution Point un-installation successfully completed on server "%1".</Description> </Message> <Message> <MessageID>9505</MessageID> <Description>Distribution Point un-installation failed to complete on server "%1".</Description> </Message> <Message> <MessageID>9506</MessageID> <Description>Package distribution cancelled by user for package "%1" on distribution point "%2".</Description> </Message> <Message> <MessageID>9507</MessageID> <Description>Pull Distribution Point "%1" started downloading package "%2".</Description> </Message> <Message> <MessageID>9508</MessageID> <Description>Pull Distribution Point "%1" is currently downloading package "%2". %3 percent download has completed.</Description> </Message> <Message> <MessageID>9509</MessageID> <Description>Pull Distribution Point "%1" completed downloading package "%2" and is now performing post download actions.</Description> </Message> <Message> <MessageID>9510</MessageID> <Description>Distribution Manager is sending package "%1" to connector on "%2".%12</Description> </Message> <Message> <MessageID>9511</MessageID> <Description>Distribution Manager failed to send package "%1" to connector on "%2".%12</Description> </Message> <Message> <MessageID>9512</MessageID> <Description>Distribution Manager sent package "%1" to connector on "%2".%12</Description> </Message> <Message> <MessageID>9513</MessageID> <Description>Connector is unable to upload version %1 of package "%2" to Windows Intune because a newer version of the package exists. %12</Description> </Message> <Message> <MessageID>9514</MessageID> <Description>The hash of package "%1" is invalid on connector "%2". Please redistribute the package.</Description> </Message> <Message> <MessageID>9515</MessageID> <Description>Successfully validated the content of package "%1" on connector "%2".</Description> </Message> <Message> <MessageID>9516</MessageID> <Description>Started uploading package "%1" to Windows Azure Intune from connector "%2".</Description> </Message> <Message> <MessageID>9517</MessageID> <Description>Failed to validate package "%1" on package share on distribution point "%2".</Description> </Message> <Message> <MessageID>9518</MessageID> <Description>The hash of package "%1" on package share on distribution point "%2", is invalid. Please redistribute it.</Description> </Message> <Message> <MessageID>9519</MessageID> <Description>The package "%1" was processed successfully, but was not copied to the Windows Intune distribution point. To be copied to the Windows Intune distribution point, the package must contain a deployment type that is supported by devices that are enrolled by Windows Intune which include Windows RT, Windows Phone 8, Android, or iOS.</Description> </Message> <Message> <MessageID>9600</MessageID> <Description>Failed to initialize. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9601</MessageID> <Description>Site has finished processing resync request for replicationgroup [%1]. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9602</MessageID> <Description>Received drs_syncstart message for replicationgroup [%1], however it is pending resync. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9603</MessageID> <Description>Received resync request for replicationgroup [%1] to version %2. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9604</MessageID> <Description>StartUpload replicationgroup [%1] last sync version %2 failed with status code %3 and error code %4. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9605</MessageID> <Description>Upload transmission [%1] blockID %2 failed with status code %3 and error code %4. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9606</MessageID> <Description>EndUpload transmission [%1] blockID %2 failed with status code %3 and error code %4. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9607</MessageID> <Description>Failed to upload. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9608</MessageID> <Description>Site has finished uploading. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9700</MessageID> <Description>Failed to initialize. Please refer to dmpdownloader.log for further details.</Description> </Message> <Message> <MessageID>9701</MessageID> <Description>Failed to download. Please refer to dmpdownloader.log for further details.</Description> </Message> <Message> <MessageID>9702</MessageID> <Description>Site has finished uploading. Please refer to dmpdownloader.log for further details.</Description> </Message> <Message> <MessageID>9800</MessageID> <Description>Notification Server on %1 failed to initialize.%12</Description> </Message> <Message> <MessageID>9801</MessageID> <Description>Notification Server on %1 initialized successfully.</Description> </Message> <Message> <MessageID>9802</MessageID> <Description>Windows Firewall on %1 does not allow clients to connect to the Notification Server via TCP port %2.%12</Description> </Message> <Message> <MessageID>9803</MessageID> <Description>Windows Firewall on %1 allows clients to connect to Notification Server via TCP port %2.</Description> </Message> <Message> <MessageID>9804</MessageID> <Description>Notification Server on %1 failed to connect to the site database %2.%12</Description> </Message> <Message> <MessageID>9805</MessageID> <Description>Notification Server on %1 successfully connected to the site database %2.</Description> </Message> <Message> <MessageID>9806</MessageID> <Description>Notification Server on %1 failed to initialize the TCP listener on port %2.%12</Description> </Message> <Message> <MessageID>9807</MessageID> <Description>Notification Server on %1 successfully initialized the TCP listener on port %2.</Description> </Message> <Message> <MessageID>9900</MessageID> <Description>Notification Manager failed to initialize.%12</Description> </Message> <Message> <MessageID>9901</MessageID> <Description>Notification Manager initialized successfully.</Description> </Message> <Message> <MessageID>9902</MessageID> <Description>The SQL Server Service Broker %1 used by Notification Manager is disabled.%12</Description> </Message> <Message> <MessageID>9903</MessageID> <Description>The SQL Server Service Broker %1 used by Notification Manager is enabled.</Description> </Message> <Message> <MessageID>10000</MessageID> <Description>Failed to initialize. Please refer to cloudusersync.log for further details.</Description> </Message> <Message> <MessageID>10001</MessageID> <Description>A data integrity error was detected for package "%1" (%2%1.pkg).%12</Description> </Message> <Message> <MessageID>10002</MessageID> <Description>Deployment "%1" was received from site "%2".%12 The client passes any supported platform requirements and Configuration Manager will add the Deployment's program to the list that will be displayed to users and/or run via assignment. If a deployment is received but not displayed on a client, verify that the current time on the client is between the deployment start and expiration times, and that the program specified in the deployment is enabled.</Description> </Message> <Message> <MessageID>10003</MessageID> <Description>An error occurred while preparing to run the program for deployment "%1" ("%4" - "%5").%12Additional program properties: Command line: %2 Working directory: %3 Drive letter (? = any): %6</Description> </Message> <Message> <MessageID>10004</MessageID> <Description>The program for deployment "%1" could not be executed ("%4" - "%5").%12Additional program properties: Command line: %2 Working directory: %3 The command line for the program cannot be executed successfully.</Description> </Message> <Message> <MessageID>10005</MessageID> <Description>Program started for deployment "%1" ("%4" - "%5").%12 Command line: %2 Working directory: %3 User context: %9</Description> </Message> <Message> <MessageID>10006</MessageID> <Description>CloudUserSync - Empty principal names found for users in cloud collection. Some users were not enabled for cloud services. Please refer to cloudusersync.log for further details.</Description> </Message> <Message> <MessageID>10007</MessageID> <Description>The program for deployment "%1" failed ("%4" - "%5"). The failure description was "%3%7%8%9". User context: %2%12</Description> </Message> <Message> <MessageID>10008</MessageID> <Description>The program for deployment "%1" completed successfully ("%4" - "%5"). User context: %9%12 Configuration Manager determines status for each program it executes. If Configuration Manager cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. This program returned an exit code that indicates it completed successfully.</Description> </Message> <Message> <MessageID>10009</MessageID> <Description>The program for deployment "%1" completed successfully ("%4" - "%5"). The success description was "%3%7%8%9". User context: %2%12 The program generated an installation status Management Information Format (MIF) file with a status value of Success. For more information, see the documentation for the program you are distributing.</Description> </Message> <Message> <MessageID>10010</MessageID> <Description>An error occurred while preparing to run the uninstall program for deployment "%1" ("%4" - "%5").%12 Additional program properties: Command line: %2 Working directory: %3 Drive letter (? = any): %6</Description> </Message> <Message> <MessageID>10018</MessageID> <Description>Deployment "%1" from site "%2" was rejected because the client's platform is not supported.%12</Description> </Message> <Message> <MessageID>10019</MessageID> <Description>Deployment "%1" from site "%2" was rejected because the deployment has expired.%12</Description> </Message> <Message> <MessageID>10021</MessageID> <Description>The program for deployment "%1" failed ("%4" - "%5"). The program was able to be executed but the system was restarted unexpectedly before the program could be completed or before status could be recorded. No installation status MIF was found after the system restarted.%12</Description> </Message> <Message> <MessageID>10022</MessageID> <Description>The program for deployment "%1" ("%4" - "%5") returned an exit code of "%2"("%12"), which indicates the operation was successful but a restart of the system is required for the operation to be complete. A restart might be pending because there is no maintenance window open. The restart will occur at the next available maintenance window. A status message indicating final success will be sent after the system has been restarted. Configuration Manager determines status for each program it executes. Any program dependencies will not be executed until after the restart occurs. If Configuration Manager cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status.</Description> </Message> <Message> <MessageID>10025</MessageID> <Description>Download of the content "%4" - "%2" has failed.%12.</Description> </Message> <Message> <MessageID>10026</MessageID> <Description>The content for "%4" - "%2" has been removed from the cache. This content has been deleted because either the cache has been automatically cleaned or the cache was deleted manually. The current cache size is %8 MB, and %7 MB of cache space is available.</Description> </Message> <Message> <MessageID>10027</MessageID> <Description>The cache size has been modified from %6 MB to %7 MB. The cache is located at %3.</Description> </Message> <Message> <MessageID>10029</MessageID> <Description>The cache location has been modified. The cache was previously located at %2. The cache is now located at %3. The current cache size is %7 MB. The contents of the cache have been cleared as a result of this change.</Description> </Message> <Message> <MessageID>10030</MessageID> <Description>Download of the content "%4" - "%2" has failed. The download failed because the content downloaded to the client does not match the content specified in the source.</Description> </Message> <Message> <MessageID>10034</MessageID> <Description>The program for the deployment "%1" ("%4" - "%5") has been cancelled due to a user request.</Description> </Message> <Message> <MessageID>10035</MessageID> <Description>The program for deployment "%1 has not yet started because the content for the package "%4" - "%5" (version %2) has not been acquired.</Description> </Message> <Message> <MessageID>10036</MessageID> <Description>The program for deployment "%1" has not be run yet ("%4" - "%5"). The program settings indicate that this program has a user logon condition that must be satisfied before it can be run, and this condition has not yet been satisfied. This program will run once the user logon condition is satisfied.</Description> </Message> <Message> <MessageID>10037</MessageID> <Description>The program for deployment "%1" has not been run yet ("%4" - "%5"). ConfigMgr is currently running another program ("%2" - "%3") on this computer, and that program must complete before this one can begin.</Description> </Message> <Message> <MessageID>10040</MessageID> <Description>The program for deployment "%1" will not be run ("%4" - "%5"). The program settings indicate that this program should only be run on computers where the previous attempt to run this program was not successful. The previous attempt to run this program was successful. This program was previously run successfully at %6.</Description> </Message> <Message> <MessageID>10041</MessageID> <Description>The program for deployment "%1" will not be run ("%4" - "%5"). The program settings indicate that this program should only be run on computers where the previous attempt to run this program was successful. The previous attempt to run this program was not successful. This program attempted to run unsuccessfully at %6.</Description> </Message> <Message> <MessageID>10042</MessageID> <Description>The program for deployment "%1" will not be run ("%4" - "%5"). The program settings indicate that this program should never be run on computers where a previous attempt to run this program has occurred. This program has been attempted on this computer. The program was previously attempted at %6.</Description> </Message> <Message> <MessageID>10043</MessageID> <Description>The program for deployment "%1" will not be run ("%4" - "%5"). The program settings indicate that this program should only be run on computers where a previous attempt to run this program has occurred. This program has never before been attempted on this computer.</Description> </Message> <Message> <MessageID>10045</MessageID> <Description>The program for the deployment "%1" ("%4" - "%5") requires content to be downloaded, but the cache does not have enough space. The current cache size is %8 MB, of which %7 MB is available. The current amount of free disk space on the cache volume is %9 MB. This program requires %6 MB to be available in the cache.</Description> </Message> <Message> <MessageID>10046</MessageID> <Description>Windows Installer per-user elevation of this program ("%4" - "%5") failed for deployment "%1".%12This program was started. Please check the status of this program to determine whether or not it was completed successfully.</Description> </Message> <Message> <MessageID>10050</MessageID> <Description>The program for the deployment "%1" ("%4" - "%5") requires content to be downloaded, but the total cache size is smaller than the size of the content. The current cache size is %8 MB, and %7 MB of cache space is available. This program requires %6 MB to be available in the cache.</Description> </Message> <Message> <MessageID>10051</MessageID> <Description>The content for "%4" - "%2" could not be located. This client will no longer attempt to locate this content.</Description> </Message> <Message> <MessageID>10052</MessageID> <Description>The program for the deployment "%1" ("%4" - "%5") could not be run because the policy contains an invalid combination of requirements: %2.</Description> </Message> <Message> <MessageID>10053</MessageID> <Description>The program for deployment "%1 has failed because download of the content "%4" - "%2" has failed.</Description> </Message> <Message> <MessageID>10054</MessageID> <Description>The program for the deployment "%1" ("%4" - "%5") requires content to be downloaded, but the cache does not have enough space. The current cache size is %8 MB, of which %7 MB is available. The current amount of free disk space on the cache volume is %9 MB. This program requires %6 MB to be available in the cache.</Description> </Message> <Message> <MessageID>10055</MessageID> <Description>An error occurred while preparing to run the program for deployment "%1" ("%4" - "%5").%12Additional program properties: Command line: %2 Working directory: %3 Drive letter (? = any): %6</Description> </Message> <Message> <MessageID>10056</MessageID> <Description>The program for deployment "%1" could not be executed ("%4" - "%5").%12Additional program properties: Command line: %2 Working directory: %3 The command line for the program cannot be executed successfully.</Description> </Message> <Message> <MessageID>10057</MessageID> <Description>The program for deployment "%1 has failed because download of the content "%4" - "%5" has failed. The download failed because the content downloaded to the client does not match the content specified in the content source.</Description> </Message> <Message> <MessageID>10058</MessageID> <Description>The program for deployment "%1 has failed because download of the content "%4" - "%2" has failed.</Description> </Message> <Message> <MessageID>10060</MessageID> <Description>The content for "%4" - "%2" can not be located. This client will attempt to locate this content again.</Description> </Message> <Message> <MessageID>10061</MessageID> <Description>The program for deployment "%1 has failed because download of the content "%4" - "%2" has failed.</Description> </Message> <Message> <MessageID>10062</MessageID> <Description>The program for deployment "%1 has failed because download of the content "%4" - "%2" has failed.</Description> </Message> <Message> <MessageID>10070</MessageID> <Description>The program for deployment "%1" ("%4" - "%5") exceeded the maximum allowed run time of %2 minute(s). Configuration Manager has stopped monitoring the program, and is unable to determine the status of the program. ConfigMgr will not automatically attempt to run this program again.</Description> </Message> <Message> <MessageID>10071</MessageID> <Description>The program for deployment "%1" ("%4" - "%5") could not be monitored. Configuration Manager has assumed this program failed and will attempt to run the program again.</Description> </Message> <Message> <MessageID>10072</MessageID> <Description>The program for deployment "%1" failed ("%4" - "%5"). A failure exit code of %2 was returned. User context: %9%12</Description> </Message> <Message> <MessageID>10073</MessageID> <Description>The program for deployment "%1" ("%4" - "%5") has not yet started because no maintenance window is currently available. The Program will be retried when a maintenance window becomes available.</Description> </Message> <Message> <MessageID>10074</MessageID> <Description>The program for deployment "%1" failed ("%4" - "%5"). There is no maintenance window with a duration at least as large as the program's defined maximum runtime. Consequently, the program may never run on the client.</Description> </Message> <Message> <MessageID>10075</MessageID> <Description>A deployment has completed and requires the machine to restart but the restart cannot be performed due to maintenance window restrictions. The restart is waiting for the next available maintenance window.</Description> </Message> <Message> <MessageID>10076</MessageID> <Description>A deployment has completed and requires the machine to restart. The machine will restart now, and will not adhere to any maintenance window restrictions.</Description> </Message> <Message> <MessageID>10077</MessageID> <Description>The deployment "%1" ("%4" - "%5") is waiting for package content from an Intranet-based Distribution Point. The system is Internet based and cannot run the program directly from a UNC location over the internet.</Description> </Message> <Message> <MessageID>10078</MessageID> <Description>The deployment "%1" ("%4" - "%5") failed to locate the package content on a distribution point that is not on the internet. The system is internet based and was unable to locate an intranet based distribution point before the retry limit was reached.</Description> </Message> <Message> <MessageID>10079</MessageID> <Description>A restart is pending for a deployment. There is no maintenance window available for this computer that will allow the restart to occur.</Description> </Message> <Message> <MessageID>10080</MessageID> <Description>The program for deployment "%1" failed ("%4" - "%5"). Operating System Deployment task sequences cannot run when the computer is on the Internet.</Description> </Message> <Message> <MessageID>10081</MessageID> <Description>The client failed to verify the BranchCache contentinfo file for content %1, downloaded from the server "%2". The error return was %3. Try redistributing the content to this server to resolve this issue.%12</Description> </Message> <Message> <MessageID>10090</MessageID> <Description>The Windows Installer source paths have been successfully updated on this computer.</Description> </Message> <Message> <MessageID>10091</MessageID> <Description>The Windows Installer source paths on this computer failed to update. The failure was caused by error %12. The update will be retried.</Description> </Message> <Message> <MessageID>10092</MessageID> <Description>The Windows Installer source paths on this computer failed to update. The failure was caused by error %12. The update will not be retried.</Description> </Message> <Message> <MessageID>10093</MessageID> <Description>The Windows Installer source paths on this computer failed to update. The client was unable to determine the correct locations for the Windows Installer program.</Description> </Message> <Message> <MessageID>10094</MessageID> <Description>The Windows Installer source paths on this computer failed to update. The client was unable to determine the correct locations for the Windows Installer program.</Description> </Message> <Message> <MessageID>10100</MessageID> <Description>The APNs account cert has expired, follow the Request Apple Notification Service CSR process to request a new APNs account cert.</Description> </Message> <Message> <MessageID>10101</MessageID> <Description>An update is required for Windows Intune integration with Configuration Manager. More information on the update can be found here: %1.</Description> </Message> <Message> <MessageID>10201</MessageID> <Description>Certificate Registration Point is responding to HTTP requests.%12</Description> </Message> <Message> <MessageID>10202</MessageID> <Description>Certificate Registration Point is not responding to HTTP requests. The error encountered was %1. Please refer to crpctrl.log for further details.%12</Description> </Message> <Message> <MessageID>10203</MessageID> <Description>Network Device Enrollment Service %1 is responding to HTTPS requests.%12</Description> </Message> <Message> <MessageID>10204</MessageID> <Description>Network Device Enrollment Service %1 is not responding to HTTPS requests. The error encountered was %1. Please refer to crpctrl.log for further details.%12</Description> </Message> <Message> <MessageID>10205</MessageID> <Description>Certificate is issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4. This certificate was issued against CI Id %5. Certificate is valid till %6.%12</Description> </Message> <Message> <MessageID>10206</MessageID> <Description>Certificate deployed to machine/device %1 (GUID:%2) for user %3 with thumbprint %4 has expired. This certificate was issued against CI Id %5.%12</Description> </Message> <Message> <MessageID>10207</MessageID> <Description>Certificate issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4 was revoked successfully. This certificate was issued against CI Id %5.%12</Description> </Message> <Message> <MessageID>10208</MessageID> <Description>Certificate Registration Point failed to revoke certificate issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4. This certificate was issued against CI Id %5. The error encountered was %6.%12</Description> </Message> <Message> <MessageID>10209</MessageID> <Description>Certificate is renewed for machine/device %1 (GUID:%2) for user %3. Old thumbprint of the certificate is %4. New thumbprint of the certificate is %5. This certificate was issued against CI Id %6. New certificate is valid till %7.%12</Description> </Message> <Message> <MessageID>10210</MessageID> <Description>Certificate Registration Point failed to renew certificate issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4. This certificate was issued against CI Id %5. The error encountered was %6.%12</Description> </Message> <Message> <MessageID>10301</MessageID> <Description>The Certificate Manager failed to revoke the certificate (Cert Serial Number: %1) issued to the device/requester %2/%3 on the Certification Authority %4.%12</Description> </Message> <Message> <MessageID>10500</MessageID> <Description>Hardware Inventory Agent successfully collected hardware inventory from this computer.</Description> </Message> <Message> <MessageID>10501</MessageID> <Description>Hardware Inventory Agent cannot connect to the Common Information Model Object Manager (CIM Object Manager).%12</Description> </Message> <Message> <MessageID>10502</MessageID> <Description>Hardware Inventory Agent cannot open the "%1" namespace.%12</Description> </Message> <Message> <MessageID>10503</MessageID> <Description>The "%1" namespace has been removed or has become corrupted.%12</Description> </Message> <Message> <MessageID>10504</MessageID> <Description>Hardware Inventory Agent has insufficient virtual memory or disk space to proceed. The inventory cycle will be delayed by as much as 8 hours.%12</Description> </Message> <Message> <MessageID>10505</MessageID> <Description>The Hardware Inventory schema has been updated successfully with a new Managed Object Format (MOF) file from site "%1". The Hardware Inventory Agent will use this updated MOF file in all subsequent inventory cycles.%12</Description> </Message> <Message> <MessageID>10506</MessageID> <Description>Hardware Inventory Agent cannot update the Hardware Inventory Schema.%12</Description> </Message> <Message> <MessageID>10507</MessageID> <Description>SMS Hardware Inventory Agent cannot update the SMS Hardware Inventory Schema. The new Managed Object Format (MOF) file from site "%1" cannot be compiled. The agent will continue attempting to recompile this MOF file and will use the default file sms_def.mof until it is successful.%12</Description> </Message> <Message> <MessageID>10508</MessageID> <Description>Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12</Description> </Message> <Message> <MessageID>10509</MessageID> <Description>Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12</Description> </Message> <Message> <MessageID>10510</MessageID> <Description>Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12</Description> </Message> <Message> <MessageID>10511</MessageID> <Description>Hardware Inventory Agent is unable to locate the Windows Management Instrumentation (WinMgmt) service.%12</Description> </Message> <Message> <MessageID>10600</MessageID> <Description>Software Inventory Agent successfully collected software inventory from this computer.%12</Description> </Message> <Message> <MessageID>10601</MessageID> <Description>Software Inventory Agent has insufficient virtual memory or disk space to proceed. The inventory cycle will be delayed by as much as 8 hours.%12</Description> </Message> <Message> <MessageID>10602</MessageID> <Description>Software Inventory Agent could not collect one or more files.%12</Description> </Message> <Message> <MessageID>10603</MessageID> <Description>Software Inventory Agent was unable to collect one or more files because the maximum size for collected files of %1 MB has been reached.%12</Description> </Message> <Message> <MessageID>10604</MessageID> <Description>Software Inventory Agent raised an exception while attempting to extract file version information from file "%1".%12</Description> </Message> <Message> <MessageID>10605</MessageID> <Description>Software Inventory Agent successfully collected %1 files, totally %2 KB of data, from this computer. These files will be transfered to the Site Server as part of the Software Inventory (SINV) file.%12</Description> </Message> <Message> <MessageID>10650</MessageID> <Description>File collection has successfully run on this computer. A total of %1 files (%2 KB) were collected that match the following path and file name: %3 %12</Description> </Message> <Message> <MessageID>10651</MessageID> <Description>The agent has not collected files matching the file name "%1" or the path "%2" from this computer because the files exceed the maximum size limit of %3 KB. You may need to reconfigure the maximum size limit to allow file collection at the next scheduled agent interval.%12</Description> </Message> <Message> <MessageID>10700</MessageID> <Description>Inventory was collected successfully on this computer. The agent completed in %1 minutes, %2 seconds.%12</Description> </Message> <Message> <MessageID>10701</MessageID> <Description>Inventory was collected successfully on this computer. The agent completed in %1 minutes, %2 seconds and generated inventory data report %3. %12</Description> </Message> <Message> <MessageID>10702</MessageID> <Description>The agent encountered an error while querying WMI to collect data from this computer. The first query to fail was "%1".%12</Description> </Message> <Message> <MessageID>10703</MessageID> <Description>The agent encountered an error while collecting data from this computer.</Description> </Message> <Message> <MessageID>10704</MessageID> <Description>The agent encountered an error while generating the inventory report (%1) for this computer.%12</Description> </Message> <Message> <MessageID>10800</MessageID> <Description>The ConfigMgr client was installed. The current version is %1.%12</Description> </Message> <Message> <MessageID>10801</MessageID> <Description>The ConfigMgr client was uninstalled.%12</Description> </Message> <Message> <MessageID>10802</MessageID> <Description>The ConfigMgr client was upgraded. The current version is %1.%12</Description> </Message> <Message> <MessageID>10803</MessageID> <Description>The client failed to download policy. The data transfer service returned "%2" (%1).%12</Description> </Message> <Message> <MessageID>10804</MessageID> <Description>The ConfigMgr client was reassigned. The previous site code was "%1". The new site code is "%2".%12</Description> </Message> <Message> <MessageID>10805</MessageID> <Description>The ConfigMgr Client has determined that its policy is incorrect. A full policy update will be requested to correct the issue. For more information see PolicyAgent.log on the client machine.%12</Description> </Message> <Message> <MessageID>10806</MessageID> <Description>An attempt to assign the ConfigMgr client to site "%1" failed. The site code could not be verified.%12</Description> </Message> <Message> <MessageID>10807</MessageID> <Description>The ConfigMgr client is already assigned to site "%1". The client site assignment was not changed.%12</Description> </Message> <Message> <MessageID>10808</MessageID> <Description>The client failed to compile one or more policies. For more information see PolicyAgentEvaluator.log on the client machine. Policy ID: %1 Policy Version: %2 Policy Source: %3 Error: %4 Object: %5 Lines: %6 - %7 %12</Description> </Message> <Message> <MessageID>10809</MessageID> <Description>The ConfigMgr client was repaired. The current version is %1.%12</Description> </Message> <Message> <MessageID>10810</MessageID> <Description>The SMS Service Host (CCMEXEC) has entered Low Memory Mode. The machine has %2 meg(s) available RAM + pagefile, which falls below the threshold of %1 meg(s). Some functionality will be disabled until more memory becomes available.%12</Description> </Message> <Message> <MessageID>10811</MessageID> <Description>The SMS Service Host (CCMEXEC) has recovered from Low Memory Mode. The machine has %2 meg(s) available RAM + pagefile, which exceeds the recovery threshold of %1 meg(s). All functionality will now be enabled.%12</Description> </Message> <Message> <MessageID>10812</MessageID> <Description>The SMS Service Host (CCMEXEC) was unable to update certificate information in the Active Directory.%12</Description> </Message> <Message> <MessageID>10813</MessageID> <Description>The SMS Service Host (CCMEXEC) successfuly updated certificate information in the Active Directory. %12</Description> </Message> <Message> <MessageID>10814</MessageID> <Description>The ConfigMgr client was installed but may require a reboot for the installation to complete.%12</Description> </Message> <Message> <MessageID>10815</MessageID> <Description>The SMS Service Host (CCMEXEC) encountered a failure (%1) when performing Certificate operations.%12</Description> </Message> <Message> <MessageID>10816</MessageID> <Description>The ConfigMgr Client generated a new SMS Unique Identifier. The old SMS Unique ID was %2. The new SMS Unique ID is %1.%12</Description> </Message> <Message> <MessageID>10817</MessageID> <Description>The ConfigMgr Client rejected the site server signing certificate due to a revocation-related failure (%1).%12</Description> </Message> <Message> <MessageID>10818</MessageID> <Description>The ConfigMgr Client rejected the site server signing certificate due to an expiration-related failure (%1).%12</Description> </Message> <Message> <MessageID>10819</MessageID> <Description>The ConfigMgr Client rejected the site server signing certificate due to a trust-related failure (%1).%12</Description> </Message> <Message> <MessageID>10820</MessageID> <Description>The ConfigMgr Client encounted an SSL-related failure (%1) when using BITS to access location %2.%12</Description> </Message> <Message> <MessageID>10821</MessageID> <Description>The ConfigMgr Client received policy that could not be verified. For more information see PolicyAgent.log on the client machine.%12</Description> </Message> <Message> <MessageID>10822</MessageID> <Description>The ConfigMgr Client encountered a certificate for Management Point %1 that could not be verified.%12</Description> </Message> <Message> <MessageID>10900</MessageID> <Description>Software Metering Agent encountered an error while collecting %1 data from WMI, error code %2. The Agent will not be able to generate the usage report in this cycle.%12</Description> </Message> <Message> <MessageID>10901</MessageID> <Description>Software Metering Agent failed to create %1 usage data file, error code %2.%12</Description> </Message> <Message> <MessageID>10902</MessageID> <Description>Software Metering Agent failed to upload %1 usage data file, error code %2. The agent will retry later to upload this file.%12</Description> </Message> <Message> <MessageID>10903</MessageID> <Description>Software Metering Agent successfully processed %1 usage data files.%12</Description> </Message> <Message> <MessageID>10904</MessageID> <Description>Software Metering Agent failed to download %1 rule file, error code %2. The agent will retry later to download this file.%12</Description> </Message> <Message> <MessageID>10905</MessageID> <Description>Software Metering Agent unable to open %1 rule file, error code %2.%12</Description> </Message> <Message> <MessageID>10906</MessageID> <Description>Software Metering Agent successfully processed %1 rule file.%12</Description> </Message> <Message> <MessageID>10907</MessageID> <Description>Software Metering Agent successfully received rule %1 for program %2, version %3.%12</Description> </Message> <Message> <MessageID>11000</MessageID> <Description>Client agent settings policy received.%12</Description> </Message> <Message> <MessageID>11001</MessageID> <Description>Invalid client agent settings policy received.%12</Description> </Message> <Message> <MessageID>11002</MessageID> <Description>Client agent settings policy is not trusted.%12</Description> </Message> <Message> <MessageID>11010</MessageID> <Description>Software Distribution Policy received for Deployment %1 (Package %2).%12</Description> </Message> <Message> <MessageID>11011</MessageID> <Description>Invalid Software Distribution Policy received for Deployment %1 (Package %2).%12</Description> </Message> <Message> <MessageID>11012</MessageID> <Description>Software Distribution Policy received for Deployment %1 (Package %2) is not trusted.%12</Description> </Message> <Message> <MessageID>11020</MessageID> <Description>Package Location response received for Deployment %1 (Package %2).%12</Description> </Message> <Message> <MessageID>11021</MessageID> <Description>Invalid Package Location response received for Deployment %1 (Package %2).%12</Description> </Message> <Message> <MessageID>11030</MessageID> <Description>Starting content download for package %1 (Deployment %2).%12</Description> </Message> <Message> <MessageID>11031</MessageID> <Description>Successfully downloaded content for package %1 (Deployment %2).%12</Description> </Message> <Message> <MessageID>11032</MessageID> <Description>Content download failed for package %1 (Deployment %2).%12</Description> </Message> <Message> <MessageID>11033</MessageID> <Description>Download aborted due to poor connectivity.%12</Description> </Message> <Message> <MessageID>11034</MessageID> <Description>Attempting to execute command line %1.%12</Description> </Message> <Message> <MessageID>11035</MessageID> <Description>The program for Deployment %1 (Package %2) executed successfully.%12</Description> </Message> <Message> <MessageID>11036</MessageID> <Description>The program for Deployment %1 (Package %2) failed. A non zero exit code of %3 was returned.%12</Description> </Message> <Message> <MessageID>11037</MessageID> <Description>Downloaded content for package %1 (Deployment %2) but the package content's hash verification failed.%12</Description> </Message> <Message> <MessageID>11070</MessageID> <Description>Hardware inventory initiated.%12</Description> </Message> <Message> <MessageID>11071</MessageID> <Description>Hardware inventory failed.%12</Description> </Message> <Message> <MessageID>11072</MessageID> <Description>Hardware inventory succeeded.%12</Description> </Message> <Message> <MessageID>11073</MessageID> <Description>Device Client failed to refresh site server signing certificate (SSSC).%12</Description> </Message> <Message> <MessageID>11074</MessageID> <Description>Device Client successfully refreshed site server signing certificate (SSSC).%12</Description> </Message> <Message> <MessageID>11080</MessageID> <Description>Software inventory initiated.%12</Description> </Message> <Message> <MessageID>11081</MessageID> <Description>Software inventory failed.%12</Description> </Message> <Message> <MessageID>11082</MessageID> <Description>Software inventory succeeded.%12</Description> </Message> <Message> <MessageID>11083</MessageID> <Description>Device Client is about to be upgraded.%12</Description> </Message> <Message> <MessageID>11084</MessageID> <Description>Device Client is about to be uninstalled.%12</Description> </Message> <Message> <MessageID>11090</MessageID> <Description>File collection initiated.%12</Description> </Message> <Message> <MessageID>11091</MessageID> <Description>File collection succeeded.%12</Description> </Message> <Message> <MessageID>11095</MessageID> <Description>File collection failed.%12</Description> </Message> <Message> <MessageID>11096</MessageID> <Description>Registration of Device Client in Native Security Mode succeeded.%12</Description> </Message> <Message> <MessageID>11100</MessageID> <Description>The OS Deployment agent successfully started the action %1.%12</Description> </Message> <Message> <MessageID>11101</MessageID> <Description>The OS installation failed action %1 with exit code %2.%12</Description> </Message> <Message> <MessageID>11102</MessageID> <Description>The OS installation has been completed successfully.%12</Description> </Message> <Message> <MessageID>11103</MessageID> <Description>The OS installation failed to request distribution points from management point %1.%12</Description> </Message> <Message> <MessageID>11104</MessageID> <Description>The OS installation failed because there are no distribution points available at this location.%12</Description> </Message> <Message> <MessageID>11105</MessageID> <Description>The OS installation failed to connect to the distribution point %1.%12</Description> </Message> <Message> <MessageID>11106</MessageID> <Description>The OS installation successfully started the Validation phase.%12</Description> </Message> <Message> <MessageID>11107</MessageID> <Description>The OS installation successfully started the State Capture phase.%12</Description> </Message> <Message> <MessageID>11108</MessageID> <Description>The OS installation successfully started the Preinstall phase.%12</Description> </Message> <Message> <MessageID>11109</MessageID> <Description>The OS installation successfully started the Install phase.%12</Description> </Message> <Message> <MessageID>11110</MessageID> <Description>The OS installation successfully started the Postinstall phase.%12</Description> </Message> <Message> <MessageID>11111</MessageID> <Description>The OS installation successfully started the State Restore phase.%12</Description> </Message> <Message> <MessageID>11112</MessageID> <Description>Package was succesfully downloaded from Multicast enabled DP.%12</Description> </Message> <Message> <MessageID>11113</MessageID> <Description>Package failed to download from Multicast enabled DP. Error %1. Will try another DP. %12</Description> </Message> <Message> <MessageID>11120</MessageID> <Description>The task sequence execution engine skipped the disabled group (%3).%12</Description> </Message> <Message> <MessageID>11121</MessageID> <Description>The task sequence execution engine failed evaluating the condition for the group (%3). Error code %4.%12</Description> </Message> <Message> <MessageID>11122</MessageID> <Description>The task sequence execution engine skipped the group (%3) because the condition was evaluated to be false.%12</Description> </Message> <Message> <MessageID>11123</MessageID> <Description>The task sequence execution engine evaluated TRUE for the condition of the group (%3).%12</Description> </Message> <Message> <MessageID>11124</MessageID> <Description>The task sequence execution engine started the group (%3).%12</Description> </Message> <Message> <MessageID>11125</MessageID> <Description>The task sequence execution engine ignored execution failure in the group (%3).%12</Description> </Message> <Message> <MessageID>11126</MessageID> <Description>The task sequence execution engine aborted execution for a failure in the group (%3).%12</Description> </Message> <Message> <MessageID>11127</MessageID> <Description>The task sequence execution engine successfully completed the group (%3).%12</Description> </Message> <Message> <MessageID>11128</MessageID> <Description>The task sequence execution engine skipped the disabled action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11129</MessageID> <Description>The task sequence execution engine failed evaluating the condition for the action (%2) in the group (%3). Error code %4.%12</Description> </Message> <Message> <MessageID>11130</MessageID> <Description>The task sequence execution engine skipped the action (%2) in the group (%3) because the condition was evaluated to be false.%12</Description> </Message> <Message> <MessageID>11131</MessageID> <Description>The task sequence execution engine evaluated TRUE for the condition of the action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11132</MessageID> <Description>The task sequence execution engine failed to start the action (%2) in the group (%3) with the win32 error code %4.%12</Description> </Message> <Message> <MessageID>11133</MessageID> <Description>The task sequence execution engine successfully started the action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11134</MessageID> <Description>The task sequence execution engine successfully completed the action (%2) in the group (%3) with exit code %4 Action output: %5%6%7%8.%12</Description> </Message> <Message> <MessageID>11135</MessageID> <Description>The task sequence execution engine failed executing the action (%2) in the group (%3) with the error code %4 Action output: %5%6%7%8.%12</Description> </Message> <Message> <MessageID>11136</MessageID> <Description>The task sequence execution engine received an external shutdown request during execution of the action (%2) in the group (%3) Partial action output: %5%6%7%8.%12</Description> </Message> <Message> <MessageID>11137</MessageID> <Description>The task sequence execution engine timeout in executing the action (%2) in the group (%3) Partial action output: %5%6%7%8.%12</Description> </Message> <Message> <MessageID>11138</MessageID> <Description>The task sequence execution engine ignored execution failure of the action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11139</MessageID> <Description>The task sequence execution engine aborted execution for a failure of the action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11140</MessageID> <Description>The task sequence execution engine started execution of a task sequence.%12</Description> </Message> <Message> <MessageID>11141</MessageID> <Description>The task sequence execution engine failed execution of a task sequence.%12</Description> </Message> <Message> <MessageID>11142</MessageID> <Description>The task sequence execution engine performed a system reboot initiated by the action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11143</MessageID> <Description>The task sequence execution engine successfully completed a task sequence.%12</Description> </Message> <Message> <MessageID>11144</MessageID> <Description>The task sequence execution engine from a non-client started execution of a task sequence.%12</Description> </Message> <Message> <MessageID>11169</MessageID> <Description>Task sequence version is not supported.%12</Description> </Message> <Message> <MessageID>11170</MessageID> <Description>The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of %1 was returned.%12</Description> </Message> <Message> <MessageID>11171</MessageID> <Description>The task sequence manager successfully completed execution of the task sequence.%12</Description> </Message> <Message> <MessageID>11200</MessageID> <Description>Software updates evaluation failed: invalid syntax or value for the specified scheduled installation window (/l).</Description> </Message> <Message> <MessageID>11201</MessageID> <Description>Software updates evaluation failed: could not determine the deployment assignment schedule. This is needed to calculate the correct begin and end times for the specified scheduled installation window (/l).</Description> </Message> <Message> <MessageID>11202</MessageID> <Description>Software updates evaluation failed: could not load software updates authorization list %1.</Description> </Message> <Message> <MessageID>11203</MessageID> <Description>Software updates evaluation failed: could not locate the scan component of the specified software update inventory tool. The scan component deployment might not have run on the client computer.</Description> </Message> <Message> <MessageID>11204</MessageID> <Description>Software updates evaluation failed: could not run the scan component of the specified software update inventory tool on the client computer. The scan component program could not be found in the client cache or it returned failure status.</Description> </Message> <Message> <MessageID>11205</MessageID> <Description>Software updates evaluation failed: error loading Win32_PatchState class from WMI.</Description> </Message> <Message> <MessageID>11206</MessageID> <Description>Software updates evaluation failed: error storing Win32_PatchState class into WMI.</Description> </Message> <Message> <MessageID>11207</MessageID> <Description>Software updates evaluation failed: unable to load resource file.</Description> </Message> <Message> <MessageID>11250</MessageID> <Description>Software updates evaluation was ended due to a scheduled installation window violation (installation started too early.)</Description> </Message> <Message> <MessageID>11251</MessageID> <Description>Software updates evaluation was ended due to a scheduled installation window violation (installation started too late.)</Description> </Message> <Message> <MessageID>11252</MessageID> <Description>Software updates installation was rescheduled by the user.%12</Description> </Message> <Message> <MessageID>11253</MessageID> <Description>Software updates installation was postponed by the user.%12</Description> </Message> <Message> <MessageID>11254</MessageID> <Description>Software updates installation was automatically postponed: the user did not choose to install the updates and the grace period has not expired.%12</Description> </Message> <Message> <MessageID>11255</MessageID> <Description>The software updates installation evaluation returned the following results: %1 Authorized, %2 attempted, %3 failed. Review the previous status message for further details about the actions taken during this update cycle. Refer to the associated detail messages from this client for each of the software update installations that were attempted for status on each update.%12</Description> </Message> <Message> <MessageID>11256</MessageID> <Description>Software update installation failed: the scheduled installation window expired while software update installation was not complete.</Description> </Message> <Message> <MessageID>11257</MessageID> <Description>Software updates installation was postponed: the user rescheduled the required system restart.</Description> </Message> <Message> <MessageID>11258</MessageID> <Description>Software updates installation was postponed: The user postponed the required pre-installation restart.</Description> </Message> <Message> <MessageID>11259</MessageID> <Description>Software updates installation was automatically postponed: a pre-installation restart was required, but the user did not choose to restart and the grace period has not expired.</Description> </Message> <Message> <MessageID>11261</MessageID> <Description>Software updates installation completed but the required restart was rescheduled by the user.%12</Description> </Message> <Message> <MessageID>11262</MessageID> <Description>Software updates installation completed but the required restart was postponed by the user.%12</Description> </Message> <Message> <MessageID>11263</MessageID> <Description>Software updates installation completed but the required restart was postponed automatically.%12</Description> </Message> <Message> <MessageID>11264</MessageID> <Description>The Software Updates Installation Agent initiated a system restart because one or more software updates required a restart in order for the installation to take effect.%12</Description> </Message> <Message> <MessageID>11266</MessageID> <Description>Software Updates Installation Agent completed successfully and suppressed the required system restart because the program was configured to suppress restarts for workstations.%12</Description> </Message> <Message> <MessageID>11267</MessageID> <Description>Software Updates Installation Agent completed successfully and suppressed the required system restart because the program was configured to suppress restarts for servers. Note: to avoid this, use the scheduled installation feature (/l) to enable automated restarts within a defined time window.%12</Description> </Message> <Message> <MessageID>11268</MessageID> <Description>Software Updates Installation Agent completed successfully and no restart was required.%12</Description> </Message> <Message> <MessageID>11269</MessageID> <Description>Software update installation was postponed: awaiting system restart.</Description> </Message> <Message> <MessageID>11270</MessageID> <Description>Restart of the computer is required in order for newly installed updates to take effect.%12</Description> </Message> <Message> <MessageID>11300</MessageID> <Description>The software update was installed and a restart of the computer was not required for the changes to take effect. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11301</MessageID> <Description>The software update was installed and a restart of the computer is required in order for the changes to take effect. Refer to the deployment status to determine the restart status of the computer. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11302</MessageID> <Description>The software update failed to install.</Description> </Message> <Message> <MessageID>11303</MessageID> <Description>The software update installation did not complete within the allocated time and was stopped by the agent.</Description> </Message> <Message> <MessageID>11304</MessageID> <Description>The software update was started, but was cancelled during installation by the user of the computer.</Description> </Message> <Message> <MessageID>11306</MessageID> <Description>The software update installation was not attempted due to a low disk space condition.</Description> </Message> <Message> <MessageID>11307</MessageID> <Description>The software update was installed and a restart of the computer was not required for the changes to take effect. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11308</MessageID> <Description>The software update was installed and a restart of the computer is required in order for the changes to take effect. Refer to the deployment status to determine the restart status of the computer. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11309</MessageID> <Description>The software update was installed due to an administrator defined enforcement date being met. A restart of the computer was not required for the changes to take effect. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11310</MessageID> <Description>The software update was installed due to an administrator defined enforcement date being met. A restart of the computer is required in order for the changes to take effect. Refer to the deployment status to determine the restart status of the computer. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11415</MessageID> <Description>Scan started by Software Updates Scan Agent.%12</Description> </Message> <Message> <MessageID>11416</MessageID> <Description>Failed to start Windows Update Agent on the client.%12</Description> </Message> <Message> <MessageID>11417</MessageID> <Description>Scan completed successfully by Software Updates Scan Agent.%12</Description> </Message> <Message> <MessageID>11418</MessageID> <Description>Software Updates Scan Agent has forcibly terminated the scan as it did not finish in the expected duration.%12</Description> </Message> <Message> <MessageID>11423</MessageID> <Description>Software Updates Scan failed.%12</Description> </Message> <Message> <MessageID>11424</MessageID> <Description>Software Update Scan - Update Source registration failed.%12</Description> </Message> <Message> <MessageID>11426</MessageID> <Description>Software Updates Scan Agent completed the scan successfully. However, scan reported error(s) %2 that might result in some updates not being detected as required or installed. Refer to the product documentation to see how these errors affect your enterprise and what steps you can take to correct possible configuration issues.%12</Description> </Message> <Message> <MessageID>11450</MessageID> <Description>Synchronization component failed: Site Code is not specified. Type = %1.%12</Description> </Message> <Message> <MessageID>11451</MessageID> <Description>Synchronization component failed: Package ID is not specified. Type = %1.%12</Description> </Message> <Message> <MessageID>11452</MessageID> <Description>Synchronization component failed: ConfigMgr Site Name is not specified. Type = %1.%12</Description> </Message> <Message> <MessageID>11453</MessageID> <Description>Synchronization component failed: package source folder is not specified. Type = %1.%12</Description> </Message> <Message> <MessageID>11454</MessageID> <Description>Synchronization component failed: Unable to write to %2. Type = %1.</Description> </Message> <Message> <MessageID>11455</MessageID> <Description>Synchronization component failed: Unable to read from %2. Type = %1.</Description> </Message> <Message> <MessageID>11456</MessageID> <Description>Synchronization component failed: the synchronization component (type = %1) failed to download %2, error code: %3.</Description> </Message> <Message> <MessageID>11457</MessageID> <Description>Software update catalog (type = %1) sync operation completed successfully. Newer version of catalog was downloaded and updated on distribution points.%12</Description> </Message> <Message> <MessageID>11458</MessageID> <Description>Synchronization component failed: the synchronization component failed to update the Distribution Points for the catalog (type = %1). Error code: %2.</Description> </Message> <Message> <MessageID>11459</MessageID> <Description>Synchronization component failed: the synchronization component failed to update the Site Database for the catalog (type = %1). See the log file for details.%12</Description> </Message> <Message> <MessageID>11460</MessageID> <Description>Software update catalog (type = %1) sync operation completed successfully. Newer version of catalog was not available.%12</Description> </Message> <Message> <MessageID>11461</MessageID> <Description> The content downloaded can't be trusted as unable to verify the certificate attached to the content, or no certificate was attached to the content therefore it can't be trusted.%12</Description> </Message> <Message> <MessageID>11462</MessageID> <Description> An existing or higher version of a scan tool is already installed at a parent site in the hierarchy. You are not allowed to have multiple instances of same scan tool in a hierarchy. You should only install a scan tool at the central site in the hierarchy.%12</Description> </Message> <Message> <MessageID>11500</MessageID> <Description>Version of device client on attached device is newer. No action taken.%12</Description> </Message> <Message> <MessageID>11501</MessageID> <Description>No device client action specified. No action taken.%12</Description> </Message> <Message> <MessageID>11502</MessageID> <Description>Device client installation completed successfully.%12</Description> </Message> <Message> <MessageID>11503</MessageID> <Description>Device client upgrade completed successfully.%12</Description> </Message> <Message> <MessageID>11504</MessageID> <Description>Installed device client state verified and settings enforced.%12</Description> </Message> <Message> <MessageID>11505</MessageID> <Description>Device client uninstallation completed successfully.%12</Description> </Message> <Message> <MessageID>11506</MessageID> <Description>Device client installation completed successfully and certificate enrollment was not required.%12</Description> </Message> <Message> <MessageID>11507</MessageID> <Description>Device client upgrade completed successfully and certificate enrollment was not required.%12</Description> </Message> <Message> <MessageID>11508</MessageID> <Description>Installed Device client state verified, settings enforced and certificate enrollment was not required.%12</Description> </Message> <Message> <MessageID>11510</MessageID> <Description>Device client installation completed successfully. Certificate installation and/or enrollment failed. Check DmInstaller.log on the Device Client for detailed error information.%12</Description> </Message> <Message> <MessageID>11511</MessageID> <Description>Device client upgrade completed successfully. Certificate installation and/or enrollment failed. Check DmInstaller.log on the Device Client for detailed error information.%12</Description> </Message> <Message> <MessageID>11512</MessageID> <Description>Installed device client state verified and settings enforced. Certificate installation and/or enrollment failed. Check DmInstaller.log on the Device Client for detailed error information.%12</Description> </Message> <Message> <MessageID>11520</MessageID> <Description>Device client deployment action failed. Failed to establish ActiveSync connection to device.%12</Description> </Message> <Message> <MessageID>11521</MessageID> <Description>Device client deployment action failed. Invalid client settings file.%12</Description> </Message> <Message> <MessageID>11522</MessageID> <Description>Device client deployment action failed. Error determining running directory for DmClientXfer.exe.%12</Description> </Message> <Message> <MessageID>11523</MessageID> <Description>Device client deployment action failed. Required ActiveSync libraries missing.%12</Description> </Message> <Message> <MessageID>11524</MessageID> <Description>Device client deployment action failed. Could not determine processor type of attached device.%12</Description> </Message> <Message> <MessageID>11525</MessageID> <Description>Device client deployment action failed. Could not determine base operating system version of attached device.%12</Description> </Message> <Message> <MessageID>11526</MessageID> <Description>Device client deployment action failed. Error determining client version for attached device.%12</Description> </Message> <Message> <MessageID>11527</MessageID> <Description>Device client deployment action failed. Error creating client settings .ini file.%12</Description> </Message> <Message> <MessageID>11528</MessageID> <Description>Device client deployment action failed. Failed copying files to attached device.%12</Description> </Message> <Message> <MessageID>11529</MessageID> <Description>Device client deployment action failed. Failed executing client installer program on attached device.%12</Description> </Message> <Message> <MessageID>11530</MessageID> <Description>Device client deployment action may have failed. Failed reading status information from device.%12</Description> </Message> <Message> <MessageID>11540</MessageID> <Description>Device client deployment action failed. Error determining running directory for client installer program.%12</Description> </Message> <Message> <MessageID>11541</MessageID> <Description>Device client deployment action failed. Error executing pre-install command line.%12</Description> </Message> <Message> <MessageID>11542</MessageID> <Description>Device client deployment action failed. Error executing post-install command line.%12</Description> </Message> <Message> <MessageID>11550</MessageID> <Description>Device client installation or upgrade failed. Error during uninstallation of previous client.%12</Description> </Message> <Message> <MessageID>11551</MessageID> <Description>Device client installation or upgrade failed. Invalid client settings file.%12</Description> </Message> <Message> <MessageID>11552</MessageID> <Description>Device client installation or upgrade failed. Error installing client CAB file.%12</Description> </Message> <Message> <MessageID>11553</MessageID> <Description>Device client installation or upgrade failed. Error starting client service.%12</Description> </Message> <Message> <MessageID>11554</MessageID> <Description>Device client installation or upgrade failed. Error updating client settings.%12</Description> </Message> <Message> <MessageID>11555</MessageID> <Description>Device Client Deployment failed with unknown error.%12</Description> </Message> <Message> <MessageID>11560</MessageID> <Description>Device client verification or repair failed. Error during uninstallation of previous client.%12</Description> </Message> <Message> <MessageID>11561</MessageID> <Description>Device client verification or repair failed. Invalid client settings file.%12</Description> </Message> <Message> <MessageID>11562</MessageID> <Description>Device client verification or repair failed. Error installing client CAB file.%12</Description> </Message> <Message> <MessageID>11563</MessageID> <Description>Device client verification or repair failed. Error starting client service.%12</Description> </Message> <Message> <MessageID>11564</MessageID> <Description>Device client verification or repair failed. Error updating client settings.%12</Description> </Message> <Message> <MessageID>11565</MessageID> <Description>Device client verification or repair failed. Error restoring required files.%12</Description> </Message> <Message> <MessageID>11566</MessageID> <Description>Device client privileged certificate installation failed. Device may have a security policy which prevents the client installer from installing certificates into the privileged and SPC certificate stores.%12</Description> </Message> <Message> <MessageID>11567</MessageID> <Description>Encountered unknown error installing the device client.%12</Description> </Message> <Message> <MessageID>11568</MessageID> <Description>Device client setup failed to launch during install.%12</Description> </Message> <Message> <MessageID>11570</MessageID> <Description>Device client uninstallation failed. Error using unload.exe to uninstall the existing client.%12</Description> </Message> <Message> <MessageID>11571</MessageID> <Description>Device client install/upgrade failed. Error enforcing new client. Device rolled back to old client (if existed before).%12</Description> </Message> <Message> <MessageID>11572</MessageID> <Description>Device client rollback failed during unsuccessful upgrade. Error enforcing old client. Need to freshly install the client.%12</Description> </Message> <Message> <MessageID>11573</MessageID> <Description>Device client failed to perform post cab install actions. Device client installation failed.%12</Description> </Message> <Message> <MessageID>11600</MessageID> <Description>The Component "%1" encountered an error %2 of category "%3" at %4.%12</Description> </Message> <Message> <MessageID>11700</MessageID> <Description>Scan tool %2 for the update %1 not available.</Description> </Message> <Message> <MessageID>11701</MessageID> <Description>Scan tool %2 for the update %1 failed.%12</Description> </Message> <Message> <MessageID>11702</MessageID> <Description>The contents hash for the update %1 provided in policy does not match with the contents downloaded.</Description> </Message> <Message> <MessageID>11703</MessageID> <Description>The contents for update %1 could not be located.%12</Description> </Message> <Message> <MessageID>11704</MessageID> <Description>Contents size for update %1 exceed free cache size available. The current cache size is %2 MB, of which %3 MB is available. The current amount of free disk space on the cache volume is %4 MB. This update requires %5 MB to be available in the cache.</Description> </Message> <Message> <MessageID>11705</MessageID> <Description>Contents size for the update %1 exceed total cache size available.%12 The current cache size is %2 MB, and %3 MB of cache space is available. This update requires %4 MB to be available in the cache.</Description> </Message> <Message> <MessageID>11706</MessageID> <Description>Failed to download contents for update %1.%12</Description> </Message> <Message> <MessageID>11707</MessageID> <Description>Update %1 cannot be attempted due to invalid commandline = %2.</Description> </Message> <Message> <MessageID>11708</MessageID> <Description>Update %1 application failed with returned exit code = %2.</Description> </Message> <Message> <MessageID>11709</MessageID> <Description>Update %1 did not finish in allocated time %2 seconds.</Description> </Message> <Message> <MessageID>11710</MessageID> <Description>Creation of process failed for update %1.%12 Commandline = %2</Description> </Message> <Message> <MessageID>11711</MessageID> <Description>Failed to get installer path for the update %1.%12</Description> </Message> <Message> <MessageID>11712</MessageID> <Description>Failed to monitor process for update %1 after service restart.%12</Description> </Message> <Message> <MessageID>11713</MessageID> <Description>SMS internal error occurred for the update %1.%12</Description> </Message> <Message> <MessageID>11714</MessageID> <Description>Bundle update "%1" failed to get content for update "%2". Please check the enforcement status of update "%2" to get further details.%12</Description> </Message> <Message> <MessageID>11715</MessageID> <Description>Bundle update "%1" failed to install update "%2". Please check the enforcement status of update "%2" to get further details.%12</Description> </Message> <Message> <MessageID>11716</MessageID> <Description>Bundle update "%1" failed to evaluate the applicability of its leaf updates.%12</Description> </Message> <Message> <MessageID>11717</MessageID> <Description>Update "%1" failed to install as no current or future maintenance window is available to accomodate this update with max runtime = %2.%12</Description> </Message> <Message> <MessageID>11750</MessageID> <Description>Updates enforcement job failed for assignment %1.%12</Description> </Message> <Message> <MessageID>11751</MessageID> <Description>Updates failures occured during enforcement for assignment %1.%12</Description> </Message> <Message> <MessageID>11752</MessageID> <Description>Some updates are still non-compliant after enforcement completion of the assignment %1.</Description> </Message> <Message> <MessageID>11753</MessageID> <Description>Post restart updates compliance checking failed.%12</Description> </Message> <Message> <MessageID>11754</MessageID> <Description>Failed to initiate enforcement of assignment %1.%12</Description> </Message> <Message> <MessageID>11755</MessageID> <Description>Failed to initiate updates evaluation for assignment %1.%12</Description> </Message> <Message> <MessageID>11756</MessageID> <Description>Updates evaluation job completed with failure for assignment %1.%12</Description> </Message> <Message> <MessageID>11757</MessageID> <Description>Invalid policy received for assignment %1.</Description> </Message> <Message> <MessageID>11758</MessageID> <Description>Failed to initiate updates advance download for assignment %1.%12</Description> </Message> <Message> <MessageID>11759</MessageID> <Description>Updates advance download job completed with failure for assignment %1.%12</Description> </Message> <Message> <MessageID>11760</MessageID> <Description>No maintenance window is defined to accommodate at least one update in the deployment %1.</Description> </Message> <Message> <MessageID>11800</MessageID> <Description>Failed to download baseline CI Id %1, version %2.</Description> </Message> <Message> <MessageID>11801</MessageID> <Description>The contents hash for baseline CI Id %1, version %2 provided in policy does not match with the contents downloaded.</Description> </Message> <Message> <MessageID>11802</MessageID> <Description>Cannot further process baseline CI Id %1, version %2. Managed client does not have the .Net framework version 2.0 installed.</Description> </Message> <Message> <MessageID>11850</MessageID> <Description>Failed to download baseline content %4 (%3), version %5.</Description> </Message> <Message> <MessageID>11851</MessageID> <Description>The contents hash for baseline content %4 (%3), version %5 provided in policy does not match with the contents downloaded.</Description> </Message> <Message> <MessageID>11852</MessageID> <Description>Failed to evaluate baseline content %4 (%3), version %5. %6.%12</Description> </Message> <Message> <MessageID>11853</MessageID> <Description>Failed to report compliance state for baseline content %4 (%3), version %5.%12</Description> </Message> <Message> <MessageID>11854</MessageID> <Description>Baseline content %4 (%3), version %5 which was previously non-compliant or had no prior discovery information is now compliant.</Description> </Message> <Message> <MessageID>11855</MessageID> <Description>Baseline content %4 (%3), version %5 which was previously compliant, had no prior discovery information, or a different non-compliance severity is now non-compliant with 'Informational' severity.</Description> </Message> <Message> <MessageID>11856</MessageID> <Description>Baseline content %4 (%3), version %5 which was previously compliant, had no prior discovery information, or a different non-compliance severity is now non-compliant with 'Warning' severity</Description> </Message> <Message> <MessageID>11857</MessageID> <Description>Baseline content %4 (%3), version %5 which was previously compliant, had no prior discovery information, or a different non-compliance severity is now non-compliant with 'Critical' severity.</Description> </Message> <Message> <MessageID>11858</MessageID> <Description>Baseline CI Id %1, version %2 could not be decompressed.</Description> </Message> <Message> <MessageID>11859</MessageID> <Description>Baseline content %4 (%3), version %5 could not be decompressed.</Description> </Message> <Message> <MessageID>11860</MessageID> <Description>Internal error - cannot further process baseline CI Id %1, version %2.</Description> </Message> <Message> <MessageID>11861</MessageID> <Description>Internal error - cannot further process baseline content %4 (%3), version %5.</Description> </Message> <Message> <MessageID>11862</MessageID> <Description>Failed to launch discovery process for baseline content %4 (%3), version %5.</Description> </Message> <Message> <MessageID>11863</MessageID> <Description>Discovery process crashed for baseline content %4 (%3), version %5.</Description> </Message> <Message> <MessageID>11864</MessageID> <Description>Baseline content %4, version %5 has model violations.</Description> </Message> <Message> <MessageID>11865</MessageID> <Description>Baseline content %4, version %5 encountered one or more errors during discovery.</Description> </Message> <Message> <MessageID>11866</MessageID> <Description>Download of baseline CI Id %1, version %2 timed out.</Description> </Message> <Message> <MessageID>11867</MessageID> <Description>Download of baseline content %4 (%3), version %5 timed out.</Description> </Message> <Message> <MessageID>11900</MessageID> <Description>The task sequence execution engine successfully installed (%6) package (%5) for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11901</MessageID> <Description>The task sequence execution engine failed to install (%6) package (%5) for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11902</MessageID> <Description>The task sequence successfully installed application %5(%6) for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11903</MessageID> <Description>The task sequence failed to install application %5(%6) for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11904</MessageID> <Description>The task sequence successfully installed application %5(%6) that was specified through TS variable for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11905</MessageID> <Description>The task sequence execution engine failed to install application %5(%6) that was specified through TS variable for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11906</MessageID> <Description>The task sequence has attempted to set UDA for users: %5 with assignment mode: %6 for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11907</MessageID> <Description>The task sequence has failed to set UDA for users: %5 with assignment mode: %6 for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11908</MessageID> <Description>The task sequence failed to install application %5(%6) for action (%2) in the group (%3). Please update maximum run time for this task sequence and run it again.%12</Description> </Message> <Message> <MessageID>11909</MessageID> <Description>The task sequence failed to install application %5(%6) for action (%2) in the group (%3) because a 'requirement was not met' warning and per user instruction warning was treated as error with exit code %4.%12</Description> </Message> <Message> <MessageID>11910</MessageID> <Description>The execution policy for running the powershell script is specified not to verify the signature of the scripts. This is unsafe and can potentially risk running malicious scripts.%12</Description> </Message> <Message> <MessageID>12000</MessageID> <Description>The out of band management agent successfully started the configuration at (%4).%12</Description> </Message> <Message> <MessageID>12001</MessageID> <Description>The out of band management agent failed to start the configuration in action (%1) with error code %2(%3).%12</Description> </Message> <Message> <MessageID>12108</MessageID> <Description>Application "%1" failed with failure exit code of %3. User name: %2.</Description> </Message> <Message> <MessageID>12109</MessageID> <Description>Application "%1" failed to download content with error code of %3. User name: %2.</Description> </Message> <Message> <MessageID>12110</MessageID> <Description>Application "%1" failed to be evaluated with error code of %3. User name: %2.</Description> </Message> <Message> <MessageID>12111</MessageID> <Description>Application "%1" failed to launch on the client with error code of %3. Additional error message is: %4. User name: %2.</Description> </Message> <Message> <MessageID>12112</MessageID> <Description>The system failed to suspend Bitlocker before a required system restart. The error returned from the suspend operation was: %1.</Description> </Message> <Message> <MessageID>12113</MessageID> <Description>The agent failed to resume Bitlocker after a require system restart. The error returned from the resume operation was: %1.</Description> </Message> <Message> <MessageID>12114</MessageID> <Description>The computer requires a restart, and the client policy requires that Bitlocker be suspended prior to the restart.</Description> </Message> <Message> <MessageID>12115</MessageID> <Description>The computer required a restart, and Bitlocker was suspended prior to the restart. Bitlocker has been resumed after %1 attempts.</Description> </Message> <Message> <MessageID>12116</MessageID> <Description>Configuration Manager restarted the computer to complete installation of software or software updates.</Description> </Message> <Message> <MessageID>13100</MessageID> <Description>Power settings failed to apply for the following reasons:%1 For more details please refer to powermgmt.log on client.</Description> </Message> <Message> <MessageID>13101</MessageID> <Description>The power schema %1 failed to apply on the client. The error code is: [%2]. [Power Schema GUID is = %3]</Description> </Message> <Message> <MessageID>13102</MessageID> <Description>The power agent detected that there is more than one power policy applied to the machine.</Description> </Message> <Message> <MessageID>13200</MessageID> <Description> Failed to verify certificate for webservice %1</Description> </Message> <Message> <MessageID>30000</MessageID> <Description>User "%1" created a package named "%5 %3 %4 %6" (%2).%12</Description> </Message> <Message> <MessageID>30001</MessageID> <Description>User "%1" modified the Package Properties of a package named "%5 %3 %4 %6" (%2).%12</Description> </Message> <Message> <MessageID>30002</MessageID> <Description>User "%1" deleted a package named "%5 %3 %4 %6" (%2).%12</Description> </Message> <Message> <MessageID>30003</MessageID> <Description>User "%1" created a program named "%2" that belongs to a package with package ID %3.%12</Description> </Message> <Message> <MessageID>30004</MessageID> <Description>User "%1" modified a program named "%2" that belongs to a package with package ID %3.%12</Description> </Message> <Message> <MessageID>30005</MessageID> <Description>User "%1" deleted a program named "%2" that belongs to a package with package ID %3.%12</Description> </Message> <Message> <MessageID>30006</MessageID> <Description>User "%1" created a deployment named "%3" (%2) deploying program "%4".%12</Description> </Message> <Message> <MessageID>30007</MessageID> <Description>User "%1" modified the deployment properties of a deployment named "%3" (%2) deploying program "%4".%12</Description> </Message> <Message> <MessageID>30008</MessageID> <Description>User "%1" deleted a deployment named "%3" (%2) deploying program "%4".%12</Description> </Message> <Message> <MessageID>30009</MessageID> <Description>User "%1" targeted a package with package ID %2 to a distribution point on %5 at site "%4 - %6".%12</Description> </Message> <Message> <MessageID>30010</MessageID> <Description>User "%1" modified a distribution point on %5 at site "%4 - %6" for a package with package ID %2.%12</Description> </Message> <Message> <MessageID>30011</MessageID> <Description>User "%1" removed a package with package ID %2 from a distribution point on %5 at site "%4 - %6".%12</Description> </Message> <Message> <MessageID>30012</MessageID> <Description>User "%1" created secondary site "%3 - %2".%12</Description> </Message> <Message> <MessageID>30013</MessageID> <Description>User "%1" upgraded or removed secondary site "%3 - %2".%12</Description> </Message> <Message> <MessageID>30014</MessageID> <Description>User "%1" deleted (removed all records from the site database) secondary site "%3 - %2".%12</Description> </Message> <Message> <MessageID>30015</MessageID> <Description>User "%1" created a collection named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30016</MessageID> <Description>User "%1" modified the Collection Properties for a collection named "%3" (%2). This collection is currently assigned to the following ConfigMgr Administrators: %4 %12</Description> </Message> <Message> <MessageID>30017</MessageID> <Description>User "%1" deleted a collection named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30018</MessageID> <Description>User "%1" created address of type "%6" connecting site %3 to %7 on %8 with priority %9.%12</Description> </Message> <Message> <MessageID>30019</MessageID> <Description>User "%1" modified the address properties for an address of type "%6" connecting site %3 to %7 on %8 with priority %9.%12</Description> </Message> <Message> <MessageID>30020</MessageID> <Description>User "%1" deleted address of type "%6" connecting site %3 to %7 on %8 with priority %9.%12</Description> </Message> <Message> <MessageID>30021</MessageID> <Description>User "%1" created file definition "%5" at secondary site %3.%12</Description> </Message> <Message> <MessageID>30022</MessageID> <Description>User "%1" modified file definition "%5" at secondary site %3.%12</Description> </Message> <Message> <MessageID>30023</MessageID> <Description>User "%1" deleted file definition "%5" at secondary site %3.%12</Description> </Message> <Message> <MessageID>30024</MessageID> <Description>User "%1" created the property "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30025</MessageID> <Description>User "%1" modified the property "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30026</MessageID> <Description>User "%1" deleted the property "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30027</MessageID> <Description>User "%1" created the property list "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30028</MessageID> <Description>User "%1" modified the property list "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30029</MessageID> <Description>User "%1" deleted the property list "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30030</MessageID> <Description>User "%1" created site definition information in the site control file for site "%3 - %6" (Parent Site Code="%7").%12</Description> </Message> <Message> <MessageID>30031</MessageID> <Description>User "%1" modified site definition information in the site control file for site "%3 - %6" (Parent Site Code="%7").%12</Description> </Message> <Message> <MessageID>30032</MessageID> <Description>User "%1" deleted site definition information in the site control file for site "%3 - %6" (Parent Site Code="%7").%12</Description> </Message> <Message> <MessageID>30033</MessageID> <Description>User "%1" created component "%7" on %6 in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30034</MessageID> <Description>User "%1" modified component "%7" on %6 in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30035</MessageID> <Description>User "%1" deleted component "%7" on %6 in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30036</MessageID> <Description>User "%1" added the role of %7 to the %6 "%8" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30037</MessageID> <Description>User "%1" modified the role of the %6 "%8" as a %7 in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30038</MessageID> <Description>User "%1" deleted the role of the %6 "%8" as a %7 in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30039</MessageID> <Description>User "%1" created a configuration for the "%4" component in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30040</MessageID> <Description>User "%1" modified the configuration of the "%4" component in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30041</MessageID> <Description>User "%1" deleted the configuration of the "%4" component in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30042</MessageID> <Description>User "%1" created client component "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30043</MessageID> <Description>User "%1" modified client component "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30044</MessageID> <Description>User "%1" deleted client component "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30045</MessageID> <Description>User "%1" created client configuration "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30046</MessageID> <Description>User "%1" modified client configuration "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30047</MessageID> <Description>User "%1" deleted client configuration "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30048</MessageID> <Description>User "%1" created SQL command "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30049</MessageID> <Description>User "%1" modified SQL command "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30050</MessageID> <Description>User "%1" deleted SQL command "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30051</MessageID> <Description>User "%1" created SQL Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30052</MessageID> <Description>User "%1" modified SQL Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30053</MessageID> <Description>User "%1" deleted SQL Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30054</MessageID> <Description>User "%1" added the site boundaries record to the site control file of site %3.%12</Description> </Message> <Message> <MessageID>30055</MessageID> <Description>User "%1" modified the site boundaries of site %3.%12</Description> </Message> <Message> <MessageID>30056</MessageID> <Description>User "%1" deleted the site boundaries record in the site control file of site %3.%12</Description> </Message> <Message> <MessageID>30057</MessageID> <Description>User "%1" created class security rights for user "%3" on object "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30058</MessageID> <Description>User "%1" modified class security rights for user "%3" on object "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30059</MessageID> <Description>User "%1" deleted class security rights for user "%3" on object "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30060</MessageID> <Description>User "%1" created instance security rights for user "%3" on instance "%4" of object type "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30061</MessageID> <Description>User "%1" modified instance security rights for user "%3" on instance "%4" of object type "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30062</MessageID> <Description>User "%1" deleted instance security rights for user "%3" on instance "%4" of object type "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30063</MessageID> <Description>User "%1" created a query named "%3" (%2) targeting the "%4" class.%12</Description> </Message> <Message> <MessageID>30064</MessageID> <Description>User "%1" modified a query named "%3" (%2) targeting the "%4" class.%12</Description> </Message> <Message> <MessageID>30065</MessageID> <Description>User "%1" deleted a query named "%3" (%2) targeting the "%4" class.%12</Description> </Message> <Message> <MessageID>30066</MessageID> <Description>User "%1" deleted a discovered resource named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30067</MessageID> <Description>User "%1" deleted all of the resources that belong to collection "%3" (%2).%12</Description> </Message> <Message> <MessageID>30068</MessageID> <Description>User "%1" updated a package named "%5 %3 %4 %6" (%2) to the site distribution points.%12</Description> </Message> <Message> <MessageID>30069</MessageID> <Description>User "%1" at "%2" initiated a Remote Control session with "%3".%12</Description> </Message> <Message> <MessageID>30070</MessageID> <Description>User "%1" at "%2" ended a Remote Control session with "%3".%12</Description> </Message> <Message> <MessageID>30076</MessageID> <Description>User "%1" at "%2" initiated Remote Control with "%3".%12</Description> </Message> <Message> <MessageID>30077</MessageID> <Description>User "%1" at "%2" ended Remote Control with "%3".%12</Description> </Message> <Message> <MessageID>30085</MessageID> <Description>User "%1" at "%2" failed to start a Remote Control session with "%3".%12</Description> </Message> <Message> <MessageID>30086</MessageID> <Description>User "%1" at "%2" failed to start a Remote Control session with "%3" due to insufficient security credentials.%12</Description> </Message> <Message> <MessageID>30091</MessageID> <Description>User "%1" created a report named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30092</MessageID> <Description>User "%1" modified a report named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30093</MessageID> <Description>User "%1" deleted a report named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30094</MessageID> <Description>User "%1" created a meter rule named "%7" (%3) for file "%4" with a product version of "%6" and Language ID of "%5".%12</Description> </Message> <Message> <MessageID>30095</MessageID> <Description>User "%1" modified a meter rule named "%7" (%3) for file "%4" with a product version of "%6" and Language ID of "%5".%12</Description> </Message> <Message> <MessageID>30099</MessageID> <Description>User "%1" created Maintenance Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30100</MessageID> <Description>User "%1" modified Maintenance Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30101</MessageID> <Description>User "%1" deleted Maintenance Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30102</MessageID> <Description>User "%2" from computer "%3" created a session using application [%4] version [%5].%12</Description> </Message> <Message> <MessageID>30103</MessageID> <Description>User "%2" from computer "%3" released its session using application [%4] version [%5].%12</Description> </Message> <Message> <MessageID>30104</MessageID> <Description>User "%1" requested that the membership be refreshed for collection "%3" (%2).%12</Description> </Message> <Message> <MessageID>30105</MessageID> <Description>User "%1" deleted a meter rule named "%7" (%3) for file "%4" with a product version of "%6" and Language ID of "%5".%12</Description> </Message> <Message> <MessageID>30106</MessageID> <Description>User "%1" requested that the CCRs be generated for query named "%3" (%2) targeting the "%4" class.%12</Description> </Message> <Message> <MessageID>30107</MessageID> <Description>User "%1" requested that the CCRs be generated for collection "%3" (%2).%12</Description> </Message> <Message> <MessageID>30108</MessageID> <Description>User "%1" requested that the CCR be generated for Machine "%2" (%3).%12</Description> </Message> <Message> <MessageID>30109</MessageID> <Description>User "%1" requested that the CCRs be generated for query named "%3" (%2) targeting the "%4" class. The SMS Provider did not generate CCRs for all the system resources returned by this query.</Description> </Message> <Message> <MessageID>30110</MessageID> <Description>User "%1" requested that the CCRs be generated for collection "%3" (%2). The SMS Provider did not generate CCRs for all the system resources in this collection.</Description> </Message> <Message> <MessageID>30111</MessageID> <Description>User "%1" requested that the CCR be generated for resource "%3". But no CCR is generated.</Description> </Message> <Message> <MessageID>30112</MessageID> <Description>User "%1" has authorized a software update. Details: ID = %2, QNumbers = %3, Product = %4, Title = %5, Locale = %6.%12</Description> </Message> <Message> <MessageID>30113</MessageID> <Description>User "%1" created a folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30114</MessageID> <Description>User "%1" modified a folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30115</MessageID> <Description>User "%1" deleted a folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30116</MessageID> <Description>User "%1" added %3 of %4 to folder "%2".%12</Description> </Message> <Message> <MessageID>30117</MessageID> <Description>User "%1" moved %3 of %4 out of folder "%2".%12</Description> </Message> <Message> <MessageID>30118</MessageID> <Description>User "%1" added software update "%2" to program "%4" in package "%3", package version "%5".%12</Description> </Message> <Message> <MessageID>30119</MessageID> <Description>User "%1" changed the link information for software update "%2" in program "%4" and package "%3", package version "%5".%12</Description> </Message> <Message> <MessageID>30120</MessageID> <Description>User "%1" removed software update "%2" from program "%4" in package "%3", package version "%5".%12</Description> </Message> <Message> <MessageID>30121</MessageID> <Description>User "%1" created software update with CI_ID "%2". Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30122</MessageID> <Description>User "%1" modified software update with CI_ID "%2". Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30123</MessageID> <Description>User "%1" deleted software update with CI_ID "%2". Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30124</MessageID> <Description>User "%1" has authorized software update "%2". Details: ID = "%3", QNumbers = "%5", Product = "%6", Title = "%4", Locale = "%7".%12</Description> </Message> <Message> <MessageID>30125</MessageID> <Description>User "%1" added new distribution points to a package named "%5 %3 %4 %6" (%2).%12</Description> </Message> <Message> <MessageID>30129</MessageID> <Description>User "%1" created device discovery translation "%2".%12</Description> </Message> <Message> <MessageID>30130</MessageID> <Description>User "%1" modified device discovery translation "%2".%12</Description> </Message> <Message> <MessageID>30131</MessageID> <Description>User "%1" deleted device discovery translation "%2".%12</Description> </Message> <Message> <MessageID>30132</MessageID> <Description>User "%1" created an instance of SMS_DeviceFQDN "%2".%12</Description> </Message> <Message> <MessageID>30133</MessageID> <Description>User "%1" modified an instance of SMS_DeviceFQDN "%2".%12</Description> </Message> <Message> <MessageID>30134</MessageID> <Description>User "%1" deleted an instance of SMS_DeviceFQDN "%2".%12</Description> </Message> <Message> <MessageID>30135</MessageID> <Description>User "%1" created relation "%3" between software update "%2" and software update "%4".%12</Description> </Message> <Message> <MessageID>30136</MessageID> <Description>User "%1" changed relation "%3" between software update "%2" and software update "%4".%12</Description> </Message> <Message> <MessageID>30137</MessageID> <Description>User "%1" removed relation "%3" between software update "%2" and software update "%4".%12</Description> </Message> <Message> <MessageID>30138</MessageID> <Description>User "%1" has created an instance of SMS_ScanTool. SMSScanToolID =%2 ToolName=%3.%12</Description> </Message> <Message> <MessageID>30139</MessageID> <Description>User "%1" has modified an instance of SMS_ScanTool. SMSScanToolID =%2 ToolName=%3.%12</Description> </Message> <Message> <MessageID>30140</MessageID> <Description>User "%1" has deleted an instance of SMS_ScanTool. SMSScanToolID =%2 ToolName=%3.%12</Description> </Message> <Message> <MessageID>30152</MessageID> <Description>User "%1" created configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30153</MessageID> <Description>User "%1" modified configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30154</MessageID> <Description>User "%1" deleted configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30155</MessageID> <Description>User "%1" enforced configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30156</MessageID> <Description>User "%1" unenforced configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30157</MessageID> <Description>User "%1" accepted the license terms for configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30158</MessageID> <Description>User "%1" declined the license terms for configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30159</MessageID> <Description>User "%1" created a CategoryInstance "%2" (LocalizedCategoryInstanceName=%3, CategoryTypeName=%4). .%12</Description> </Message> <Message> <MessageID>30160</MessageID> <Description>User "%1" modified a CategoryInstance "%2" (LocalizedCategoryInstanceName=%3, CategoryTypeName=%4). .%12</Description> </Message> <Message> <MessageID>30161</MessageID> <Description>User "%1" deleted CategoryInstance "%2" (LocalizedCategoryInstanceName=%3, CategoryTypeName=%4). .%12</Description> </Message> <Message> <MessageID>30162</MessageID> <Description>User "%1" created a CategoryInstance Membership (CategoryInstanceID(%2),ObjectType(%3),ObjectKey(%4)). .%12</Description> </Message> <Message> <MessageID>30163</MessageID> <Description>User "%1" delete a CategoryInstance Membership (CategoryName(%2), ObjectType(%3), ObjectName(%4)). .%12</Description> </Message> <Message> <MessageID>30165</MessageID> <Description>User "%1" created a license terms Content "%2" (license terms ContentUniqueID=%3). .%12</Description> </Message> <Message> <MessageID>30166</MessageID> <Description>User "%1" modified a license terms Content "%2" (license terms ContentUniqueID=%3). .%12</Description> </Message> <Message> <MessageID>30167</MessageID> <Description>User "%1" deleted license terms Content "%2" (license terms ContentUniqueID=%3). .%12</Description> </Message> <Message> <MessageID>30168</MessageID> <Description>User "%1" resend configuration item "%2" (CI_UniqueID=%3, CIVersion=%4) to all child sites. .%12</Description> </Message> <Message> <MessageID>30169</MessageID> <Description>User "%1" resend a CategoryInstance "%2" (CategoryInstance_UniqueID=%3, CategoryTypeName=%4) to all child sites. .%12</Description> </Message> <Message> <MessageID>30170</MessageID> <Description>User "%1" resend a SDMPackage "%2" (SDMPackageName=%3, SDMPackageVersion=%4) to all child sites. .%12</Description> </Message> <Message> <MessageID>30171</MessageID> <Description>User "%1" resend a license terms Content "%2" (license terms ContentUniqueID=%3) to all child sites. .%12</Description> </Message> <Message> <MessageID>30172</MessageID> <Description>User "%1" resend software update with CI_ID "%2" to all child sites. Update Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30173</MessageID> <Description>User "%1" has resend an instance of SMS_ScanTool to all child sites. SMSScanToolID =%2 ToolName=%3.%12</Description> </Message> <Message> <MessageID>30180</MessageID> <Description>User "%1" created a state association between sourceclient (%2) and restoreclient (%3).%12</Description> </Message> <Message> <MessageID>30181</MessageID> <Description>User "%1" deleted a state association between sourceclient (%2) and restoreclient (%3).%12</Description> </Message> <Message> <MessageID>30183</MessageID> <Description>User "%1" attempted to download the content for software update with CI_ID "%2". Update Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30185</MessageID> <Description>User "%1" attempted to import the content for software update with CI_ID "%2". Update Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30186</MessageID> <Description>User "%1" created the SUM deployment template with TemplateUniqueID "%2" (Name = "%3"). .%12</Description> </Message> <Message> <MessageID>30187</MessageID> <Description>User "%1" modified the SUM deployment template with TemplateUniqueID "%2" (Name = "%3"). .%12</Description> </Message> <Message> <MessageID>30188</MessageID> <Description>User "%1" deleted the SUM deployment template with TemplateUniqueID "%2" (Name = "%3"). .%12</Description> </Message> <Message> <MessageID>30189</MessageID> <Description>User "%1" added content with ContentID %2 to PackageID "%3" (ContentVersionInPkg = %4). .%12</Description> </Message> <Message> <MessageID>30190</MessageID> <Description>User "%1" modified content with ContentID %2 in PackageID "%3 (ContentVersionInPkg = %4)". .%12</Description> </Message> <Message> <MessageID>30191</MessageID> <Description>User "%1" removed content with ContentID %2 from PackageID "%3". .%12</Description> </Message> <Message> <MessageID>30192</MessageID> <Description>User "%1" initiated a package change notification for Package named "%5 %3 %4 %6" (%2).%12</Description> </Message> <Message> <MessageID>30193</MessageID> <Description>User "%1" created CI assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30194</MessageID> <Description>User "%1" modified CI assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30195</MessageID> <Description>User "%1" deleted CI assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30196</MessageID> <Description>User "%1" created updates assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30197</MessageID> <Description>User "%1" modified updates assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30198</MessageID> <Description>User "%1" deleted updates assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30199</MessageID> <Description>User "%1" created an instance of SMS_DeviceSettingItem %2 (Name = %3, Type = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30200</MessageID> <Description>User "%1" modified an instance of SMS_DeviceSettingItem %2 (Name = %3, Type = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30201</MessageID> <Description>User "%1" deleted an instance of SMS_DeviceSettingItem %2 (Name = %3, Type = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30202</MessageID> <Description>User "%1" created an instance of SMS_DeviceSettingPackage %2 (Name = %3, PlatformType = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30203</MessageID> <Description>User "%1" modified an instance of SMS_DeviceSettingPackage %2 (Name = %3, PlatformType = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30204</MessageID> <Description>User "%1" deleted an instance of SMS_DeviceSettingPackage %2 (Name = %3, PlatformType = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30205</MessageID> <Description>User "%1" created an instance of SMS_DeviceSettingPackageItem (DeviceSettingPkgID = %2, DeviceSettingItemID = %3). .%12</Description> </Message> <Message> <MessageID>30206</MessageID> <Description>User "%1" modified an instance of SMS_DeviceSettingPackageItem (DeviceSettingPkgID = %2, DeviceSettingItemID = %3). .%12</Description> </Message> <Message> <MessageID>30207</MessageID> <Description>User "%1" deleted an instance of SMS_DeviceSettingPackageItem (DeviceSettingPkgID = %2, DeviceSettingItemID = %3). .%12</Description> </Message> <Message> <MessageID>30208</MessageID> <Description>User "%1" modified summary task (%2) (RunInterval=%3 Enabled=%4 TaskParameter=%5). .%12</Description> </Message> <Message> <MessageID>30209</MessageID> <Description>User "%1" requested to execute summary task (%2). .%12</Description> </Message> <Message> <MessageID>30210</MessageID> <Description>User "%1" created user account %6. .%12</Description> </Message> <Message> <MessageID>30211</MessageID> <Description>User "%1" modified user account %6. .%12</Description> </Message> <Message> <MessageID>30212</MessageID> <Description>User "%1" deleted user account %6. .%12</Description> </Message> <Message> <MessageID>30213</MessageID> <Description>User "%1" imported machine at site "%3 - %2" (NetbiosName=%4, MACAddress=%5, SMBIOSGUID=%6).%12</Description> </Message> <Message> <MessageID>30214</MessageID> <Description>User "%1" submitted a registration record at site "%3 - %2" (SMSID=%4).%12</Description> </Message> <Message> <MessageID>30215</MessageID> <Description>User "%1" received policies for Task Sequence %3 using Deployment "%2".%12</Description> </Message> <Message> <MessageID>30216</MessageID> <Description>User "%1" received client configuration policies.%12</Description> </Message> <Message> <MessageID>30217</MessageID> <Description>User "%1" changed the Approved Status to %2 for %3 clients. ResourceIDs (%4).%12</Description> </Message> <Message> <MessageID>30218</MessageID> <Description>User "%1" changed the Allowed Status to %2 for %3 clients. ResourceIDs (%4).%12</Description> </Message> <Message> <MessageID>30219</MessageID> <Description>User "%1" created authorization list "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30220</MessageID> <Description>User "%1" modified authorization list "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30221</MessageID> <Description>User "%1" deleted authorization list "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30222</MessageID> <Description>User "%1" created per-computer settings for %3 (ResourceID %2).%12</Description> </Message> <Message> <MessageID>30223</MessageID> <Description>User "%1" modified per-computer settings for %3 (ResourceID %2).%12</Description> </Message> <Message> <MessageID>30224</MessageID> <Description>User "%1" changed the Block Status to %2 for Certificate (SMSID=%3).%12</Description> </Message> <Message> <MessageID>30225</MessageID> <Description>User "%1" resolved the pending registration record (SMSID=%2, FQDN=%3, ConflictSMSID=%4, Action=%5).%12</Description> </Message> <Message> <MessageID>30226</MessageID> <Description>User "%1" created a deployment of application "%3" to collection "%4".%12</Description> </Message> <Message> <MessageID>30227</MessageID> <Description>User "%1" modified the deployment of application "%3" to collection "%4".%12</Description> </Message> <Message> <MessageID>30228</MessageID> <Description>User "%1" deleted the deployment of application "%3" to collection "%4".%12</Description> </Message> <Message> <MessageID>30229</MessageID> <Description>User "%1" created update group assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30230</MessageID> <Description>User "%1" modified update group assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30231</MessageID> <Description>User "%1" deleted update group assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30232</MessageID> <Description>User "%1" created per-user settings for %3 (ResourceID %2).%12</Description> </Message> <Message> <MessageID>30233</MessageID> <Description>User "%1" modified per-user settings for %3 (ResourceID %2).%12</Description> </Message> <Message> <MessageID>30234</MessageID> <Description>User "%1" changed the Ownership Type to %2 for %3 clients. ResourceIDs (%4).%12</Description> </Message> <Message> <MessageID>30235</MessageID> <Description>User "%1" changed the site to %2 for %3 clients. ResourceIDs (%4).%12</Description> </Message> <Message> <MessageID>30240</MessageID> <Description>User "%1" created alert (ID=%2, Type=%3, Instance=%4, Enabled=%5, SkipUntil=%6).%12</Description> </Message> <Message> <MessageID>30241</MessageID> <Description>User "%1" modified alert (ID=%2, Type=%3, Instance=%4, Enabled=%5, SkipUntil=%6).%12</Description> </Message> <Message> <MessageID>30242</MessageID> <Description>User "%1" deleted alert (ID=%2, Type=%3, Instance=%4).%12</Description> </Message> <Message> <MessageID>30243</MessageID> <Description>User "%1" set SkipUntil of alert (ID=%2, Type=%3, Instance=%4).%12</Description> </Message> <Message> <MessageID>30244</MessageID> <Description>User "%1" closed alert (ID=%2, Type=%3, Instance=%4).%12</Description> </Message> <Message> <MessageID>30300</MessageID> <Description>User "%1" at "%2" started an OOB Console session to "%3".%12</Description> </Message> <Message> <MessageID>30301</MessageID> <Description>User "%1" at "%2" attempt to disconnect from "%3". Success.%12</Description> </Message> <Message> <MessageID>30302</MessageID> <Description>User "%1" at "%2" attempt to perform a status information query from "%3". Success.%12</Description> </Message> <Message> <MessageID>30303</MessageID> <Description>User "%1" at "%2" attempt to perform a system inventory query from "%3". Success.%12</Description> </Message> <Message> <MessageID>30304</MessageID> <Description>User "%1" at "%2" attempt to perform a power control command to "%3". Success.%12</Description> </Message> <Message> <MessageID>30305</MessageID> <Description>User "%1" at "%2" attempt to perform a serial over lan session to "%3". Success.%12</Description> </Message> <Message> <MessageID>30306</MessageID> <Description>User "%1" at "%2" attempt to perform a IDE-R session to "%3". Success.%12</Description> </Message> <Message> <MessageID>30307</MessageID> <Description>User "%1" at "%2" attempt to unprovision "%3". Success.%12</Description> </Message> <Message> <MessageID>30308</MessageID> <Description>User "%1" at "%2" has no permission to connect "%3". Success.%12</Description> </Message> <Message> <MessageID>30309</MessageID> <Description>User "%1" at "%2" attempt to connect to "%3".%12</Description> </Message> <Message> <MessageID>30310</MessageID> <Description>User "%1" at "%2" attempt to perform a IDE-R session to "%3", but IDE-R session to this device has already been opened .%12</Description> </Message> <Message> <MessageID>30311</MessageID> <Description>User "%1" at "%2" failed to perform a status information query from "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30312</MessageID> <Description>User "%1" at "%2" failed to perform a system inventory query from "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30313</MessageID> <Description>User "%1" at "%2" failed to perform a power control command to "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30314</MessageID> <Description>User "%1" at "%2" failed to perform a serial over lan session to "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30315</MessageID> <Description>User "%1" at "%2" failed to perform a IDE-R session to "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30316</MessageID> <Description>User "%1" at "%2" failed to unprovision "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30317</MessageID> <Description>User "%1" at "%2" failed to disconnect from "%3".%12</Description> </Message> <Message> <MessageID>30318</MessageID> <Description>User "%1" at "%2" failed to connect to "%3".%12</Description> </Message> <Message> <MessageID>30319</MessageID> <Description>User "%1" at "%2" failed to connect to special resource %3 in this site.%12</Description> </Message> <Message> <MessageID>30320</MessageID> <Description>User "%1" at "%2" failed to perform a status information query from "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30321</MessageID> <Description>User "%1" at "%2" failed to perform a system inventory query from "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30322</MessageID> <Description>User "%1" at "%2" failed to perform a power control command to "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30323</MessageID> <Description>User "%1" at "%2" failed to perform a serial over lan session to "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30324</MessageID> <Description>User "%1" at "%2" failed to perform a IDE-R session to "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30325</MessageID> <Description>User "%1" at "%2" failed to unprovision "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30326</MessageID> <Description>User "%1" created a remote application subscription ID (%2).%12</Description> </Message> <Message> <MessageID>30327</MessageID> <Description>User "%1" modified a remote application subscription ID (%2).%12</Description> </Message> <Message> <MessageID>30328</MessageID> <Description>User "%1" deleted a remote application subscription ID (%2).%12</Description> </Message> <Message> <MessageID>30330</MessageID> <Description>User "%1" created a virtual App named %4 (VirtualAppID = %2) for the Package(%3).%12</Description> </Message> <Message> <MessageID>30331</MessageID> <Description>User "%1" modified a virtual App named %4 (VirtualAppID = %2) for the Package(%3).%12</Description> </Message> <Message> <MessageID>30332</MessageID> <Description>User "%1" deleted a virtual App named %4 (VirtualAppID = %2) for the Package(%3).%12</Description> </Message> <Message> <MessageID>30400</MessageID> <Description>User "%1" changed the AMT Status to %2 for AMT Certificate (CertID=%3).%12</Description> </Message> <Message> <MessageID>30401</MessageID> <Description>User "%1" initiated "Power on" command on "%3" (%2) .%12</Description> </Message> <Message> <MessageID>30402</MessageID> <Description>User "%1" initiated "Restart" command on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30403</MessageID> <Description>User "%1" initiated "Shut down" command on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30404</MessageID> <Description>User "%1" enabled Audit Log on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30405</MessageID> <Description>User "%1" disabled Audit Log on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30406</MessageID> <Description>User "%1" cleared Audit Log on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30407</MessageID> <Description>User "%1" updates the provision data on machine "%3" (%2).%12</Description> </Message> <Message> <MessageID>30408</MessageID> <Description>User "%1" unprovisioned machine "%3" (%2).%12</Description> </Message> <Message> <MessageID>30409</MessageID> <Description>User "%1" initiated "Discover" command on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30500</MessageID> <Description>User added the following distribution points to a package (Package ID=%1): %2</Description> </Message> <Message> <MessageID>30501</MessageID> <Description>User removed the distribution point (NALPATH=%2) from package (Package ID=%1).</Description> </Message> <Message> <MessageID>30502</MessageID> <Description>User Refreshed the distribution point (NALPATH=%2) of package (Package ID=%1).</Description> </Message> <Message> <MessageID>30503</MessageID> <Description>User updated the following distribution points of package (Package ID=%1): %2</Description> </Message> <Message> <MessageID>30504</MessageID> <Description>User updated the schedule of Deployment (ID=%1), PresentTime and ExpirationTime were changed from %2 to %3, mandatory schedule and offer flags changed from %4 to %5.</Description> </Message> <Message> <MessageID>30505</MessageID> <Description>User updated the target collection of Deployment (ID=%1), Collection ID was changed from %2 to %3.</Description> </Message> <Message> <MessageID>30506</MessageID> <Description>User updated the schedule of SUM (ID=%1), PresentTime and ExpirationTime were changed from %2 to %3.</Description> </Message> <Message> <MessageID>30507</MessageID> <Description>User updated the target collection of SUM (ID=%1), Collection ID was changed from %2 to %3.</Description> </Message> <Message> <MessageID>30600</MessageID> <Description>User "%1" created relationship (ID=%2) between machine %3 and user %4.%12</Description> </Message> <Message> <MessageID>30601</MessageID> <Description>User "%1" modified relationship (ID=%2) between machine %3 and user %4.%12</Description> </Message> <Message> <MessageID>30602</MessageID> <Description>User "%1" deleted relationship (ID=%2) between machine %3 and user %4.%12</Description> </Message> <Message> <MessageID>30603</MessageID> <Description>User "%1" added a source (SourceID=%2) for relationship (ID=%3) between machine %4 and user %5.%12</Description> </Message> <Message> <MessageID>30604</MessageID> <Description>User "%1" removed a source (SourceID=%2) for relationship (ID=%3) between machine %4 and user %5.%12</Description> </Message> <Message> <MessageID>30605</MessageID> <Description>User "%1" added a type (TypeID=%2) for relationship (ID=%3) between machine %4 and user %5.%12</Description> </Message> <Message> <MessageID>30606</MessageID> <Description>User "%1" removed a type (TypeID=%2) for relationship (ID=%3) between machine %4 and user %5.%12</Description> </Message> <Message> <MessageID>30700</MessageID> <Description>User "%1" created a search folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30701</MessageID> <Description>User "%1" modified a search folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30702</MessageID> <Description>User "%1" deleted a search folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30800</MessageID> <Description>Administrative user %1 approved request of application %2 for user %3.%12</Description> </Message> <Message> <MessageID>30801</MessageID> <Description>Administrative user %1 denied request of application %2 for user %3.%12</Description> </Message> <Message> <MessageID>30900</MessageID> <Description>User "%1" created a migration job named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30901</MessageID> <Description>User "%1" modified a migration job named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30902</MessageID> <Description>User "%1" deleted a migration job named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30903</MessageID> <Description>User "%1" started a migration job named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30904</MessageID> <Description>User "%1" stopped a migration job named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30905</MessageID> <Description>User "%1" created a migration site mapping with ID "%3" (%2).%12</Description> </Message> <Message> <MessageID>30906</MessageID> <Description>User "%1" modified a migration site mapping with ID "%3" (%2).%12</Description> </Message> <Message> <MessageID>30907</MessageID> <Description>User "%1" deleted a migration site mapping with ID "%3" (%2).%12</Description> </Message> <Message> <MessageID>31000</MessageID> <Description>User "%1" created an inventory report with ID "%2".%12</Description> </Message> <Message> <MessageID>31001</MessageID> <Description>User "%1" modified an inventory report with ID "%2".%12</Description> </Message> <Message> <MessageID>31002</MessageID> <Description>User "%1" deleted an inventory report with ID "%2".%12</Description> </Message> <Message> <MessageID>31200</MessageID> <Description>Administrative user %1 successfully created a custom security role %3.%12</Description> </Message> <Message> <MessageID>31201</MessageID> <Description>Administrative user %1 successfully modified security role %2.%12</Description> </Message> <Message> <MessageID>31202</MessageID> <Description>Administrative user %1 successfully deleted a custom security role %2.%12</Description> </Message> <Message> <MessageID>31203</MessageID> <Description>Administrative user %1 tried to create a custom security role but does not have sufficient permissions. User %1 requires at least "Create role" permissions.%12</Description> </Message> <Message> <MessageID>31204</MessageID> <Description>Administrative user %1 tried to modify a custom security role but does not have sufficient permissions. User %1 requires at least "Modify role" permissions.%12</Description> </Message> <Message> <MessageID>31205</MessageID> <Description>Administrative user %1 tried to delete a custom role but does not have sufficient permissions. User %1 requires at least "Delete role" permissions.%12</Description> </Message> <Message> <MessageID>31206</MessageID> <Description>Administrative user %1 was not allowed to import a security role, due to insufficient permissions. User %1 requires at least "Create role" permission.%12</Description> </Message> <Message> <MessageID>31207</MessageID> <Description>Administrative user %1 has successfully imported custom security role %2.%12</Description> </Message> <Message> <MessageID>31208</MessageID> <Description>Administrative user %1 successfully exported security role %2.%12</Description> </Message> <Message> <MessageID>31209</MessageID> <Description>Administrative user %1 tried to export security role %2 but has insufficient rights. User %1 requires at least "read role" permission.%12</Description> </Message> <Message> <MessageID>31220</MessageID> <Description>Administrative user %1 successfully created the new security scope %2.%12</Description> </Message> <Message> <MessageID>31221</MessageID> <Description>Administrative user %1 successfully modified security scope %2.%12</Description> </Message> <Message> <MessageID>31222</MessageID> <Description>Administrative user %1 successfully deleted security scope %2.%12</Description> </Message> <Message> <MessageID>31223</MessageID> <Description>Administrative user %1 was not allowed to create a new security scope due to insufficient permissions. User %1 requires at least "Create security scope" permission.%12</Description> </Message> <Message> <MessageID>31224</MessageID> <Description>Administrative user %1 was not allowed to modify security scope %2 due to insufficient permission. User %1 requires at least "Modify security scope" permission.%12</Description> </Message> <Message> <MessageID>31225</MessageID> <Description>Administrative user %1 was not allowed to delete security scope %2 due to insufficient permissions. User %1 requires at least "Delete security scope" permission.%12</Description> </Message> <Message> <MessageID>31226</MessageID> <Description>User %1 associated securable object %4 (Type: %3) with the following security scope: %2.%12</Description> </Message> <Message> <MessageID>31227</MessageID> <Description>User %1 deassociated securable object %4 (Type: %3) with the following security scope: %2.%12</Description> </Message> <Message> <MessageID>31240</MessageID> <Description>Administrative user %1 has successfully added and associated %3 with the roles %4 and security scopes %5 and collections %6 to the Configuration Manager environment.%12</Description> </Message> <Message> <MessageID>31241</MessageID> <Description>User "%1" modified and associated %3 with the roles %4 and security scopes %5 and collections %6 to the Configuration Manager environment.%12</Description> </Message> <Message> <MessageID>31242</MessageID> <Description>Administrative user %1 has successfully removed %3 from the Configuration Manager environment.%12</Description> </Message> <Message> <MessageID>31243</MessageID> <Description>The Configuration Manager provider on server "%1" was unable to connect to Active Directory domain controller "%2" (result code: "%3"), as a result user %4 was unable to add a Configuration Manager administrator user or group to the Configuration Manager environment. Please check the Windows event log on the Configuration Manager provider machine and Active Directory domain controllers.%12</Description> </Message> <Message> <MessageID>31244</MessageID> <Description>Administrative user %1 failed to add a new Configuration Manager administrator user or security group in the Configuration Manager environment due to insufficient rights. User %1 requires at least "Add administrator" and "Read role" permissions.%12</Description> </Message> <Message> <MessageID>31245</MessageID> <Description>Administrative user %1 failed to modify a new Configuration Manager administrator user or security group in the Configuration Manager environment due to insufficient rights. User %1 requires at least "Modify administrator" and "Read role" permissions.%12</Description> </Message> <Message> <MessageID>31246</MessageID> <Description>Administrative user %1 failed to remove a Configuration Manager administrator user or security group from the Configuration Manager environment, due to insufficient rights. User %1 requires at least "Remove administrator" permissions.%12</Description> </Message> <Message> <MessageID>31247</MessageID> <Description>Administrative user %1 tried to remove his or her own account from Configuration Manager. An administrator cannot remove his or her own account from Configuration Manager.%12</Description> </Message> <Message> <MessageID>31248</MessageID> <Description>Administrative user %1 tried to remove Configuration Manager administrator %2 which is the last Configuration Manager administrator associated with the "ConfigMgr Administrator" security role. The Configuration Manager environment requires at least 1 user or security group associated with the "ConfigMgr Administrator" security role.%12</Description> </Message> <Message> <MessageID>31249</MessageID> <Description>The Configuration Manager provider on server "%1" was unable to add user or group "%2", to the "SMS Admins" security group on server "%1". Please manually add user or group "%2" to the "SMS Admins" security group on server "%1", to enable user or group "%2" to administer the Configuration Manager environment.%12</Description> </Message> <Message> <MessageID>39997</MessageID> <Description>%1%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>39998</MessageID> <Description>%1%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>39999</MessageID> <Description>%1%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>40100</MessageID> <Description>User "%1" modified Client Health Settings.%12</Description> </Message> <Message> <MessageID>40200</MessageID> <Description>User "%1" created enrollment record (Device Name=%2) for owner %3.%12</Description> </Message> <Message> <MessageID>40201</MessageID> <Description>User "%1" modified enrollment record (Device Name=%2, Owner=%3).%12</Description> </Message> <Message> <MessageID>40202</MessageID> <Description>User "%1" deleted enrollment record (Device Name=%2, Owner=%3).%12</Description> </Message> <Message> <MessageID>40203</MessageID> <Description>User "%1" regenerated pin for enrollment record (Device Name=%2, Owner=%3).%12</Description> </Message> <Message> <MessageID>40204</MessageID> <Description>User "%1" created enrollment profile (ProfileID=%2, Description=%3) for owner %3.%12</Description> </Message> <Message> <MessageID>40205</MessageID> <Description>User "%1" modified enrollment profile (ProfileID=%2, Description=%3).%12</Description> </Message> <Message> <MessageID>40206</MessageID> <Description>User "%1" deleted enrollment profile (ProfileID=%2, Description=%3).%12</Description> </Message> <Message> <MessageID>40300</MessageID> <Description>User "%1" created client settings object (ID=%2).%12</Description> </Message> <Message> <MessageID>40301</MessageID> <Description>User "%1" modified client settings object (ID=%2).%12</Description> </Message> <Message> <MessageID>40302</MessageID> <Description>User "%1" deleted client settings object (ID=%2).%12</Description> </Message> <Message> <MessageID>40303</MessageID> <Description>User "%1" created client settings assignment (SettingsID=%2, CollectionID=%3).%12</Description> </Message> <Message> <MessageID>40304</MessageID> <Description>User "%1" modified client settings assignment (SettingsID=%2, CollectionID=%3).%12</Description> </Message> <Message> <MessageID>40305</MessageID> <Description>User "%1" deleted client settings assignment (SettingsID=%2, CollectionID=%3).%12</Description> </Message> <Message> <MessageID>40400</MessageID> <Description>User "%1" created Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40401</MessageID> <Description>User "%1" modified Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40402</MessageID> <Description>User "%1" deleted Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40403</MessageID> <Description>User "%1" added one or more packages or applications to the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40404</MessageID> <Description>User "%1" removed one or more packages or applications from the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40405</MessageID> <Description>User "%1" added one or more distribution points to the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40406</MessageID> <Description>User "%1" removed one or more distribution points from the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40407</MessageID> <Description>User "%1" associated one or more collections to the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40408</MessageID> <Description>User "%1" removed one or more collections associated with the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40409</MessageID> <Description>User "%1" cancelled distribution of package "%2" to distribution point "%3".</Description> </Message> <Message> <MessageID>40500</MessageID> <Description>User "%1" created Boundary Group "%3".%12</Description> </Message> <Message> <MessageID>40501</MessageID> <Description>User "%1" modified Boundary Group "%3".%12</Description> </Message> <Message> <MessageID>40502</MessageID> <Description>User "%1" deleted Boundary Group "%3".%12</Description> </Message> <Message> <MessageID>40600</MessageID> <Description>User "%1" created Boundary "%3".%12</Description> </Message> <Message> <MessageID>40601</MessageID> <Description>User "%1" modified Boundary "%3".%12</Description> </Message> <Message> <MessageID>40602</MessageID> <Description>User "%1" deleted Boundary "%3".%12</Description> </Message> <Message> <MessageID>40700</MessageID> <Description>User "%1" created configuration policy assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>40701</MessageID> <Description>User "%1" modified configuration policy assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>40702</MessageID> <Description>User "%1" deleted configuration policy assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>40800</MessageID> <Description>User %1 initiated client operation %3 to collection %2.%12</Description> </Message> <Message> <MessageID>40801</MessageID> <Description>User %1 initiated client operation %3 to %4 members of collection %2.%12</Description> </Message> <Message> <MessageID>40802</MessageID> <Description>User %1 initiated client operation %3 to %4 resources.%12</Description> </Message> <Message> <MessageID>40803</MessageID> <Description>User %1 cancelled client operation %2.%12</Description> </Message> <Message> <MessageID>40804</MessageID> <Description>User %1 deleted client operation %2.%12</Description> </Message> <Message> <MessageID>40850</MessageID> <Description>User %1 invoked action (Name=%2) for device (ResourceId=%3, ResourceType=%4).%12</Description> </Message> <Message> <MessageID>40900</MessageID> <Description>User %1 modified Site [%2] RCM SQL Control Property for DVIEW %3.%12</Description> </Message> <Message> <MessageID>41000</MessageID> <Description>User "%1" created side loading key %2 (%3) . .%12</Description> </Message> <Message> <MessageID>41001</MessageID> <Description>User "%1" modified side loading key %2 (%3) . .%12</Description> </Message> <Message> <MessageID>41002</MessageID> <Description>User "%1" deleted side loading key %2 (%3). .%12</Description> </Message> <Message> <MessageID>42000</MessageID> <Description>User %1 requested retire for a device. ResourceId: %2.%12</Description> </Message> <Message> <MessageID>42001</MessageID> <Description>User %1 requested wipe for a device. ResourceId: %2.%12</Description> </Message> <Message> <MessageID>42010</MessageID> <Description>Administrative user %1 clicked Enable action for the extension Feature %2 %3.%12</Description> </Message> <Message> <MessageID>42011</MessageID> <Description>Administrative user %1 clicked Disable action for the extension Feature %2 %3.%12</Description> </Message> <MessageSolution> <MessageID>-2147012894</MessageID> <Description>The request has timed out.</Description> </MessageSolution> <MessageSolution> <MessageID>2554</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>2600</MessageID> <Description>Possible cause: SQL Server problem on this site or one or more secondary sites. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2601</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2605</MessageID> <Description>Possible cause: Low disk space on the disk drive of the Data Loader inbox. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2606</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2608</MessageID> <Description>Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2609</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2610</MessageID> <Description>Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2612</MessageID> <Description>Possible cause: Refer to the previous SMS Discovery Data Manager message.</Description> </MessageSolution> <MessageSolution> <MessageID>2613</MessageID> <Description>Possible cause: The file "%1" is corrupt. Solution: Delete file "%1". Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2614</MessageID> <Description>Possible cause: The file "%1" is corrupt. Solution: Delete file "%1". Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2615</MessageID> <Description>Possible cause: The file "%1" is corrupt. Solution: Delete file "%1". Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2616</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2617</MessageID> <Description>Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2618</MessageID> <Description>Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2619</MessageID> <Description>Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2620</MessageID> <Description>Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2621</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2622</MessageID> <Description>Possible cause: an SMS Discovery Data Manager bug. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. Possible cause: Something other than SMS created the DDR, and no value was specified as the Name. Solution: Every discovery item needs to have some value that can be identified as the name of the resource. In System DDRs, for example, one of the following values is used as the Name: NetBIOS Name, Resource Names, IP Addresses, IPX Addresses, or MAC Addresses. If none of these are available, or if you have created a DDR of a new architecture, then pick a property and flag it as the Name by ORing decimal 64 in the property's Flags column.</Description> </MessageSolution> <MessageSolution> <MessageID>2623</MessageID> <Description>Solution: Increase the number of client access licenses. You can purchase more from your Microsoft sales representative.</Description> </MessageSolution> <MessageSolution> <MessageID>2624</MessageID> <Description>Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will recreate it. If there is no .ncf file in that directory, stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2625</MessageID> <Description>Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will recreate it. If there is no .ncf file in that directory, stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2626</MessageID> <Description>Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will recreate it. If there is no .ncf file in that directory, stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2627</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2628</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2629</MessageID> <Description>Possible cause: Low disk space on the disk drive containing Asstdata.box. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2631</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2632</MessageID> <Description>Possible cause: Because these notifications are done by a file, there is probably low disk space on one or more destination disk drives. Solution: Make more space available on those disks.%12</Description> </MessageSolution> <MessageSolution> <MessageID>2633</MessageID> <Description>Possible cause: Low disk space on site "%2". Solution: Make more space available on the disk drive containing \Sms\inboxes on site "%2".</Description> </MessageSolution> <MessageSolution> <MessageID>2635</MessageID> <Description>Possible cause: Something other than SMS created the DDR, and no value was specified as the Architecture. Solution: Re-create the DDR, specifying an architecture as part of the discovery item format. Possible cause: an SMS Discovery Data Manager bug. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2636</MessageID> <Description>Possible cause: On a Primary site, it is probably a SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Possible cause: On a secondary site, SMS Discovery Data Manager probably cannot write to a file on the site server, so check for low disk space on the site server. Solution: Make more space available on the site server.</Description> </MessageSolution> <MessageSolution> <MessageID>2639</MessageID> <Description>Possible cause: The operating system and SMS client have been reinstalled on this computer.%12</Description> </MessageSolution> <MessageSolution> <MessageID>2640</MessageID> <Description>Possible cause: The hardware properties of this client have changed substantially, and the client has generated a new SMS identifier.%12</Description> </MessageSolution> <MessageSolution> <MessageID>2642</MessageID> <Description>Possible cause: %1 has been imaged, recovered from backup, or migrated to a new computer. Solution: In the ConfigMgr console, under Computer Management, in the Conflicting Records node, right click %1 and then choose one of the following options: Merge to match the conflicting record with the existing record, New to create a new client record, or Block to block this record from being a client.</Description> </MessageSolution> <MessageSolution> <MessageID>2700</MessageID> <Description>Possible cause: The file is invalid or corrupt. Solution: Do nothing. The file will be moved to the BADMIFs directory where it will be checked for corruption. Any formatting errors will be logged in Dataldr.log. If there are no formatting errors, there might have been a memory error, in which case the MIF will be retried.</Description> </MessageSolution> <MessageSolution> <MessageID>2701</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2702</MessageID> <Description>Possible cause: The delta MIF file came from an SMS 1.2 site, and these sites do not have discovery agents. Solution: Verify that the delta MIF file is from a 1.2 site. If so, do nothing. Possible cause: Discovery Data Manager is not running. Solution: Stop and restart Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2703</MessageID> <Description>Possible cause: The file attempted to update inventory information in the SMS site database that does not already exist, or the file contains invalid syntax. Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the status messages 2714 and 2715, which indicate the resynchronization has begun.</Description> </MessageSolution> <MessageSolution> <MessageID>2706</MessageID> <Description> Solution: Review the immediately preceding status messages from this component for more details. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2712</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2719</MessageID> <Description>Solution: Increase the maximum allowable size, which is defined in the registry key HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Max MIF Size (the default is 5 MB), and wait for SMS Inventory Data Loader to retry the operation.</Description> </MessageSolution> <MessageSolution> <MessageID>2720</MessageID> <Description>Possible cause: SMS Inventory Data Loader detected a MIF file (from the resource with GUID %1) that contains an update request for data that is not in the SMS site database. Therefore, SMS Inventory Data Loader wants to request a resynchronization, or full MIF file, from that resource. Solution: On the resource with GUID %1, set the registry key HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Resynchronize Clients to 1 (true).</Description> </MessageSolution> <MessageSolution> <MessageID>2721</MessageID> <Description>Possible cause: The file has been edited with changes that are not valid for MOF file syntax. Solution: Review the last set of changes to the file for adherence to MOF file syntax.</Description> </MessageSolution> <MessageSolution> <MessageID>2802</MessageID> <Description>Possible cause: Some site configuration change requests contained in the file might not have been applied to the actual site control file; consequently, the site might not be fully reconfigured. Solution: SMS Site Control Manager will try to process the file again the next time a new delta site control file arrives at "%2" or the next time SMS Site Control Manager is restarted, whichever comes first. You can force SMS Site Control Manager to try to process the file again by stopping and restarting SMS Site Control Manager using the SMS Service Manager application.</Description> </MessageSolution> <MessageSolution> <MessageID>2803</MessageID> <Description>Possible cause: The file could be unnecessarily processed again, or it might temporarily seem that the site has not been fully reconfigured. Solution: Both of these problems will be resolved the next time a new delta site control file arrives at "%2" for processing, or the next time SMS Site Control Manager is restarted, whichever comes first. You can force this to occur immediately by stopping and restarting SMS Site Control Manager using the SMS Service Manager application.</Description> </MessageSolution> <MessageSolution> <MessageID>2804</MessageID> <Description>Possible cause: The delta site control file contained a corrupt or invalid site configuration change request. Any successfully processed site configuration change requests in this file will remain in effect (i.e., those changes will not be "undone" from the actual site control file). However, the corrupt site configuration change request and all subsequent site configuration change requests in this file, were not made to the site configuration. Solution: If the file was submitted by an SMS server component, the component will detect that the change was not made and will submit a new delta site control file, usually within a few minutes. If the file was submitted by the SMS Provider on behalf of one of its clients (such as the SMS Administrator console), SMS Hierarchy Manager will eventually detect that the change was not made and submit a new delta site control file. If the file was submitted by the SMS Provider at the current site, SMS Hierarchy Manager should submit a new file within 24 hours. If the file was submitted by the SMS Provider at a parent site, it could take longer than 24 hours. You can cause a new file to be submitted immediately by stopping and restarting SMS Hierarchy Manager at the site that submitted the file using the SMS Service Manager application. SMS Hierarchy Manager will continue to submit new delta site control files until all outstanding site configuration change requests have been made.</Description> </MessageSolution> <MessageSolution> <MessageID>2805</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2806</MessageID> <Description>Possible cause: This site configuration change request and the remaining change requests in the file are unusable. Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2816</MessageID> <Description>Solution: The SMS server components cannot function without this file. SMS Site Control Manager will shut down SMS Executive immediately. Contact Microsoft for help in restoring the actual site control file.</Description> </MessageSolution> <MessageSolution> <MessageID>2817</MessageID> <Description>Solution: SMS Site Control Manager can run only on the site server. SMS Site Control Manager will shut down immediately. Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2818</MessageID> <Description>Solution: The SMS server components cannot run without this item. Site Component Manager will shut down SMS Executive immediately. Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2821</MessageID> <Description>Solution: SMS Site Control Manager will submit a new copy of the actual site control file to SMS Hierarchy Manager the next time a new delta site control file is processed at "%3", or the next time SMS Site Control Manager is restarted, whichever comes first. You can force this to occur immediately by stopping and restarting SMS Site Control Manager using the SMS Service Manager application.</Description> </MessageSolution> <MessageSolution> <MessageID>2822</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2823</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2824</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2825</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2826</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2827</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2828</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2829</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2830</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2831</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2832</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2833</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2834</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2835</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.%12</Description> </MessageSolution> <MessageSolution> <MessageID>2836</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2837</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2838</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2839</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2840</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2841</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2842</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2843</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2844</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2845</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2846</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2847</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2848</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2849</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2850</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2851</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2852</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2853</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2854</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2855</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2856</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2857</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur from time to time, depending on the performance of your network. If this happens repeatedly again, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2858</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur from time to time, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>5805</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>5806</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>5807</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>5808</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6003</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6004</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6005</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6006</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6007</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6100</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: The State System is waiting for the information to become available and will retry obtaining the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>6200</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: The State System is waiting for the information to become available and will retry obtaining the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>6201</MessageID> <Description>Possible cause: Restoring Clients haven't restored the state yet or store deletion wait time has not been reached. Solution: Wait for periodic store deletion time and retry or free up some disk space on SMP drives.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6202</MessageID> <Description>Possible cause: Restoring clients have not restored the state yet or state retention time has not expired. Solution: Wait for store retention time to expire.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6206</MessageID> <Description>Possible cause: Client machine is not part of the domain or access account presented by client is not found.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6207</MessageID> <Description>Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base.</Description> </MessageSolution> <MessageSolution> <MessageID>6208</MessageID> <Description>Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the SMP. For more information, refer to Microsoft Knowledge Base article 838891.</Description> </MessageSolution> <MessageSolution> <MessageID>6300</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: Restart the WDS Service.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6318</MessageID> <Description>Possible cause: PXE may be overloaded. Solution: Reapply the setting at a later time.</Description> </MessageSolution> <MessageSolution> <MessageID>6319</MessageID> <Description>Possible cause: PXE service point is not started or not responding. Solution: Manually restart the PXE service point. Possible cause: WDS service is not responding. Solution: Manually restart the WDS service.</Description> </MessageSolution> <MessageSolution> <MessageID>6320</MessageID> <Description>Possible cause: PXE service point encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow PXE Service Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the PXE Service Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the PXE service point to connect to the SQL server is a member of the SMS_SiteSystemToSQLConnection_<sitecode> group on the SQL server, that the account is not locked out, and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_<sitecode>.) Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered.</Description> </MessageSolution> <MessageSolution> <MessageID>6400</MessageID> <Description>Possible cause: Site server "%4" is under heavy load and is either CPU or I/O constrained. Solution: Use Task Manager to check for processes causing high CPU or I/O utilization. Possible cause: Site server "%4" has a high backlog of files in its inboxes. Solution: Give the system time to work through the current backlog. Do not create any additional tasks that would load the system further.</Description> </MessageSolution> <MessageSolution> <MessageID>6500</MessageID> <Description>Possible cause: The information is not yet available. Solution: The component is waiting for the information to become available and will retry obtaining the information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>6507</MessageID> <Description>Possible cause:Client data was unavailable. Possible cause:Error occurred while reading client data. Possible cause:A network error occurred.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6508</MessageID> <Description>Possible cause:Client data was unavailable. Possible cause:Error occurred while reading client data. Possible cause:A network error occurred. Solution: Sending will be retried on the next retry time.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6509</MessageID> <Description>Possible cause:Client data was unavailable. Possible cause: Solution:%12</Description> </MessageSolution> <MessageSolution> <MessageID>6511</MessageID> <Description>Possible cause:An error occured accessing the information. Solution:%12</Description> </MessageSolution> <MessageSolution> <MessageID>6600</MessageID> <Description>Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.</Description> </MessageSolution> <MessageSolution> <MessageID>6602</MessageID> <Description>Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.</Description> </MessageSolution> <MessageSolution> <MessageID>6603</MessageID> <Description>Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.</Description> </MessageSolution> <MessageSolution> <MessageID>6607</MessageID> <Description>Solution: WSUS Server configuration on the WSUS Site System requires WSUS Server remoting API of version 3.0 SP1 or greater to be installed on the site server. To install the remoting API for version 3.0 SP1 run "WSUSSetup.exe console_install=1" on the site server or refer to the documentation.</Description> </MessageSolution> <MessageSolution> <MessageID>6707</MessageID> <Description>Possible cause: Server %1 synchronization is disabled. Solution: Enable upstream synchronization for server %1 or manually import data from upstream server %2.</Description> </MessageSolution> <MessageSolution> <MessageID>6800</MessageID> <Description>Possible cause: Wrong name specified or permissions to "%1" are incorrect. Solution: Verify that a readable backup control file named "%1" exists.</Description> </MessageSolution> <MessageSolution> <MessageID>6802</MessageID> <Description>Possible cause: "%1" is an interactive Windows application and is waiting for user confirmation of the stop request. Solution: Manually stop this application.</Description> </MessageSolution> <MessageSolution> <MessageID>6804</MessageID> <Description>Possible cause: "%1" does not exist in the specified location on the local computer. Solution: Verify that an executable "%1" exists on the local computer. Also specify its full path in the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>6806</MessageID> <Description>Possible cause: SMS Writer does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. If this problem persists, refer to the SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>10209</MessageID> <Description>Solution: Verify that the client currently has a reliable connection with its assigned client access point (CAP). If the problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>10210</MessageID> <Description>Solution: Verify that the client currently has a reliable connection with its assigned client access point (CAP). If the problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>10211</MessageID> <Description>Solution: Verify that the client currently has a reliable connection with its assigned client access point (CAP). If the problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>10212</MessageID> <Description>Solution: Verify that the client currently has a reliable connection with its assigned client access point (CAP). If the problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>10213</MessageID> <Description>Possible cause: Low disk space. Solution: If this computer is running the Windows NT, 95, or 98 operating system, repair the installation by using the Systems Management tool in Control Panel. Select the Components tab, highlight "SMS Client Base Components," and then click "Repair Installation."</Description> </MessageSolution> <MessageSolution> <MessageID>10214</MessageID> <Description>Possible cause: Low disk space. Solution: Free up some disk space on the client computer.</Description> </MessageSolution> <MessageSolution> <MessageID>10215</MessageID> <Description>Solution: Verify that SMS_Executive is running on the SMS site server. Then, check the client account permissions to verify that the client has read permission to the Clicomp.box directory.</Description> </MessageSolution> <MessageSolution> <MessageID>10216</MessageID> <Description>Solution |