CM2007 SP2 StatusMessages v2

MessageID 1001
Severity
ERROR
Message Source
System Health Validator
1002
ERROR
1003
ERROR
1004
ERROR
1005
ERROR
1006
ERROR
1007
ERROR
1008 1009
ERROR ERROR
System Health Validator System Health Validator
1013
INFORMATIONAL Site Component Manager
1014 1015 1016
INFORMATIONAL Site Component Manager INFORMATIONAL Site Component Manager ERROR Site Component Manager
1017
1018 1019 1020
1021
1022
1023 1024
INFORMATIONAL Site Component Manager ERROR Site Component Manager
1025
ERROR
Site Component Manager
1026 1027
INFORMATIONAL Site Component Manager INFORMATIONAL Site Component Manager
1028
ERROR
1029
1030
1031
ERROR
1032
1033
1034
ERROR
1035
ERROR
1036
ERROR
1037
ERROR
1038
ERROR
1039
ERROR
1040
1041
1042
ERROR
1043
ERROR
1044
ERROR
1045
ERROR
1046
1047
1048
ERROR
1049
ERROR
1050
ERROR
1051
1052
ERROR
1053
1054
ERROR
1055
ERROR
1056
ERROR
1057
1058
ERROR
1059
1060
ERROR
1061
1062
1063
1064
1065
1066
1067
WARNING
1068
1069 1070
1071
1072
WARNING
1073
ERROR
1074
ERROR
1075
1076
ERROR
1077
ERROR
1078 1079
1080
ERROR
1081
ERROR
1082
ERROR
1083
ERROR
1084
ERROR
1085
ERROR
1086
ERROR
1087
ERROR
1088
1089 1090
1091
ERROR
1092 1093 1094
INFORMATIONAL Site Component Manager INFORMATIONAL Site Component Manager INFORMATIONAL Site Component Manager
1095 1096 1097
INFORMATIONAL Site Component Manager INFORMATIONAL Site Component Manager INFORMATIONAL Site Component Manager
1098
ERROR
1099
ERROR
1104
ERROR
SMS Executive
1105
INFORMATIONAL SMS Executive
1106
INFORMATIONAL SMS Executive
1107
WARNING
SMS Executive
1108
ERROR
SMS Executive
1109
ERROR
SMS Executive
1200
INFORMATIONAL Status Manager
1201
1202
WARNING
Status Manager
1203
1204
1205
ERROR
Status Manager
1209
WARNING
Status Manager
1210
WARNING
Status Manager
1211
WARNING
Status Manager
1212
WARNING
Status Manager
1214
WARNING
Status Manager
1215
WARNING
Status Manager
1300
INFORMATIONAL Network Discovery
1301
1302 1303
INFORMATIONAL Network Discovery INFORMATIONAL Network Discovery
1304 1305 1306
INFORMATIONAL Network Discovery INFORMATIONAL Network Discovery INFORMATIONAL Network Discovery
1307
1308 1309
INFORMATIONAL Network Discovery ERROR Network Discovery
1310
ERROR
Network Discovery
1311
ERROR
Network Discovery
1312
WARNING
Network Discovery
1313
WARNING
Network Discovery
1314
ERROR
Network Discovery
1315
ERROR
Network Discovery
1316
ERROR
Network Discovery
1317
WARNING
Network Discovery
1318
ERROR
Network Discovery
1319
WARNING
Network Discovery
1320
WARNING
Network Discovery
1321
ERROR
Network Discovery
1322
ERROR
Network Discovery
1323
ERROR
Network Discovery
1324
1400
INFORMATIONAL NT Logon Server Manager
1401
1402
1403
1404 1405
INFORMATIONAL NT Logon Server Manager ERROR NT Logon Server Manager
1406
WARNING
NT Logon Server Manager
1407
ERROR
1408
1409
1410
1411
1412
WARNING
1413
WARNING
1414
1415
1416
WARNING
1417
1418
WARNING
1419
WARNING
1420
ERROR
1421
WARNING
1500
WARNING
NT Logon Discovery
1501
INFORMATIONAL NT Logon Discovery
1502
1503
ERROR
NT Logon Discovery
1504
ERROR
NT Logon Discovery
1505
ERROR
NT Logon Discovery
1506
1507
1600
ERROR
NT Logon Installation
1601
INFORMATIONAL NT Logon Installation
1602 1603
INFORMATIONAL NT Logon Installation ERROR NT Logon Installation
1604
ERROR
1605
ERROR
1606
1607
1700 1701
INFORMATIONAL Netware Bindery Logon Server Manager ERROR Netware Bindery Logon Server Manager
1702
INFORMATIONAL Netware Bindery Logon Server Manager
1703
1704
1705
1706
ERROR
Netware Bindery Logon Server Manager
1707
ERROR
1708
ERROR
1709
1710
1713
WARNING
1714
WARNING
1715
1716
1717
WARNING
1718
1719
WARNING
1720
WARNING
1721
ERROR
1723
WARNING
1724
1725
ERROR
1800
ERROR
Netware Bindery Logon Discovery
1801
INFORMATIONAL Netware Bindery Logon Discovery
1802 1803
INFORMATIONAL Netware Bindery Logon Discovery ERROR Netware Bindery Logon Discovery
1804
ERROR
1805
ERROR
1806
1807
1808
WARNING
1900
ERROR
Netware Bindery Logon Installation
1901
INFORMATIONAL Netware Bindery Logon Installation
1902
1903
ERROR
1904
ERROR
1905
ERROR
1906
1907
2000
INFORMATIONAL Netware NDS Logon Manager
2001
ERROR
Netware NDS Logon Manager
2002
2003
2004
2005
2006
ERROR
2007
ERROR
2008
ERROR
2009
2010
2016
2017
WARNING
2018
2020
WARNING
2021
ERROR
2023
WARNING
2024
ERROR
2100
ERROR
Netware NDS Logon Discovery
2101
INFORMATIONAL Netware NDS Logon Discovery
2102 2103
INFORMATIONAL Netware NDS Logon Discovery ERROR Netware NDS Logon Discovery
2104
ERROR
2105
ERROR
2106
2107
2108
WARNING
2200
ERROR
Netware NDS Logon Installation
2201
INFORMATIONAL Netware NDS Logon Installation
2202
2203
ERROR
2204
ERROR
2205
ERROR
2206
2207
2300 2301 2302
INFORMATIONAL Distribution Manager INFORMATIONAL Distribution Manager ERROR Distribution Manager
2303 2304
INFORMATIONAL Distribution Manager INFORMATIONAL Distribution Manager
2305
ERROR
Distribution Manager
2306
ERROR
2307
ERROR
2308
ERROR
2309
ERROR
2310 2311
INFORMATIONAL Distribution Manager INFORMATIONAL Distribution Manager
2312
ERROR
2313
ERROR
2314
INFORMATIONAL Distribution Manager
2315 2316
INFORMATIONAL Distribution Manager ERROR Distribution Manager
2317 2318
2319
ERROR
2320
ERROR
2321
ERROR
2322
2323
ERROR
2324
ERROR
2325
ERROR
2326
ERROR
2327
ERROR
2328
ERROR
2329 2330 2331 2332
INFORMATIONAL Distribution Manager INFORMATIONAL Distribution Manager INFORMATIONAL Distribution Manager ERROR Distribution Manager
2333
2334 2335 2336
INFORMATIONAL Distribution Manager INFORMATIONAL Distribution Manager ERROR Distribution Manager
2337
ERROR
2338
2339
2340
ERROR
2341
ERROR
2342 2343
2344
ERROR
2345
ERROR
2346
ERROR
2347
WARNING
2348
ERROR
2349
ERROR
2350
2351
WARNING
2352
ERROR
2353
ERROR
2354
ERROR
2355
WARNING
2400
ERROR
SQL Monitor
2401
WARNING
SQL Monitor
2402
ERROR
SQL Monitor
2404
INFORMATIONAL SQL Monitor
2405
2406
2407
ERROR
SQL Monitor
2408
2409
2410
2411
2412
2413
2414
2415
2416
WARNING
SQL Monitor
2417
2418
2419
2420
WARNING
SQL Monitor
2421 2422 2500
WARNING WARNING ERROR
SQL Monitor SQL Monitor Collection Evaluator
2501
INFORMATIONAL Collection Evaluator
2502
2503
2504
WARNING
Collection Evaluator
2505
WARNING
2506
2507
ERROR
2508
2509
WARNING
2510
2511
ERROR
2512
ERROR
2513
2514
ERROR
2516
2517
ERROR
2518
ERROR
2519
ERROR
2520
ERROR
2521
ERROR
2522
ERROR
2523
ERROR
2524
ERROR
2525
ERROR
2526
ERROR
2527
ERROR
2528
WARNING
2529
ERROR
2530
ERROR
2531
ERROR
2532
ERROR
2533
ERROR
2534
WARNING
2535
ERROR
2536
2537 2538 2539
INFORMATIONAL Collection Evaluator INFORMATIONAL Collection Evaluator INFORMATIONAL Collection Evaluator
2540
2541 2542
INFORMATIONAL Collection Evaluator WARNING Collection Evaluator
2543
WARNING
2544 2545 2546 2547 2548
INFORMATIONAL Collection Evaluator INFORMATIONAL Collection Evaluator CEP Handler INFORMATIONAL Collection Evaluator CEP Handler INFORMATIONAL Collection Evaluator CEP Handler ERROR Collection Evaluator CEP Handler
2549
WARNING
Collection Evaluator CEP Handler
2550
ERROR
2551
ERROR
2552
ERROR
2553
WARNING
Collection Evaluator MEP Handler
2554
ERROR
Collection Evaluator MEP Handler
2600
ERROR
Discovery Data Manager
2601
ERROR
2602 2603
INFORMATIONAL Discovery Data Manager INFORMATIONAL Discovery Data Manager
2604
WARNING
2605
ERROR
2606
ERROR
2607 2608
INFORMATIONAL Discovery Data Manager ERROR Discovery Data Manager
2609
ERROR
2610
ERROR
2611
INFORMATIONAL Discovery Data Manager
2612
ERROR
2613
ERROR
2614
ERROR
2615
ERROR
2616
ERROR
2617
ERROR
2618
ERROR
2619
ERROR
2620
ERROR
2621
ERROR
2622
ERROR
2623
ERROR
2624
ERROR
2625
ERROR
2626
ERROR
2627
ERROR
2628
WARNING
2629
WARNING
2630
2631
ERROR
2632
ERROR
2633
ERROR
2634
2635
ERROR
2636
ERROR
2637
2638
2639
2640
2641
ERROR
2642
2700
ERROR
Data Loader
2701
ERROR
Data Loader
2702
WARNING
Data Loader
2703
WARNING
Data Loader
2704
INFORMATIONAL Data Loader
2705
2706
ERROR
Data Loader
2707
WARNING
Data Loader
2708
2709
2710
2711
2712
ERROR
Data Loader
2713
2714
2715
2716
2717
2718
2719
ERROR
Data Loader
2720
WARNING
Data Loader
2721
ERROR
Data Loader
2722
2723
2724
WARNING
Data Loader
2725
WARNING
Data Loader
2800
INFORMATIONAL Site Control Manager
2801 2802
INFORMATIONAL Site Control Manager WARNING Site Control Manager
2803
WARNING
Site Control Manager
2804
WARNING
2805
WARNING
2806
ERROR
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
ERROR
2817
ERROR
2818
ERROR
2819
2820
2821
WARNING
2822
WARNING
2823
WARNING
2824
WARNING
2825
WARNING
2826
WARNING
2827
WARNING
2828
WARNING
2829
WARNING
2830
WARNING
2831
WARNING
2832
WARNING
2833
WARNING
2834
WARNING
2835
WARNING
2836
WARNING
2837
WARNING
2838
WARNING
2839
WARNING
2840
WARNING
2841
WARNING
2842
WARNING
2843
WARNING
2844
WARNING
2845
WARNING
2846
WARNING
2847
WARNING
2848
WARNING
2849
WARNING
2850
WARNING
2851
WARNING
2852
WARNING
2853
WARNING
2854
WARNING
2855
WARNING
2856
WARNING
2857
WARNING
2858
WARNING
2859
WARNING
2860
WARNING
2861
WARNING
2862
WARNING
2863
WARNING
2864
WARNING
2865
2866
2867
2868
WARNING
2869
2870
WARNING
2900
ERROR
Client Install Data Manager
2901
ERROR
2902
ERROR
2903
ERROR
2904
ERROR
2905
ERROR
2906
ERROR
2907
ERROR
2908
INFORMATIONAL Client Install Data Manager
2909
2910
WARNING
2911
2912
WARNING
2913
2914
2915
2916
WARNING
2917
ERROR
2918
WARNING
2919
WARNING
2920
ERROR
2921
ERROR
3000
ERROR
Client Configuration Manager
3001
ERROR
3002
WARNING
3003
ERROR
3004
ERROR
3005
ERROR
3006
WARNING
3007
WARNING
3008
WARNING
3009
WARNING
3010
WARNING
3011
ERROR
3012
ERROR
3013
WARNING
3014
WARNING
3015
WARNING
3016
WARNING
3017
WARNING
3018
WARNING
3019
WARNING
3100
ERROR
WinNT Remote Client Install Manager
3101
ERROR
WinNT Remote Client Install Manager
3102
INFORMATIONAL WinNT Remote Client Install Manager
3103
3104
3200
ERROR
Inventory Processor
3201
ERROR
Inventory Processor
3300
ERROR
Hierarchy Manager
3301
ERROR
Hierarchy Manager
3302
ERROR
Hierarchy Manager
3303
ERROR
Hierarchy Manager
3304
ERROR
Hierarchy Manager
3305
ERROR
Hierarchy Manager
3306
INFORMATIONAL Hierarchy Manager
3307
3308
ERROR
Hierarchy Manager
3309
3310
3311
3312
3313
WARNING
Hierarchy Manager
3314
ERROR
Hierarchy Manager
3315
ERROR
Hierarchy Manager
3316
ERROR
Hierarchy Manager
3317
WARNING
Hierarchy Manager
3318
WARNING
Hierarchy Manager
3319
ERROR
Hierarchy Manager
3320
ERROR
Hierarchy Manager
3321 3322
INFORMATIONAL Hierarchy Manager WARNING Hierarchy Manager
3323 3324
INFORMATIONAL Hierarchy Manager WARNING Hierarchy Manager
3400
ERROR
Scheduler
3401
WARNING
Scheduler
3402
INFORMATIONAL Scheduler
3500
ERROR
LAN, RAS, WINSOCK Sender/Receiver
3501
ERROR
3502
ERROR
3503
ERROR
3504
ERROR
3505
ERROR
3506
ERROR
3507
ERROR
3508
ERROR
3509
ERROR
3510
ERROR
3511
ERROR
3512
ERROR
3513
ERROR
3514
INFORMATIONAL LAN, RAS, WINSOCK Sender/Receiver
3515
3516
3517
ERROR
3518
ERROR
3519
ERROR
3520
ERROR
3521
ERROR
3522
ERROR
3523 3524
INFORMATIONAL LAN, RAS, WINSOCK Sender/Receiver ERROR LAN, RAS, WINSOCK Sender/Receiver
3525 3526 3527
INFORMATIONAL LAN, RAS, WINSOCK Sender/Receiver ERROR LAN, RAS, WINSOCK Sender/Receiver
3528 3529
INFORMATIONAL LAN, RAS, WINSOCK Sender/Receiver WARNING LAN, RAS, WINSOCK Sender/Receiver
3530
ERROR
3531
3532
WARNING
3533
3600
WARNING
Inbox Manager, Inbox Manager Assistant
3601
ERROR
3602
ERROR
3603
ERROR
3604
ERROR
3605
ERROR
3606
WARNING
Inbox Monitor
3607
WARNING
Outbox Monitor
3700 3701
INFORMATIONAL Software Inventory Processor WARNING Software Inventory Processor
3702
ERROR
Software Inventory Processor
3703
INFORMATIONAL Software Inventory Processor
3704
3705
3706
WARNING
3707
WARNING
3708
ERROR
3709
3800 3801 3802 3803 3804
ERROR ERROR ERROR ERROR
Offer Status Summarizer Offer Status Summarizer Offer Status Summarizer Offer Status Summarizer
INFORMATIONAL Offer Status Summarizer
3805
INFORMATIONAL Offer Status Summarizer
3806 3807 3808 3809 3810 3811 3812
WARNING WARNING WARNING WARNING WARNING WARNING WARNING
Offer Status Summarizer Offer Status Summarizer Offer Status Summarizer Offer Status Summarizer Offer Status Summarizer Offer Status Summarizer Offer Status Summarizer
3813
WARNING
Offer Status Summarizer
3814
WARNING
Offer Status Summarizer
3900 3901 4000
INFORMATIONAL Offer Manager INFORMATIONAL Offer Manager INFORMATIONAL Replication Manager
4001
WARNING
Replication Manager
4100
INFORMATIONAL NT User Group Discovery Agent
4101
ERROR
NT User Group Discovery Agent
4102 4103
INFORMATIONAL NT User Group Discovery Agent ERROR NT User Group Discovery Agent
4104
ERROR
4105
ERROR
4200
ERROR
NT Server Discovery Agent
4201
WARNING
NT Server Discovery Agent
4202
INFORMATIONAL NT Server Discovery Agent
4300
ERROR
NT User Discovery Agent
4301
WARNING
4302 4303
INFORMATIONAL NT User Discovery Agent ERROR NT User Discovery Agent
4304
ERROR
4305
ERROR
4400 4401
INFORMATIONAL Despooler ERROR Despooler
4402
ERROR
Despooler
4403
ERROR
Despooler
4404
ERROR
Despooler
4405
ERROR
Despooler
4406
ERROR
Despooler
4407 4500 4501 4502 4503 4504 4505 4506 4507 4508
INFORMATIONAL Despooler INFORMATIONAL Base Summarizer INFORMATIONAL Base Summarizer INFORMATIONAL Base Summarizer INFORMATIONAL Base Summarizer WARNING WARNING WARNING WARNING WARNING Base Summarizer Base Summarizer Base Summarizer Base Summarizer Base Summarizer
4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4600
WARNING WARNING WARNING WARNING WARNING WARNING ERROR ERROR ERROR ERROR
Base Summarizer Base Summarizer Base Summarizer Base Summarizer Base Summarizer Base Summarizer Base Summarizer Base Summarizer Base Summarizer Base Summarizer
INFORMATIONAL Base Summarizer INFORMATIONAL Base Summarizer INFORMATIONAL Component Summarizer
4601
WARNING
Component Summarizer
4602
INFORMATIONAL Component Summarizer
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
WARNING
4613
WARNING
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4700
INFORMATIONAL Site System Status Summarizer
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4800
ERROR
Netware Bindery Server Discovery Agent
4801
WARNING
Netware Bindery Server Discovery Agent
4802
INFORMATIONAL Netware Bindery Server Discovery Agent
4900 4901 4902
4903
ERROR
4904
4905
ERROR
4906
4907
ERROR
4908
ERROR
4909
ERROR
4910
4911 4912
4913
ERROR
4914 4915
4916
ERROR
4917
ERROR
4918
WARNING
4919
4920
ERROR
4921
4922
ERROR
4923 4924
ERROR WARNING
Site Component Manager Site Component Manager
4950
ERROR
4951
ERROR
4952
ERROR
4953
ERROR
4954
ERROR
4955
ERROR
4956
ERROR
4957
ERROR
4958
ERROR
4959
ERROR
4960
ERROR
4961
ERROR
4962
ERROR
4963
ERROR
4964
ERROR
4965
ERROR
4966
ERROR
4967
ERROR
4968
ERROR
4969
ERROR
4970
ERROR
5000
ERROR
Site Backup
5001 5002
INFORMATIONAL Site Backup ERROR Site Backup
5003 5004
5005 5006
5007
INFORMATIONAL Site Backup
5008
ERROR
Site Backup
5009 5010
INFORMATIONAL Site Backup WARNING Site Backup
5011
5012
WARNING
Site Backup
5013
5014
WARNING
Site Backup
5015 5016
5017
ERROR
Site Backup
5018
ERROR
Site Backup
5019
ERROR
Site Backup
5020 5021
5022
ERROR
Site Backup
5023 5024
5025
ERROR
Site Backup
5026
ERROR
Site Backup
5027
ERROR
Site Backup
5028
WARNING
Site Backup
5029
WARNING
Site Backup
5030
WARNING
Site Backup
5031
WARNING
Site Backup
5032
ERROR
Site Backup
5033
ERROR
Site Backup
5034
WARNING
Site Backup
5035 5036 5037 5038 5039
INFORMATIONAL Site Backup INFORMATIONAL Site Backup INFORMATIONAL Site Backup WARNING WARNING Site Backup Site Backup
5040 5041
5042
5043
ERROR
Site Backup
5044
ERROR
Site Backup
5045
ERROR
Site Backup
5046 5047 5048
ERROR ERROR ERROR
Site Backup Site Backup Site Backup
5049
ERROR
Site Backup
5050
ERROR
Site Backup
5051
WARNING
Site Backup
5052
WARNING
Site Backup
5053
WARNING
Site Backup
5054 5055
INFORMATIONAL Site Backup INFORMATIONAL Site Backup
5056
5057 5058
5100
INFORMATIONAL Policy Provider
5101
5102 5103 5104 5105 5106 5107
INFORMATIONAL Policy Provider INFORMATIONAL Policy Provider INFORMATIONAL Policy Provider INFORMATIONAL Policy Provider INFORMATIONAL Policy Provider INFORMATIONAL Policy Provider
5108
5109 5110
INFORMATIONAL Policy Provider INFORMATIONAL Policy Provider
5111 5112
ERROR WARNING
Policy Provider Policy Provider
5113
ERROR
Policy Provider
5114
5115
ERROR
Policy Provider
5116
5117 5118
INFORMATIONAL Policy Provider ERROR Policy Provider
5200
ERROR
Active Directory System Discovery Agent
5201
WARNING
5202
INFORMATIONAL Active Directory System Discovery Agent
5203
WARNING
5204
ERROR
5300
ERROR
Active Directory User Discovery Agent
5301
WARNING
5302
INFORMATIONAL Active Directory User Discovery Agent
5303
WARNING
5304
ERROR
5350
ERROR
Active Directory Security Group Discovery Agent
5351
WARNING
5352
INFORMATIONAL Active Directory Security Group Discovery Agent
5353
WARNING
5354
ERROR
5400
ERROR
Management Point
5401
WARNING
Management Point
5410
ERROR
Management Point
5411
WARNING
Management Point
5412
ERROR
Management Point
5413
WARNING
Management Point
5414
ERROR
Management Point
5415
WARNING
Management Point
5416
WARNING
Management Point
5417
WARNING
Management Point
5418
WARNING
Management Point
5419
WARNING
Management Point
5420
ERROR
Management Point
5421
INFORMATIONAL Management Point
5430
WARNING
Management Point
5431
WARNING
Management Point
5432
ERROR
Management Point
5433
ERROR
Management Point
5434
ERROR
Management Point
5435
ERROR
Management Point
5436
ERROR
Management Point
5437
ERROR
Management Point
5438
ERROR
Management Point
5439
ERROR
Management Point
5440
WARNING
Management Point
5441 5442 5443
ERROR
Management Point
INFORMATIONAL Management Point WARNING Management Point
5444 5445
WARNING WARNING
Management Point Management Point
5446 5447
WARNING WARNING
Management Point Management Point
5480
ERROR
Management Point
5481
ERROR
Management Point
5482
ERROR
Management Point
5483
ERROR
Management Point
5484
INFORMATIONAL Management Point
5485
WARNING
Management Point
5486
ERROR
Management Point
5487
ERROR
Management Point
5500
ERROR
Active Directory System Group Discovery Agent
5501
WARNING
5502
INFORMATIONAL Active Directory System Group Discovery Agent
5503
WARNING
5504
ERROR
5600
ERROR
Software Metering Processor
5601
ERROR
5602
ERROR
5603
ERROR
5604
ERROR
5605
ERROR
5606
ERROR
5607
ERROR
5608
WARNING
5609
INFORMATIONAL Software Metering Processor
5610
INFORMATIONAL Software Metering Processor
5611 5612
INFORMATIONAL Software Metering Processor ERROR Software Metering Processor
5613
ERROR
5614
ERROR
5615
ERROR
5616
WARNING
5617
ERROR
5700 5701 5702
ERROR WARNING ERROR
Device Management Point Device Management Point Device Management Point
5703 5720 5721 5722 5723 5724 5725 5726 5727 5728 5729 5740 5741 5742 5743 5744 5745 5746 5747 5760 5761 5762 5763 5800 5801 5802
ERROR WARNING WARNING ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR
Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point Device Management Point
ERROR Device Management Point INFORMATIONAL Configuration Item Assignment Manager INFORMATIONAL Configuration Item Assignment Manager INFORMATIONAL Configuration Item Assignment Manager
5803
INFORMATIONAL Configuration Item Assignment Manager
5804
ERROR
Configuration Item Assignment Manager
5805
WARNING
5806
ERROR
5807
ERROR
5808
ERROR
6000 6001 6002
INFORMATIONAL Object Replication Manager INFORMATIONAL Object Replication Manager INFORMATIONAL Object Replication Manager
6003
ERROR
Object Replication Manager
6004
ERROR
6005
ERROR
6006
WARNING
6007
ERROR
6100
ERROR
State System
6101
ERROR
State System
6103
ERROR
State System
6104
ERROR
State System
6105
ERROR
State System
6200
ERROR
State Migration Point
6201
ERROR
6202
ERROR
6203 6204
WARNING WARNING
State Migration Point State Migration Point
6205 6206
INFORMATIONAL State Migration Point ERROR State Migration Point
6207
ERROR
6208
ERROR
6209 6210
ERROR ERROR
State Migration Point State Migration Point
6300
ERROR
PXE Service Point
6301
ERROR
PXE Service Point
6302
ERROR
PXE Service Point
6303
ERROR
PXE Service Point
6304
ERROR
PXE Service Point
6305
ERROR
PXE Service Point
6306
WARNING
PXE Service Point
6307
ERROR
PXE Service Point
6308
ERROR
PXE Service Point
6309
ERROR
PXE Service Point
6310
WARNING
PXE Service Point
6311
INFORMATIONAL PXE Service Point
6312
6313
6314
6315
ERROR
PXE Service Point
6316
ERROR
PXE Service Point
6317
WARNING
PXE Service Point
6318
ERROR
PXE Service Point
6319
ERROR
PXE Service Point
6320
ERROR
PXE Service Point
6321
6322
6400
WARNING
Component Monitor
6500
ERROR
Wake On LAN
6501 6502 6503 6504
INFORMATIONAL Wake On LAN INFORMATIONAL Wake On LAN INFORMATIONAL Wake On LAN INFORMATIONAL Wake On LAN
6505
INFORMATIONAL Wake On LAN
6506
6507
WARNING
Wake On LAN
6508
ERROR
Wake On LAN
6509
ERROR
Wake On LAN
6510
6511
ERROR
Wake On LAN
6512
6513
ERROR
Wake On LAN
6600
ERROR
WSUS Configuration Manager
6602
ERROR
6603
ERROR
6607
ERROR
6609
INFORMATIONAL WSUS Configuration Manager
6610
WARNING
6611
WARNING
6612 6613
ERROR ERROR
WSUS Configuration Manager WSUS Configuration Manager
6614
ERROR
6615
6616
6617
ERROR
6618
6700
ERROR
WSUS Sync Manager
6701 6702 6703
INFORMATIONAL WSUS Sync Manager INFORMATIONAL WSUS Sync Manager ERROR WSUS Sync Manager
6704
INFORMATIONAL WSUS Sync Manager
6705
6706
6707
WARNING
WSUS Sync Manager
6709 6710 6711 6800
INFORMATIONAL WSUS Sync Manager INFORMATIONAL WSUS Sync Manager ERROR WSUS Sync Manager ERROR Site VSS Writer
6801 6802
INFORMATIONAL Site VSS Writer ERROR Site VSS Writer
6803 6804
6805
INFORMATIONAL Site VSS Writer
6806
ERROR
Site VSS Writer
6807 6808
6809 6810
INFORMATIONAL Site VSS Writer WARNING Site VSS Writer
6811
ERROR
Site VSS Writer
6812 6813
6814
ERROR
Site VSS Writer
6815
WARNING
Site VSS Writer
6816
WARNING
Site VSS Writer
6817
WARNING
Site VSS Writer
6818
WARNING
Site VSS Writer
6819
ERROR
Site VSS Writer
6820
ERROR
Site VSS Writer
6821
ERROR
Site VSS Writer
6822 6823 6824
INFORMATIONAL Site VSS Writer INFORMATIONAL Site VSS Writer WARNING Site VSS Writer
6825
ERROR
Site VSS Writer
6826 6827 6828
ERROR ERROR WARNING
Site VSS Writer Site VSS Writer Site VSS Writer
6829 6830 6831 6832 6833 6900
INFORMATIONAL Site VSS Writer INFORMATIONAL Site VSS Writer INFORMATIONAL Site VSS Writer WARNING Site VSS Writer INFORMATIONAL Site VSS Writer ERROR Fallback Status Point
6901
ERROR
Fallback Status Point
6902
WARNING
6903
ERROR
6904
ERROR
6905
ERROR
7000
ERROR
WSUS Control Manager
7001
ERROR
7002
ERROR
7003
ERROR
7004
ERROR
7100
ERROR
Multicast Service Point
7101
ERROR
7102
ERROR
7103
ERROR
7104
ERROR
7105
ERROR
7106
ERROR
7107
ERROR
7108
ERROR
7109 7110 7111 7150 7200
WARNING WARNING WARNING ERROR ERROR
Multicast Service Point Multicast Service Point Multicast Service Point Multicast Service Point AMT Operation Manager
7201
ERROR
AMT Operation Manager
7202
INFORMATIONAL AMT Operation Manager
7203
INFORMATIONAL AMT Operation Manager
7204
ERROR
7205 7206
WARNING ERROR
AMT Operation Manager AMT Operation Manager
7207
ERROR
7208
ERROR
7209
ERROR
7210
WARNING
7211
ERROR
7212
ERROR
7213
ERROR
7214
ERROR
7215 7216
ERROR ERROR
AMT Operation Manager AMT Operation Manager
7217
WARNING
7300
ERROR
Asset Intelligence Update Service Point
7400 7401 7402 7403 7404 7405 7500
ERROR ERROR ERROR ERROR ERROR ERROR WARNING
SRS Reporting Point SRS Reporting Point SRS Reporting Point SRS Reporting Point SRS Reporting Point SRS Reporting Point Asset Intelligence KB Manager
7501
ERROR
Asset Intelligence KB Manager
7502
WARNING
Asset Intelligence KB Manager
7600
ERROR
AMT Control Manager
7601
ERROR
AMT Control Manager
7602
ERROR
AMT Control Manager
7603
ERROR
AMT Control Manager
7604
ERROR
AMT Control Manager
7605
WARNING
AMT Control Manager
7606
ERROR
AMT Control Manager
7607
ERROR
AMT Control Manager
7608
WARNING
AMT Control Manager
7609
ERROR
AMT Control Manager
Message Text
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. Solution: Either extend the schema for the currently designated Active Directory forest, or configure Network Access Protection to store the health state references in a different Active Directory forest that has the Configuration Manager 2007 schema extensions. For more information about extending the schema, see the Help topic How to Extend the Active Directory Schema for Configuration Manager. For more information on configuring the location of the health state references, see the Help topic How to Specify the Location of the Health State Reference.
The Active Directory (AD) Cache Client failed to search the AD Forest for NAP-related ConfigMgr Health Information. The error encountered was %1. The file cache store in the System Health Validator point failed to initialize properly. The error encountered was %1. The File Cache Store update failed. This will potentially cause the ConfigMgr System Health Validator to not validate the incoming NAP statement of health requests correctly. The error encountered was %1. The File Cache Store could not be persisted to disk properly. This will potentially cause the ConfigMgr System Health Validator to not validate the incoming NAP statement of health requests correctly. The error encountered was %1. The ConfigMgr System Health Validator Registry Settings failed to get loaded properly. This will prevent the ConfigMgr System Health Validator Service from functioning properly. The error encountered was %1. Changes to ConfigMgr System Health Validator Registry Settings failed to get processed properly. This might prevent the ConfigMgr System Health Validator Service from functioning as desired. The error encountered was %1. The ConfigMgr System Health Validator Service failed to initialize properly. The error encountered was %1. The AD Cache Client failed to initialize properly. The error encountered was %1.
SMS Site Component Manager detected that this component should be installed on this site system. SMS Site Component Manager will attempt to install the component every %1 minutes until the installation succeeds. SMS Site Component Manager is installing this component on this site system. SMS Site Component Manager successfully installed this component on this site system. SMS Site Component Manager failed to install this component on this site system. Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the installation in %1 minutes. To force SMS Site Component Manager to immediately retry the installation, stop and restart SMS Site Component Manager using the SMS Service Manager. SMS Site Component Manager detected that this component should be reinstalled on this site system. SMS Site Component Manager will attempt to install the component every %1 minutes until the installation succeeds. SMS Site Component Manager is reinstalling this component on this site system. SMS Site Component Manager successfully reinstalled this component on this site system. SMS Site Component Manager failed to reinstall this component on this site system. Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the reinstallation in %1 minutes. To force SMS Site Component Manager to immediately retry the reinstallation, stop and restart SMS Site Component Manager using the SMS Service Manager. SMS Site Component Manager detected that this component should be deinstalled from this site system. SMS Site Component Manager will attempt to deinstall the component every %1 minutes. SMS Site Component Manager will abort the deinstallation if it fails to succeed after %2 minutes. SMS Site Component Manager is deinstalling this component from this site system.
SMS Site Component Manager successfully deinstalled this component from this site system. SMS Site Component Manager failed to deinstall this component from this site system. Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the deinstallation in %1 minutes. To force SMS Site Component Manager to immediately retry the deinstallation, stop and restart SMS Site Component Manager using the SMS Service Manager. SMS Site Component Manager failed to deinstall this component from this site system. Solution: Review the previous status messages to determine the exact reason for the failure. The deinstallation has repeatedly failed for %1 minutes and will probably never succeed, therefore SMS Site Component Manager not retry the deinstallation. You might ignore this message and do nothing if the site system is no longer in service or the operating system has been reinstalled on the site system. Otherwise the component may still be installed on this site system, and you will have to manually deinstall it. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS Site Component Manager is configuring site system "%1" to receive SMS server components. SMS Site Component Manager successfully configured site system "%1" to receive SMS server components. SMS Site Component Manager will now begin installing the components on the site system. SMS Site Component Manager failed to configure site system "%1" to receive SMS server components. Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager cannot install any SMS server components on this site system until the site system is configured successfully. SMS Site Component Manager will automatically retry this operation in %2 minutes. To force SMS Site Component Manager to immediately retry this operation, stop and restart SMS Site Component Manager using the SMS Service Manager. SMS Site Component Manager is reconfiguring site system "%1" to receive SMS server components.
SMS Site Component Manager successfully reconfigured site system "%1" to receive SMS server components. SMS Site Component Manager will now begin reinstalling the components on the site system. SMS Site Component Manager failed to reconfigure site system "%1" to receive SMS server components. Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager cannot reinstall any SMS server components on this site system until the site system is reconfigured successfully. SMS Site Component Manager will automatically retry this operation in %2 minutes. To force SMS Site Component Manager to immediately retry this operation, stop and restart SMS Site Component Manager using the SMS Service Manager. SMS Site Component Manager detected that all SMS server components have been deinstalled from site system "%1". SMS Site Component Manager is removing remaining accounts, files, and registry keys associated with the SMS server components from the site system. SMS Site Component Manager successfully removed all accounts, files, and registry keys associated with the SMS server components from site system "%1". SMS Site Component Manager failed to remove all accounts, files, and registry keys associated with the SMS server components from site system "%1". Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry this operation in %2 minutes. To force SMS Site Component Manager to immediately retry this operation, stop and restart SMS Site Component Manager using the SMS Service Manager.
SMS Site Component Manager failed to remove all accounts, files, and registry keys associated with the SMS server components from site system "%1". Solution: Review the previous status messages to determine the exact reason for the failure. This operation has repeatedly failed for %2 minutes and will probably never succeed, therefore SMS Site Component Manager not retry this operation again. You might ignore this message and do nothing if the site system is no longer in service or the operating system has been reinstalled on the site system. Otherwise some remnants of the SMS server components might still be installed on this site system, and you will have to manually remove them. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS Site Component Manager could not access site system "%1" due to an unexpected failure within the network abstraction layer (NAL).%12 Solution: To examine the exact failure, turn on logging for SMS Site Component Manager using the SMS Service Manager, wait for SMS Site Component Manager to retry this operation, and review the log messages for SMS Site Component Manager. Please refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Site Component Manager could not access site system "%1".%12 Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to connect to the site system. Solution: Verify that the Site Server's computer$ account has administrator rights on the remote site system. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. Possible cause: You took the site system out of service and do not intend on using it as a site system any more. Solution: Remove this site system from the list of site systems for this site. The list appears in the Site Systems node of the Administrator console.
SMS Site Component Manager detected that site system "%1" is not running the Microsoft Windows NT Server operating system.%12 Possible cause: You have not installed the required version of Windows NT Server on the site system. Solution: Install the required version of Windows NT Server on the site system. Refer to your SMS documentation to determine the required version. Possible cause: You accidentally configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console.
SMS Site Component Manager detected that the site server does not contain the binary files for the platform (processor architecture) of site system "%1".%12 Possible cause: When installing this site, you did not specify that the binary files for this site system's platform should be installed on the site server. Solution: Use SMS Setup to modify the configuration of this site. When asked to select the server platforms for this site, select this site system's platform. Possible cause: You accidently configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Component Manager detected that site system "%1" is SMS Site based on an Intel x86 or compatible platform (processor architecture). SMS Site Component Manager detected that site system "%1" is based on the Alpha platform (processor architecture).
SMS Site Component Manager could not detect which version of the Microsoft Windows NT Server operating system is running on site system "%1".%12 Possible cause: You have not installed the required version of Windows NT Server on the site system. Solution: Install the required version of Windows NT Server on the site system. Refer to your SMS documentation to determine the required version. Possible cause: You accidentally configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. SMS Site Component Manager detected that site system "%1" is running the Microsoft Windows NT Server operating system version %2, which is not a supported operating system for this version of SMS. Possible cause: You have not installed the required version of Windows NT Server on the site system. Solution: Install the required version of Windows NT Server on the site system. Refer to your SMS documentation to determine the required version. Possible cause: You accidentally configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console.
SMS Site Component Manager detected that site system "%1" is running the Microsoft Windows NT Server operating system version %2 service pack %3, which is not a supported operating system for this version of SMS. Possible cause: You have not installed the required version of Windows NT Server on the site system. Solution: Install the required version of Windows NT Server on the site system. Refer to your SMS documentation to determine the required version. Possible cause: You accidentally configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console. SMS Site Component Manager detected that site system "%1" is running the Microsoft Windows NT Workstation operating system, which is not a supported operating system for this version of SMS. Possible cause: You have not installed the required version of Windows NT Server on the site system. Solution: Install the required version of Windows NT Server on the site system. Refer to your SMS documentation to determine the required version. Possible cause: You accidentally configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console. SMS Site Component Manager detected that site system "%1" is running the Microsoft Windows NT Server operating system version %2. SMS Site Component Manager detected that site system "%1" is running the Microsoft Windows NT Server operating system version %2 service pack %3.
SMS Site Component Manager detected that site system "%1" is currently in use by SMS site %2. Possible cause: You accidentally configured SMS to use this site system as part of this site and as part of site %2. Solution: Remove this site system from the list of site systems for this site or for site %2. The list appears in the Site Systems node of the SMS Administrator console. SMS Site Component Manager could not find an NTFS partition on site system "%1" to hold the SMS server components' files.%12 Possible cause: The site system does not contain an NTFS partition. Solution: Using the Windows NT Disk Administrator, create an NTFS partition on the site system, or convert an existing FAT partition to NTFS. Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: You might have disabled the default drive letter shares for security purposes. SMS requires these shares. Please reenable these shares using the Windows NT Disk Administrator. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site
SMS Site Component Manager could not create the SMS server components' installation directory "%2" on site system "%1" or set the correct permissions on the directory.%12 Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: You might have disabled the default drive letter shares for security purposes. SMS requires these shares. Please reenable these shares using the Windows NT Disk Administrator. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. SMS Site Component Manager created the SMS server components' installation directory "%2" on site system "%1". SMS Site Component Manager selected this partition because it was the NTFS partition with the most free space.
SMS Site Component Manager could not create the "%2" account on site system "%1".%12 Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. When SMS Site Component Manager installs SMS 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.
SMS Site Component Manager created the "%2" account on site system "%1". When SMS Site Component Manager installs SMS 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.
SMS Site Component Manager could not verify that the "%2" account exists on site system "%1".%12 Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. When SMS Site Component Manager installs SMS 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.
SMS Site Component Manager could not read the SMS Server Network Connection account data, which is stored in the SMS installation directory on the site server.%12 Possible cause: The SMS Service account no longer has sufficient access rights to read the data. Solution: Verify that the SMS Service account has full administrative rights to the site server, and that the SMS_SITE_COMPONENT_MANAGER service is configured to log in as the SMS Service account. Possible cause: The data is corrupt. Possible cause: Please refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Site Component Manager could not read the write SMS Server Network Connection account data to the SMS server components' installation directory "%2" on site system "%1".%12 Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: You might have disabled the default drive letter shares for security purposes. SMS requires these shares. Please reenable these shares using the Windows NT Disk Administrator. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. Because site system "%1" might have malfunctioned, as a safety measure SMS Site Component Manager will attempt to reconfigure it to receive SMS server components and reinstall all of the SMS server components on it. This attempt will occur in %2 minutes.
SMS Site Component Manager could not remove the "%2" account from site system "%1".%12 Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. When SMS Site Component Manager installed SMS services on the site system, it configured 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.
SMS Site Component Manager removed the "%2" account from site system "%1". When SMS Site Component Manager installed SMS services on the site system, it configured them to log in using this account. If the site system is a stand-alone server, the account was a local machine account with full administrative rights. If the site system is a domain controller, the account was a domain account with domain user rights and full administrative rights only to the site system.
SMS Site Component Manager could not remove the SMS server components' installation directory "%2" on site system "%1".%12 Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: You might have disabled the default drive letter shares for security purposes. SMS requires these shares. Please reenable these shares using the Windows NT Disk Administrator. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network.
SMS Site Component Manager removed the SMS server components' installation directory "%2" on site system "%1". SMS Site Component Manager detected that the SMS service account has changed, and will now reinstall all of the SMS server components that are installed on the site server. SMS Site Component Manager was instructed by SMS Setup to shut down the site in preparation for a site upgrade, modification, or reset operation. SMS Site Component Manager will now stop all of the SMS server components on all of the site systems, mark all of these components for reinstallation, and then stop itself. SMS Site Component Manager will reinstall all of the components when it is restarted by SMS Setup at the end of the site upgrade, modification, or reset operation. SMS Site Component Manager is stopping all of the SMS server components on site system "%1".
SMS Site Component Manager will not stop any SMS server components on site system "%1" because no SMS server components are installed on the site system. SMS Site Component Manager will now try again to stop all of the SMS server components on site system "%1", as requested by SMS Setup. SMS Site Component Manager will now cease trying to stop all of the SMS server components on site system "%1", as requested by SMS Setup. The SMS server components were not properly deinstalled from the site system. Solution: Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Site Component Manager was instructed by SMS Setup to deinstall the site. SMS Site Component Manager will now deinstall all of the SMS server components from all of the site systems. SMS Site Component Manager is deinstalling all of the SMS server components from site system "%1". SMS Site Component Manager will not deinstall any SMS server components from site system "%1" because no SMS server components are installed on the site system. SMS Site Component Manager will now try again to deinstall all of the SMS server components from site system "%1", as requested by SMS Setup. SMS Site Component Manager will now cease trying to deinstall all of the SMS server components from site system "%1", as requested by SMS Setup. The SMS server components were not properly deinstalled from the site system. Solution: Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Site Component Manager could not detect how much disk space was available in the "%1" directory on this site system.%12 Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager 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 connect to the site system. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network.
SMS 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. Solution: Make at least %1 available on the drive containing the "%2" directory. SMS 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. SMS Site Component Manager will proceed with the installation of this component.
SMS Site Component Manager could not copy file "%1" to "%2".%12 SMS 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. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager 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. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network.
SMS Site Component Manager could not copy file "%1" to "%2".%12 SMS 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. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager 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. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network.
SMS Site Component Manager copied file "%1" to "%2". SMS Site Component Manager did not copy file "%1" to "%2", because the source file is not a newer version than the destination file.
SMS Site Component Manager detected that the %1 service was installed on site system "%2", but SMS Site Component Manager could not deinstall the service.%12 Possible cause: SMS Site Component Manager 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. SMS Site Component Manager uses the %1 service to install SMS server components, and cannot install component %3 until the existing %1 service can be deinstalled. If this problem persists and you cannot fix it, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12 Possible cause: SMS Site Component Manager 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. Possible cause: Something other than SMS deleted account "%3" or changed its password. Solution: Reset the site using SMS Setup. SMS Site Component Manager will recreate the account as part of the reset process. SMS Site Component Manager uses the %1 service to install SMS server components, and cannot install component %4 until the %1 service can be installed. If this problem persists and you cannot fix it, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12 Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the SMS Service or Site System Connection accounts are properly configured to allow SMS to administer the site system. If advanced security verify the site server machine account are properly configured to allow SMS to administer the site system. Possible cause: The service account on the site system is disabled due to password expiration policy. Solution: Re-enable the service account. Possible cause: Something other than SMS deleted account "%3" or changed its password. Solution: Reset the site using SMS Setup. SMS Site Component Manager will recreate the account as part of the reset process. Possible cause: The account "%3" is disabled. Solution: Enable the account. SMS Site Component Manager uses the %1 service to install SMS server components, and cannot install component %4 until the %1 service can be started. If this problem persists and you cannot fix it, refer to your SMS documentation or the Microsoft
SMS 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 Possible cause: SMS Site Component Manager 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. SMS Site Component Manager cannot install component %7 until the program runs successfully. If this problem persists and you cannot fix it, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12 Possible cause: You deleted account "%3" or changed its password, but forgot to notify SMS. Solution: Use SMS Setup to modify the installation of the site. Specify the correct account and password in SMS Setup. Possible cause: SMS Site Component Manager 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.
SMS Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12 Possible cause: You deleted account "%3" or changed its password, but forgot to notify SMS. Solution: Use SMS Setup to modify the installation of the site. Specify the correct account and password in SMS Setup. Possible cause: SMS Site Component Manager 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. Possible cause: The account "%3" is disabled. Solution: Enable the account.
SMS Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12 Possible cause: SMS Site Component Manager 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 your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12 Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the SMS Service or Site System Connection accounts are properly configured to allow SMS to administer the site system. If advanced security verify the site server machine account is properly configured to allow SMS to administer the site system. Possible cause: The account "%3" is disabled. Solution: Enable the account. If this problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. SMS Site Component Manager installed the %1 service on site system "%2". The service will log on as account "%3". SMS Site Component Manager started the %1 service on site system "%2". SMS Site Component Manager could not stop the %1 service on site system "%2".%12 Possible cause: SMS Site Component Manager 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 your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Site Component Manager could not deinstall the %1 service from site system "%2".%12 Possible cause: SMS Site Component Manager 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 your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Site Component Manager stopped the %1 service on site system "%2". SMS Site Component Manager deinstalled the %1 service from site system "%2". SMS Site Component Manager installed this component as a thread of the SMS Executive service on this site system. SMS Site Component Manager started this component on this site system. SMS Site Component Manager stopped this component on this site system. SMS Site Component Manager deinstalled this component as a thread of SMS Executive on this site system. SMS Site Component Manager could not start this component on this site system because the SMS Executive service is not running. Solution: Review the status messages reported by SMS Executive on this site system, and fix any problems it is experiencing. SMS Site Component Manager signaled this component on this site system to stop, but it did not stop after 60 seconds. SMS Executive detected that this component stopped unexpectedly.%12 Possible cause: The component is experiencing a severe problem that caused it to stop unexpectedly. Solution: Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. SMS Executive is next scheduled to start this component on "%1".
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 SMS Administrator console and adjust its schedule to an appropriate setting. SMS Executive is scheduled to start this component now, but cannot because it is already running. Possible cause: The component is scheduled to run so frequently that it cannot complete its work before the next scheduled run time. Solution: Adjust the component's schedule in the SMS Administrator console so that it will not run so frequently. Possible cause: The component is running for an abnormally long time. Solution: Examine the other status messages reported by the component. If the component is experiencing a problem, correct it. SMS Executive could not start this component because it could not load \"%1\" using the MFC AfxLoadLibrary() function.%12 Possible cause: The DLL was somehow corrupted or deleted. Solution: Restore the DLL by manually copying it from your SMS CD to \"%1\". Possible cause: The file "%1" exists, but something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS component can access the file. Possible cause: The DLL depends on another DLL, which does not exist or cannot be found via the PATH environment variable. Solution: Determine all of the DLLs that this DLL depends on (using Depends.exe from the Win32 SDK) and insure they exist and can be found via the PATH environment variable for the user account that the SMS_EXECUTIVE service runs under.
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 Possible cause: The DLL was somehow corrupted or deleted. Solution: Restore the DLL by manually copying it from your SMS CD to \"%1\". Possible cause: This is a defective DLL that is part of an add-on product to Microsoft Systems Management Server. The DLL is defective because it does not export a ThreadMain() function. Solution: Contact the manufacturer of this product for more information.
In the last %1 hours, SMS 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 NT Events on the site server, and %6 were passed as command-line parameters to external programs. During this time, SMS 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. SMS Status Manager periodically reports this message for your convenience; you can ignore it if your not interested in monitoring SMS Status Manager's processing performance. SMS Status Manager will report this message again in %10 hours.%12
SMS Status Manager successfully initialized the "SMS Status Messages" performance object. Every time SMS 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 NT Performance Monitor. For example, you can monitor the total number of status messages written to the site database by SMS Status Manager by monitoring the "_Total" instance of the "Written To SMS Database" counter. SMS Status Manager resets all of the counts when it is restarted, and the counts cannot be viewed when SMS Status Manager is not running.%12 Due to an internal error, SMS Status Manager could not initialize the "SMS Status Messages" performance object. You can measure SMS Status Manager's processing performance by monitoring this performance object with the Windows NT Performance Monitor. This problem will not affect SMS 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 SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.%12
SMS 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 highlevel summary, which you can view under the System Status node of the SMS Administrator console. You can monitor the performance of the in-memory queue in the Windows NT 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 SMS Status Manager has forwarded to the summarizer. The counts are reset when both SMS Status Manager and the summarizer are restarted, which typically occurs when SMS Executive is restarted. The counts cannot be viewed when SMS Status Manager and the summarizer are both not running.%12
SMS 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 SMS Administrator console. If you reenable the summarizer in the SMS Administrator console, SMS Status Manager will resume forwarding messages to the summarizer.%12 Due to an internal error, SMS 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 SMS Administrator console. Until this problem is fixed, the high-level summary will be inaccurate or not available. Please refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.%12 SMS Status Manager has created %1 instances of the "SMS Status Messages" performance object, which is the maximum allowed number of instances. Every time SMS Status Manager receives a status message it will update the performance counters contained by this performance object. You can measure SMS Status Manager's processing performance by monitoring this performance object with the Windows NT Performance Monitor. Because the maximum limit was reached, SMS Status Manager will not create any more instances of this performance object. SMS Status Manager builds the list of instances as it receives status messages. You can reset the list by restarting SMS Status Manager.%12
SMS 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.) Possible cause: The program and command-line arguments are blank or contain an invalid escape sequence. Solution: Correct the value of the Program box on the Actions tab of the Status Filter Rule Properties page in the SMS Administrator console. (Note that you are not limited to %2 characters in the Program box.).
SMS 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 Possible cause: The Status Filter Rule specifies a program that is invalid or does not exist. Solution: Correct the value of the Program box on the Actions tab of the Status Filter Rule Properties page in the SMS Administrator console. (Note that you are not limited to %3 characters in the Program box.) Be sure to explicitly specify the path to the program. For example, specify "c:\winnt\system32\net.exe" instead of just "net.exe"..
SMS 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. Possible cause: The Status Filter Rule specifies a program that runs interactively and the program will not exit until it receives user input. This would happen, for example, if you specified "notepad.exe" as the program. Solution: First correct the Status Filter Rule to specify a program that runs to completion without requiring user input; this is done by editing the Program box on the Actions tab of the Status Filter Rule Properties page in the SMS Administrator console. (Note that you are not limited to %3 characters in the Program box.) Then verify that the old program is not still running on the site server using the Windows NT Task Manager. If the old program is still running, use End Process in Task Manager to stop it. Possible cause: The Status Filter Rule specifies a program that takes a long time to run. Solution: Ignore this message, but consider changing the Status Filter Rule to specify a program that runs quickly. Slow programs, when executed frequently, will slow down the rate at which SMS Status Manager can process status messages, and might cause a large number of running processes to build up on your site
SMS Status Manager received a status message with an invalid time stamp. The status message was reported by component "%1" running on computer "%2". Possible cause: The system clock on computer "%2" is not synchronized with the site server's system clock. Most likely, the system clock on computer "%2" is set to some date greater than 2035 or less than 1970. Solution: Synchronize the system clock of computer "%2" with the site server's system clock. Please refer to your Windows NT Server documentation or the Microsoft Knowledge Base for further information. When SMS Status Manager receives status messages with invalid time stamps, it will stamp these messages with the current system time on the site server. The messages will then be processed successfully, but their time and date might not be truly representative of when they were reported in real time. SMS Status Manager will continue to report this problem every 24 hours until you fix it. SMS 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. Possible cause: The system clock on computer "%2" is %3 or more seconds ahead of the site server's system clock. Solution: Synchronize the system clock of computer "%2" with the site server's system clock. Please refer to your Windows NT Server documentation or the Microsoft Knowledge Base for further information. SMS Status Manager will process status messages with improper time stamps when the site server's system clock surpasses the improper time stamps. For example, this status message will not be processed for %3 seconds. SMS Status Manager will continue to report this problem every 24 hours until you fix it. SMS Status Manager will not report this problem if the system clock of computer "%2" is less than %4 seconds ahead of the site server's system clock. This interval is configurable in the SMS site control file. Please refer to the Microsoft Knowledge Base for further information. Network Discovery is starting.%12
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. Network Discovery protocol modules are initializing.%12 Network Discovery is starting protocol operations. Network Discovery is querying network devices to discover devices related to the specified configuration.%12 Network Discovery is stopping protocol operations.%12 Network Discovery is stopping the Network Discovery protocol modules.%12 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 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 Network Discovery has stopped.%12 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. Possible cause: the DHCP server is running in a domain in which the SMS Service account is not available. (Network Discovery runs under the SMS Service account as part of SMS Executive.) Solution: Create an account on the DHCP server's domain with the same name and password as the SMS Service account.
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 Solution: If you are using Microsoft DHCP servers, then refer to the specific error string for details. 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. Network Discovery failed to perform a WinSock operation.%12 Solution: Ensure that the TCP/IP stack is installed and running. Also, verify that you are using Windows NT version 4.0 or later. 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.
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 Possible cause: Some other network software on the server is preventing Network Discovery from joining the OSPF multicast group. Solution: Ensure that the TCP/IP stack is installed and running. Also, verify that you are using Windows NT version 4.0 or later. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs. Network Discovery did not have time to finish. Therefore, the information in the SMS site database is not as complete as it should be.%12 Solution: Increase the duration of the discovery. In the Network Discovery Properties dialog box, on the Schedule tab, select a schedule and open the Schedule dialog box. Note that the duration of the discovery is the amount of time spent performing protocol transactions, not the overall time Network Discovery performs processing.
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 Possible cause: CIM Object Manager is not installed on this computer. Solution: Install CIM Object Manager by running Sms\bin\i386\wmicore.exe. 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 Possible cause: This computer has an incompatible version of CIM Object Manager, or there was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe. Network Discovery failed to read information from CIM Object Manager. Network Discovery cannot continue.%12 Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe.
Network Discovery failed to read information from CIM Object Manager. Network Discovery will continue, but slowly.%12 Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe.
Network Discovery failed to write information to CIM Object Manager. Network Discovery cannot continue.%12 Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe.
Network Discovery failed to write information to CIM Object Manager. Network discovery will continue, but slowly.%12 Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe.
Network Discovery failed to execute a query from CIM Object Manager. Network discovery will continue, but slowly.%12 Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF. Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe.
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 Possible cause: Too many SNMP-related applications are running on this computer. Solution: Close some SNMP-related applications. Possible cause: An internal error. Solution: Re-run Network Discovery. If that does not work, reboot. If that does not work, contact your network administrator. Network Discovery failed to export a device to the Discovery Data Manager. Therefore, discovered devices will not appear in the SMS site database.%12 Possible cause: There is not enough free disk space on the SMS site server. Solution: Free some disk space and re-run Network Discovery. Network Discovery failed to export a network to the Discovery Data Manager. Therefore, discovered devices will not appear in the SMS site database.%12 Possible cause: There is not enough free disk space on the SMS site server. Solution: Free some disk space and re-run Network Discovery. Network Discovery failed to enumerate the computers on one or more domains.%12 Possible cause: The specified domains do not exist. Solution: Re-specify domains; go to the Network Discovery Properties dialog box, Domains tab. Possible cause: Domain access problems exist. Solution: Contact your network administrator.%12 SMS NT Logon Server Manager successfully modified logon scripts for %1 users and failed to modify logon scripts for %2 users. SMS NT Logon Server Manager examined a total of %3 users in the Windows NT domain %4, and modified %5 files.
SMS NT Logon Server Manager is beginning a processing cycle for all of the domains configured for the Windows Networking Logon Discovery or Client Installation methods. SMS NT Logon Server Manager completed a processing cycle for all of the domains configured for the Windows Networking Logon Discovery or Client Installation methods. SMS NT Logon Server Manager is beginning a processing cycle for domain "%1", which includes: 1. Enumerating the domain controllers for this domain. 2. Making each domain controller a site system serving the SMS Logon Point role. 3. Modifying user logon scripts on each domain controller, if instructed to do so by the configuration of the Windows Networking Logon Discovery and Client Installation methods. 4. Creating and updating the contents of the "SMSLOGON" share on each domain controller. 5. Installing the SMS_NT_LOGON_DISCOVERY_AGENT service on each domain controller. SMS NT Logon Server Manager successfully completed a processing cycle for domain "%1". SMS NT Logon Server Manager failed to complete a processing cycle for domain "%1". Solution: Review the status messages previously reported by SMS NT Logon Server Manager to determine the exact reasons for this failure. SMS NT Logon Server Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.
SMS NT Logon Server Manager failed to access a domain controller for domain "%1".%12 Possible cause: Domain "%1" does not exist. Solution: Using the SMS Administrator console, remove domain "%1" from the lists of domains in the Windows Networking Logon Discovery and/or Client Installation methods. Add the correct domain to the lists. Possible cause: The all of the domain controllers are turned off, not connected to the network, or not functioning properly. Solution: Verify that the domain controllers are turned on, connected to the network, and functioning properly. Possible cause: SMS NT Logon Server Manager does not have sufficient access rights to remotely administer the domain controllers. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer the domain controllers. Possible cause: Network problems are preventing SMS NT Logon Server Manager from properly accessing the domain controllers. Solution: Investigate and correct any problems with your network.
SMS NT Logon Server Manager will configure the following domains to use the Windows Networking Logon Discovery and/or Client Installation methods: %1. SMS NT Logon Server Manager will configure the following domains to no longer use the Windows Networking Logon Discovery or Client Installation methods: %1.
SMS NT Logon Server Manager determined that the current site is the senior site for domain "%1". SMS NT Logon Server Manager will now configure all of the domain controllers for this domain. The SMS NT Logon Server Manager at the senior site performs the following configuration tasks for this domain on behalf of all of the sites using this domain: 1. Modifying the user logon scripts on each domain controller, if instructed to do so by the configuration of the Windows Networking Logon Discovery and Client Installation methods. 2. Creating and updating the "SMSLOGON" share and the directories and files associated with it on each domain controller 3. Installing the SMS_NT_LOGON_DISCOVERY_AGENT service on each domain controller.
SMS NT Logon Server Manager determined that the current site is not the senior site for domain "%1". SMS NT Logon Server Manager will instruct the senior site to configure the domain controllers for this domain. The SMS NT Logon Server Manager at the senior site performs the following configuration tasks for this domain on behalf of all of the sites using this domain: 1. Modifying the user logon scripts on each domain controller, if instructed to do so by the configuration of the Windows Networking Logon Discovery and Client Installation methods. 2. Creating and updating the "SMSLOGON" share and the directories and files associated with it on each domain controller 3. Installing the SMS_NT_LOGON_DISCOVERY_AGENT service on each domain controller.
SMS NT Logon Server Manager failed to find a suitable drive on domain controller "%1" for domain "%2" to hold the "SMSLOGON" directory. Possible cause: Every NTFS drive on the domain controller has less than 50 MB of free disk space. Solution: Either free up enough space on an NTFS drive or manually create the "SMSLOGON" directory on the root directory of an NTFS drive and share it out as "SMSLOGON". If you manually create the directory, it might have less than 50 MB of free disk space.
SMS NT Logon Server Manager failed to create share "%1" on domain controller "%2" for domain "%3".%12 Possible cause: The domain controller is turned off, not connected to the network, or not functioning properly. Solution: Verify that the domain controller is turned on, connected to the network, and functioning properly. Possible cause: SMS NT Logon Server Manager does not have sufficient access rights to remotely administer the domain controller. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer the domain controller. Possible cause: Network problems are preventing SMS NT Logon Server Manager from properly accessing the domain controller. Solution: Investigate and correct any problems with your network. SMS NT Logon Server Manager created share "%1" on domain controller "%2" for domain "%3". SMS clients will access this share during the client discovery and installation process. SMS NT Logon Server Manager detected that the current site is the senior site for domain "%2", and that site "%1" is also using this domain for Windows Networking Logon Discovery and/or Client Installation, but that site "%1" has not recently completed a processing cycle for this domain. Possible cause: Site "%1" is temporarily out of service. Solution: Ignore this message, but bring site "%1" back into service soon. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message. Eventually the SMS NT Logon Server Manager will remove site "%1" from the list of sites that use this domain for Windows Networking Logon Discovery and Client Installation.
SMS NT Logon Server Manager detected that the current site is the senior site for domain "%2", and that site "%1" is also using this domain for Windows Networking Logon Discovery and/or Client Installation, but that site "%1" has not completed a processing cycle for this domain in over seven days. SMS NT Logon Server Manager will remove site "%1" from the list of sites that use this domain for Windows Networking Logon Discovery and Client Installation. Possible cause: Site "%1" is temporarily out of service. Solution: Bring site "%1" back into service. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message. SMS NT Logon Server Manager determined that no sites are configured to use domain "%2" for the Windows Networking Logon Discovery or Client Installation methods. SMS NT Logon Server Manager will now configure domain controller "%1" to no longer serve as an SMS Logon Point for this site. This task includes: 1. Removing the SMS Logon Point role from the site system "%1". 2. Undoing any modifications made by SMS to the user logon scripts on the domain controller. 3. Deleting the "SMSLOGON" share and any directories and files associated with it. 4. Deinstalling the SMS_NT_LOGON_DISCOVERY_AGENT service.
SMS NT Logon Server Manager failed to complete all of the configuration tasks on domain controller "%1" for domain "%2". These tasks include: 1. Assigning the SMS Logon Point role to the site system "\\%1". 2. Modifying the user logon scripts, if instructed to do so by the configuration of the Windows Networking Logon Discovery and Client Installation methods. 3. Creating and updating the "SMSLOGON" share and the directories and files associated with it. 4. Installing the SMS_NT_LOGON_DISCOVERY_AGENT service.
SMS NT Logon Server Manager failed to update the site control file.%12 Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS Setup and reset the current installation. 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.
SMS NT Logon Server Manager failed to read the site control file.%12 Possible cause: The file exists, but it is corrupt. Solution: Restore the site control file from a backup copy, or run SMS Setup and reset the current installation. Possible cause: The file is being read from a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NT Logon Server Manager could not create the share "%1" on domain controller "%2" for domain "%3" because the share already exists and it was not created by SMS. SMS NT Logon Discovery Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has. SMS NT Logon Discovery Manager is beginning to update the configuration of SMS NT Logon Server Manager. Any changes to the configuration of the Windows Networking Logon Discovery method in the SMS Administrator console will now be propagated to SMS NT Logon Server Manager. SMS NT Logon Discovery Manager successfully updated the configuration of SMS NT Logon Server Manager.
SMS NT Logon Discovery Manager failed to update the configuration of SMS NT Logon Server Manager.%12 Solution: Review the previous status messages to determine the exact reason for the failure. SMS NT Logon Discovery Manager failed to read file "%1", which contains the configuration of SMS NT Logon Server Manager.%12 Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NT Logon Discovery Manager failed to write to file "%1", which contains the configuration of SMS NT Logon Server Manager.%12 Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NT Logon Discovery Manager successfully updated file "%1", which contains the configuration of SMS NT Logon Server Manager. SMS NT Logon Discovery Manager will instruct SMS NT Logon Server Manager to configure the following domains for the Windows Networking Logon Discovery method: %1. SMS NT Logon Installation Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has. SMS NT Logon Installation Manager is beginning to update the configuration of SMS NT Logon Server Manager. Any changes to the configuration of the Windows Networking Logon Client Installation method in the SMS Administrator console will now be propagated to SMS NT Logon Server Manager. SMS NT Logon Installation Manager successfully updated the configuration of SMS NT Logon Server Manager. SMS NT Logon Installation Manager failed to update the configuration of SMS NT Logon Server Manager.%12 Solution: Review the previous status messages to determine the exact reason for the failure.
SMS NT Logon Installation Manager failed to read file "%1", which contains the configuration of SMS NT Logon Server Manager.%12 Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NT Logon Installation Manager failed to write file "%1", which contains the configuration of SMS NT Logon Server Manager.%12 Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NT Logon Installation Manager successfully updated file "%1", which contains the configuration of SMS NT Logon Server Manager.
SMS NT Logon Installation Manager will instruct SMS NT Logon Server Manager to configure the following domains for the Windows Networking Logon Client Installation method: %1. SMS NW Logon Server Manager successfully modified the system login script on NetWare bindery server "%1". SMS NW Logon Server Manager failed to modify the system login script on the NetWare bindery server "%1".%12 Possible cause: The server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the server is turned on, connected to the network, and functioning properly. Possible cause: SMS NW Logon Server Manager does not have sufficient access rights to remotely administer the server. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer the server. Possible cause: Network problems are preventing SMS NW Logon Server Manager from properly accessing the server. Solution: Investigate and correct any problems with your network.
SMS NW Logon Server Manager is beginning a processing cycle for all of the NetWare bindery servers configured for the NetWare Bindery Logon Discovery or Client Installation methods. SMS NW Logon Server Manager completed a processing cycle for all of the NetWare bindery servers configured for the NetWare Bindery Logon Discovery or Client Installation methods. SMS NW Logon Server Manager is beginning a processing cycle for NetWare bindery server "%1", which includes: 1. Making this server a site system serving the SMS Logon Point role. 2. Modifying the system login scripts on this server, if instructed to do so by the configuration of the NetWare Bindery Logon Discovery and Client Installation methods. 3. Creating and updating the contents of the "SMSLOGON" directory on this server. SMS NW Logon Server Manager successfully completed a processing cycle for NetWare bindery server "%1".
SMS NW Logon Server Manager failed to complete a processing cycle for NetWare bindery "%1". Solution: Review the status messages previously reported by SMS NW Logon Server Manager to determine the exact reasons for this failure. SMS NW Logon Server Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has. SMS NW Logon Server Manager failed to access NetWare bindery server "%1".%12 Possible cause: Server "%1" does not exist. Solution: Using the SMS Administrator console, remove server "%1" from the lists of servers in the Windows Networking Logon Discovery and/or Client Installation methods. Add the correct server to the lists. Possible cause: The server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the server is turned on, connected to the network, and functioning properly. Possible cause: SMS NW Logon Server Manager does not have sufficient access rights to remotely administer the server. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer the server. Possible cause: Network problems are preventing SMS NW Logon Server Manager from properly accessing the server. Solution: Investigate and correct any problems with your network.
SMS NW Logon Server Manager will configure the following NetWare bindery servers to use the NetWare Bindery Logon Discovery and/or Client Installation methods: %1.
SMS NW Logon Server Manager will configure the following NetWare bindery servers to no longer use the NetWare Bindery Logon Discovery or Client Installation methods: %1. SMS NW Logon Server Manager failed to find a suitable volume on NetWare bindery server "%1" to hold the "SMSLOGON" directory. Possible cause: Every volume on the server has less than 50 MB of free space. Solution: Either free up enough space on a volume or manually create the "SMSLOGON" directory on the root directory of a volume. If you manually create the directory, it might have less than 50 MB of free space. SMS NW Logon Server Manager is unable to create the directory "%1" on the NetWare bindery server "%2".%12 Possible cause: The server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the server is turned on, connected to the network, and functioning properly. Possible cause: SMS NW Logon Server Manager does not have sufficient access rights to remotely administer the server. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer the server. Possible cause: Network problems are preventing SMS NW Logon Server Manager from properly accessing the server. Solution: Investigate and correct any problems with your network.
SMS NW Logon Server Manager successfully created the directory "%1" on NetWare bindery server "%2". SMS clients will access this directory during the client discovery and installation process.
SMS NW Logon Server Manager detected that site "%1" is using NetWare bindery server "%2" for NetWare Bindery Logon Discovery and/or Client Installation, but that site "%1" has not recently completed a processing cycle for this server. Possible cause: Site "%1" is temporarily out of service. Solution: Ignore this message, but bring site "%1" back into service soon. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message. Eventually the SMS NW Logon Server Manager will remove site "%1" from the list of sites that use this server for NetWare Bindery Logon Discovery and Client Installation. SMS NW Logon Server Manager detected that site "%1" is using NetWare bindery server "%2" for NetWare Bindery Logon Discovery and/or Client Installation, but that site "%1" has not completed a processing cycle for this server in over seven days. SMS NW Logon Server Manager will remove site "%1" from the list of sites that use this server for NetWare Bindery Logon Discovery and Client Installation. Possible cause: Site "%1" is temporarily out of service. Solution: Bring site "%1" back into service. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message. SMS NW Logon Server Manager determined that no sites are configured to use NetWare bindery server "%1" for the NetWare Bindery Logon Discovery or Client Installation methods. SMS NW Logon Server Manager will now configure the server to no longer serve as an SMS Logon Point for this site. This task includes: 1. Removing the SMS Logon Point role from the site system "%1". 2. Undoing any modifications made by SMS to the system login scripts on the server. 3. Deleting the "SMSLOGON" directory and any directories and files associated with it.
SMS NW Logon Server Manager failed to complete all of the configuration tasks on NetWare bindery server "%1". These tasks include: 1. Assigning the SMS Logon Point role to the site system "%1". 2. Modifying the system login scripts, if instructed to do so by the configuration of the NetWare Bindery Logon Discovery and Client Installation methods. 3. Creating and updating the "SMSLOGON" directory and the directories and files associated with it. SMS NW Logon Server Manager failed to update the site control file.%12 Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS Setup and reset the current installation. 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.
SMS NW Logon Server Manager failed to read the site control file.%12 Possible cause: The file exists, but it is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS Setup and reset the current installation. Possible cause: The file is being read from a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NW Logon Server Manager detected that there is no NetWare bindery redirector installed on the site server. SMS NW Logon Server Manager cannot configure NetWare bindery servers for the NetWare Bindery Logon Discovery and Client Installation methods until an appropriate redirector is installed on the site server. Solution: Install an appropriate NetWare bindery redirector on the site server. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information. SMS NW Logon Server Manager detected that the "SMSLOGON" directory is missing from volume "%2" on NetWare bindery server "%1". Solution: SMS NW Logon Server Manager will automatically recreate the directory now.
SMS NW Logon Server Manager detected that NetWare bindery server "%1" is already being used as an SMS Logon Point by another SMS site. Solution: Only one SMS site should be configured to use server "%1" as an SMS Logon Point. Using the SMS Administrator console, remove this server from the list of Logon Points used for the SMS NetWare Bindery Logon Discovery and Installation methods, either for this site or the site that is currently using this server as an SMS Logon Point. SMS NW Logon Discovery Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has. SMS NW Logon Discovery Manager is beginning to update the configuration of SMS NW Logon Server Manager. Any changes to the configuration of the NetWare Bindery Logon Discovery method in the SMS Administrator console will now be propagated to SMS NW Logon Server Manager. SMS NW Logon Discovery Manager successfully updated the configuration of SMS NW Logon Server Manager. SMS NW Logon Discovery Manager failed to update the configuration of SMS NW Logon Server Manager.%12 Solution: Review the previous status messages to determine the exact reason for the failure.
SMS NW Logon Discovery Manager failed to read file "%1", which contains the configuration of SMS NW Logon Server Manager.%12 Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NW Logon Discovery Manager failed to write to file "%1", which contains the configuration of SMS NW Logon Server Manager.%12 Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NW Logon Discovery Manager successfully updated file "%1", which contains the configuration of SMS NW Logon Server Manager.
SMS NW Logon Discovery Manager will instruct SMS NW Logon Server Manager to configure the following NetWare bindery servers for the NetWare Bindery Logon Discovery method: %1. SMS NW Logon Discovery Manager detected that there is no NetWare bindery redirector installed on the site server. SMS NW Logon Discovery Manager cannot function until an appropriate redirector is installed on the site server. Solution: Install an appropriate NetWare bindery redirector on the site server. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS NW Logon Installation Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has. SMS NW Logon Installation Manager is beginning to update the configuration of SMS NW Logon Server Manager. Any changes to the configuration of the NetWare Bindery Logon Client Installation method in the SMS Administrator console will now be propagated to SMS NW Logon Server Manager. SMS NW Logon Installation Manager successfully updated the configuration of SMS NW Logon Server Manager. SMS NW Logon Installation Manager failed to update the configuration of SMS NW Logon Server Manager.%12 Solution: Review the previous status messages to determine the exact reason for the failure.
SMS NW Logon Installation Manager failed to read file "%1", which contains the configuration of SMS NW Logon Server Manager.%12 Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NW Logon Installation Manager failed to write file "%1", which contains the configuration of SMS NW Logon Server Manager.%12 Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NW Logon Installation Manager successfully updated file "%1", which contains the configuration of SMS NW Logon Server Manager.
SMS NW Logon Installation Manager will instruct SMS NW Logon Server Manager to configure the following NetWare bindery servers for the NetWare Bindery Logon Client Installation method: %1. SMS NDS Logon Server Manager successfully modified the container login script for NetWare NDS container "%2" in tree "%1". SMS NDS Logon Server Manager failed to modify the container login script for NetWare NDS container "%2" in tree "%1". Possible cause: SMS NDS Logon Server Manager does not have sufficient access rights to remotely administer the container. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer container. Possible cause: Network problems are preventing SMS NDS Logon Server Manager from properly accessing the container. Solution: Investigate and correct any problems with your network.
SMS NDS Logon Server Manager is beginning a processing cycle for all of the NetWare NDS containers and volumes configured for the NetWare NDS Logon Discovery or Client Installation methods. SMS NDS Logon Server Manager completed a processing cycle for all of the NetWare NDS containers and volumes configured for the NetWare NDS Logon Discovery or Client Installation methods. SMS NDS Logon Server Manager is beginning a processing cycle for NetWare NDS container "%2" and volume "%3" in tree "%1", which includes: 1. Making this volume a site system serving the SMS Logon Point role. 2. Modifying the container login scripts on this container, if instructed to do so by the configuration of the NetWare NDS Logon Discovery and Client Installation methods. 3. Creating and updating the contents of the "SMSLOGON" directory on this volume. SMS NDS Logon Server Manager successfully completed a processing cycle for NetWare NDS container "%2" and volume "%3" in tree "%1".
SMS NDS Logon Server Manager failed to complete a processing cycle for NetWare NDS container "%2" and volume "%3" in tree "%1".%12 The processing tasks includes: 1. Making this volume a site system serving the SMS Logon Point role. 2. Modifying the container login scripts on this container, if instructed to do so by the configuration of the NetWare NDS Logon Discovery and Client Installation methods. 3. Creating and updating the contents of the "SMSLOGON" directory on this volume. Possible cause: SMS NDS Logon Server Manager does not have sufficient access rights to remotely administer the container or volume. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer container or volume. Possible cause: Network problems are preventing SMS NDS Logon Server Manager from properly accessing the container or volume. Solution: Investigate and correct any problems with your network.
SMS NDS Logon Server Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct and problems it is experiencing. SMS NetWare NDS Logon Server Manager failed to access NetWare NDS volume "%3" in tree "%1" due to a memory allocation failure. Possible cause: The site server is low on virtual memory or not functioning properly. Solution: Verify that the site server is functioning properly. Stop any processes that are using up all of the virtual memory. If necessary, reboot the site server to free up virtual memory.
SMS NDS Logon Server Manager will configure NetWare NDS container "%2" and volume "%3" in tree "%1" to use the NetWare NDS Logon Discovery and/or Client Installation methods. SMS NDS Logon Server Manager will configure NetWare NDS container "%2" and volume "%3" in tree "%1" to no longer use the NetWare NDS Logon Discovery and/or Client Installation methods. SMS NDS Logon Server Manager detected that site "%1" is using NetWare NDS container "%3" and volume "%4" in tree "%2" for NetWare NDS Logon Discovery and/or Client Installation, but that site "%1" has not recently completed a processing cycle for this container and volume. Possible cause: Site "%1" is temporarily out of service. Solution: Ignore this message, but bring site "%1" back into service soon. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message. Eventually the SMS NDS Logon Server Manager will remove site "%1" from the list of sites that use this container and volume for NetWare NDS Logon Discovery and Client Installation. SMS NDS Logon Server Manager detected that site "%1" is using NetWare NDS container "%3" and volume "%4" in tree "%2" for NetWare NDS Logon Discovery and/or Client Installation, but that site "%1" has not completed a processing cycle for this container and volume in over seven days. SMS NDS Logon Server Manager will remove site "%1" from the list of sites that use this container and volume for NetWare NDS Logon Discovery and Client Installation. Possible cause: Site "%1" is temporarily out of service. Solution: Bring site "%1" back into service. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message.
SMS NDS Logon Server Manager determined that no sites are configured to use NetWare NDS container "%2" and volume "%3" in tree "%1" for the NetWare NDS Logon Discovery or Client Installation methods. SMS NDS Logon Server Manager will now configure the container and volume to no longer serve as an SMS Logon Point for this site. This task includes: 1. Removing the SMS Logon Point role from this volume. 2. Undoing any modifications made by SMS to the container login scripts for this container. 3. Deleting the "SMSLOGON" directory and any directories and files associated with it from this volume. SMS NDS Logon Server Manager failed to update the site control file. Error %1.%12 Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the site control file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file exists, but it is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS Setup and reset the current installation. 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.
SMS NDS Logon Server Manager failed to read the site control file. Error %1.%12 Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS Setup and reset the current installation. 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. SMS NDS Logon Server Manager detected that there is no NetWare NDS redirector installed on the site server. SMS NDS Logon Server Manager cannot configure NetWare NDS containers and volumes for the NetWare NDS Logon Discovery and Client Installation methods until an appropriate redirector is installed on the site server. Solution: Install an appropriate NetWare NDS redirector on the site server. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS NDS Logon Server Manager detected that NetWare NDS context "%1" is already being used as an SMS Logon Point by another SMS site. Solution: Only one SMS site should be configured to use context "%1" as an SMS Logon Point. Using the SMS Administrator console, remove this context from the list of Logon Points used for the NetWare NDS Logon Discovery and Installation methods, either for this site or the site that is currently using this context as an SMS Logon Point. SMS NDS Logon Discovery Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct and problems it is experiencing. SMS NDS Logon Discovery Manager is beginning to update the configuration of SMS NDS Logon Server Manager. Any changes to the configuration of the NetWare NDS Logon Discovery method in the SMS Administrator console will now be propagated to SMS NDS Logon Server Manager. SMS NDS Logon Discovery Manager successfully updated the configuration of SMS NDS Logon Server Manager. SMS NDS Logon Discovery Manager failed to update the configuration of SMS NDS Logon Server Manager.%12 Solution: Review the previous status messages to determine the exact reason for the failure.
SMS NDS Logon Discovery Manager failed to read file "%1", which contains the configuration of SMS NDS Logon Server Manager.%12 Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NDS Logon Discovery Manager failed to write file "%1", which contains the configuration of SMS NDS Logon Server Manager.%12 Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NDS Logon Discovery Manager successfully updated file "%1", which contains the configuration of SMS NDS Logon Server Manager.
SMS NDS Logon Discovery Manager will instruct SMS NDS Logon Server Manager to configure the following NetWare NDS contexts for the NetWare NDS Logon Discovery method: %1. SMS NDS Logon Discovery Manager detected that there is no NetWare NDS redirector installed on the site server. SMS NDS Logon Discovery Manager cannot function until an appropriate redirector is installed on the site server. Solution: Install an appropriate NetWare NDS redirector on the site server. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information. SMS NDS Logon Installation Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct and problems it is experiencing. SMS NDS Logon Installation Manager is beginning to update the configuration of SMS NDS Logon Server Manager. Any changes to the configuration of the NetWare NDS Logon Client Installation method in the SMS Administrator console will now be propagated to SMS NDS Logon Server Manager. SMS NDS Logon Installation Manager successfully updated the configuration of SMS NDS Logon Server Manager. SMS NDS Logon Installation Manager failed to update the configuration of SMS NDS Logon Server Manager.%12 Solution: Review the previous status messages to determine the exact reason for the failure.
SMS NDS Logon Installation Manager failed to read file "%1", which contains the configuration of SMS NDS Logon Server Manager.%12 Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NDS Logon Installation Manager failed to write file "%1", which contains the configuration of SMS NDS Logon Server Manager.%12 Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS NDS Logon Installation Manager successfully updated file "%1", which contains the configuration of SMS NDS Logon Server Manager.
SMS NDS Logon Installation Manager will instruct SMS NDS Logon Server Manager to configure the following NetWare NDS contexts for the NetWare NDS Logon Client Installation method: %1. SMS Distribution Manager is beginning to process package "%1" (package ID = %2).%12 SMS Distribution Manager successfully processed package "%1" (package ID = %2).%12 SMS Distribution Manager failed to process package "%1" (package ID = %2).%12 Possible cause: Distribution manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point. Possible cause: The package source directory contains files that might be in use by an active process. Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it. SMS Distribution Manager refreshed package "%1" on distribution point "%2".%12 SMS Distribution Manager is retrying to distribute package "%1".%12 Wait to see if the package is successfully distributed on the retry.
SMS Distribution Manager failed to process package "%1" without a source directory.%12 Possible cause: The Source directory is not specified. Solution: Verify that you have specified the package source directory on the Data Source tab in the Package Properties dialog box in the SMS Administrator console. The source directory "%1" for package "%2" does not exist.%12 Solution: Make sure you have specified a valid package source directory on the Data Source tab in the Package Properties dialog box in the SMS Administrator console. If you specify a local path, it must be a local path on the site server. If you specify a path on a network drive, verify that the path exists and that the path is typed correctly.
SMS Distribution Manager failed to access the source directory "%1" for package "%2".%12 Possible cause: SMS Distribution Manager does not have sufficient rights to the package source directory. Solution: Verify that the SMS Service account has at least Read access to the directory you specify as the package source directory. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. SMS Distribution Manager failed to remove the previously compressed copy for package "%1" located at "%2".%12 Possible cause: The SMS Service account does not have sufficient access rights to delete file "%2". Solution: Verify that the file's permissions will permit the SMS Service account to delete it.
SMS Distribution Manager failed to compress package "%1" from "%2" to "%4". The file that failed the compression is "%3".%12 Possible cause: The drive containing file "%4" does not have enough free disk space. Solution: Verify that there is enough free disk space. Possible cause: If the package source directory "%2" is on a remote machine, that machine is turned off, not connected to the network, or not functioning properly. Solution: Verify that the machine containing the package source directory is turned on, connected to the network, and functioning properly. Verify that the network itself is functioning properly. Possible cause: The SMS Service account does not have sufficient access rights to the package source directory "%2" or the file "%3". Solution: Verify that the SMS Service account has read access to the package source directory and the problem file.
SMS Distribution Manager compressed package "%1" from "%2" to "%3".%12 SMS Distribution Manager successfully created or updated package "%1".%12
SMS Distribution Manager failed to update the distribution source for package "%1".%12 Possible cause: SMS Distribution Manager cannot update the package data in the SMS site database. 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: Low disk space on the drive containing the package source files. Solution: Make more space available on that drive. Possible cause: The package source files are being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: The package sourceremove package "%1" from SMS Distribution Manager failed to files exist, but something "%2".%12 Possible cause: The share type or the share name have been changed since the package was created. Solution: Verify that the share defined for this package is accessible to SMS Distribution Manager running on the site server and that the name of the share has not been changed. If users are currently accessing the share, disconnect them before making any changes to the share. If the package distribution point is located on a Windows computer, you can force users to disconnect by clicking on the "Disconnect users from distribution points" box in the Data Access tab of the Package Properties dialog box. SMS Distribution Manager removed package "%1" from "%2" due to changes in the share type or the share name.%12
SMS Distribution Manager deleted the compressed image of package "%1" at "%2".%12 SMS Distribution Manager failed to delete the compressed image of package "%1" at "%2".%12 Possible cause: The SMS Service account does not have sufficient access rights to file "%2". Solution: Verify that the SMS Service account has delete access to the file. SMS Distribution Manager is refreshing package "%1" on distribution point "%2".%12 SMS Distribution Manager failed to distribute package "%1".%12 Possible cause: The specified share is a hidden Windows NT drive share or a hidden Windows NT admin share. Solution: Specify a different share name on the Data Access tab of the Package Properties dialog box in the SMS Administrator console. SMS Distribution Manager failed to decompress package "%1" from "%2".%12 Possible cause: The compressed image "%2" is either missing or corrupt. SMS Distribution Manager will attempt to recover the package by requesting a new compressed package image from the site that sent it. There is not enough free disk space on the site server to decompress package "%1".%12 Possible cause: At least %2 megabytes of free disk space are required. Solution: Allocate more free disk space for the site server. SMS Distribution Manager failed to decompress package "%1" from "%2" to "%3". The file that failed to decompress is "%4".%12 Possible cause: The drive containing directory "%3" does not have enough free disk space. Solution: Verify that there is enough free disk space. SMS Distribution Manager decompressed package "%1" from "%2" to "%3".%12
SMS Distribution Manager failed to initialize the network abstraction layer (NAL).%12 Possible cause: SMS Distribution Manager cannot access the NAL. Solution: Use the SMS Service Manager to enable logging for SMS Distribution Manager. Then, investigate the log file for specific NAL errors. Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. SMS Distribution Manager failed to find or create the defined share or volume on distribution point "%1" for distributing package "%2".%12 Possible cause: Windows NT distribution points might not have at least one available NTFS drive. Solution: Verify that there is at least one NTFS drive with enough free disk space to store the package. Then, verify that the distribution point directory exists, has the proper permissions, and is accessible. SMS Distribution Manager failed to create subdirectories on distribution point "%1" for distributing package "%2".%12 Possible cause: SMS Distribution Manager does not have sufficient rights to create subdirectories on the distribution point. Solution: In the SMS Administrator console, create a new site system connection account or verify that an existing account has sufficient privileges.
SMS Distribution Manager failed to save package status for package "%1" to the SMS site database.%12 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.
SMS Distribution Manager failed to update the package properties on distribution points for package "%1".%12 Solution: Verify that there is enough free disk space on the site server to update the package. SMS Distribution Manager failed to copy package "%1" from "%2" to "%3".%12 Possible cause: SMS Distribution Manager does not have sufficient rights to read from the package source directory or to write to the destination directory on the distribution point. Solution: In the SMS Administrator console, verify that the site system connection accounts have sufficient privileges to the source and destination directories. Possible cause: The distribution point might not be accessible to SMS Distribution Manager running on the site server. Solution: If users are currently accessing the package files on the distribution point, disconnect the users first. If the package distribution point is located on a Windows NT computer, you can force users to disconnect by clicking on the "Disconnect users from distribution points" box in the Data Access tab of the Package Properties dialog box. Possible cause: The distribution point does not have enough free disk space to store the package. Solution: Verify that there is enough free disk space. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling "%1" from "%2" to SMS Distribution Manager copied package the files using a "%3".%12 SMS Distribution Manager successfully distributed package "%1" to distribution point "%2".%12 SMS Distribution Manager successfully removed package "%1" from distribution point "%2".%12 SMS Distribution Manager failed to remove package "%1" from distribution path "%2".%12 Possible cause: The distribution point might not be accessible to SMS Distribution Manager running on the site server. Solution: If users are currently accessing the package files on the distribution point, disconnect the users first.
SMS Distribution Manager is preparing to send the compressed image of package "%1" to child site "%2".%12 SMS Distribution Manager created a 1.x style instruction to send package "%1" to 1.x child site "%2".%12 SMS Distribution Manager instructed SMS Scheduler and Sender to send package "%1" to child site "%2".%12 SMS Distribution Manager failed to create a 1.x style instruction to send package "%1" to 1.x child site "%2".%12 Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file.
SMS Distribution Manager failed to instruct SMS Scheduler to send package "%1" to child site "%2".%12 Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file. SMS Distribution Manager created a 1.x style instruction to send package definition for package "%1" to 1.x child site "%2".%12 SMS Distribution Manager instructed SMS Scheduler and Sender to send the package information for package "%1" to child site "%2".%12 SMS 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 Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file. SMS Distribution Manager failed to send the package information for package "%1" to child site "%2".%12 Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file. SMS Distribution Manager is starting to distribute package "%1" to distribution point "%2".%12 There is not enough free disk space to copy package "%1" to "%2".%12 Solution: Verify that "%2" has at least %3 kbytes of free disk.%12
Failed to create virtual directory on the defined share or volume on distribution point "%1".%12 Possible cause: Distribution Manager requires that IIS base components be installed on the local SMS Site Server in order to create the virtual directory. Distribution Manager also requires that IIS Web Services be installed on the Distribution Point Server that needs to support Background Intelligent Transfer Service (BITS). Solution: Verify that IIS base components are installed on the local SMS Site Server, and IIS Web Services are installed on the Distribution Point Server. Failed to delete virtual directory on the defined share or volume on distribution point "%1".%12 Possible cause: The IIS base components may not be installed on the local SMS Site Server or IIS Web Services may not be installed on the Distribution Point Server. Solution: Verify that IIS base components are installed on the local SMS Site Server, and IIS Web Services are installed on the Distribution Point Server. SMS Distribution Manager failed to distribute package "%1".%12 Possible cause: The specified share is a hidden SMS share. Solution: Specify a different share name on the Data Access tab of the Package Properties dialog box in the SMS Administrator console.
Distribution Manger upgraded the SMS Hidden File ISAPI on the DP but was unable to load it as the old ISAPI was in use. To load the new ISAPI please restart IIS on machine "%1".%12 SMS Distribution Manager failed to decompress package "%1" from "%2".%12 Possible cause: The compressed image "%2" is either missing or corrupt. SMS Distribution Manager will not attempt to recover the package. Please update the package to repair the compressed image
The WebDAV server extensions are disabled on SMS distribution point "%1".%12 As a result, clients will not be able to use BITS support on the SMS 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. SMS Distribution Manager instructed SMS Scheduler and Sender to send a forwarding request to site "%2", requesting that site to forward package "%1" to site "%3".%12 SMS 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 Possible cause: A package update has recently been triggered. The package source site has been recently recovered. Possible workaround: If the package has been recently updated, verify that sites "%2" receive the package directly from package source site. If package source site has been recently recovered, verify that all recovery steps for this package have been followed.
SMS 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 Possible cause: A package update has recently been triggered. This site "%5" has been recently recovered. Possible workaround: If the package has been recently updated, verify that sites "%2" receive the package directly from package source site. If this site has been recently recovered, verify that all recovery steps for this package have been followed.
Failed to configure ports in IIS on the defined share or volume on distribution point "%1".%12 Possible cause: Distribution Manager requires that IIS base components be installed on the local SMS Site Server in order to configure the ports. Distribution Manager also requires that IIS Web Services be installed on the Distribution Point Server that needs to support Background Intelligent Transfer Service (BITS). Solution: Verify that IIS base components are installed on the local SMS Site Server, and IIS Web Services are installed on the Distribution Point Server. Failed to validate package status file "%1" received from Branch Distribution Point %2 for package %3.%12 Possible cause: The package status file is signed by the BDP client and then matched with the public key of the client on the site server. This signature verification failure will cause this error. This error can also happen if the BDP client is not in the boundaries of the site where the BDP Site System belongs to. Solution: Verify that the correct Branch Distribution Point is reporting this message. Make sure that the BDP client is assigned to and is in the boundaries of the site where the BDP Site System was created. Package "%1" does not have any Standard DP of site "%2" assigned to it. Branch DP requires a Standard DP to be added to the package.%12 The Branch DP downloads package content from a Standard DP of the site where the Branch DP client is assigned to.
SMS SQL Monitor failed to copy file smsxp.dll from the \SMS\bin\i386 directory (or \SMS\bin\alpha if this is an Alpha computer) to its required place in the\Winnt\system32 directory. Smsxp.dll must exist in the system32 directory for all SMS triggering operations to function, such as notification to the server components of a new package or collection.%12 Possible cause: The file "%1" exists, but it is corrupt. Solution: Delete the file, and then stop and restart SMS SQL Monitor. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. Possible cause: The file is being read from a remote computer (the site server) that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: The file smsxp.dll exists, but something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. 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.
SMS SQL Monitor failed to execute database maintenance task "%1".%12 Possible cause: A SQL Server problem prevented this task from running. 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. Most database maintenance tasks are designed to optimize database performance. If a task fails once, the effect on the system will be small and you can ignore the failure. But if a task fails repeatedly you should investigate and fix the problem.
SMS SQL Monitor failed to execute database maintenance SQL command "%1".%12 Possible cause: The SQL command contains syntax errors. Solution: Manually execute the command using the Microsoft SQL Server ISQL/w application, and fix any problems you discover. When you are satisfied the command runs successfully in ISQL/w, correct in the SMS Administrator console. 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 Smsdbmon.log for SQL Server error logs.
The database maintenance SQL task "%1" completed successfully. The task deleted %2 items from the SMS site database. SMS SQL Monitor is installing trigger "%1" for table "%2" and actions "%3" in the SMS site database. Server components such as SMS Hierarchy Manager, SMS Collection Evaluator, and SMS Discovery Data Manager instruct SMS SQL Monitor to install SQL triggers. Then, when certain kinds of data are added to, changed in, or removed from the SMS site database, the SQL triggers notify SMS SQL Monitor. In turn, SMS SQL Monitor notifies the appropriate server components.
SMS SQL Monitor is removing trigger "%1" from the SMS site database. Server components such as SMS Hierarchy Manager, SMS Collection Evaluator, and SMS Discovery Data Manager instruct SMS SQL Monitor to install SQL triggers. Then, when certain kinds of data are added to, changed in, or removed from the SMS site database, the SQL triggers notify SMS SQL Monitor. In turn, SMS SQL Monitor notifies the appropriate server components. This trigger is being removed because it is no longer needed.
SMS SQL Monitor failed to install trigger "%1" in the SMS site database.%12 Possible cause: Either table "%2" or column "%3" of table "%2" does not exist in the SMS site database. Solution: If you modified table "%2", restore it to its original, unmodified state. 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 this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. SMS SQL Monitor is executing database maintenance SQL command/task "%1". You can configure the execution schedule for this SQL command/task in the SMS Administrator console under Site Database -> Site Hierarchy -> site code - site name -> Site Settings -> Database Maintenance -> SQL Commands or Tasks.
The Delete Aged Collected Files database maintenance task completed successfully. The task deleted %1 collected files and %2 directories. The Rebuild Indexes database maintenance task successfully recreated index "%1" on table "%2" in the SMS site database. The Rebuild Indexes task periodically recreates the indexes in the SMS site database to provide optimal query performance.
The Rebuild Indexes task has dropped index "%1" on table "%2" in the SMS site database. The Rebuild Indexes task periodically recreates the indexes in the SMS 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. 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 The Software Metering File Usage Summarization task has completed, %1 rows have been added to the summary tables.%12 The Software Metering Data Monthly Usage Summarization task has completed, %1 rows have been added or updated in the summary tables.%12 The Clear Install Flag for Undiscovered Clients task has completed, %1 rows have been updated in system discovery tables.%12 SMS SQL Monitor could not start the SMS Backup service on server %1.%12 Possible cause: You changed the service setting for the SMS Backup service, but forgot to notify SMS. Solution: Use SMS Setup to modify the installation of the site. Possible cause: SMS SQL Monitor does not have sufficient access rights to administer the site server. Solution: Verify that the server connection accounts are properly configured to allow the SMS SQL Monitor to administer the site server. The Delete Inactive Client Discovery Data task has completed, %1 inactive clients have been removed from the database.%12
The Delete Obsolete Client Discovery Data task has completed, %1 obsolete clients have been removed from the database.%12 The Client Access License Usage Data Summarization task has completed, %1 rows have been added or updated in the summary table.%12 The task "%1" is configured to run today, but it could not run within the scheduled time. %12 Possible cause: The task has been enabled recently or updated to run today, but this occurred after the end of the scheduled time. Or, other tasks that were scheduled to run today did not complete before the end of the scheduled time, preventing this task from starting. Solution: Allow more time for this task to run, or schedule this task to run at another day or time. You can configure the schedule for this SQL command or task in the Configuration Manager console under Site Database / Site Management / <site code> - <site name> / Site Settings / Site Maintenance -> SQL Commands or Tasks. SMS SQL Monitor succeed to start task Reset AMT Computer Passwords.%12 SMS SQL Monitor succeed to start task Evaluate Provisioned AMT Computer Certificates.%12 SMS Collection Evaluator failed to enumerate collections.%12 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.
SMS Collection Evaluator created an .adc (create collection) file for collection "%1". If this occurs at startup, it is not a problem and this message can be ignored.%12 Possible cause: The SMS SQL Monitor service is not running. Solution: Restart SMS SQL Monitor. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. Possible cause: The collection was created before SMS SQL Monitor had time to install the trigger. Solution: Look in the registry for HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Triggers\<site _code>\Coll_Add. If that key exists, the trigger was installed (make sure Active is set to 0x1). If not, SMS Collection Evaluator was unable to write to the registry. In that case, check for low disk space on the site server, or an SMS Service account that lacks privileges to write to the registry.
SMS Collection Evaluator created an .udc (update collection) file for collection "%1". If this occurs at startup, it is not a problem and this message can be ignored.%12 Possible cause: The SMS SQL Monitor service is not running. Solution: Restart SMS SQL Monitor. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. Possible cause: The collection was created before SMS SQL Monitor had time to install the trigger. Solution: Look in the registry for HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Triggers\<site _code>\Coll_Upd. If that key exists, the trigger was installed (make sure Active is set to 0x1). If not, SMS Collection Evaluator was unable to write to the registry. In that case, check for low disk space on the site server, or an SMS Service account that lacks privileges to write to the registry.
SMS Collection Evaluator replicated full collection details for collection "%1" to all subsites.%12
SMS Collection Evaluator failed to find collection "%1". SMS Collection Evaluator received a .udc (update collection) or .adc (create collection) file for a collection that does not exist.%12 Possible cause: The collection was deleted shortly after being created or updated, but SMS SQL Monitor and SMS Collection Evaluator processed the create or update file out of sequence. Solution: None needed. The create or update file will simply not be processed for the nonexistent collection.
A SQL Server operation successfully updated collection "%1", but the operation could not set the collection's Update flag to 0, meaning the collection will be updated again next time whether it needs to be or not.%12 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. This site has changed its parent site. SMS Collection Evaluator is deleting all collections from the previous parent site.%12
SMS Collection Evaluator failed to delete collection "%1".%12 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.
Site "%1" has been created. SMS Collection Evaluator is preparing to replicate all collections to the new child site.%12 Collection "%1" has no update schedule. SMS Collection Evaluator will not automatically update this collection's membership.%12 Solution: Update the collection manually using the SMS Administrator console. Right-click the collection, point to All Tasks, then choose Update Collection Membership. Alternatively, you can specify an update schedule for the collection using the SMS Administrator console. SMS Collection Evaluator is beginning to update the membership of collection "%1".%12
SMS Collection Evaluator failed to update the membership of collection "%1".%12 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. SMS Collection Evaluator failed to replicate collection "%1" to child sites.%12 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. SMS Collection Evaluator received an .adc (add collection) file for collection "%1", is creating a result table in the SMS site database, and is updating the collection's membership.%12
SMS Collection Evaluator received an .adc (add collection) file for collection "%1", but failed to create a result table in the SMS site database.%12 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. SMS Collection Evaluator received an .adc (add collection) file for collection "%1", created a result table in the SMS site database, and updated the collection's membership.%12 SMS Collection Evaluator failed to replicate file "%1" to child sites.%12 Possible cause: Low disk space on the disk drive containing \Sms\inboxes\colleval.box. Solution: Make more space available on that drive. Otherwise, look for other status messages before this one; they will give you clues about what is happening.
SMS Collection Evaluator failed to enumerate the member site list for a resource with SMS identifier (GUID or SMSID): "%1".%12 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.
SMS Collection Evaluator failed to enumerate members of collection "%1" at site "%2".%12 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.
SMS Collection Evaluator failed to write to file "%1".%12 Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. Possible cause: The file "%1" is read-only. Solution: Clear the Read-only attribute from the file's properties dialog box. Possible cause: Another process has the file "%1" locked. Solution: Wait for the other process to finish, then retry the operation. Possible cause: The file "%1" is corrupt. Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. SMS Collection Evaluator failed to retrieve collection "%1" from the collection source. (On primary sites, the collection source is the SMS site database. On secondary sites, it is \Sms\inboxes\colleval.box.)%12 Possible cause on primary sites: 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 secondary sites: The file in \Sms\inboxes\colleval.box is corrupt. Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
SMS Collection Evaluator failed to write to file "%1".%12 Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. Possible cause: The file "%1" is read-only. Solution: Clear the Read-only attribute from the file's properties dialog box. Possible cause: Another process has the file "%1" locked. Solution: Wait for the other process to finish, then retry the operation. Possible cause: The file "%1" is corrupt. Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. SMS Collection Evaluator failed to enumerate membership rules for collection "%1".%12 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.
SMS Collection Evaluator failed to write to file "%1".%12 Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. Possible cause: The file "%1" is read-only. Solution: Clear the Read-only attribute from the file's properties dialog box. Possible cause: Another process has the file "%1" locked. Solution: Wait for the other process to finish, then retry the operation. Possible cause: The file "%1" is corrupt. Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. SMS Collection Evaluator failed to enumerate subcollections for collection "%1".%12 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.
SMS Collection Evaluator failed to write to file "%1".%12 Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. Possible cause: The file "%1" is read-only. Solution: Clear the Read-only attribute from the file's properties dialog box. Possible cause: Another process has the file "%1" locked. Solution: Wait for the other process to finish, then retry the operation. Possible cause: The file "%1" is corrupt. Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. SMS Collection Evaluator failed to read file "%1".%12 Possible cause: The file "%1" is corrupt. Solution: Delete the file, stop and restart SMS Collection Evaluator (You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components), and then update all collection memberships; in the SMS Administrator console, right-click Collections, point to All Tasks, and then choose Update Collection Membership. SMS Collection Evaluator cannot continue processing collection "%2" because subcollection "%1" has not been defined yet.%12 SMS Collection Evaluator is skipping collection "%2" and will retry after it processes other collections. Solution: Manually update the subcollection's membership at the parent site; in the SMS Administrator console, right-click the collection, point to All Tasks, then choose Update Collection Membership. SMS Collection Evaluator at a secondary site failed to write member data to collection "%1".%12 Possible cause: Low disk space on the drive containing \Sms\inboxes\colleval.box. Solution: Make more space available on that drive.
SMS Collection Evaluator failed to update collection "%1" in the collection source. (On primary sites, this is the SMS site database. On secondary sites, this is \Sms\inboxes\colleval.box.)%12 Possible cause: Low disk space on the disk drive of the site server inbox. Solution: Make more space available on that drive. SMS Collection Evaluator failed to retrieve a SQL Server command from the collection membership rule.%12 Possible cause: An SMS Provider failure occurred while inserting the WBEM Query Language (WQL) string into the SQL Server database, or the rule was added improperly. Solution: Recreate the rule in the SMS Administrator console and save it. If the WQL string had been stored correctly, it should remain after it was resaved, and the proper SQL string should be stored in the database. SMS Collection Evaluator failed to connect to the SMS site database.%12 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.
SMS Collection Evaluator failed to enumerate discovery architectures because it cannot retrieve the discovery architecture list from the database.%12 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. SMS Collection Evaluator failed to update the membership of collection "%1" because it has been locked. SMS Collection Evaluator will retry updating the collection's membership, and the update will eventually occur, but getting this message repeatedly might mean that a server process is locking a collection and then failing to unlock it when the process is finished. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.%12 Collection "%1" has no name. SMS Collection Evaluator cannot continue processing the collection without a name.%12 Solution: Add a name by editing the collection in the SMS Administrator console. SMS Collection Evaluator has created the collection result table for collection "%1" in the SMS site database.%12 SMS Collection Evaluator has updated the membership of collection "%1".%12 SMS Collection Evaluator has processed all direct rules for collection "%1".%12 SMS Collection Evaluator has processed all membership rules for collection "%1".%12
SMS Collection Evaluator has removed duplicate resources for collection "%1".%12 Resources can be included in the same collection more than once if the same resource matches more than one membership criterion. Duplicates are removed to prevent the same resource from receiving the same advertisement multiple times. SMS Collection Evaluator has updated the results for collection "%1".%12 SMS Collection Evaluator failed to update the query rule "%1" of collection "%2" (%3).%12 Possible cause: Inventory or Resource classes referenced in the query do not exist at this site, resulting in a SQL error. Solution: Enable the collection of the missing Inventory or Resource information at this site.n 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.
SMS Collection Evaluator failed to evalute some of the query rules for collection "%1" (%2).%12 Possible cause: Inventory or Resource classes referenced in the query do not exist at this site, resulting in a SQL error. Solution: Review the immediately preceding status messages from this component about query rule failures. Enable the collection of the missing Inventory or Resource information at this site. 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.
SMS Collection Evaluator is updating the results for collection "%1", there are %2 member changes.%12 SMS Collection Evaluator successfully processed new Collection Settings %1.%12 SMS Collection Evaluator successfully processed Update to Collection Settings %1.%12 SMS Collection Evaluator successfully removed Collection Settings Policy for Collection %1.%12 SMS Collection Evaluator failed to process Collection Settings changes. These changes will be retried on next processing cycle.%12 Solution: Review the previous status messages and logs for further clarification about this problem. SMS Collection Evaluator failed to process Collection Settings for Collection %1. This Collection Settings will be retried %2 times on the next processing cycles.%12 Solution: Review the previous status messages and logs for further clarification about this problem.
SMS 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 Solution: Review the previous status messages and logs for further clarification about this problem. SMS 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 Solution: Review the previous status messages and logs for further clarification about this problem. SMS 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 Solution: Review the previous status messages and logs for further clarification about this problem. SMS Policy Provider failed to process Machine Settings for Machine %1. This Machine Settings will be retried on the next processing cycles.%12 Solution: Review the previous status messages and logs for further clarification about this problem. SMS Policy Provider failed to process Machine Settings changes. These changes will be retried on next processing cycle.%12 Solution: Review the previous status messages and logs for further clarification about this problem.
SMS 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 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.
SMS Discovery Data Manager failed to connect to the discovery database.%12 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. SMS Discovery Data Manager is removing references from deleted site "%1".%12 SMS 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
SMS Discovery Data Manager failed to send discovery data to the new parent site. SMS Discovery Data Manager will retry, resuming where it left off.%12 SMS Discovery Data Manager failed to move the new parent site notification file to the Data Loader inbox.%12 Possible cause: Low disk space on the disk drive of the Data Loader inbox. Solution: Make more space available on that drive. SMS Discovery Data Manager has tried ten times to send the discovery database to the new parent site, and SMS Discovery Data Manager has been unsuccessful each time. SMS Discovery Data Manager is giving up.%12 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. SMS Discovery Data Manager has successfully sent the discovery database to the parent site.%12 SMS Discovery Data Manager failed to send file "%1" to site "%2".%12 Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.
SMS Discovery Data Manager failed to enumerate discovery architectures.%12 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. SMS Discovery Data Manager failed to create the discovery data record (DDR) to send to the new parent site.%12 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.
SMS Discovery Data Manager has detected a change in assignment rules. SMS Discovery Data Manager will not process discovery data records (DDRs) until it completes the rule refresh operation.%12 SMS Discovery Data Manager failed to complete the rule refresh process.%12 Possible cause: Refer to the previous SMS Discovery Data Manager message. SMS Discovery Data Manager failed to read the serial number from the parsed discovery data record (DDR) "%1".%12 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.
SMS Discovery Data Manager failed to read the new discovery item from the parsed discovery data record (DDR) "%1".%12 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.
SMS Discovery Data Manager failed to parse the new discovery item data from the parsed discovery data record (DDR) %1.%12 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.
SMS Discovery Data Manager failed to insert the new item from file "%1" into the data source.%12 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. SMS Discovery Data Manager failed to write the serial number record to file "%1".%12 Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.
SMS Discovery Data Manager failed to write the item key record to file "%1".%12 Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive. SMS Discovery Data Manager failed to write item buffer to file "%1". SMS 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 Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive. SMS Discovery Data Manager failed to format discovery data into file "%1".%12 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. SMS Discovery Data Manager failed to enumerate properties for architecture "%1".%12 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.
SMS Discovery Data Manager failed to process file "%1" because it cannot detect any Name properties. SMS 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 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. SMS Discovery Data Manager failed to insert discovery data because SMS is out of client access licenses.%12 Solution: Increase the number of client access licenses. You can purchase more from your Microsoft sales representative. SMS Discovery Data Manager failed to read the current site's .ncf (assignment rule) file.%12 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.
SMS Discovery Data Manager failed to read the .ncf (assignment rule) file for site "%1".%12 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. SMS Discovery Data Manager failed to open the .ncf (assignment rule) file for site "%1".%12 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. SMS Discovery Data Manager failed to read the site control file for site "%1". Because the SMS site database maintains the site control files for this site and all sites beneath it, SMS Discovery Data Manager reads site control files only from the SMS site database.%12 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.
SMS Discovery Data Manager failed to write the .ncf (assignment rule) file "%1". SMS Discovery Data Manager will retry writing this file during its next processing cycle.%12 Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive.
SMS Discovery Data Manager failed to copy the .ncf (assignment rule) file "%1" to Asstdata.box, the point of replication to client access points (CAPs). SMS Discovery Data Manager will retry copying this file during its next processing cycle.%12 Possible cause: Low disk space on the disk drive containing Asstdata.box. Solution: Make more space available on that drive. During a refresh, SMS Discovery Data Manager detected that assignment rules had changed. Therefore, SMS Discovery Data Manager is stopping the refresh now, but will perform it later.%12 SMS Discovery Data Manager failed to create a full refresh file to send to the secondary site.%12 Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. SMS Discovery Data Manager failed to notify all consumers that a full refresh has occurred and that users need to refresh their data store.%12 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 SMS Discovery Data Manager failed to send file "%1" to site "%2".%12 Possible cause: Low disk space on site "%2". Solution: Make more space available on the disk drive containing \Sms\inboxes on site "%2". SMS Discovery Data Manager will resume processing because it has successfully completed assignment-rule processing.%12
While parsing discovery data record (DDR) "%1", SMS Discovery Data Manager found a blank Architecture field, which makes "%1" a bad DDR.%12 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. SMS Discovery Data Manager failed to process the discovery data record (DDR) "%1", because it cannot update the data source.%12 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. SMS Discovery Data Manager is updating statistics in all tables in the SMS site database, which helps ensure optimal performance of SQL Server 6.5.%12 SMS Discovery Data Manager has interpreted discovery data record (DDR) "%1" as a delete request. Therefore, SMS Discovery Data Manager is deleting item "%2" of architecture "%3". DDR "%1" contains an old item, but not a new item.%12
SMS 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. Possible cause: The operating system and SMS client have been reinstalled on this computer.%12 SMS 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. Possible cause: The hardware properties of this client have changed substantially, and the client has generated a new SMS identifier.%12 SMS 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 ConfigMgr has detected a record that might be conflicting with the following client record in the site database: %1.%12 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.
SMS Inventory Data Loader failed to read the delta MIF file "%1" and will move the file to the BADMIFs directory.%12 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.
SMS Inventory Data Loader encountered a SQL Server problem and is stopping the MIF processing thread.%12 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. SMS Inventory Data Loader failed to process the delta MIF file "%1" because the file does not have a corresponding discovery record. SMS Inventory Data Loader has moved this file to the Orphans directory as file "%2" and will retry processing it within 10 minutes.%12 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.
SMS Inventory Data Loader failed to process the delta MIF file "%1" and has moved it to "%2."%12 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. SMS 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 SMS Administrator console, under Component Configuration, Data Processing and Storage Properties.%12 SMS Inventory Data Loader has finished processing %1 MIF files and is terminating the MIF file processing thread.%12 Each time the processing cycle completes, SMS Inventory Data Loader generates this message to report the number of MIF files it has processed. SMS Inventory Data Loader has quit trying to update inventory after failing 10 times. SMS Inventory Data Loader detected that the parent site was changed to a new site, and then SMS Inventory Data Loader tried to send all inventory to the new parent through the inventory update process. However, SMS Inventory Data Loader tried this process 10 times and failed each time.%12 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.
SMS 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, 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.
SMS Inventory Data Loader detected that the parent site has changed to a new site, and now SMS Inventory Data Loader is trying to send all inventory to the new parent through the inventory update process.%12 The SMS Inventory Data Loader inventory update process has initialized the inventory update status file, which controls the inventory update process's ability to restart.%12 The SMS Inventory Data Loader has detected that the inventory update process has already been completed. Therefore, SMS 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 The SMS Inventory Data Loader inventory update process will use the directory %1. SMS Inventory Data Loader will create delta MIF files in this folder to send to the parent site.%12
The SMS Inventory Data Loader inventory update process failed to write the MIF file for machine %1 of architecture %2.%12 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.
The SMS Inventory Data Loader inventory update process has finished successfully. All inventory has been sent to the parent site.%12 SMS 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 SMS 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, SMS 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 SMS Inventory Data Loader is going to widen attribute %2 of group %1 from %3 to %4. SMS 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
SMS 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 SMS Inventory Data Loader has added the architecture %1. SMS 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 SMS Inventory Data Loader failed to process the file %1 because it is larger than the defined maximum allowable size of %2.%12 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.
SMS 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 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).
SMS 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 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.
SMS 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 SMS Inventory Data Loader requested a resynchronization for machine "%1" because a hardware inventory file was sent without a public key information.%12 SMS Inventory Data Loader detected more than %1 class redefinitions in %2 minutes. Will switch to single-threaded operation after exceeding %3.%12 SMS Inventory Data Loader detected more than %1 class redefinitions in %2 minutes. Switching to single-threaded operation for the next %3 minutes.%12 SMS Site Control Manager is beginning to process delta site control file "%1".%12 SMS server components and SMS Provider clients (such as the SMS Administrator 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 SMS Site Control Manager receives and processes a delta site control file and then updates the actual site control file with the new configuration data. SMS Site Control Manager successfully processed delta site control file %1. SMS Site Control Manager could not completely process delta site control file %1.%12 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.
A non-critical problem occurred while SMS Site Control Manager was processing delta site control file %1.%12 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. SMS Site Control Manager aborted the processing of delta site control file %1.%12 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.
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 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. 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 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. 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". SMS 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 SMS Administrator console) more than once. When an SMS Provider client submits a delta site control file containing a site configuration change request, SMS 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.
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 SMS 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. SMS 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 SMS Hierarchy Manager continues to submit this site configuration change request for an extraordinarily long time, there might be a problem with SMS 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 SMS Hierarchy Manager, Replication Manager, Scheduler, and the Sender components at these sites.
SMS Site Control Manager created the temporary file "%1".%12 In a moment, SMS Site Control Manager will rename this file to %2, and it will become the new actual site control file.%12
SMS 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 SMS server components will detect that a new actual site control file is available, read it, and reconfigure themselves accordingly. SMS 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.
SMS 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. SMS 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. SMS 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. The actual site control file %1 does not exist.%12 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. This computer "%1" is not the site server (%2).%12 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. The actual site control file %1 does not contain a "%2" item.%12 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.
SMS 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.
SMS Site Control Manager wrote a copy of the actual site control file %1 to %2.%12 In a moment, SMS Site Control Manager will move this file into the SMS Hierarchy Manager inbox ("%3") for processing. SMS Site Control Manager could not write a copy of the actual site control file %1 to %2. Consequently, SMS 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 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.
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 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.
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 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.
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 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.
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 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.
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 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.
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 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.
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 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.
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 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. 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 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.
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 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. 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 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.
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 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.
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 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. 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 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
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 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.
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 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.
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 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. 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 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.
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 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.
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 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.
The "%1" item in a site configuration change request in delta site control file %2does not specify the domain of the SMS Service account. This site configuration change request and the remaining change requests in the file are unusable.%12 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.
The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SMS Service account. This site configuration change request and the remaining change requests in the file are unusable.%12 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.
The "%1" item in a site configuration change request in delta site control file %2 does not specify the plain text name of the SMS Service account. This site configuration change request and the remaining change requests in the file are unusable.%12 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.
The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the SMS Service account. This site configuration change request and the remaining change requests in the file are unusable.%12 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.
The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting the SMS Service account and password. This site configuration change request and the remaining change requests in the file are unusable.%12 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. The "%1" item in a site configuration change request in delta site control file %2 specifies an invalid public key for decrypting the SMS Service account and password. This site configuration change request and the remaining change requests in the file are unusable.%12 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. The "%1" item in a site configuration change request in delta site control file %2 specifies an SMS 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 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.
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 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. 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 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.
The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SMS site database. This site configuration change request and the remaining change requests in the file are unusable.%12 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.
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 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.
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 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.
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 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.
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 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.
The "%1" item in a site configuration change request in delta site control file %2 contains information for the software metering database, but software metering is not currently installed at this site. This site configuration change request and the remaining change requests in the file are unusable.%12 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.
The "%1" item in a site configuration change request in delta site control file %2 does not contain configuration information for the software metering database. This site configuration change request and the remaining change requests in the file are unusable.%12 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.
The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL server for the software metering database. This site configuration change request and the remaining change requests in the file are unusable.%12 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. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the software metering database. This site configuration change request and the remaining change requests in the file are unusable.%12 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.
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 for the software metering database. This site configuration change request and the remaining change requests in the file are unusable.%12 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.
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 for the software metering database. This site configuration change request and the remaining change requests in the file are unusable.%12 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.
The "%1" item in a site configuration change request in delta site control file %2 does not specify the public key for decrypting the SQL administrator account and password for the software metering database. This site configuration change request and the remaining change requests in the file are unusable.%12 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.
The "%1" item in a site configuration change request in delta site control file %2 specifies a SQL administrator account name and/or password for the software metering database 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 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.
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 SMS server components might not be using the site system connection accounts you created in the SMS Administrator console and might be unable to access some site systems.%12 Solution: Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to SMS 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, SMS Hierarchy Manager will update this site's database with the copy. If this is a child site of another site, SMS Hierarchy Manager will replicate the copy up the site hierarchy, updating each parent site's database. SMS Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to SMS Hierarchy Manager as a heartbeat site control file.%12 SMS Site Control Manager periodically submits heartbeat site control files to SMS 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, SMS Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, SMS Hierarchy Manager will replicate the copy up the site hierarchy and ensure that each parent site's database contains the up-to-date configuration. SMS Site Control Manager will then submit a heartbeat site control file to SMS Hierarchy Manager at "%3".
SMS Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to SMS Hierarchy Manager as a heartbeat site control file.%12 SMS Site Control Manager periodically submits heartbeat site control files to SMS 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, SMS Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, SMS Hierarchy Manager will replicate the copy up the site hierarchy and ensure that each parent site's database contains the up-to-date configuration. SMS Site Control Manager is configured so that no more heartbeat site control files will be submitted to SMS Hierarchy Manager.%12 Possible cause: If SMS is functioning properly, this configuration will not produce any problems. However, if inter-site communication problems interrupt the proper replication of site control files and replicated site control files are lost, the site hierarchy might take a long time to recover or might not recover at all. During this time, parent sites might not have the most upto-date configuration of this site. Solution: If this happens, you can either reconfigure SMS Site Control Manager to submit heartbeat site control files again, or you can cause it to immediately submit a heartbeat site control file by stopping and restarting SMS Site Control Manager using the SMS Service Manager application.
The schedule at which SMS Site Control Manager submits heartbeat site control files to SMS Hierarchy Manager has changed.%12 The next heartbeat site control file will be submitted at "%1". SMS Site Control Manager periodically submits heartbeat site control files to SMS 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, SMS Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, SMS 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.
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 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.
SMS Client Installation Data Manager (CIDM) failed to read the install map for site %1.%12 Solution: Do nothing. CIDM will retry in the next interval. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. SMS Client Installation Data Manager failed to read the site control file for site %1.%12 Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. .SMS Client Installation Data Manager failed to create a thread.%12 Possible cause: The computer is low on memory or other resources. Solution: Reboot.
SMS Client Installation Data Manager failed to establish inbox %1 on the site server.%12 Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: Insufficient permissions on the SMS Service account. Solution: See the SMS documentation for the necessary privileges of the Site Server account, then ensure that the SMS Service account has such privileges. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. SMS Client Installation Data Manager failed to establish inbox %1 on client access points.%12 Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Client Installation Data Manager failed to access directory %1.%12 Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: The file is on a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The file is corrupt. Solution: Delete the file, and then stop and restart SMS Client Installation Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
SMS Client Installation Data Manager failed to access file %1.%12 Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: The file is on a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The file is corrupt. Solution: Delete the file, and then stop and restart SMS Client Installation Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
SMS Client Installation Data Manager failed to create an inbox rule to copy the files "%1" from the inbox %2 to the inbox %3.%12 Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: The registry is full. Solution: Allocate more space for the registry. Possible cause: The computer is low on memory or other resources. Solution: Reboot. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. The list of CAPs in the site control file is empty.%12 If you want to specify CAPs, use the SMS Administrator console, Site Systems.%12 The list of CAPs from the site control file has been written to the file %1. Either CAPs in the site control file have changed, or SMS Client Installation Data Manager is refreshing the file for the first time.%12 SMS Client Installation Data Manager failed to write the list of CAPs to the file %1.%12 Possible cause: The file %1 was locked by another process. Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive.
The client configuration items from the site control file were written to the files %1 and %2. Either the SMS Service generated these files initially, or Client_Configuration site control file items were changed.%12
SMS Client Installation Data Manager failed to write client configuration items to the files %1 and %2.%12 Possible cause: The files were locked by another process. Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The files are corrupt. Solution: Delete the files, and then stop and restart SMS Client Installation Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
Since SMS Client Installation Data Manager last ran, the SMS client component %1 has been removed from the list of available client components.%12 SMS Client Installation Data Manager detected that the SMS client component %1 is no longer enabled for clients. To enable the component, use the SMS Administrator console.%12 SMS Client Installation Data Manager detected that the SMS client component %1 is enabled for clients. To disable the component, use the SMS Administrator console.%12
SMS Client Installation Data Manager failed to write the configuration for the SMS client component %1.%12 Possible cause: The files were locked by another process. Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The files are corrupt. Solution: Delete the files, and then stop and restart SMS Client Installation Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
An error occurred while SMS Client Installation Data Manager was activating the inbox for the SMS client component %1.%12 Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: The registry is full. Solution: Allocate more space for the registry. Possible cause: The computer is low on memory or other resources. Solution: Reboot. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Client Installation Manager failed to refresh the advertisement or package information for the SMS client component %1.%12 Possible cause: A package definition file for the component does not exist in Clicfg.src or Clicomp.src. Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: Low disk space on the drive containing Clicfg.src or Clicomp.src. Solution: Make more space available on that drive. Possible cause: Something other than SMS has changed the permissions or attributes of Clicfg.src or Clicomp.src or the directory containing them. Solution: Restore the permissions or attributes of Clicfg.src and Clicomp.src so that this SMS service can access them. SMS Client Installation Data Manager failed a memory allocation.%12 Possible cause: This computer is low on virtual memory. Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Solution: Shut down some applications. Solution: Stop and restart the SMS Executive. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. SMS has detected that there are %1 computers in this site that are running Windows 2000 and above and have the SMS Legacy Client installed. The SMS Advanced Client provides for a more secure configuration. You should upgrade these computers to the SMS Advanced Client as soon as possible. You can use the web report and query titled 'Computers recommended for Advanced Client upgrade' to easily identify these computers and deploy the Advanced Client to them. Systems Management Server will no longer support the Legacy Client on computers running Windows 2000 or above beginning with the next release or service pack of SMS.
SMS has detected that there are %1 computers in this site that are running Windows 2000 and above and have the SMS Legacy Client installed. The SMS Legacy Client will not be automatically upgraded on these computers. The SMS Advanced Client provides for a more secure configuration. You should upgrade these computers to the SMS Advanced Client as soon as possible. You can use the web report and query titled 'Computers recommended for Advanced Client upgrade' to easily identify these computers and deploy the Advanced Client to them. Systems Management Server no longer supports the Legacy Client on computers running Windows 2000 or above.
SMS Client Configuration Manager (CCM) failed to read the site control file for site "%1."%12 Solution: Do nothing. If CCM has just started, it will retry every hour, but if CCM has already read the site control file, it will continue to use the old data. Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS and reset the current installation. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your
SMS Client Configuration Manager failed to read the site identification values from the registry in \HKLM\Software\Microsoft\SMS\Identification key.%12 Solution: Reboot. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. SMS Client Configuration Manager failed to connect to the registry of site server %1.%12 Solution: Reboot. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. SMS Client Configuration Manager (CCM) failed to read the SMS Service account information for site %1.%12 Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS and reset the current installation. If you ignore this problem, CCM will continue using any SMS Client Remote Installation account that is available (if specified), but client installations might not be successful.
SMS Client Configuration Manager (CCM) failed to read the component item "%1" from the site control file on the server "%2".%12 Possible cause: The file is being read from a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS and reset the current installation. 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. If you ignore this problem, CCM will continue using previously read information, but client installations might not be successful. SMS Client Configuration Manager (CCM) failed to create a thread.%12 Possible cause: The computer is low on memory or other resources. Solution: Reboot.
SMS Client Configuration Manager failed to establish inbox "%1" on the site server.%12 Solution: Do nothing. SMS Client Configuration Manager will retry in the next interval (the default is one minute). Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: Insufficient permissions on the SMS Service account. Solution: See the SMS documentation for the necessary privileges of the SMS Service account, then ensure that the SMS Service account has such privileges. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. SMS Client Configuration Manager failed to establish inbox "%1" on CAPs.%12 Solution: Do nothing. SMS Client Configuration Manager will retry in the next interval (the default is one minute). Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: Insufficient permissions on the SMS Service account. Solution: See the SMS documentation for the necessary privileges of the SMS Service account, then ensure that the SMS Service account has such privileges. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Client Configuration Manager failed to create an inbox rule to copy files "%1" from inbox "%2" to inbox "%3."%12 Solution: Do nothing. SMS Client Configuration Manager will retry in the next interval. Possible cause: The registry is full. Solution: Allocate more space for the registry. Possible cause: The computer is low on memory or other resources. Solution: Reboot, or stop and restart the SMS Executive. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Client Configuration Manager reports that queue "%1" contains %2 Client Configuration Requests (CCRs), which exceeds the queue's threshold.%12 Possible cause: If the Incoming queue threshold (default 100) or the Processing queue threshold (default 150) is being exceeded, there might suddenly be many clients needing installation, in which case simply be aware that it will take a while to get them all installed. However, it is more likely that this error means SMS Client Configuration Manager is not processing CCRs properly. Solution: Stop and restart SMS Client Configuration Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. Possible cause: If the Retry queue's threshold (default 150) is being exceeded, there is probably a client access problem. Solution: Verify that the SMS Service account or (if specified) the SMS Client Remote Installation account have the required privileges, as specified in the SMS documentation.
In the past %3 hours, SMS Client Configuration Manager (CCM) has made %1 unsuccessful attempts to install SMS on client "%2". CCM will continue to attempt to install this client.%12 Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account have the required privileges, as specified in the SMS documentation.
SMS Client Configuration Manager (CCM) failed to complete the SMS installation on client "%1". In the past %3 hours, CCM has made %2 unsuccessful attempts.%12 Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account have the required privileges, as specified in the SMS documentation. SMS Client Configuration Manager failed to complete its periodic account maintenance cycle.%12 Possible cause: Network problems. Solution: Do nothing. SMS Client Configuration Manager will retry in the next interval (the default is 30 days). This error will not cause problems with the operation of SMS. The account maintenance cycle merely deletes obsolete domain accounts. The SMS Client Remote Installation account list has been reset to a single account.%12 Possible cause: A version of the SMS Administrator console earlier than SMS 2.0 SP2 was used to modify the list. These earlier versions recognize and retain only the first account in the list. Solution: To maintain multiple SMS Client Remote Installation accounts for this site, use the latest version of the SMS Administrator console to manage the account list.
SMS Client Configuration Manager cannot connect to the machine "%1".%12 Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account has the required privileges, as specified in the SMS documentation. Possible cause: A remote client installation account was not specified in the SMS Admin console, the account is not valid, is disabled, or has an expired password. Solution: Ensure one or more valid and active remote client installation accounts are specified in the SMS Admin console, that the account names and passwords are correct, and that the account has the required administrator rights on the target machines. SMS Client Configuration Manager cannot find machine "%1" on the network.%12 Possible cause: The client is offline. Solution: Verify that the client is connected to the network. SMS Client Configuration Manager cannot install a client to machine "%1", because it is not a supported platform for this action. Clients must be Windows NT 4.0, or greater. SMS 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. At least once today, in standard security mode, the SMS Client Configuration Manager attempted to install an advanced client without a network access account. SMS Client Configuration Manager cannot install the Advanced Client to machine "%1". This platform is not supported by the Advanced Client. The Advanced Client requires Windows 2000 or newer Operating System.
SMS Windows NT Remote Client Installation Manager failed to initialize, but it will retry in one hour.%12 Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has. SMS Windows NT Remote Client Installation Manager failed to set up change notifications, but it will retry in one hour.%12 Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.
SMS Windows NT Remote Client Installation Manager failed to create the client configuration request "%1" for the resource "%2" in SMS Client Configuration Manager inbox %3.%12 Possible cause: The specified directory, %3, does not exist. Solution: Create it. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.
SMS Windows NT Remote Client Installation Manager created the client configuration request "%1" for the resource "%2" in SMS Client Configuration Manager inbox %3.%12
Summary Information: In the past 24 hours, SMS Windows NT Remote Client Installation Manager examined %1 discovery data records (DDRs) and created %2 client configuration requests (CCRs) for the DDRs. Therefore, SMS Windows NT Remote Client Installation Manager filtered out %3 DDRs, meaning it did not create CCRs for them.%12 SMS Inventory Processor failed to process MIF file %1.%12 Possible cause: The MIF file is not formatted correctly. Solution: Check the inboxes\invproc\BADMIFs directory for the MIF. Determine what the error is, correct it, and resubmit the file. SMS Inventory Processor failed to process inventory RAW file %1.%12 Possible cause: The file might be corrupt. Solution: The file will be moved to the inboxes\invproc.box\BADRAWs directory. Regenerate the RAW file by reinstalling the client. Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. 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. Solution: Configure the site hierarchy properly; it must not contain loops. See the SMS documentation for information on how to create a proper site hierarchy. Site "%1" (%2) has the same site code as another site. Possible cause: SMS Hierarchy Manager has detected that a child site has the same site code as this site or another child site. Solution: Each site must have a unique site code. Deinstall the child site and reinstall it using a unique site code.
The parent site for this site cannot be changed from site "%1" (%2). Possible cause: You attempted to configure this site to report to a different parent site, but you attempted this using an SMS Administrator console that was not connected to this site's database. Solution: To change configure this site to report to a different parent site, use an SMS Administrator console that is connected to the this site's database. If this site is a secondary site, use SMS Setup to configure this site to report to a different parent site. SMS Hierarchy Manager cannot connect to the SMS site database.%12 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. SMS Hierarchy Manager cannot save site information to the SMS site database for site "%1". %12 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.
SMS Hierarchy Manager detected that site code "%1" is already in use by existing site "%2".%12 Possible cause: Site "%3" is using the same site code as another site. Solution: Each site must have a unique site code. Deinstall one of these sites and reinstall it using a unique site code. SMS Hierarchy Manager successfully processed "%1", which represented serial number %4 of the site control file for site "%2" (%3). If this site is a primary site, SMS Hierarchy Manager stored this site control file in the SMS site database. If this site reports to a parent site, SMS Hierarchy Manager instructed SMS Replication Manager to replicate this file to the parent site at high priority. SMS Hierarchy Manager detected that a change was requested by this site to the configuration of site "%1". SMS Hierarchy Manager created a delta site control file for this request. If this site is site "%1", SMS Hierarchy Manager submitted this file to SMS Site Control Manager at this site. If site "%1" is a child site, SMS Hierarchy Manager instructed SMS Replication Manager to deliver the file to SMS Site Control Manager at site "%1" at high priority.
SMS Hierarchy Manager cannot reinstall the SMS Site Component Manager under the new service account and password.%12 Possible cause: The service account and password are not valid. Solution: Specify a valid service account and password using the SMS Administrator console. Possible cause: The account does not have Administrator permissions and "Log on as a service" rights. Solution: Ensure that the service account is directly or indirectly in the administrator's group on the site server and has 'Logon as a service' rights. Possible cause: The new service account is disabled. Solution: Enable the account. Possible cause: Due to an OS error, the SMS Site Component Manager is marked for deletion. Solution: Perform a site reset and then reboot the site server to recover from this error. SMS Hierarchy Manager reinstalled SMS Site Component Manager using the new service account and password. SMS Site Component Manager will now reinstall all of the other server components at this site. SMS 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 SMS Sender components. SMS 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 SMS Sender components. SMS 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 SMS Sender components. SMS Hierarchy Manager failed to execute site maintenance task "%1".%12 Possible cause: Service containing the maintenance task, %1, is not installed or in not running. Solution: Check the status of the service containing the maintenance task.
SMS Hierarchy Manager cannot convert the local site from standard security to advanced security because the site database is on Microsoft SQL Server 7.0.%12 Cause: Microsoft SQL Server 7.0 does not support remote access through machine accounts. SMS Hierarchy Manager has detected secondary site "%1" has enabled the logon discovery and installation features. SMS 2003 no longer supports these features, they must be disabled before the site can be upgraded to SMS 2003.
SMS Hierarchy Manager cannot convert the local site from standard security to advanced security because the site server is not in an Active Directory domain.%12 Cause: Microsoft Windows NT 4 domains do not support remote access through machine accounts. SMS Hierarchy Manager cannot add machine account %1 for secondary site %2 to the address group %3, this must be done manually. SMS Hierarchy Manager cannot add address account %1 for secondary site %2 to the address group %3, this must be done manually. SMS Hierarchy Manager cannot convert the local site from standard security to advanced security because the site server does not have Windows QFE 325804 installed. Solution: Apply Windows QFE 325804 on the site server. This QFE is included on the SMS 2003 CD under the WinQFE directory. Solution: Install Windows 2000 service pack 4 or above on the site server. Solution: Upgrade the site server to Windows Server 2003 or above.
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.
SMS Hierarchy Manager detected that this site switched from Mixed to Native mode. SMS Hierarchy Manager cannot remove the computer account of site system %1 from database role %2. This needs to be done manually. SMS Hierarchy Manager detected that this site switched from Native to Mixed mode. SMS 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 ConfigMgr Console. The bootmedia CDs created on the site may also need to be recreated. Please refer to your ConfigMgr documentation or the Microsoft Knowledge Base for further information. SMS 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 Solution: Define a valid address at site "%2" for site "%1" in the SMS Administrator console under Site Hierarchy -> %2 -> Site Settings -> Addresses. SMS 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. Solution: If you purposefully configured the addresses this way, ignore this message. Otherwise, modify the addresses' scheduling in the SMS Administrator console under Site Hierarchy -> %2 -> Site Settings -> Addresses. SMS Scheduler at site %1 has received package %2 version %3 and has instructed the SMS Sender to send the package to the following sites: %4.%12
The sender cannot connect to remote site "%1" over the LAN.%12 Possible cause: Remote site server "%2" might not be connected to the LAN. Solution: Verify that site server "%2" is connected to the LAN and functioning properly. Possible cause: Share "%3" might not be accessible. Solution: Verify that share "%3" is visible and that the address connection account has the necessary permissions to access the share. Possible cause: Network load might be too high. Solution: Verify that the network is not saturated. Verify that you can move large amounts of data across the network. The sender cannot connect to site "%1" over RAS.%12 Possible cause: Remote site server "%2" might be down. Solution: Verify that remote site server "%2" is connected to the network and functioning properly. Possible cause: Remote site server "%2" might not be running RAS Server Service. Solution: Verify that remote site server "%2" is running RAS Server Service. Possible cause: The phone book entry "%3" in the default phone book might not contain the correct information. Solution: Verify that the phone book entry "%3" contains valid information. Possible cause: Share "%4" might not be accessible. Solution: Verify that share "%4" is visible and that the address connection account has the necessary permissions to access the share. For a detailed explanation of the RAS error code, see the Windows NT documentation. The address to site "%1" is invalid.%12 Possible cause: The destination site server name is missing. Solution: Define a valid address in the SMS Administrator console under Site Hierarchy -> site code - site name -> Site Settings -> Addresses.
The address to site "%1" is invalid.%12 Possible cause: The destination share name is missing. Solution: Define a valid address in the SMS Administrator console under Site Hierarchy -> site code - site name -> Site Settings -> Addresses. The sender cannot install secondary site "%1" on server "%2".%12 Possible cause: The targeted installation directory "%3" does not reside on an NTFS partition. Solution: Select an NTFS partition for the installation directory or convert the current partition to NTFS. The sender cannot install secondary site "%1" on server "%2" because the sender cannot create the SMS Bootstrap initialization file "%3".%12 Possible cause: The SMS Service account for site "%1" might not have the appropriate privileges to create the initialization file Solution: Verify that the account has Administrator privileges to server "%2". Possible cause: There is not enough free disk space on server "%2". Solution: Make more space available on the destination drive.
The sender cannot install secondary site "%1" on server "%2" because it cannot retrieve the encryption public key.%12 Please refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
The sender cannot install secondary site "%1" on server "%2" because it cannot query the status of the SMS Bootstrap service on server "%2".%12 Possible cause: The SMS Service account for site "%1" might not have the appropriate privileges to server "%2". Solution: Make sure the service account has Administrator privileges to server "%2".
The sender cannot install secondary site "%1" on server "%2" because it cannot stop the SMS Bootstrap service on server "%2".%12 Possible cause: The SMS Service account for site "%1" might not have the appropriate privileges to server "%2". Solution: Make sure the service account has Administrator privileges to server "%2". The sender cannot install, upgrade, or deinstall secondary site "%1" on server "%2".%12 Possible cause: The server is running Windows NT %3 %4, but this does not meet the minimum installation requirements for an SMS site server. Solution: Install a version of Windows NT that meets the installation requirements. Please refer to your SMS documentation for more information. The sender cannot install secondary site "%1" on server "%2".%12 Possible cause: The server is already in use as a site system for another SMS site. Solution: Install secondary site "%1" on a different server. The sender cannot install secondary site "%1" on server "%2" because the sender could not copy the SMS Bootstrap service file from "%3" to "%4".%12 Possible cause: The SMS Service account for site "%1" might not have the appropriate privileges to create the destination file. Solution: Verify that the account has Administrator privileges to server "%2". Possible cause: There is not enough free disk space on server "%2". Solution: Make more space available on the destination drive.
The sender cannot install secondary site "%1" on server "%2" because the sender failed to install the SMS Bootstrap service.%12 Possible cause: The SMS Service account for site "%1" might not be valid. Solution: Verify that the service account is valid. Possible cause: The service account might not have the appropriate privileges. Solution: Ensure that the account has Administrator privileges and the "Log on as a service" right on server "%2".%12 The sender cannot install secondary site "%1" on server "%2" because the sender cannot start the SMS Bootstrap service.%12 Possible cause: The SMS Service account for site "%1" might not be valid. Solution: Verify that the service account is valid. Possible cause: The service account might not have the appropriate privileges. Solution: Ensure that the account has Administrator privileges and the "Log on as a service" right on server "%2".%12
The sender has installed the SMS Bootstrap service on server "%1". The SMS Bootstrap service will finish the installation of secondary site "%2" by running SMS Setup with a script that specifies the installation parameters for site "%2". You can track the progress of SMS Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of SMS Setup by monitoring "smssetup.log" on server "%1". The sender has installed the SMS Bootstrap service on server "%1". The SMS Bootstrap service will finish the upgrade of secondary site "%2" by running SMS Setup with a script that specifies the upgrade parameters for site "%2". You can track the progress of SMS Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of SMS Setup by monitoring "smssetup.log" on server "%1".
The sender has installed the SMS Bootstrap service on server "%1". The SMS Bootstrap service will finish the deinstallation of secondary site "%2" by running SMS Setup with a script that specifies the deinstallation parameters for site "%2". You can track the progress of SMS Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of SMS Setup by monitoring "smssetup.log" on server "%1". 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 SMS installation drive.%12 %1 failed to start.%12 Possible cause: Server "%2" might not be running RAS Server Service. Solution: Verify that server "%2" is running RAS Server Service. The Winsock sender cannot connect to remote site server "%2" for site "%1" over the TCP/IP.%12 Possible cause: Remote site server "%2" might not be connected to the network. Solution: Verify that site server "%2" is connected to the network and functioning properly. Possible cause: The specified server name "%2" is unrecognizable. Solution: Verify that server name "%2" is recognizable by DNS server. Possible cause: The Winsock Sender/Receiver compononents are not started on the remote server. Solution: Verify that the Winsock Sender has been created on the remote server "%2". Possible cause: Network load might be too high. Solution: Verify that the network is not saturated. Verify that you can move large amounts of data across the network. The Winsock receiver on site server "%1" cannot start.%12 Possible cause: The Winsock DLL or the TCP/IP is mising on server "%1". Solution: Verify that TCP/IP is installed properly.
The Winsock receiver on site server "%1" cannot create a connection for clients.%12 Possible cause: Winsock Receiver can not get enough resoures(memorry) to handle a new connection. Solution: Verify that system resources are not exhausted. The sender cannot install secondary site "%1" on server "%2" because some fatal error occured in SMS 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 SMS Administrator's Console and rerun the secondary site creation wizard.%12 The SMS Bootstrap service running on secondary site "%1" on server "%2", started SMS Setup successfully.%12 The SMS Bootstrap service running on secondary site "%1" on server "%2", failed to start SMS Setup. Please check the logs on secondary site.%12 The SMS Setup running on secondary site "%1" on server "%2" has completed.%12 The SMS Setup running on secondary site "%1" on server "%2", failed. Please check the logs on secondary site.%12 The SMS Bootstrap service running on secondary site "%1" on server "%2", started package decompression.%12 The SMS Bootstrap service running on secondary site "%1" on server "%2", completed successfully.%12 The SMS Bootstrap service running on secondary site "%1" on server "%2", failed to connect to parent site.%12 Possible cause: Either connection to the parent site is unavailable or the sender address provided is not correct. Solution: If the secondary site does not show up even if the connection is there, please reinstall the site with correct sender address.
The sender cannot connect to remote site "%1" over the LAN.%12 Possible cause: Remote site server "%2" might not be connected to the LAN. Solution: Verify that site server "%2" is connected to the LAN and functioning properly. Possible cause: Share "%3" might not be accessible. Solution: Verify that share "%3" is visible and that the site server machine account has the necessary permissions to access the share. Possible cause: Network load might be too high. Solution: Verify that the network is not saturated. Verify that you can move large amounts of data across the network. SMS Sender is currently sending software distribution package %1 version %2 to site %3, %4 percent of the sending has already completed. SMS Sender encountered errors while sending software distribution package %1 version %2 to site %3, %4 percent of the sending has already completed. SMS Sender has successfully sent software distribution package %1 version %2 to site %3.
SMS Inbox Manager cannot copy files from "%1" to "%2".%12 Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Inbox Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Inbox Manager from properly accessing the site system. Solution: Investigate and correct any problems with your network.
SMS Inbox Manager cannot create directory "%1" with the desired security rights on server "%2".%12 Possible cause: The destination drive is full. Solution: Make more space available on that drive.
SMS Inbox Manager cannot create directory "%1" with the desired security rights on client access point "%2".%12 Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Inbox Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Inbox Manager from properly accessing the site system. Solution: Investigate and correct any problems with your network.
SMS 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 Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Inbox Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Inbox Manager from properly accessing the site system. Solution: Investigate and correct any problems with your network.
SMS Inbox Manager Assistant running on the client access point "%1" cannot connect to site server "%2".%12 Possible cause: The site server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site server is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing SMS Inbox Manager Assistant from properly accessing the site server. Solution: Investigate and correct any problems with your network. SMS Inbox Manager cannot create the client access point on site system "%1".%12 Possible cause: Site system "%1" does not have any drives or volumes that support file and directory permissions. For example, the FAT file system does not support permissions, but the NTFS file system does. Solution: Choose a site system that supports file and directory permissions.
SMS Inbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 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. SMS Outbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 Possible cause: Site system "%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 system "%4" has a high backlog of files in its outboxes. Solution: Give the system time to work through the current backlog. Do not create any additional tasks that would load the system further. SMS Software Inventory Processor successfully processed %1 software inventory files.%12 SMS Software Inventory Processor failed to process software inventory file "%1," and has moved it to "%2."%12 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 subsequent message 3703, which indicates the resynchronization has begun.
SMS Software Inventory Processor is terminating its processing cycle due to a SQL Server problem.%12 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. SMS Software Inventory Processor requested a resynchronization for machine "%1" because an attempt was made to update inventory information in the SMS site database that does not already exist.%12 SMS 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 SMS 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 SMS Administrator console, under Component Configuration, Data Processing and Storage Properties. SMS Software Inventory Processor was unable to store collected file "%1" for resource "%2".%12 Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive.
SMS Software Inventory Processor failed to process software inventory file "%1" because the file does not have a corresponding discovery record. SMS Software Inventory Processor has moved this file to the Orphans directory as file "%2" and will retry processing it later.%12 When SMS 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 SMS 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 SMS Software Inventory Processor retries the file every 10 minutes. Possible cause: SMS Discovery Data Manager is not running. 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.
SMS Software Inventory Processor failed to process the file %1 because it is larger than the defined maximum allowable size of %2.%12 Solution: Increase the maximum allowable size, which is defined in the registry key HKLM\Software\Microsoft\SMS\Components\SMS_SOFTWARE_I NVENTORY_PROCESSOR\Max File Size (the default is 5 MB), and wait for SMS Software Inventory Processor to retry the operation. SMS Software Inventory Processor requested a resynchronization for machine "%1" because a software inventory file was sent without a public key information.%12 Received more than 10 NULL status message pointers from the Offer Status Queue.%12 Unable to create a file to store the replication data at %1.%12 Unable to open the incoming %1 replication file.%12 While initializing, no records of the proper type were found in the data store.%12 Received a status message from site %1, but this is site %2. Ignoring message.%12
The Offer summary %1,%2 has not been heard from for %3 days. This summary has been marked for deletion.%12 Failed to send the replication file. Will try again later.%12 Interval %1 not found in OfferSummaryDetail record.%12 No data store was found at %1 to initialize from.%12 The file %1 is not the correct type of replication file for this summarizer, deleting the file.%12 Unable to create a file to store the summary data. Will try again in %1 seconds.%12 Unable to send changed records to the data store. Will try again in %1 seconds.%12 SMS 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 Advertisement Status summary data in the SMS Administrator 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. SMS Offer Status Summarizer cannot process a status message because it does not contain an Advertisement ID. As a result, the Advertisement Status summary data in the SMS Administrator 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. SMS Offer Status Summarizer cannot process a status message because it contains the invalid Advertisement ID "%6". As a result, the Advertisement Status summary data in the SMS Administrator 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. SMS Offer Manager successfully processed new advertisement %1.%12 SMS Offer Manager successfully removed advertisement %1.%12 SMS Replication Manager successfully instructed SMS Scheduler to send files to site "%1".
SMS Replication Manager received files from the "%1" component at a child site, but that component is not enabled at the current site. SMS Replication Manager will throw away these files. Solution: Either enable component "%1" at the current site, or reconfigure it at all child sites to not replicate to the current site. SMS NT User Group Discovery Agent failed to read the necessary registry information, but it will retry at its next interval.%12 SMS NT User Group Discovery Agent failed to read the location of the outbox, but it will retry at its next interval.%12 Solution: Do nothing. SMS NT User Group Discovery Agent will retry at its next interval. SMS NT User Group Discovery Agent processed %1 user groups from domain %2.%12 SMS NT User Group Discovery Agent failed to enumerate user groups from the domain %1. No users from the trusted domains will be discovered.%12 Possible cause: The primary domain controller is not accessible. Solution: Verify that the primary domain controller is running and accessible. Possible cause: The domain %1 does not exist. Solution: Verify that the domain name was specified correctly. In SMS Administrator console, under Site Settings, Discovery Methods, open the Windows NT User Group Discovery dialog box. Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights.
SMS NT User Group Discovery Agent failed to determine the trusted domains for the domain %1. Therefore, no users from the trusted domains will be discovered.%12 Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights. SMS NT User Group Discovery Agent failed to find the primary domain controller for the domain %1.%12 Possible cause: The primary domain controller is not accessible. Solution: Verify that the primary domain controller is running and accessible. Possible cause: The domain %1 does not exist. Solution: Verify that the domain name was specified correctly. In SMS Administrator console, under Site Settings, Discovery Methods, open the Windows NT User Group Discovery dialog box. Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights. SMS Windows NT Server Discovery Agent failed to read the necessary registry information.%12 Possible cause: The registry information is not available yet. Solution: SMS Windows NT Server Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval.
SMS Windows NT Server Discovery Agent failed to read the location of the outbox.%12 Possible cause: The information necessary to complete the initialization is not available now. Solution: Windows NT Server Discovery Agent is waiting for the information to become available and will retry at its next interval.
SMS Windows NT 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
SMS NT User Discovery Agent failed to read the necessary registry information, but it will retry at its next interval.%12 SMS NT User Discovery Agent failed to read the location of the outbox, but it will retry at its next interval.%12 Solution: Do nothing. SMS NT User Group Discovery Agent will retry at its next interval. SMS NT User Discovery Agent processed %1 users from domain %2.%12 SMS NT User Discovery Agent failed to enumerate users from the domain %1. No users from the trusted domains will be discovered.%12 Possible cause: The primary domain controller is not accessible. Solution: Verify that the primary domain controller is running and accessible. Possible cause: The domain %1 does not exist. Solution: Verify that the domain name was specified correctly. In SMS Administrator console, under Site Settings, Discovery Methods, open the Windows NT User Group Discovery dialog box. Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights. SMS NT User Discovery Agent failed to determine the trusted domains for the domain %1. Therefore, no users from the trusted domains will be discovered.%12 Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights.
SMS NT User Discovery Agent failed to find the primary domain controller for the domain %1.%12 Possible cause: The primary domain controller is not accessible. Solution: Verify that the primary domain controller is running and accessible. Possible cause: The domain %1 does not exist. Solution: Verify that the domain name was specified correctly. In SMS Administrator console, under Site Settings, Discovery Methods, open the Windows NT User Group Discovery dialog box. Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights. SMS Despooler successfully stored the compressed binaries for package "%1" at "%2".%12 SMS Despooler failed to decompress package "%1" from "%2".%12 Possible cause: The compressed image "%2" is either missing or corrupt. Solution: SMS Distribution Manager will attempt to recover the package by requesting a new compressed package image from the site that sent it. SMS Despooler failed to merge delta to the compressed package "%1".%12 Possible cause: The destination drive is full. Solution: Make more space available on that drive. SMS Despooler will attempt to merge the delta again during its next retry interval SMS Despooler deleted an instruction and package file from SMS 2.0 child site %1 because this site doesn't allow any child sites that are SMS 2.0 SP4 or earlier. Solution: Upgrade the 2.0 child site to SMS 2.0 SP5 or above, or upgrade the 2.0 child site to SMS 2003, or change the site property site connection setting in the Administrator UI to allow child sites that are SMS 2.0 SP4 or earlier.
SMS 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. Solution: Extend the Active Directory schema to allow SMS sites to publish their public keys into AD, or use the preinst.exe tool to manually replicate the public keys, or change the site property site connection setting in the Administrator UI to allow unsigned key exchange between sites. SMS 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. Solution: Extend the Active Directory schema to allow sites to publish their public keys into AD, or use the preinst.exe tool to manually replicate the public keys. SMS 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.
SMS Despooler successfully received the compressed image for package %1 version %2.%12 Sent a replication file to %1.%12 A replication file has been created, the replication file is %1.%12 Processing the incoming replication file %1.%12 The file %1 is not a replication file for this summarizer, deleting the file.%12 Unable to decrypt the SQL server login user name and/or password.%12 Unable to find this summarizer's component section in the site control file.%12 Unable to open the site control file.%12 Unable to read the site configuration.%12 An error occurred while setting or resetting a change notification for the site control file.%12
An error occurred while setting or resetting a change notification for the summarizer's inbox.%12 Unable to create the status message queue.%12 Failed to send a replication file to site %1.%12 The data store %1 was not found.%12 .Could not read all of the records in the file %1. The error code is %2.%12 Unable to write changed records to the data store.%12 Unable to initialize the summarizer. The returned error code is %1.%12 The site properties are not set in the registry.%12 The error %1 has occurred while initializing the status message queue.%12 The summarizer cannot continue and is stopping. The exit code is %1.%12 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 Reset specific tally intervals as requested from %1, by user %2, on system %3, at site %4.%12 SMS Component Status Summarizer detected that the list of Component Status Display Intervals specified in the site control file has changed.%12 SMS Component Status Summarizer will reconfigure itself to use the new set of Display Intervals. SMS Component Status Summarizer detected that entry "%1" of the Component Thresholds property list in the site control file is corrupt.%12 Possible cause: The site control file entry does not contain a component name. Solution: SMS Component Status Summarizer will ignore this entry, which might result in the Status column of the Component Status display in the SMS Administrator console being improperly set for a particular component. This problem might be the result of a code defect. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS 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 Possible cause: SMS Component Status Summarizer will now begin tracking the status of this component as if it were properly listed in the site control file. If this component is an SMS component, it could mean the component should have been deinstalled sometime in the past by Site Component Manager. Solution: Investigate whether or not the component should really be installed and running on this computer. If it should not be installed, the problem might be the result of defective code. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS 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 Possible cause: The count equals or exceeds the Component Status Critical Threshold (%5 status messages) for Informational status messages for the component. Solution: SMS Component Status Summarizer will set the component's status to Critical in the Component Status summary in the SMS Administrator console. SMS 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 Possible cause: The count equals or exceeds the Component Status Critical Threshold (%5 status messages) for Warning status messages for the component. Solution: SMS Component Status Summarizer will set the component's status to Critical in the Component Status summary in the SMS Administrator console.
SMS 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 Possible cause: The count equals or exceeds the Component Status Critical Threshold (%5 status messages) for Error status messages for the component. Solution: SMS Component Status Summarizer will set the component's status to Critical in the Component Status summary in the SMS Administrator console. SMS 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 Possible cause: The count equals or exceeds the Component Status Warning Threshold (%5 status messages) for Informational status messages for the component. Solution: If the component's status is not already set to Warning, SMS Component Status Summarizer will set the component's status to Warning in the Component Status summary in the SMS Administrator console. SMS 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 Possible cause: The count equals or exceeds the Component Status Warning Threshold (%5 status messages) for Warning status messages for the component. If the component's status is not already set to Warning, SMS Component Status Summarizer will set the component's status to Warning in the Component Status summary in the SMS Administrator console.
SMS 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 Possible cause: The count equals or exceeds the Component Status Warning Threshold (%5 status messages) for Error status messages for the component. Solution: If the component's status is not already set to Warning, SMS Component Status Summarizer will set the component's status to Warning in the Component Status summary in the SMS Administrator console. SMS Component Status Summarizer set the status of component "%1", running on computer "%2", to Critical.%12 Possible cause: The component is experiencing a problem. Solution: Diagnose and fix the problem by: 1. Examining the status messages that the component reports. 2. Correcting the problem. 3. Instructing SMS Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the SMS Administrator console. When the counts are reset, SMS Component Status Summarizer will change the status of the component to OK. This might take some time if site "%3" is a child site. 4. Delete any unwanted status messages from the SMS site database, if necessary. 5. Monitor the component occasionally to verify that the problem does not reoccur. Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component. Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the SMS Administrator console.
SMS Component Status Summarizer set the status of component "%1" running on computer "%2" to Warning.%12 Possible cause: The component is experiencing a problem. Solution: Diagnose and fix the problem by: 1. Examine the status messages that the component reports. 2. Correcting the problem. 3. Instructing SMS Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the SMS Administrator console. When the counts are reset, SMS Component Status Summarizer will change the status of the component to OK. This might take some time if site "%3" is a child site. 4. Deleting any unwanted status messages from the site database, if necessary. 5. Monitor the component occasionally to verify the problem does not reoccur. Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component. Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the SMS Administrator console.
SMS Component Status Summarizer reset the status of component "%1", running on computer "%2", to OK.%12 SMS 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", SMS 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. Solution: SMS Component Status Summarizer will also reset a component's status to OK when an administrator manually resets the counts of status messages reported by the component for the Threshold Period. Solution: SMS Component Status Summarizer will also reset a component's status to OK when an administrator adjusts the Component Status Thresholds to be higher than the current counts of status messages reported by the component.
SMS Component Status Summarizer has not received a status message from component "%1", running on computer "%2", in %3 hours.%12 Possible cause: There is no record of this component in the site control file. Solution: The SMS Component Status Summarizer will assume the component was deinstalled and will remove it from the Component Status summary.%12
SMS 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 SMS Component Status Summarizer is running.%12 Possible cause: SMS Component Status Summarizer is designed to process only status messages reported by components at the site where SMS Component Status Summarizer is running. Solution: SMS Component Status Summarizer will ignore this status message. Possible cause: This problem might 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.
SMS 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". SMS 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". SMS 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".
SMS 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". SMS 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". Possible cause: "%9" is a custom Display Interval you have configured the SMS Component Status Summarizer to use. SMS Component Status Summarizer cannot display a an unencrypted version of "%9" in a status message. Solution: If you wish to decode "%9" into something more readable, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS 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 SMS 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
SMS 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 SMS 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 SMS 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 SMS Component Status Summarizer to use. SMS Component Status Summarizer cannot display an unencrypted version of "%9" in a status message.%12 SMS 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 24hour 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 SMS 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
SMS 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 SMS 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 SMS 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 SMS Component Status Summarizer to use. SMS Component Status Summarizer cannot display an unencrypted version of "%9" in a status message.%12 SMS Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Online. SMS Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Failed.%12 Possible cause: This component has failed to generate a heartbeat within its heartbeat interval or has reported with its heartbeat that it is in a failure state. Solution: Verify that the condition persists by examining compmon.log and then check the component's log file.
SMS Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Degraded.%12 Possible cause: This component has with its heartbeat that it is in a degraded state. Solution: Verify that the condition persists by examining the component's log file and performance counters. SMS Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Offline.%12 Possible cause: This component is under maintenance or shutdown. Solution: Verify that maintenance is not being performed at this time and the component is running. If the component is not running, restart it using SMS Service Manager. SMS Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Unknown.%12 Possible cause: This component does not have an Availability State, it could not be accessed or it has not been updated. Solution: Verify that the Site Server can connect to the registry of the server on which this component resides.
SMS Site System Status Summarizer could not access storage object "%1" on site system "%2".%12 Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site System Status Summarizer does not have sufficient access rights to connect to the site system and access the storage object. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to connect to the site system and access the storage object. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the site system. Solution: Investigate and correct any problems on your network. Possible cause: You took the site system out of service and do not intend to use it as a site system any more. Solution: Remove the site system from the list of site systems used by this site; this list appears in the Site Systems node of the SMS Administrator console. Possible cause: You accidentally deleted the storage object or took the storage object out of service. Solution: The SMS components will eventually detect that the
SMS Site System Status Summarizer still cannot access storage object "%1" on site system "%2".%12 Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site System Status Summarizer does not have sufficient access rights to connect to the site system and access the storage object. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to connect to the site system and access the storage object. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the site system. Solution: Investigate and correct any problems on your network. Possible cause: You took the site system out of service and do not intend on using it as a site system any more. Solution: Remove the site system from the list of site systems used by this site; this list appears under Site Systems in the SMS Administrator console. Possible cause: You accidentally deleted the storage object or took the storage object out of service. Solution:System Status Summarizer eventually detect that the SMS Site The SMS components will successfully accessed storage object "%1" on site system "%2".%12 Possible cause: The storage object had been inaccessible since "%3". Solution: If the storage object has sufficient free storage space, SMS Site System Status Summarizer will now restore the status of the storage object to OK in the Site System Status summary in the SMS Administrator console.
SMS Site System Status Summarizer could not access the "%1" database on SMS Site Database Server "%2". Possible cause: The SMS Site Database Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the SMS Site Database Server is turned on, connected to the network, and functioning properly. Possible cause: The SQL Server account is misconfigured in the SMS Administrator console. Solution: Verify that the SQL Server account in the SMS Administrator console contains the correct user name and password, and that the account has sufficient access rights to the SMS Site Database Server. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the SMS Site Database Server. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your SMS site. SMS Site System Status Summarizer will now set the status of the "%1" database to Critical in the Site System Status summary in the SMS Administrator console. When you correct the problem and SMS Site System Status Summarizer successfully accesses the database, SMS Site System Status Summarizer will set the status
SMS Site System Status Summarizer still cannot access the "%1" database on SMS Site Database Server "%2".%12 Possible cause: The SMS Site Database Server is turned off, not connected to the network, or not functioning properly. Solution: verify that the SMS Site Database Server is turned on, connected to the network, and functioning properly. Possible cause: The SQL Server account is misconfigured in the SMS Administrator console. Solution: Verify that the SQL Server account in the SMS Administrator console contains the correct user name and password, and that the account has sufficient access rights to the SMS Site Database Server. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the SMS Site Database Server. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your SMS site. The database has been inaccessible since "%3". When you correct the problem and SMS Site System Status Summarizer successfully accesses the database, SMS Site System Status Summarizer will set the status of the database to OK, providing that the database has sufficient free successfully accessed the SMS Site System Status Summarizer space. "%1" database on SQL server "%2".%12 Possible cause: The database had been inaccessible since "%3". Solution: If the database has sufficient free space, SMS Site System Status Summarizer will now restore the status of the database to OK in the Site System Status summary in the SMS Administrator console.
SMS Site System Status Summarizer could not access the transaction log for the "%1" database on SQL server "%2".%12 Possible cause: The SMS Site Database Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the SMS Site Database Server is turned on, connected to the network, and functioning properly. Possible cause: The SQL Server account is misconfigured in the SMS Administrator console. Solution: Verify that the SQL Server account in the SMS Administrator console contains the correct user name and password, and that the account has sufficient access rights to the SMS Site Database Server. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the SMS Site Database Server. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your SMS site. SMS Site System Status Summarizer will now set the status of the transaction log to Critical in the Site System Status summary in the SMS Administrator console. When you correct the problem and SMS Site System Status Summarizer successfully accesses the transaction log, SMS Site System Status Summarizer will set the
SMS Site System Status Summarizer still cannot access the transaction log for the "%1" database on SQL server "%2".%12 Possible cause: The SQL server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the SQL server computer is turned on, connected to the network, and functioning properly. Possible cause: The SQL server account is misconfigured in the SMS Administrator console. Solution: Verify that the SQL server account in the SMS Administrator console contains the correct user name and password, and that the account has sufficient access rights to the SQL server computer. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the SQL server computer. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your SMS site. The transaction log has been inaccessible since "%3". When you correct the problem and SMS Site System Status Summarizer successfully accesses the transaction log, SMS Site System Status Summarizer will set the status of the transaction log to OK, providingSystem Status Summarizer successfullyfree space. SMS Site that the transaction log has sufficient 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, SMS Site System Status Summarizer will now restore the status of the transaction log to OK in the Site System Status summary in the SMS Administrator console.
SMS 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. SMS Site System Status Summarizer will now set the status of the storage object to OK in the Site System Status summary in the SMS Administrator console.
SMS 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. Possible cause: The storage object is almost full. Solution: Make more space available on the storage object by deleting unneeded files. Possible cause: The Warning Free Space Threshold is set too high for this storage object. Solution: Decrease the Warning Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 -> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for this storage object. SMS Site System Status Summarizer will now set the status of the storage object to Warning in the Site System Status summary in the SMS Administrator console. SMS 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. Possible cause: The storage object is almost full. Solution: Make more space available on the storage object by deleting unneeded files. Possible cause: The Critical Free Space Threshold is set too high for this storage object. Solution: Decrease the Critical Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 -> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for this storage object. SMS Site System Status Summarizer will now set the status of the storage object to Critical in the Site System Status summary in the SMS Administrator console.
SMS Site System Status Summarizer detected that the "%1" database on SMS site database server "%2" has %3 KB of free space, which is above the Free Space Thresholds for the database. SMS Site System Status Summarizer will now set the status of the database to OK in the Site System Status summary in the SMS Administrator console. SMS Site System Status Summarizer detected that the "%1" database on SMS 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. Possible cause: The database is almost full. Solution: Make more space available in the database by deleting unneeded data. Possible cause: The database is too small. Solution: Increase the size of the database using SQL Enterprise Manager. Possible cause: The Warning Free Space Threshold is set too high for the database. Solution: Decrease the Warning Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 -> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the database. SMS Site System Status Summarizer will now set the status of the database to Warning in the Site System Status summary in the SMS Administrator console.
SMS Site System Status Summarizer detected that the database "%1" on SMS 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. Possible cause: The database is almost full. Solution: Make more space available in the database by deleting unneeded data. Possible cause: The database is too small. Solution: Increase the size of the database using SQL Enterprise Manager. Possible cause: The Critical Free Space Threshold is set too high for the database. Solution: Decrease the Critical Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 -> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the database. SMS Site System Status Summarizer will now set the status of the database to Critical in the Site System Status summary in the SMS Administrator console. SMS Site System Status Summarizer detected that the transaction log for the "%1" database on SMS site database server "%2" has %3 KB of free space, which is above the Free Space Thresholds for the transaction log. SMS Site System Status Summarizer will now set the status of the transaction log to OK in the Site System Status summary in the SMS Administrator console.
SMS Site System Status Summarizer detected that the transaction log for the "%1" database on SMS 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. Possible cause: The transaction log is too small. Solution: Increase the size of the transaction log using SQL Enterprise Manager. Possible cause: The Warning Free Space Threshold is set too high for the transaction log. Solution: Decrease the Warning Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 -> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the transaction log. SMS Site System Status Summarizer will now set the status of the transaction log to Warning in the Site System Status summary in the SMS Administrator console.
SMS Site System Status Summarizer detected that the transaction log for the "%1" database on SMS 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. Possible cause: The transaction log is too small. Solution: Increase the size of the transaction log using SQL Enterprise Manager. Possible cause: The Critical Free Space Threshold is set too high for the transaction log. Solution: Decrease the Critical Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 -> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the transaction log. Possible cause: A software defect caused the transaction log to fill up completely. Solution: investigate why the transaction log is full (see the SQL Server documentation for details). If you suspect a software defect, contact Microsoft for more information. Stop and start SQL Server to empty the transaction log. SMS Site System Status Summarizer will now set the status of the database to Critical in the Site System Status summary in the SMS Administrator console. Summarizer has not been able to access SMS Site System Status the storage object "%1" on Site Object "%2" for %3 hours. SMS 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.
SMS 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. Possible cause: The storage object is almost full or the storage status has not yet been received from the Branch Distribution Point. Solution: Verify that the messages from the Branch Distribution Point are successfully received. Make more space available on the storage object by deleting unneeded files. Possible cause: The Critical Free Space Threshold is set too high for this storage object. Solution: Decrease the Critical Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 -> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for this storage object. SMS Site System Status Summarizer will now set the status of the storage object to Critical in the Site System Status summary in the SMS Administrator console.
SMS Site System Status Summarizer detected that the availability of the "%1" role on SMS Server "%2" has changed to Online. SMS Site System Status Summarizer detected that the availability of the "%1" role on SMS Server "%2" has changed to Failed.%12 Possible cause: This SMS Server Role is unable to function. Solution: Verify that no security or configuration problems exist and that all related components are running.
SMS Site System Status Summarizer detected that the availability of the "%1" role on SMS Server "%2" has changed to Degraded.%12 Possible cause: This SMS Server Role is experiencing a severe impact to its performance and or partial loss of functionality. Solution: Check the overall CPU, Memory and Disk performance on this server. Solution: Verify that no security or configuration problems exist that could be impacting availability of this role.
SMS Site System Status Summarizer detected that the availability of the "%1" role on SMS Server "%2" has changed to Offline.%12 Possible cause: This SMS Server Role is under maintenance or shutdown. Solution: Verify that maintenance is not being performed at this time and that all related components are running.
SMS Site System Status Summarizer detected that the availability of the "%1" role on SMS Server "%2" has changed to Unknown.%12 Possible cause: This SMS Server Role does not have an Availability State, it could not be accessed or it has not been updated. Solution: Verify that the Site Server can connect to the registry of the site system. SMS NetWare Bindery Server Discovery Agent failed to read the necessary registry information.%12 Possible cause: The registry information is not available yet. Solution: NetWare Bindery Server Discovery Agent will try to obtain the registry information at its next interval. SMS NetWare Bindery Server Discovery Agent failed to read the location of the outbox.%12 Possible cause: The information necessary to complete the initialization is not available now. Solution: NetWare Bindery Server Discovery Agent is waiting for the information to become available and will try again at its next interval.
SMS NetWare Bindery Server Discovery Agent read the system roles and found %1 server role entries in the site control file.%12 NetWare Bindery 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.
SMS Site Component Manager is deinstalling all SMS server components from site system "%1". SMS Site Component Manager successfully deinstalled all SMS server components from site system "%1". SMS Site Component Manager failed to deinstall all SMS server components from site system "%1". Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry this operation in %2 minutes. To force SMS Site Component Manager to immediately retry this operation, stop and restart SMS Site Component Manager using the SMS Service Manager. SMS Site Component Manager failed to deinstall all SMS server components from site system "%1". Solution: Review the previous status messages to determine the exact reason for the failure. This operation has repeatedly failed for %2 minutes and will probably never succeed, therefore SMS Site Component Manager not retry this operation again. You might ignore this message and do nothing if the site system is no longer in service or the operating system has been reinstalled on the site system. Otherwise some remnants of the SMS server components might still be installed on this site system, and you will have to manually remove them. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS Site Component Manager successfully installed the performance counters for this component on this site system.
SMS Site Component Manager failed to install the performance counters for this component on this site system. Possible cause: The site system's registry is full. Solution: Increase the size of the site system's registry. Possible cause: SMS Site Component Manager 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. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in SMS Site Component Manager's log file "sitecomp.log" and the perfsetup.log on the site system.
SMS Site Component Manager successfully removed the performance counters for this component from this site system.
SMS Site Component Manager failed to remove the performance counters for this component from this site system. Possible cause: SMS Site Component Manager 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. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in SMS Site Component Manager's log file "sitecomp.log" and the perfsetup.log on the site system.
SMS Site Component Manager could not add machine account "%1" to the SQL Access Group "%2" on the SQL Server machine "%3". Possible cause: This site's SMS Service account or the site server's machine account might not have administrative access to the SQL Server computer. Solution: Manually add the machine account "%1" to the SQL Access Group "%2" on the SQL Server machine "%3".
SMS Systems Management Server could not locate the "System Management" container in Active Directory. 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. Possible cause: This site's SMS Service account or the site server's machine account might not have the correct rights to update active directory. Solution: Either give the Service Account rights to update the domain's System Container, or manually create the "System Management" container in this domain's Active Directory system container, and give the Service Account full rights to that container (and all children objects.) SMS Systems Management Server created a default "System Management" container in Active Directory. This will be used to publish all necessary Active Directory objects for this site. Systems Management Server successfully created the object "%1" in Active Directory. Systems Management Server cannot update the already existing object "%1" in Active Directory. Possible cause: This site's SMS Service account or the site server's machine account may not have full control rights for the "System Management" container in Active Directory Solution: Give the site's SMS Service account full control rights to the "System Management" container, and all child objects in Active Directory. Possible cause: The Active Directory object "%1" has been moved to a location outside of the "System Management" container, or has been lost. Solution: Delete the object from its current location, and let SMS create a new object. Possible cause: The Active Directory schema has not been extended with the correct SMS Active Directory classes and attributes. Solution: Turn off Active Directory publishing for each site in the forest, until the schema can be extended. The schema can be extended with the tool "extadsch.exe" from the SMS CD.
Systems Management Server cannot create the object "%1" in Active Directory. Possible cause: This site's SMS Service account or the site server's machine account may not have full control rights for the "System Management" container in Active Directory Solution: Give the site's SMS Service account full control rights to the "System Management" container, and all child objects in Active Directory. Possible cause: Another Active Directory object named "%1" already exists somewhere outside of the "System Management" container Solution: Locate the other object with the same name, and delete the object from its current location. Then allow SMS create a new object. Possible cause: The Active Directory schema has not been extended with the correct SMS Active Directory classes and attributes. Solution: Turn off Active Directory publishing for each site in the forest, until the schema can be extended. The schema can be extended with the tool "extadsch.exe" from the SMS CD.
Systems Management Server successfully deleted the object "%1" from Active Directory. Systems Management Server cannot delete the object "%1" in Active Directory. Possible cause: This site's SMS Service account or the site server's machine account may not have full control rights for the "System Management" container in Active Directory Solution: Give the site's SMS Service account full control rights to the "System Management" container, and all child objects in Active Directory. Possible cause: The Active Directory object "%1" has been moved to a location outside of the "System Management" container Solution: Manually delete the object from its current location.
Site Component Manager could not grant the Management Point's machine account permissions to update the Active Directory object: "%1". Possible cause: This site's SMS Service account or the site server's machine account might not have full control rights for the "System Management" container in Active Directory Solution: Manually add the Management Point's machine account to the Active Directory object "%1". Possible cause: The Management Point server is not in a trusted domain, or its machine account has not replicated the domain controllers necessary for completing this action. Solution: Verify that the Management Point's machine account is trusted by the forest, and that it has replicated to the domain controllers. Until the permissions for Active Directory object "%1" are set up correctly, clients for this site will be unable to communicate with that Management Point.
SMS Server Locator Point encountered an error when connecting to its Database. Possible cause: The SQL server site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the SQL server site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Server Locator Point does not have sufficient access rights to the SQL server site system. Solution: Verify that the SQL server is properly configured to allow Server Locator Point access. Verify that the credentials used by Server Locator Point to connect to the Database have not expired. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Server Locator Point to use an NT integrated security account, with appropriate access. Possible cause: Network problems are preventing SMS Server Locator Point from properly accessing the SQL server. Solution: Investigate and correct any problems with your network.
Systems Management Server cannot update the dNSHostName property for the existing object "%1" in Active Directory. This property is used to publish fully qualified host names in Active Directory. Possible cause: The Active Directory schema has not been extended with latest version of the SMS Active Directory classes and attributes. Solution: Ensure the schema has been extended with the latest version of the SMS Active Directory classes and attributes. The schema can be extended with the tool "extadsch.exe" from the SMS directory on the SMS Site server that reported this message. SMS Site Component Manager successfully installed the COM access registry keys for this component on this site system. SMS Site Component Manager failed to install the COM access registry keys for this component on this site system. Possible cause: The site system's registry is full. Solution: Increase the size of the site system's registry. Possible cause: SMS Site Component Manager 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. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in SMS Site Component Manager's log file "sitecomp.log" and the comregsetup.log on the site system.
SMS Site Component Manager successfully removed the COM access registry keys for this component from this site system.
SMS Site Component Manager failed to remove the COM access registry for this component from this site system. Possible cause: SMS Site Component Manager does not have administrator rights to this site system. Solution: Verify that the either the site server computer account or the Site System Installation account is a member of the local Administrators group on the site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in SMS Site Component Manager's log file "sitecomp.log" and the comregsetup.log on the site system.
SMS System Health Validator %1 encountered an error. ErrorCode = %2.%12 SMS Site Component Manager failed to add machine account %1 to the user group %2, this must be done manually.
SMS Site Component Manager failed to install this component, because it can't configure Microsoft Internet Information Services (IIS). Possible cause: Microsoft Internet Information Services (IIS) is not installed or running. Solution: Use Add/Remove Programs to install Microsoft Internet Information Services (IIS), and verify that the World Wide Web Service is running. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer and configure Microsoft Internet Information Services (IIS) on this site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component %1 until Microsoft Internet Information Services (IIS) is installed and configured correctly. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS 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 SMS documentation and the Microsoft Knowledge Base for further information. SMS 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 SMS documentation and the Microsoft Knowledge Base for further information. SMS Site Component Manager failed to install this component, because the Installation Program (ReportingInstall.exe) for this component could not complete successfully. Refer to the component's installation log, as well as the SMS documentation and the Microsoft Knowledge Base for further information.
SMS Site Component Manager failed to install this component, because the virtual directory required for this component is already in use. Possible cause: Another SMS site is using this virtual directory name for its reporting. Solution: Use a different virtual directory name. Possible cause: A previous installation of Report Viewer was not completely removed. Solution: Manually delete the directory containing the previous installation of Report Viewer. Refer to the component's installation logs, as well as the SMS documentation and the Microsoft Knowledge Base for further information. SMS Site Component Manager failed to install this component, because it can't find and configure Microsoft Message Queuing Services (MSMQ). Possible cause: Microsoft Message Queuing Services (MSMQ) is not installed or running. Solution: Use Add/Remove Programs to install Microsoft Message Queuing Services (MSMQ). Possible cause: SMS Site Component Manager does not have sufficient access rights to administer and configure Microsoft Message Queuing Services (MSMQ) on this site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component %1 until Microsoft Message Queuing Services (MSMQ) is installed and configured correctly. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS Site Component Manager successfully installed this component, However a reboot is required to complete the installation. Possible cause: Some files could not be replaced because they were in use by another process Solution: Reboot the machine to complete the installation. The component %1 may not be fully operational until a reboot. Refer to your SMS documentation or the Microsoft Knowledge Base for further information. SMS 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. Possible cause: Background Intelligent Transfer Service (BITS) is not installed or running. Solution: Use Add/Remove Programs to install Background Intelligent Transfer Service (BITS) . Possible cause: SMS Site Component Manager does not have sufficient access rights to administer and configure Background Intelligent Transfer Service (BITS) on this site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component %1 until Background Intelligent Transfer Service (BITS) is installed and configured correctly. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS Site Component Manager failed to install this component, because it couldn't determine the the name of the IIS anonymous user account. Possible cause: The account is not configured correctly in IIS. Solution: Configure the account in IIS. SMS Site Component Manager cannot install component %1 until this account is configured correctly. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS Site Component Manager successfully installed this component. However the SQL Server Principal Name (SPN) could not be validated in Active Directory. Possible cause: The MSSQL Service is running under a user account, instead of the computer account. In this case, SQL does not publish its own SPN. Solution: Manually publish the SQL SPN in Active Directory. The component %1 will operate correctly. However remote site systems requiring access to SQL Server (i.e., server locator points, or management points) might not be able to access SQL in advanced security mode. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS Site Component Manager failed to install this component, because the designated Web Site of Internet Information Services is not running or started. Possible cause: The designated Web Site is in the Stopped or Paused state. Solution: Start the designated Web Site using the Internet Services Manager. Possible cause: The World Wide Publishing Service is in the Stopped or Paused or Disabled state. Solution: Start the World Wide Publishing Service on the machine. SMS Site Component Manager cannot install component %1 until the designated Web Site is started. Refer to your SMS documentation or the Microsoft Knowledge Base for further information. SMS 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. SMS 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.
MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.%12 Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly.
SMS Site Component Manager failed to install this component, because Secure Sockets Layer (SSL) is not configured properly on the Internet Information Server. Possible cause: No Server Certificate is attached to the designated Web Site. Solution: Refer to SMS Documentation regarding how to create and attach a proper Server Certificate to the designated Web Site. Possible cause: The Server Certificate is invalid or expired. Solution: Refer to SMS Documentation regarding how to create and attach a proper Server Certificate to the designated Web Site.
SMS Site Component Manager failed to install this component, because it can't configure Microsoft Internet Authentication Service (IAS). Possible cause: Microsoft Internet Authentication Service (IAS) is not installed or running. Solution: Use Add/Remove Programs to install Microsoft Internet Authentication Service (IAS). Possible cause: SMS Site Component Manager does not have sufficient access rights to administer and configure Microsoft Internet Authentication Service (IAS) on this site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component %1 until Microsoft Internet Authentication Service (IAS) is installed and configured correctly. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS 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. Possible cause: You have not installed the required version of Windows Server on the site system. Solution: Install the required version of Windows Server on the site system. Refer to the Configuration Manager Documentation Library to determine the required version. Possible cause: You accidentally configured ConfigMgr to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the Configuration Manager console.
SMS Site Component Manager failed to install this component, because it can't configure Microsoft Windows Deployement Services (WDS). Possible cause: Microsoft Windows Deployment Services (WDS) is not installed. Solution: Use Add/Remove Programs to install Windows Deployment Services (WDS). Possible cause: SMS Site Component Manager does not have sufficient access rights to configure Microsoft Windows Deployment Services (WDS) on this site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component %1 until Microsoft Windows Deployment Services (WDS) is installed. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.
SMS Site Component Manager failed to install this component, because it either can't find or configure WSUS. Possible cause: WSUS service is not installed or running. Solution: Use Add/Remove Programs to install WSUS.
SMS Site Component Manager failed to install WSUS role on server %1. Refer to the SMS documentation and the Microsoft Knowledge Base for further information. SMS Site Component Manager faild to install component %1 on server %2. The WebDAV server extension is either not installed or not configured properly. Solution: Make sure WebDAV is installed and enabled. Make sure there is an authoring rule that allow "All users" read access to "All content". Make sure the WebDAV settings "Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true" and "Allow Custom Properties" is set to false.%12
SMS Site Backup was unable to open control file "%1". Site backup did not occur.%12 Possible cause: Wrong name specified or permissions to "%1" are incorrect. Solution: Verify that a readable backup control file named "%1" exists. SMS Site Backup stopped the "%1" executable on the local computer.%12 SMS Site Backup could not stop the "%1" executable on the local computer.%12 Possible cause: "%1" is an interactive Windows application and is waiting for user confirmation of the stop request. Solution: Manually stop this application. SMS Site Backup started the "%1" executable on the local computer.%12 SMS Site Backup could not start the "%1" executable on the local computer.%12 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. SMS Site Backup stopped the %1 service on site system %2.%12 SMS Site Backup could not stop the %1 service on site system %2.%12 Possible cause: SMS Site Backup 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. SMS Site Backup started the %1 service on site system %2.%12
SMS Site Backup could not start the %1 service on site system %2.%12 Possible cause: SMS Site Backup 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. SMS Site Backup successfully backed up file system object %1 to %2.%12 SMS Site Backup was unable to back up file system object %1 to %2.%12 Possible cause: %1 is not readable, or %2 is not writable. Solution: Adjust file attributes and/or permissions of %1 and/or %2. Possible cause: The destination directory %2 did not already exist, and SMS Site Backup was unable to create it. Solution: Verify that a regular file with the same name as %2 or one of its parent directories does not exist, or replace %2 with an existing directory. Possible cause: %1 or %2 are on remote computers that SMS Site Backup does not have sufficient access rights to administer. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. Possible cause: Source %1 being copied to %2 may cause a recursive operation Solution:Backupthat destination folder does not key %1 to the SMS Site Verify successfully backed up registry exist within %2.%12
SMS Site Backup was unable to back up registry key %1 to %2.%12 Possible cause: SMS Site Backup was unable to connect to or set backup privileges for the source registry. Solution: If %1 is in a remote registry, verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer; otherwise, reboot. Possible cause: %1 specifies a registry key relative to a hive other than HKEY_LOCAL_MACHINE. Solution: Change %1 so it is relative to HKEY_LOCAL_MACHINE. Possible cause: %2 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %2 and/or its directory. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application.
SMS Site Backup successfully backed up %1 database %2 to %3.%12
SMS Site Backup was unable to back up %1 database %2 to %3.%12 Possible cause: %3 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %3 and its directory. 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. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. SMS Site Backup successfully ran command line "%1", which completed with exit status %2.%12 SMS Site Backup was unable to run command line "%1" (error #%2).%12 Possible cause: "%1" does not exist at the specified location or is not in the system path. Solution: Install "%1" at the specified location, or add its directory to the system path. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application.
SMS 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 Possible causes: the backup control file was truncated or contains a syntax error. Solution: Verify completeness of the backup control file and fix any errors. SMS 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 Possible cause: The backup control file contains a syntax error on line %1. Solution: Fix any errors in the backup control file. SMS 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 Possible cause: The backup control file contains an invalid section name on line %1. Solution: Verify that line %1 specifies a valid section name. Possible cause: The section starting at line %1 contains no valid definitions. Solution: If the section contains invalid definitions, correct any errors. If the section contains no definitions, remove the section or add at least one definition. Possible cause: The backup control file contains a syntax error on or before line %1. Solution: Fix any errors in the backup control file. SMS Site Backup stopped the %1 SMS client application on the local computer.%12 The %1 SMS client application on the local computer did not respond to SMS Site Backup's stop request.%12 Possible cause: %1 is not an SMS client application and so cannot respond to a "close" event. Solution: Stop this application manually or as a standard executable. Possible cause: %1 was not running. Solution: Remove the "clientapp %1" definition from the backup control file.
SMS Site Backup could not stop the %1 SMS client application on the local computer.%12 Possible cause: %1 does not exist on the local computer. Solution: Verify that there are no errors in the "clientapp %1" definition, or remove the definition from the backup control file. SMS Site Backup started the %1 SMS client application on the local computer.%12 SMS Site Backup could not start the %1 SMS client application on the local computer.%12 Possible causes: %1 is not in the system path or does not exist on the local computer. Solution: Verify that an SMS client application "%1" exists on the local system. Either add its directory to the system path, or specify its full path in the backup control file. SMS Site Backup was run, but the %1 token had no value. Site backup did not occur.%12 Possible cause: The current SMS site's "Backup SMS Site Server" Maintenance Task has no value set for its "Backup Destination" field. Solution: Set the "Backup Destination" field using the SMS Administrator Console. SMS Site Backup was run, but the backup destination directory ( %1 ) is invalid. Site backup did not occur.%12 Possible cause: The current SMS site's "Backup SMS Site Server" Site Maintenance Task has invalid value set for its "Backup destination" field or "Backup destination" exists inside SMS root folder or Backup was unable to create this directory. Solution: Set a valid location to the "Backup destination" field using the SMS Administrator Console Make sure "Backup destination" does not exist inside SMS root folder. Check the privileges for proper rights
SMS Site Backup found syntax errors on the following lines:%1 in backup control file. Site backup did not occur.%12 Possible cause: There are syntax errors or unsupported commands that need to be removed. Solution: Edit backup control file and remove syntax errors on the given lines. The following utility tools were not available to be run: %1 Their output is not provided so you might miss some configuration information.%12 Possible cause: %1 is/are missing from their predefined location. Solution: Please copy the unavailable tools to their designated folder.
Unable to verify the installation of the service : %1 This service will not be stopped or restarted.%12 Possible cause: if %1 is a service then it is not installed or cannot be reached. Solution: Check the name and location of the Service and make sure that service is installed and the machine is reachable. 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 Token Symbol (%1) already defined. First value (%2) will be used.%12 Possible cause: %1 is either a built-in symbol or already defined in Backup Control file. Solution: If it is a built-in symbol, it cannot be redefined, remove added definition from backup control file otherwise use only a single definition.
SMS Site Backup was unable to back up registry key %1 to %2.%12 Possible cause: SMS Site Backup was unable to connect to or set backup privileges for the source registry. Solution: If %1 is in a remote registry, verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer; otherwise, reboot. Possible cause: %1 specifies a registry key relative to a hive other than HKEY_LOCAL_MACHINE. Solution: Change %1 so it is relative to HKEY_LOCAL_MACHINE. Possible cause: %2 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %2 and/or its directory. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application.
SMS Site Backup was unable to back up %1 database %2 to %3.%12 Possible cause: %3 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %3 and its directory. 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. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. SMS Site Backup could not start the "%1" executable on the local computer.%12 Possible cause: "%1" is not found in the specified location. Solution: Verify that the executable "%1" exists on the local computer. Please specify its full path in the backup control file.
SMS Site Backup completed successfully with zero errors but still there could be some warnings.%12 SMS Site Backup tried to stop the %1 service on site system %2. This service is already stopped.%12 SMS Site Backup tried to stop the %1 executable. This executable is already stopped.%12 SMS Site Backup service was stopped manually. Backup operation is not completed.%12 %1 utility initiated by SMS Site Backup did not complete in timely fashion. Terminating this utility. You may need to get its generated information manually.%12
SMS Site Backup successfully initiated command file "%1".%12 SMS Site Backup was unable to initiate command file "%1" .%12 Possible cause: Unable to find command shell to execute this file. Solution: Install command shell (CMD.EXE) in the system directory. Possible cause: Command shell failed to execute this file. Solution: Verify that CMD.EXE or "%1" are not corrupted.
SMS Site Backup did not find command file "%1" at its predefined location. Command file "%1" not launched.%12 SMS Site Backup was unable to back up file system object %1 to %2.%12 Possible cause: %1 is not readable, or %2 is not writable. Solution: Adjust file attributes and/or permissions of %1 and/or %2. Possible cause: The destination directory %2 did not already exist, and SMS Site Backup was unable to create it. Solution: Verify that a regular file with the same name as %2 or one of its parent directories does not exist, or replace %2 with an existing directory. Possible cause: %1 or %2 are on remote computers that SMS Site Backup does not have sufficient access rights to administer. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. Possible cause: Source %1 being copied to %2 may cause a recursive operation Solution:Backupthat destination folderVSS services. Abortingthe SMS Site Verify failed to initialize the does not exist within the backup operation. Please verify that the VSS services are up and running.%12
SMS 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 SMS Site Backup failed while reading the VSS writers meta data. Aborting the backup operation.%12 SMS Site Backup failed while creating the snapshot using the VSS services. Aborting the backup operation.%12 SMS Site Backup failed while trying to copy the files to the destination. Backup operation is not completed. Possible Cause: The Volume Shadow Copy Service may not have sufficient disk space to create the shadow copy of the site backup snapshot information. Check the storage associations for the drives containing Configuration Manager data and ensure that they are configured to use a volume with free space equivalent to at least 50% of the size of the Configuration Manager data. The backup destination should not be on the source volume, and the storage association should refer to a different volume than the source volume.%12 SMS Site Backup could not connect to the registy on the SQL machine. Aborting the backup operation. Please verify if the account running the SMS Backup has previliges to connect to the registry of the sql machine.%12 SMS Site Backup could not find the registy entries on the SQL machine. SMS SQL Backup service might not be running on the SQL machine.%12 SMS Site Backup found that the SMS SQL Backup service on the SQL machine is currently backing up the SMS database. It cannot start the new backup until the previous backup task is completed.%12 SMS SQL Backup service on the SQL server %1 failed to backup the SMS database %2. The error reported by the service is %3. Backup operation is not completed.%12 SMS SQL Backup service on the SQL server %1 did not start the SMS database backup. SMS SQL Backup service might not be running on the SQL machine.%12 SMS SQL Backup service on the SQL server %1 successfully backed up the SMS database.%12 SMS 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 SMS Site Backup is starting to copy the files from the snapshot.%12
SMS Site Backup has successfully completed copying the files from the snapshot.%12 SQL Backup path is empty or invalid. For remote SQL 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 ConfigMgr maintenance task properties in the ConfigMgr Console.%12 SMS Policy Provider successfully created a policy and a policy assignment based on package %1 (%2), program %3 and advertisement %4 (%5).%12 SMS Policy Provider successfully updated the policy and the policy assignment that were created from package %1 (%2), program %3 and advertisement %4 (%5).%12 SMS Policy Provider successfully removed policy %1 and the related policy assignment.%12 SMS Policy Provider successfully created a settings policy and a settings policy assignment.%12 SMS Policy Provider successfully updated a settings policy and a settings policy assignment.%12 SMS Policy Provider successfully created a metering policy and a metering policy assignment.%12 SMS Policy Provider successfully updated a metering policy and a metering policy assignment.%12 SMS Policy Provider successfully created a policy and a policy assignment based on Distribution Point %1 (%2).%12 SMS Policy Provider successfully updated the policy and the policy assignment that were created from Distribution Point %1 (%2).%12 SMS Policy Provider successfully created a policy and a policy assignment based on package %1.%12 SMS Policy Provider successfully updated the policy and the policy assignment that were created from package %1.%12 The site server signing certificate with hashcode '%1' is missing in the Certificate Store.%12 The site server signing certificate will expire in %1 day(s). Please ensure that this certificate is renewed for the proper operation of the SMS Site.%12 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
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 SMS Policy Provider has failed to sign one or more policy assignments. It will retry this operation automatically.%12 SMS Policy Provider successfully signed all policy assignments with the new Site Server Signing Certificate.%12 The hashing algorithm has changed. The Policy at this Site will be re-signed by the Site Server.%12 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 advertisement (ID: %3)will not run on clients until the platform requirements are corrected.%12 SMS Active Directory System Discovery Agent failed to read the necessary registry information.%12 Possible cause: The registry information is not available yet. Solution: SMS Active Directory System Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval.
SMS Active Directory System Discovery Agent failed to read the location of the outbox.%12 Possible cause: The information necessary to complete the initialization is not available now. Solution: SMS Active Directory System Discovery Agent is waiting for the information to become available and will retry at its next interval. SMS 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
SMS Active Directory System Discovery Agent reported errors for %1 objects. DDR's were generated for %2 objects that had errors while reading non-critical properties. DDR's were not generated for %3 objects that had errors while reading critical properties.%12 Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information. SMS Active Directory System Discovery Agent failed to bind to container %1. Error: %2.%12 Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried. SMS Active Directory User Discovery Agent failed to read the necessary registry information.%12 Possible cause: The registry information is not available yet. Solution: SMS Active Directory User Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval.
SMS Active Directory User Discovery Agent failed to read the location of the outbox.%12 Possible cause: The information necessary to complete the initialization is not available now. Solution: SMS Active Directory User Discovery Agent is waiting for the information to become available and will retry at its next interval. SMS 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
SMS Active Directory User Discovery Agent reported warnings for %1 objects. DDR's were generated for %2 objects that had warnings while reading non-critical properties. DDR's were not generated for %3 objects that had warnings while reading critical properties.%12 Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information. SMS Active Directory User Discovery Agent failed to bind to container %1. Error: %2.%12 Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried. SMS Active Directory Security Group Discovery Agent failed to read the necessary registry information.%12 Possible cause: The registry information is not available yet. Solution: SMS Active Directory Security Group Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval.
SMS Active Directory Security Group Discovery Agent failed to read the location of the outbox.%12 Possible cause: The information necessary to complete the initialization is not available now. Solution: SMS Active Directory Security Group Discovery Agent is waiting for the information to become available and will retry at its next interval. SMS 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). You may ignore this difference if there is any because no DDR was generated for the well-known security groups.%12
SMS Active Directory Security Group Discovery Agent reported warnings for %1 object(s). DDR's were generated for %2 object(s) that had warning(s) while reading non-critical properties. DDR's were not generated for %3 object(s) that had warnings while reading critical properties.%12 Possible cause: OU name or Security Group name may contain at least a Unicode character which has conversion problem between Unicode and your system ANSI locale(e.g. Korean characters in English System Locale). The SMS Service might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information.
SMS Active Directory Security Group Discovery Agent failed to bind to container %1. Error: %2.%12 Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried. MP File Dispatch Manager running on the management point "%1" cannot connect to site server "%2".%12 Possible cause: The site server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site server is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing MP File Dispatch Manager from properly accessing the site server. Solution: Investigate and correct any problems with your network. Possible cause: The account used to connect the MP to the site server may be locked out or may not have needed permissions. Solution: Check that the account is not locked out and that it has needed permissions. Refer to SMS security documentation for more information.
MP File Dispatch Manager cannot copy files from "%1" to "%2".%12 Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: MP File Dispatch Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing MP File Dispatch Manager from properly accessing the site system. Solution: Investigate and correct any problems with your network.
MP common layer cannot read the registry configuration when processing %1.%12 Possible cause: The corruption of the registry or an installation problem. Solution: Check the registry entries for MP or reinstall MP.
MP has experienced out of memory condition when processing %1.%12 Possible cause: Temporary spike in processing requests. Solution: If the condition persists check the logs to identify the cause and if necessary install NLB.
MP has incurred an unexpected error when processing %1.%12 Possible cause: Unforeseen system error. Solution: Check the logs to pinpoint the source of the problem and the reason for the condition. If unsuccessful raise the issue to Microsoft support.
MP has discarded a report when processing %1.%12 Possible cause: Corruption or invalid user definition. Solution: Check the logs to identify the cause. If the problem is persistent raise the issue with Microsoft support
MP could not complete a task when processing %1.%12 Check the logs for clues. Possible cause: Out of disk space. Solution: Increase the disk space, remove unprocessable files.
MP cannot load the hardware inventory class mapping table when processing %1.%12 Possible cause: MP cannot communicate with the SQL data base. Solution: Check the network connection between MP and the machine hosting the SQL data base (likely the PSS). Possible cause: The SQL data base not initialized properly or corrupted. Solution: Check the data for consistency. Recreate the hardware definition tables if necessary.
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 SMS are added to the collected classes.%12 Possible cause: Inconsistent way the new definitions have been introduced. Solution: Check that the mapping tables contain the information consistent with the hardware definition tables and that the definitions have been propagated properly. Possible cause: Corruption of the data base. Solution: Check the consistency of the data base.
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 Possible cause: Temporary spike in processing requests. Solution: If the condition persists, check the logs to identify the cause and if necessary install NLB.
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 Possible cause: This might indicate that the report has become obsolete due to a new HW inventory policy or that a customer's private definitions haven't been properly propagated to the sms_def.mof at the PSS. Solution: See if the missing classes or properties are genuinely missing in the current sms_def.mof and find out why the client put them in the xml report.
MP retry component gave up on a report when processing %1 and moved it to the bad report directory. %12 Possible cause: The file was too old to start with due to propagation problems. Solution: Ignore. Possible cause: MP's cache of class definitions could not be reloaded for a long time. Solution: Fix the network connection or SQL data base replication problem for the affected MP.
SMS management point encountered an error when connecting to the database %3 on SQL Server %2. The OLEDB error code was %4. %12 Possible cause: The computer running SQL Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the computer running SQL Server site system is turned on, connected to the network, and functioning properly. Possible cause: Management point does not have sufficient access rights to the SQL server site system. Solution: Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database. Possible cause: Network problems are preventing the management point from properly accessing the SQL Server. Solution: Investigate and correct any problems with your network. Possible cause: The management point having problems is at a secondary site, and SQL access account being used was recently reset by the parent site. Solution: This can automatically repair itself after one hour , as long as the account in use is not locked out. Check that the account in use is not locked out. Instead of waiting an hour, you The SMS Management Point was repaired.%12
MP failed to register with the local WINS server.%12 Possible cause: WINS server is not running. Solution: Make sure that the WINS server on the local network is up and running. Possible cause: MP's IP configuration has an invalid address of the WINS server. Solution: Supply a valid WINS IP address.
MP failed to unregister from the local WINS server.%12 Possible cause: WINS server is not running. Solution: Make sure that the WINS server on the local network is up and running. Manually delete that MP's entry from the WINS server Possible cause: The MP's entry at the WINS server is missing. Solution: Ignore the issue.
MP could not write out CCM setting to WMI.%12 Possible cause: MP didn't get installed properly. Solution: Ensure MP setup succeeded; if not, reinstall MP
MP could not update its settings to the new values.%12 Possible cause: MP may be overloaded. Solution: Reapply the setting at a later time.
Some or all of the MP Component Managers could not be started.%12 Possible cause:MP didn't get installed properly. Solution: Ensure MP setup succeeded; if not, reinstall MP Possible cause: MP may be overloaded. Solution: Manually start the SMS Agent Host service on the MP.
Some or all of the MP Component Managers could not be stopped.%12 Possible cause:MP didn't get installed properly. Solution: Ensure MP setup succeeded; if not, reinstall MP Possible cause: MP may be overloaded. Solution: Manually start the SMS Agent Host service on the MP.
MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is %1, %2.%12 Possible cause: Management point encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database. Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868. 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
MP Control Manager detected NLB MP is not responding to HTTP requests. The http status code and text is %1, %2.%12 Possible cause: MP encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the MP 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. Review Q829868. 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. MP Control Manager detected MP is not responding to HTTP requests. The http error is %1.%12 Possible cause: MP service is not started or not responding. Solution: Manually restart the SMS Agent Host service on the MP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891.
MP Control Manager detected NLB MP is not responding to HTTP requests. The http error is %1.%12 Possible cause: MP service is not started or not responding on all MP physical machines. Solution: Manually restart the SMS Agent Host service on the MP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891. MP has rejected a message from client %1 because it was signed with a public key that does not match the key published in the database.%12 Possible causes: The client is incorrectly identifying itself, or the client's signing certificate was re-created, resulting in a new public key.
The SMS Service Host (CCMEXEC) was unable to update certificate information in the Active Directory.%12 The SMS Service Host (CCMEXEC) successfuly updated certificate information in the Active Directory. %12 MP has rejected a message from client %2 because it was signed with a public key that does not match the key published in the database.%12 Possible causes: The client is incorrectly identifying itself, or the client's signing certificate was re-created, resulting in a new public key.
MP has rejected policy request from %2 because this SMSID is marked as blocked.%12 MP has rejected registration request due to failure in client certificate (Subject Name: %2) chain validation. If this is a valid client SMS Administrator needs to place the Root Certification Authority and Intermediate Certificate Authorities in the MPs Certificate store.%12 MP has rejected the request because %2 certificate has expired.%12 MP has rejected a policy request from %2 because it was not approved.%12
MP Control Manager detected DMP is not responding to HTTP requests. The http status code and text is %1, %2.%12 Possible cause: DMP encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Device Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Device Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the DMP 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. Review Q829868. 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. MP Control Manager detected DMP is not responding to HTTP requests. The http error is %1.%12 Possible cause: DMP service is not started or not responding on all DMP physical machines. Solution: Manually restart the SMS Agent Host service on the DMP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891.
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 Possible cause: MP encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the MP 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. Review Q829868. 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 whichdetected that this node of the NLB MP is MP Control Manager SMS is configured to use. not responding to HTTP requests. The http error is %1.%12 Possible cause: MP service is not started or not responding on all MP physical machines. Solution: Manually restart the SMS Agent Host service on the MP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891.
MP Control Manager detected that this node of the NLB MP is online. Node status code is %1 (%2).%12
MP Control Manager detected that this node of the NLB MP is degraded. Node status code is %1 (%2).%12 Possible cause: The node will be taken offline for maintenance or retired. Solution: Confirm with the system administrator responsible for the cluster. MP Control Manager detected that this node of the NLB MP is offline. Node status code is %1 (%2).%12 Possible cause: The node has been suspended or stopped. Solution: Confirm with the system administrator responsible for the cluster. Possible cause: The node is in the process of converging. Solution: This should resolve itself when the node has completed converging.
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 Desired Configuration Management in ConfigMgr to fail.%12 Possible cause: The database is a site database, not a replica, and ConfigMgr setup failed to enable the CLR. Solution: Open the SQL SQL Server Surface Area Configuration tool and select Surface Area Configuration for Feature. Select the Enable CLR Integration checkbox. Possible cause: The Management Point is configured to communicate with a replica database on a SQL Server that does not have CLR enabled. Solution: Open the SQL SQL Server Surface Area Configuration tool and select Surface Area Configuration for Feature. Select the Enable CLR Integration checkbox.
SMS Active Directory System Group Discovery Agent failed to read the necessary registry information.%12 Possible cause: The registry information is not available yet. Solution: SMS Active Directory System Group Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval.
SMS Active Directory System Group Discovery Agent failed to read the location of the outbox.%12 Possible cause: The information necessary to complete the initialization is not available now. Solution: SMS Active Directory System Group Discovery Agent is waiting for the information to become available and will retry at its next interval. SMS Active Directory System Group Discovery Agent read the AD Containers and found %1 valid AD Container entries in the site control file. Active Directory System Group 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 SMS Active Directory System Group Discovery Agent reported errors for %1 objects. DDR's were generated for %2 objects that had errors while reading non-critical properties. DDR's were not generated for %3 objects that had errors while reading critical properties.%12 Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information. SMS Active Directory System Group Discovery Agent failed to bind to container %1. Error: %2.%12 Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried.
SMS Software Metering Processor failed to read and configure the registry keys necessary for this component.%12 Possible cause: The registry information is not available yet. Solution: SMS Software Metering Processor is waiting for the information to become available and will retry obtaining the registry information at its next interval.
SMS Software Metering Processor failed to process the usage file "%1" for client "%2".%12 Possible cause: The file is corrupt. Solution: If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. SMS Software Metering Processor was unable to copy the definition for rule %1 to the master rule file for this site. %12 Solution: Review the previous status messages to determine the exact reason for the failure and fix any problems it is experiencing. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS 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 Possible cause: MSXML 3.0 has not been installed on the system. Solution: Download and install MSXML 3.0 from http://www.microsoft.com/xml. Possible cause: The site server drive is full. Solution: Make more space available on that drive. Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors.
SMS Software Metering Processor failed to replicate the definition for rule %1 to child sites. %12 Solution: Review the previous status messages to determine the exact reason for the failure and fix any problems it is experiencing. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.. SMS Software Metering Processor failed to process a rule replicated from the parent site. %12 Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. SMS Software Metering Processor failed to replicate summary data to the parent site.%12 Possible cause: The site server drive is full. Solution: Make more space available on that drive.. SMS Software Metering Processor could not process replicated summary data from a child site.%12 Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS 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 Possible cause: The client that reported the metering data does not exist in the database. Solution: Verify that the client is active and attached to the network. Possible cause: MSXML 3.0 has not been installed on the system. Solution: Download and install MSXML 3.0 from http://www.microsoft.com/xml. Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is enabled. SMS Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is disabled. SMS Software Metering Processor maintenance cycle deleted %1 files from directory %2. SMS Software Metering Processor experienced an error while processing and forwarding usage data to the parent site.%12 Possible cause: The destination drive is full. Solution: Make more space available on that drive. SMS 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 Solution: Review the previous status messages to determine the exact reason for the failure and fix any problems it is experiencing. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
SMS 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 Possible cause: The clock on the client computer is not accurate or has been recently changed. Solution: Reset the time on the client computer to the current time. Problem: The time on the SMS Site Server is incorrect. Solution: Reset the time on the SMS Site Server to the current time. SMS 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. SMS 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 Possible cause: A child site was recently attached and some of the discovery records have not yet been processed by the Discovery Data Manager. Solution: No action is required; the problem will resolve itself once all of the discovery records have been processed.
SMS 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 Possible cause: A computer has been deleted from the database on the current site but not from the child site. Solution: The summary file has been deleted, no further action is required. SMS Device Management Point has encountered an unexpected error when processing %1.%12 SMS Device Management Point has experienced out of memory condition when processing %1. %12 SMS Device Management Point encountered an error when connecting to its database. %12
SMS Device Management Point failed to authenticate the client %1. %12 Received an undefined message. Client ID is %1.%12 Received message from unknown or unauthorized client %1.%12 Received an invalid poll message. Client ID is %1.%12 Received an invalid download instructions request message. Client ID is %1.%12 Received an invalid package location request message. Client ID is %1.%12 Received an invalid status message. Client ID is %1.%12 Received an invalid hardware inventory message. Client ID is %1.%12 Received an invalid software inventory message. Client ID is %1.%12 Received an invalid file collection message. Client ID is %1.%12 Received an invalid registration message. Client ID is %1.%12 Error generating or sending discovery message. Client ID is %1.%12 Error generating or sending hardware inventory message. Client ID is %1.%12 Error generating or sending software inventory message. Client ID is %1.%12 Error generating or sending file collection message. Client ID is %1.%12 Error generating or sending status message. Client ID is %1.%12 Error generating or sending package location request message. Client ID is %1.%12 Error processing download instructions request message. Client ID is %1.%12 Error processing registration request message. Client ID is %1.%12 Error sending poll response. Client ID is %1.%12 Error sending download instructions. Client ID is %1.%12 Error sending package location response. Client ID is %1.%12 Error sending registration response. Client ID is %1.%12 SMS CI Assignment Manager successfully processed new CI Assignment %1.%12 SMS CI Assignment Manager successfully processed Update to CI Assignment %1.%12 SMS CI Assignment Manager successfully removed CI Assignment %1.%12
SMS CI Assignment has been directly deleted from SMS 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 SMS Database, to verify this deletion was due to Collection delete review the CI Assignment Manager and Collection Evaluator Logs.%12 SMS CI Assignment Manager failed to process CI Assignment changes. These changes will be retried on next processing cycle.%12 Solution: Review the previous status messages and logs for further clarification about this problem. SMS CI Assignment Manager failed to process CI Assignment %1. This CI Assignment will be retried %2 times on the next processing cycles.%12 Solution: Review the previous status messages and logs for further clarification about this problem. SMS 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 Solution: Review the previous status messages and logs for further clarification about this problem. SMS 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 Solution: Review the previous status messages and logs for further clarification about this problem. SMS 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 Solution: Review the previous status messages and logs for further clarification about this problem. SMS Object Replication Manager successfully processed SMS Object %1 of Type %2.%12 SMS Object Replication Manager successfully processed modification to SMS Object %1 of Type %2.%12 SMS Object Replication Manager successfully removed SMS Object %1 of Type %2.%12
SMS Object Replication Manager failed to process SMS Object %1 of Type %2. This Object has been retried %3 times and has reached the maximum retry limit.%12 Solution: Review the previous status messages and logs for further clarification about this problem. SMS Object Replication Manager failed to process SMS Object changes. These changes will be retried on next processing cycle.%12 Solution: Review the previous status messages and logs for further clarification about this problem. SMS Object Replication Manager failed to process SMS Object Replication File %1. This SMS Object Replication file has been retried %2 times and has reached the maximum retry limit.%12 Solution: Review the previous status messages and logs for further clarification about this problem. SMS Object Replication Manager failed to process SMS Object %1 of Type %2. This Object will be retried %3 times on the next processing cycles.%12 Solution: Review the previous status messages and logs for further clarification about this problem. SMS Object Replication Manager failed to process SMS Object Replication File %1 as SMS Object %2 of Type %3 referenced object of type %4 does not exists. This SMS Object Replication file has been retried %5 times and has reached the maximum retry limit.%12 Solution: Review the previous status messages and logs for further clarification about this problem. The SMS State System failed to read and configure the registry keys necessary for this component.%12 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. The SMS State System message file processing experienced a severe error and suspended file processing. Review the statesys.log file for further details.%12
The SMS State System summary task '%1' failed to execute. Review the statesys.log file for further details.%12 The SMS 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 The SMS 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 The SMS State Migration Point failed to read and configure the registry keys necessary for this component. 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. The SMS State Migration Point reached the minimum disk space threshold on all drives of computer %1. 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 The State Migration Point has reached the maximum client threshold on all drives on computer %1. 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 Client with GUID %1 requested capture request while the store from previous request exists.%12 The SMS 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 The SMS State Migration Point has removed the state store %2 on computer %1.%12 The SMS State Migration Point can not authenticate the client %1. Possible cause: Client machine is not part of the domain or access account presented by client is not found.%12
SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is %1, %2.%12 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.
SMP Control Manager detected SMP is not responding to HTTP requests. The http error is %1.%12 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.
SMS State Migration Point cannot access the state store %1 on computer %2.%12 SMS 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 The SMS PXE Service Point failed to read and configure the registry keys necessary for this component. Possible cause: The registry information is not available yet. Solution: Restart the WDS Service.%12
The SMS PXE Service Point failed to initialize the WDS PXE Provider. Check Previous Messages for more error information.%12 The SMS PXE Service Point failed to perform a clean shutdown. %12 The SMS PXE Service Point failed to initialize performance counters. %12 The SMS PXE Service Point failed to initialize worker threads. %12 The SMS PXE Service Point failed to process PXE request. %12 The SMS PXE Service Point is not actively processing PXE messages. Ignoring request from device. Device MAC Address:%1 SMBIOS GUID:%2. %12 The SMS PXE Service Point failed to Lookup device in the database. Device MAC Address:%1 SMBIOS GUID:%2. %12 The SMS PXE Service Point failed to get boot action from database for device. Device MAC Address:%1 SMBIOS GUID:%2. %12 The SMS PXE Service Point failed to find boot image for package %3 while handling device. Device MAC Address:%1 SMBIOS GUID:%2. %12
The SMS 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. %12 The SMS PXE Service Point instructed the device to boot to the bootimage %3 based on advertisement %4. Device MAC Address:%1 SMBIOS GUID:%2. %12 The SMS PXE Service Point encountered an unknown device. Device MAC Address:%1 SMBIOS GUID:%2. %12 The SMS PXE Service Point intructed device to boot normally since it already had executed advertisement %3. Device MAC Address:%1 SMBIOS GUID:%2. %12 The SMS PXE Service Point intructed device to boot normally since it has no PXE advertisement assigned. Device MAC Address:%1 SMBIOS GUID:%2. %12 The SMS PXE Service Point failed to Initialize the Database Connection. %12 The SMS PXE Certificate used for PXE clients is not valid. Please provide a valid certificate. %12 The SMS PXE Certificate used for PXE clients will expire soon. Please renew the certificate. %12
PXE control manager could not update its settings to the new values.%12 Possible cause: PXE may be overloaded. Solution: Reapply the setting at a later time.
PXE Control Manager detected PXE service point is not responding to PXE requests. The error is %1.%12 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.
PXE Control Manager detected PXE service point is not responding to PXE requests. The status code and text is %1, %2.%12 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.
The SMS 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. %12 The SMS 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. %12 SMS Component Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 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. The SMS Wake On LAN component has failed to read the site control file settings. 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. The SMS Wake On LAN component was enabled by the SMS Administrator.%12 The SMS Wake On LAN component was disabled by the SMS Administrator.%12 The SMS Wake On LAN component settings have been updated by the SMS Administrator.%12 The SMS Wake On LAN component is starting to send wakeup packets for the object id=%1 of type=%2.%12
The SMS Wake On LAN component component completed sending wakeup packets for the object id=%1 of type=%2.%12 The SMS Wake On LAN component component successfully sent wakeup packets to all clients targeted for the object id=%1 of type=%2.%12 The SMS Wake On LAN component component failed to send wakeup packets for some clients targeted by object id=%1 of type=%2. Possible cause:Client data was unavailable. Possible cause:Error occurred while reading client data. Possible cause:A network error occurred.%12 The SMS Wake On LAN component component failed to start sending wakeup packets for object id=%1 of type=%2. 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
The SMS Wake On LAN component failed access the database. Possible cause:Client data was unavailable. Possible cause: Solution:%12 The SMS Wake On LAN component successfully processed wakeup information for the object id=%1 of type=%2.%12 The SMS Wake On LAN failed to process wakeup information for the object id=%1 of type=%2. Possible cause:An error occured accessing the information. Solution:%12 The SMS Wake On LAN component has recovered from an unavailable state. The component is now online.%12 The SMS 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
SMS WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "%1".%12 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. SMS WSUS Configuration Manager failed to get update categories, classifications and locales from WSUS Server "%1".%12 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. SMS WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server "%1".%12 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.
SMS WSUS Configuration Manager will not be able to configure WSUS Server "%1" as the WSUS Server remoting API's of version 3.0 SP1 or greater are not installed on this site server.%12 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.
SMS WSUS Configuration Manager has configured WSUS Server "%1" to sync from the parent WSUS Server instead of sync from Microsoft Update.%12 SMS 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 SMS Admin UI to sync from either Microsoft Update or Do not Sync.%12
SMS WSUS Configuration Manager has detected that Software Updates Point is not configured yet. client boot-strapper packag publishing will be tried later.%12 SMS WSUS Configuration Manager failed to get package info from SDP file.%12 SMS WSUS Configuration Manager failed to publish client bootstrapper package "%1" with version "%2" to the Software Updates Point.%12 SMS WSUS Configuration Manager failed to unpublish client bootstrapper package "%1" with version "%2" from the Software Updates Point.%12 SMS WSUS Configuration Manager successfully published client boot-strapper package "%1" with version "%2" to the Software Updates Point.%12 SMS WSUS Configuration Manager successfully unpublished client boot-strapper package "%1" with version "%2" to the Software Updates Point.%12 SMS WSUS Configuration Manager failed to unpublish client bootstrapper package "%1" from the Software Updates Point.%12 SMS WSUS Configuration Manager successfully unpublished client boot-strapper package "%1" to the Software Updates Point.%12 SMS WSUS Sync Manager error. Message: %2. Source: %1. %12 SMS WSUS Synchronization started. %12 SMS WSUS Synchronization done. %12 SMS WSUS Synchronization failed. Message: %2. Source: %1. %12 SMS WSUS Synchronization in progress. Current phase: Synchronizing WSUS Server. %12 SMS WSUS Synchronization in progress. Current phase: Synchronizing SMS Database. %12 SMS WSUS Synchronization in progress. Current phase: Synchronizing Internet facing WSUS Server. %12
Content of WSUS Server %1 is out of sync with upstream server %2.%12 Possible cause: Server %1 synchronization is disabled. Solution: Enable upstream synchronization for server %1 or manually import data from upstream server %2. SMS Legacy Update Synchronization started. %12 SMS Legacy Update Synchronization done.%12 SMS Legacy Update Synchronization failed.%12 SMS Writer was unable to open control file "%1". Site backup will fail.%12 Possible cause: Wrong name specified or permissions to "%1" are incorrect. Solution: Verify that a readable backup control file named "%1" exists. SMS Writer stopped the "%1" executable on the local computer.%12 SMS Writer could not stop the "%1" executable on the local computer.%12 Possible cause: "%1" is an interactive Windows application and is waiting for user confirmation of the stop request. Solution: Manually stop this application. SMS Writer started the "%1" executable on the local computer.%12 SMS Writer could not start the "%1" executable on the local computer.%12 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. SMS Writer stopped the %1 service on site system %2.%12
SMS Writer could not stop the %1 service on site system %2.%12 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.
SMS Writer started the %1 service on site system %2.%12 SMS Writer could not start the %1 service on site system %2.%12 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.
SMS Writer stopped the %1 SMS client application on the local computer.%12 The %1 SMS client application on the local computer did not respond to SMS Writer's stop request.%12 Possible cause: %1 is not an SMS client application and so cannot respond to a "close" event. Solution: Stop this application manually or as a standard executable. Possible cause: %1 was not running. Solution: Remove the "clientapp %1" definition from the backup control file. SMS Writer could not stop the %1 SMS client application on the local computer.%12 Possible cause: %1 does not exist on the local computer. Solution: Verify that there are no errors in the "clientapp %1" definition, or remove the definition from the backup control file.
SMS Writer started the %1 SMS client application on the local computer.%12 SMS Writer could not start the %1 SMS client application on the local computer.%12 Possible causes: %1 is not in the system path or does not exist on the local computer. Solution: Verify that an SMS client application "%1" exists on the local system. Either add its directory to the system path, or specify its full path in the backup control file. SMS Writer found syntax errors on the following lines:%1 in backup control file. Site backup will fail.%12 Possible cause: There are syntax errors or unsupported commands that need to be removed. Solution: Edit backup control file and remove syntax errors on the given lines. The following utility tools were not available to be run: %1 Their output is not provided so you might miss some configuration information.%12 Possible cause: %1 is/are missing from their predefined location. Solution: Please copy the unavailable tools to their designated folder.
Unable to verify the installation of the service : %1 This service will not be stopped or restarted.%12 Possible cause: if %1 is a service then it is not installed or cannot be reached. Solution: Check the name and location of the Service and make sure that service is installed and the machine is reachable. 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 Token Symbol (%1) already defined. First value (%2) will be used.%12 Possible cause: %1 is either a built-in symbol or already defined in Backup Control file. Solution: If it is a built-in symbol, it cannot be redefined, remove added definition from backup control file otherwise use only a single definition.
SMS Writer was unable to locate the file system object %1.%12 Possible cause: %1 is not readable. Solution: Adjust file attributes and/or permissions of %1. Possible cause: %1 are on remote computers that SMS Site Backup does not have sufficient access rights to administer. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer.
SMS Writer was unable to export the registry key %1 to %2.%12 Possible cause: SMS Writer was unable to connect to or set backup privileges for the source registry. Solution: If %1 is in a remote registry, verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer; otherwise, reboot. Possible cause: %1 specifies a registry key relative to a hive other than HKEY_LOCAL_MACHINE. Solution: Change %1 so it is relative to HKEY_LOCAL_MACHINE.
SMS Writer was unable to write the machine info to the temporary backup destination %1.%12 Possible cause: %1 might be locked by another process. Solution: Delete %1 and restart SMS Writer; SMS Writer tried to stop the %1 service on site system %2. This service is already stopped.%12 SMS Writer tried to stop the %1 executable. This executable is already stopped.%12 SMS Writer service was stopped manually. All the backup operations will be affected and cannot be completed.%12 SMS Writer was unable to initialize the service.%12 Possible cause: VSS services may not be running. SMS Writer was unable to subscribe to the VSS services.%12 SMS Writer failed to build the metadata. SMS Site Backup tasks will fail.%12 The backup application has not included all the required components in the backup list.%12
SMS Writer is about to stop the SMS Services as part of the preparation for the SMS Site backup.%12 The snapshots of the volumes required for the SMS backup have been successfully created.%12 SMS Writer has started the SMS Services successfully. %12 SMS backup task has been aborted.%12 SMS backup task has completed successfully.%12 The SMS Fallback Status Point failed to read and configure the registry keys necessary for this component. 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. The SMS Fallback Status Point can not authenticate the client %1. Possible cause: Client machine is not part of the domain or access account presented by client is not found.%12 The SMS Fallback Status Point can not process any more messages. Possible cause: The disk is full.%12 The SMS Fallback Status Point could not load valid topics from registry. Possible causes: The registry can not be accessed or the registry is empty.%12 The SMS Fallback Status Point could not write messages to the staging folder. Possible causes: The registry can not be accessed or the registry is empty or the staging folder can not be accessed.%12 The SMS Fallback Status Point could not transfer messages from the staging folder to the outbox. Possible causes: The outbox is not accessible or is an invalid location.%12
SMS WSUS Configuration Manager failed to configure proxy settings on WSUS Server "%1".%12 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.You can receive failure because proxy is set but proxy name is not specified or proxy server port is invalid. Failures were reported on WSUS Server "%1" for WSUS components "%2".%12 Solution: Verify that the failed WSUS components are installed and running. Failures were reported on WSUS Server "%1" while trying to make WSUS database connection with SQL Exception error code %2.%12 Possible cause: SQL Database service is not running or cannot be accessed. Solution: Verify that the SQL Server and SQL Server Agent services are running and can be contacted. SMS WSUS Configuration Manager failed to monitor WSUS Server "%1".%12 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. SMS WSUS Configuration Manager will not be able to configure WSUS Server "%1" as the WSUS Server of version 3.0 SP1 or greater is not installed on this site system.%12 Solution: WSUS Site System requires WSUS Server of version 3.0 SP1 or greater to be installed on the site system. Verify that the correct version is installed The SMS Multicast Service Point failed to open multicast session. Possible cause: The WDS Multicast service is not running. Solution: Restart the WDS Service.%12
MCS Control Manager detected MCS is not responding to HTTP requests. The http status code and text is %1, %2.%12 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.
MCS Control Manager detected MCS is not responding to HTTP requests. The http error is %1.%12 Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MCS. For more information, refer to Microsoft Knowledge Base article 838891.
SCCM Multicast Service was unable to create a WDS multicast namaspace for package with UNC "%2" and packageID "%3". The error is %1.%12
SCCM Multicast Service was unable to initialize multicast service. The error is %1.%12
SCCM Multicast Service was unable to initialize multicast provider. The error is %1.%12
SCCM Multicast Service was unable to initialize ISAPI. The error is %1.%12
SCCM Multicast Service did not grant access to directory %2 for client with account %3. The error is %1.%12
SCCM 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 SCCM Multicast Service has rejected a request from %2 for site %3 because it was not approved.%12 SCCM Multicast Service has rejected request from %2 because this SMSID is marked as blocked.%12 SCCM Multicast Service has rejected the request because %2 certificate has expired.%12 The SCCM Multicast Service failed to initialize properly. The error encountered was %1. The out of band service point failed to read notification registry. Possible cause: The out of band service point is not setup successfully. Possible cause: The registry is not accessible. Solution: Wait some time to verify out of band service point is setup successfully. Verify the registry can be accessible.
The out of band service point failed to initialize the inbox of %1. %Possible cause: The inboxes folder is not accessible. Possible cause: Inbox manager is not running. Solution: Verify the inboxer folder is accessible. Verify inbox manager is running. The out of band service point is starting to send packets to completion port.
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. WinRM out of band service is not enabled. Solutions: Install WinRM out of band service manager and start it in out of band service point site role machine. The port specified for incoming Hello packets is in use by another application. The out of band service point failed to provision %1 with error %2: %3.%12 Possible cause: This condition can be caused by transient network connectivity errors. Possible cause: The account used to provision systems is not authorized to provision the management controller. Possible cause: the management controller is not in a state capable of being provisioned or updated. Solution: Verify network connectivity is functional between the out of band service point and the management controller. Verify that the account used to provision the management controller has sufficient permissions to update or provision the management controller. It may be necessary to reset the management controller to factory mode before it can be provisioned. The out of band service point failed to %1 %2 with error %3.%12 Possible cause: This condition can be caused by transient network connectivity errors. The credential used to connect management controller is invalid. The management controllers are in unavailable status. Solution: Verify network connectivity is functional between the out of band service point and the management controller. Verify that the credential used to connect the management controller is valid. It may be necessary to reset the management controller to factory mode and provision it again.
Provisioning failed because of an unsupported provisioning scenario. 12 Possible causes: WinHTTP Proxy is being used between the out of band service point and the AMT-based computer; the AMTbased computer is not on a wired connection; the FQDN of the AMT-based computer exceeds the maximum allowed length of 44 bytes. Solution: Remedy the unsupported scenario by doing one of the following: Reconfigure the proxy configuration or remove the proxy requirement; connect the AMT-based computer to a wired network; reduce the length of the FQDN for the AMT-based computer. Then retry to provision the AMT-based computer. Provisioning for %1 %2 failed due to an improper or missing provisioning certificate.%12 Possible cause: This condition is caused when no provisioning certificate is selected or an incorrect certificate is selected. Solution: Create or apply provision certificates from trusted certificates authorities(for example: Verisign, etc). Select the certificates in the Component Configuration settings for the out of band component. The provisioning certificate with the thumbprint %1 will expire in %2 day(s). Please ensure that this certificate is renewed.%12 The provisioning certificate with the thumbprint %1 will expire in %2 day(s). Please ensure that this certificate is renewed.%12 The out of band service point failed to provision %1 with error %2: %3.%12 Possible cause: This error can be caused by network configuration errors or because AMT has the wrong IP address for wired network access . Solution: Ensure that the DHCP scope for AMT is configured correctly with the options 006 (DNS Servers) and 015 (DNS Domain Name). Also check in AMT that the correct IP address is configured for wired network access.
Provisioning for %1 %2 failed due to all accounts failed to authentication with target device.%12 Possible cause: The remote admin account password of this AMT device is out of sync with SCCM database. This condition might be caused by this device is provisioned by some other provision server, the MEBx password of this device has been changed locally or hasn't been configured as a provision account in the Component Configuration settings for the out of band component. Solution: If this device is provisioned by other provision server, please refer to migration scenario. If the MEBx password is changed, please change it into someone already known by SCCM, or configure this MEBx password as a provision account. The provisioning certificate with the thumbprint %1 failed to pass revocation check with error %2.%12 Possible cause: This condition can be caused when the certificate is revoked by certificate authority. The computer does not have network connectivity to the certification authority. The proxy settings for the CRL checking are not set correctly. Solution: Verify that the certificate is unrevoked by certificate authority. Verify that the the system can connect to the certification authority (it could require internet connectivity for certain certification authorities). Verify the proxy configuration settings for the CRL checking are set correctly.
The provisioning certificate with the thumbprint %1 is invalid. Please ensure that CN name or OID is correct. The out of band service point failed to run %1 on %2 with error %3.%12 Possible cause: This error can occur when the AMT audit log is full and when %1 is set as critical event in the audit log settings. Solution: Verify the audit log settings on %2. Disable and then reenable the AMT audit log settings on %2 in the Configuration Manager console.
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. Solution: You can change the precedence order by typing the following commands in a command prompt: "netsh interface ipv6 delete prefix ::ffff:0:0/96" and then "netsh interface ipv6 add prefix prefix=::ffff:0:0/96 precedence=45 label=4". Asset Intelligence Update Service site role failed to install on "%1".%12 Solution: Verify that the .Net Framework 2.0 or greater is installed. SRS Reporting Point site role failed to configure SRS on "%1". SRS install is invalid on "%1". SMS SRS Reporting Point failed to monitor SRS Server on "%1". SMS SRS web service is not running on SRS Reporting point server "%1". SRS is not installed or properly configured on SRS Reporting point server "%1". SRS root folder "%1" is not present or not properly configured SRS Reporting point server "%2". Asset Intelligence KB Manager encountered errors processing file %1. This file will be retried %2 times in subsequent processing cycles. Asset Intelligence KB Manager encountered errors processing file %1. This file has been retried %2 times and has reached the maximum retry limit. 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.
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 Possible cause: This condition may occur when the SMS service account does not have permission to apply the requested certificate from the certification authority to the out of band management controller. Possible Cause: This condition may occur if the network connectivity is intermittent or failed during the attempt to update the out of band management controller with the requested certificate. Solution: Verify that the account used by SMS_EXECUTIVE service has permission to update the out of band management controller. For Intel AMT devices, the required permission (realm) is "PT Administer". Additionally, ensure that the network connection between the certification authority, the site server and the out of band management device is operational and required infrastructure components are accessilbe during the update.
Failure: The AMT Proxy Manager failed to apply certificate for "%1" from CA at "%2" with certificate trust error.%12 Possible cause: This condition may occur when the root certificate of the CA is not in the store "Trusted Root Certification Authorities" or the root certificate is invalid. Solution: Verify that the root certificate of the CA is in the store "Trusted Root Certification Authorities" and it is valid.
Failure: The AMT Proxy Manager failed to add a object into AD. FQDN: %1, ADDN: %2, UUID: %3, AMT Version: %4.%12 Possible cause: the SMS service account does not have permission to publish the object in the Active Directory. Failure: The AMT Proxy Manager failed to remove a object into AD. FQDN: %1, ADDN: %2.%12 Possible cause: the SMS service account does not have permission to remove the object in the Active Directory.
Failure: The AMT Proxy Manager failed to update a object in the AD. FQDN: %1, ADDN: %2.%12 Possible cause: the SMS service account does not have permission to remove the object in the Active Directory, or this object doesn't exist. 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.
The out of band service point failed to register the %1 in DNS. The machine's FQDN is %2.%12 Possible cause: The site server does not have sufficient permission to update DNS. Solution: Check that the account used by SMS_EXECUTIVE has permission to publish records for the site server's DNS server. The out of band service point failed to unregister the %1 in DNS.%12 Possible cause: The site server does not have sufficient permission to update DNS. Solution: Check that the account used by SMS_EXECUTIVE has permission to publish records for the site server's DNS server. 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. 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.
Symbolic Name
SRVMSG_SHV_ERROR_AD_SCHEMA_NOT_EXTENDED
SRVMSG_SHV_ERROR_AD_LOOKUP_ERROR
SRVMSG_SHV_ERROR_FILECACHESTORE_INITIALIZE_FAILURE
SRVMSG_SHV_ERROR_FILECACHESTORE_UPDATE_FAILED
SRVMSG_SHV_ERROR_FILECACHESTORE_PERSIST_FAILED
SRVMSG_SHV_ERROR_REGISTRY_SETTINGS_LOAD_FAILED
SRVMSG_SHV_ERROR_SERVICE_REGISTRY_SETTINGS_CHANGE_FAILED
SRVMSG_SHV_ERROR_SERVICE_INITIALIZATION_FAILED SRVMSG_SHV_ERROR_ADCACHECLIENT_INITIALIZATION_FAILED
SRVMSG_SITECOMP_INFO_COMP_FLAGGED_FOR_INSTALL
SRVMSG_SITECOMP_INFO_COMP_INSTALL_STARTED SRVMSG_SITECOMP_INFO_COMP_INSTALL_SUCCEEDED SRVMSG_SITECOMP_ERROR_COMP_INSTALL_FAILED
SRVMSG_SITECOMP_INFO_COMP_FLAGGED_FOR_REINSTALL
SRVMSG_SITECOMP_INFO_COMP_REINSTALL_STARTED SRVMSG_SITECOMP_INFO_COMP_REINSTALL_SUCCEEDED SRVMSG_SITECOMP_ERROR_COMP_REINSTALL_FAILED
SRVMSG_SITECOMP_INFO_COMP_FLAGGED_FOR_DEINSTALL
SRVMSG_SITECOMP_INFO_COMP_DEINSTALL_STARTED
SRVMSG_SITECOMP_INFO_COMP_DEINSTALL_SUCCEEDED SRVMSG_SITECOMP_ERROR_COMP_DEINSTALL_FAILED
SRVMSG_SITECOMP_ERROR_COMP_DEINSTALL_FAILED_AND_ABORTED
SRVMSG_SITECOMP_INFO_SERVER_INSTALL_STARTED SRVMSG_SITECOMP_INFO_SERVER_INSTALL_SUCCEEDED
SRVMSG_SITECOMP_ERROR_SERVER_INSTALL_FAILED
SRVMSG_SITECOMP_INFO_SERVER_REINSTALL_STARTED
SRVMSG_SITECOMP_INFO_SERVER_REINSTALL_SUCCEEDED
SRVMSG_SITECOMP_ERROR_SERVER_REINSTALL_FAILED
SRVMSG_SITECOMP_INFO_SERVER_DEINSTALL_STARTED
SRVMSG_SITECOMP_INFO_SERVER_DEINSTALL_SUCCEEDED
SRVMSG_SITECOMP_ERROR_SERVER_DEINSTALL_FAILED
SRVMSG_SITECOMP_ERROR_SERVER_DEINSTALL_FAILED_AND_ABORTED
SRVMSG_SITECOMP_ERROR_NAL_PROBLEM_CONNECTING_TO_SERVER
SRVMSG_SITECOMP_ERROR_SERVER_IS_DOWN
SRVMSG_SITECOMP_ERROR_SERVER_NOT_WINDOWS_NT_SERVER
SRVMSG_SITECOMP_ERROR_SERVER_INVALID_PLATFORM
SRVMSG_SITECOMP_INFO_SERVER_VALID_PLATFORM_X86
SRVMSG_SITECOMP_INFO_SERVER_VALID_PLATFORM_ALPHA
SRVMSG_SITECOMP_ERROR_SERVER_COULD_NOT_DETERMINE_NT_VERSION
SRVMSG_SITECOMP_ERROR_SERVER_INVALID_NT_SERVER_VERSION
SRVMSG_SITECOMP_ERROR_SERVER_INVALID_NT_SERVER_VERSION_AND_SP
SRVMSG_SITECOMP_ERROR_SERVER_INVALID_NT_WORKSTATION_VERSION
SRVMSG_SITECOMP_INFO_SERVER_VALID_NT_SERVER_VERSION
SRVMSG_SITECOMP_INFO_SERVER_VALID_NT_SERVER_VERSION_AND_SP
SRVMSG_SITECOMP_ERROR_SERVER_IN_USE_BY_OTHER_SITE
SRVMSG_SITECOMP_ERROR_SERVER_NO_NTFS_DRIVE
SRVMSG_SITECOMP_ERROR_SERVER_COULD_NOT_CREATE_INSTALL_DIR
SRVMSG_SITECOMP_INFO_SERVER_CREATED_INSTALL_DIR
SRVMSG_SITECOMP_ERROR_SERVER_COULD_NOT_CREATE_REMOTE_SERVICE_ACCOUNT
SRVMSG_SITECOMP_INFO_SERVER_CREATED_REMOTE_SERVICE_ACCOUNT
SRVMSG_SITECOMP_ERROR_SERVER_COULD_NOT_VERIFY_REMOTE_SERVICE_ACCOUNT
SRVMSG_SITECOMP_ERROR_SERVER_COULD_NOT_READ_CONNECT_ACCOUNT
SRVMSG_SITECOMP_ERROR_SERVER_COULD_NOT_WRITE_CONNECT_ACCOUNT
SRVMSG_SITECOMP_INFO_SERVER_IS_DOWN_FLAGGING_FOR_REINSTALL
SRVMSG_SITECOMP_ERROR_SERVER_COULD_NOT_DELETE_REMOTE_SERVICE_ACCOUNT
SRVMSG_SITECOMP_INFO_SERVER_DELETED_REMOTE_SERVICE_ACCOUNT
SRVMSG_SITECOMP_ERROR_SERVER_COULD_NOT_DELETE_INSTALL_DIR
SRVMSG_SITECOMP_INFO_SERVER_DELETED_INSTALL_DIR
SRVMSG_SITECOMP_INFO_TRANSACTION_SERVICE_ACCT_CHANGED
SRVMSG_SITECOMP_INFO_TRANSACTION_SHUTDOWN
SRVMSG_SITECOMP_INFO_TRANSACTION_SHUTDOWN_SERVER
SRVMSG_SITECOMP_INFO_TRANSACTION_SHUTDOWN_SERVER_NOT_NECESSARY
SRVMSG_SITECOMP_INFO_TRANSACTION_SHUTDOWN_SERVER_RETRY_FAILURE
SRVMSG_SITECOMP_WARNING_TRANSACTION_SHUTDOWN_SERVER_IGNORE_FAILURE
SRVMSG_SITECOMP_INFO_TRANSACTION_DEINSTALL
SRVMSG_SITECOMP_INFO_TRANSACTION_DEINSTALL_SERVER SRVMSG_SITECOMP_INFO_TRANSACTION_DEINSTALL_SERVER_NOT_NECESSARY
SRVMSG_SITECOMP_INFO_TRANSACTION_DEINSTALL_SERVER_RETRY_FAILURE
SRVMSG_SITECOMP_WARNING_TRANSACTION_DEINSTALL_SERVER_IGNORE_FAILURE
SRVMSG_SITECOMP_ERROR_COMP_DISK_SPACE_CHECK_FAILED
SRVMSG_SITECOMP_ERROR_COMP_INSUFFICIENT_DISK_SPACE
SRVMSG_SITECOMP_INFO_COMP_SUFFICIENT_DISK_SPACE
SRVMSG_SITECOMP_ERROR_COMP_COULD_NOT_COPY_FILE_TO_INSTALL_DIR
SRVMSG_SITECOMP_ERROR_COMP_COULD_NOT_COPY_FILE_TO_WINDOWS_DIR
SRVMSG_SITECOMP_INFO_COMP_COPIED_FILE SRVMSG_SITECOMP_INFO_COMP_DID_NOT_COPY_FILE_TO_WINDOWS_DIR
SRVMSG_SITECOMP_ERROR_COMP_COULD_NOT_DEINSTALL_EXISTING_BOOTSTRAP
SRVMSG_SITECOMP_ERROR_COMP_COULD_NOT_INSTALL_BOOTSTRAP
SRVMSG_SITECOMP_ERROR_COMP_COULD_NOT_START_BOOTSTRAP
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_OPERATION_FAILED
SRVMSG_SITECOMP_ERROR_COMP_COULD_NOT_INSTALL_SERVICE_ON_SITESERVER
SRVMSG_SITECOMP_ERROR_COMP_COULD_NOT_START_SERVICE_ON_SITESERVER
SRVMSG_SITECOMP_ERROR_COMP_COULD_NOT_INSTALL_SERVICE_ON_REMOTE_SERVER
SRVMSG_SITECOMP_ERROR_COMP_COULD_NOT_START_SERVICE_ON_REMOTE_SERVER
SRVMSG_SITECOMP_INFO_COMP_INSTALLED_SERVICE
SRVMSG_SITECOMP_INFO_COMP_STARTED_SERVICE SRVMSG_SITECOMP_ERROR_COMP_COULD_NOT_STOP_SERVICE
SRVMSG_SITECOMP_ERROR_COMP_COULD_NOT_DEINSTALL_SERVICE
SRVMSG_SITECOMP_INFO_COMP_STOPPED_SERVICE SRVMSG_SITECOMP_INFO_COMP_DEINSTALLED_SERVICE SRVMSG_SITECOMP_INFO_COMP_INSTALLED_THREAD
SRVMSG_SITECOMP_INFO_COMP_STARTED_THREAD SRVMSG_SITECOMP_INFO_COMP_STOPPED_THREAD SRVMSG_SITECOMP_INFO_COMP_DEINSTALLED_THREAD
SRVMSG_SITECOMP_INFO_COMP_COULD_NOT_START_THREAD
SRVMSG_SITECOMP_INFO_COMP_COULD_NOT_STOP_THREAD
SRVMSG_SMSEXEC_ERROR_AUTOSTART_THREAD_COMP_STOPPED
SRVMSG_SMSEXEC_INFO_THREAD_COMP_SCHEDULED_TO_START
SRVMSG_SMSEXEC_INFO_THREAD_COMP_NOT_SCHEDULED_TO_START
SRVMSG_SMSEXEC_WARNING_SCHEDULED_THREAD_COMP_STILL_RUNNING
SRVMSG_SMSEXEC_ERROR_LOADLIBRARY_FAILED
SRVMSG_SMSEXEC_ERROR_NO_THREADMAIN
SRVMSG_STATMGR_INFO_PERFORMANCE_STATISTICS
SRVMSG_STATMGR_INFO_PERFOBJECT_INITIALIZED
SRVMSG_STATMGR_WARNING_PERFOBJECT_FAILED_TO_INITIALIZE
SRVMSG_STATMGR_INFO_SUMMARIZER_REGISTERED
SRVMSG_STATMGR_INFO_SUMMARIZER_UNREGISTERED
SRVMSG_STATMGR_ERROR_SUMMARIZER_FAILED_TO_REGISTER
SRVMSG_STATMGR_WARNING_PERF_INSTANCE_LIMIT_REACHED
SRVMSG_STATMGR_WARNING_INVALID_CMDLINE
SRVMSG_STATMGR_WARNING_CMDLINE_FAILED_TO_EXECUTE
SRVMSG_STATMGR_WARNING_CMDLINE_STILL_EXECUTING
SRVMSG_STATMGR_WARNING_RECEIVED_MESSAGE_WITH_INVALID_TIME
SRVMSG_STATMGR_WARNING_RECEIVED_MESSAGE_FROM_FUTURE
SRVMSG_NETDISC_INFO_STARTING
SRVMSG_NETDISC_INFO_READING_PREVIOUS_DEVICES
SRVMSG_NETDISC_INFO_PROTOCOL_MODULES_STARTING SRVMSG_NETDISC_INFO_PROTOCOL_OPERATIONS_STARTING
SRVMSG_NETDISC_INFO_PROTOCOL_OPERATIONS_STOPPING SRVMSG_NETDISC_INFO_PROTOCOL_MODULES_STOPPING SRVMSG_NETDISC_INFO_WRITING_DEVICES_TO_CIMOM
SRVMSG_NETDISC_INFO_EXPORTING_DEVICES
SRVMSG_NETDISC_INFO_STOPPING SRVMSG_NETDISC_ERROR_DHCP_ACCESS_DENIED
SRVMSG_NETDISC_ERROR_DHCP_ACCESS_ERROR
SRVMSG_NETDISC_ERROR_WINSOCK_ERROR_FAILED
SRVMSG_NETDISC_ERROR_WINSOCK_MULTICAST
SRVMSG_NETDISC_WARNING_OUT_OF_TIME
SRVMSG_NETDISC_ERROR_CIMOM_CONNECTION_ERROR1
SRVMSG_NETDISC_ERROR_CIMOM_CONNECTION_ERROR2
SRVMSG_NETDISC_ERROR_CIMOM_READ_ERROR_CRITICAL
SRVMSG_NETDISC_WARNING_CIMOM_READ_ERROR
SRVMSG_NETDISC_ERROR_CIMOM_WRITE_ERROR_CRITICAL
SRVMSG_NETDISC_WARNING_CIMOM_WRITE_ERROR
SRVMSG_NETDISC_WARNING_CIMOM_QUERY_ERROR
SRVMSG_NETDISC_ERROR_SNMP_ERROR
SRVMSG_NETDISC_ERROR_EXPORT_DEVICE_FAILED
SRVMSG_NETDISC_ERROR_EXPORT_NETWORK_FAILED
SRVMSG_NETDISC_INFO_DOMAIN_ENUM_FAILED
SRVMSG_NTLGMNGR_INFO_SCRIPTS_CHANGED
SRVMSG_NTLGMNGR_INFO_UPDATESITE_START
SRVMSG_NTLGMNGR_INFO_UPDATESITE_DONE
SRVMSG_NTLGMNGR_INFO_UPDATEDOMAIN_START
SRVMSG_NTLGMNGR_INFO_UPDATEDOMAIN_SUCCESS SRVMSG_NTLGMNGR_INFO_UPDATEDOMAIN_FAIL
SRVMSG_NTLGMNGR_ERROR_INIT
SRVMSG_NTLGMNGR_ERROR_BAD_DOMAIN
SRVMSG_NTLGMNGR_INFO_DOMAIN_INSTALL
SRVMSG_NTLGMNGR_INFO_DOMAIN_DEINSTALL
SRVMSG_NTLGMNGR_INFO_SENIOR
SRVMSG_NTLGMNGR_INFO_NOTSENIOR
SRVMSG_NTLGMNGR_WARNING_NOVALIDDRIVE
SRVMSG_NTLGMNGR_WARNING_CREATESHARE
SRVMSG_NTLGMNGR_INFO_CREATESHARE
SRVMSG_NTLGMNGR_WARNING_STATUSCHANGEINACTIVE
SRVMSG_NTLGMNGR_WARNING_STATUSCHANGEDEAD
SRVMSG_NTLGMNGR_INFO_DELETESERVER
SRVMSG_NTLGMNGR_WARNING_INSTALLSERVER
SRVMSG_NTLGMNGR_WARNING_UPDATESCF
SRVMSG_NTLGMNGR_ERROR_READSCF
SRVMSG_NTLGMNGR_WARNING_CREATEDUPSHARE
SRVMSG_NTLGDISC_ERROR_INIT
SRVMSG_NTLGDISC_INFO_UPDATEPCF_START
SRVMSG_NTLGDISC_INFO_UPDATEPCF_SUCCESS
SRVMSG_NTLGDISC_INFO_UPDATEPCF_FAIL
SRVMSG_NTLGDISC_ERROR_DATAPCFMISSING
SRVMSG_NTLGDISC_ERROR_WRITEPCF
SRVMSG_NTLGDISC_INFO_WROTEPCF
SRVMSG_NTLGDISC_INFO_DOMAIN_LIST
SRVMSG_NTLGINST_ERROR_INIT
SRVMSG_NTLGINST_INFO_UPDATEPCF_START
SRVMSG_NTLGINST_INFO_UPDATEPCF_SUCCESS SRVMSG_NTLGINST_INFO_UPDATEPCF_FAIL
SRVMSG_NTLGINST_ERROR_DATAPCFMISSING
SRVMSG_NTLGINST_ERROR_WRITEPCF
SRVMSG_NTLGINST_INFO_WROTEPCF
SRVMSG_NTLGINST_INFO_DOMAIN_LIST
SRVMSG_NWLGMNGR_INFO_SCRIPTS_CHANGED SRVMSG_NWLGMNGR_INFO_SCRIPTS_CHANGEFAILED
SRVMSG_NWLGMNGR_INFO_UPDATESITE_START
SRVMSG_NWLGMNGR_INFO_UPDATESITE_DONE
SRVMSG_NWLGMNGR_INFO_UPDATESERVER_START
SRVMSG_NWLGMNGR_INFO_UPDATESERVER_SUCCESS
SRVMSG_NWLGMNGR_INFO_UPDATESERVER_FAIL
SRVMSG_NWLGMNGR_ERROR_INIT
SRVMSG_NWLGMNGR_ERROR_BAD_SERVER
SRVMSG_NWLGMNGR_INFO_SERVER_INSTALL
SRVMSG_NWLGMNGR_INFO_SERVER_DEINSTALL
SRVMSG_NWLGMNGR_WARNING_NOVALIDDRIVE
SRVMSG_NWLGMNGR_WARNING_CREATESHARE
SRVMSG_NWLGMNGR_INFO_CREATESHARE
SRVMSG_NWLGMNGR_WARNING_STATUSCHANGEINACTIVE
SRVMSG_NWLGMNGR_WARNING_STATUSCHANGEDEAD
SRVMSG_NWLGMNGR_INFO_DELETESERVER
SRVMSG_NWLGMNGR_WARNING_INSTALLSERVER
SRVMSG_NWLGMNGR_WARNING_UPDATESCF
SRVMSG_NWLGMNGR_ERROR_READSCF
SRVMSG_NWLGMNGR_ERROR_NONETWARE
SRVMSG_NWLGMNGR_INFO_SVR_SHOULD_EXIST
SRVMSG_NWLGMNGR_ERROR_LOGONPNT_IN_USE
SRVMSG_NWLGDISC_ERROR_INIT
SRVMSG_NWLGDISC_INFO_UPDATEPCF_START
SRVMSG_NWLGDISC_INFO_UPDATEPCF_SUCCESS SRVMSG_NWLGDISC_INFO_UPDATEPCF_FAIL
SRVMSG_NWLGDISC_ERROR_DATAPCFMISSING
SRVMSG_NWLGDISC_ERROR_WRITEPCF
SRVMSG_NWLGDISC_INFO_WROTEPCF
SRVMSG_NWLGDISC_INFO_SERVER_LIST
SRVMSG_NWLGDISC_WARNING_NONETWARE
SRVMSG_NWLGINST_ERROR_INIT
SRVMSG_NWLGINST_INFO_UPDATEPCF_START
SRVMSG_NWLGINST_INFO_UPDATEPCF_SUCCESS
SRVMSG_NWLGINST_INFO_UPDATEPCF_FAIL
SRVMSG_NWLGINST_ERROR_DATAPCFMISSING
SRVMSG_NWLGINST_ERROR_WRITEPCF
SRVMSG_NWLGINST_INFO_WROTEPCF
SRVMSG_NWLGINST_INFO_DOMAIN_LIST
SRVMSG_NDLGMNGR_INFO_SCRIPTS_CHANGED
SRVMSG_NDLGMNGR_INFO_SCRIPTS_CHANGEFAILED
SRVMSG_NDLGMNGR_INFO_UPDATESITE_START
SRVMSG_NDLGMNGR_INFO_UPDATESITE_DONE
SRVMSG_NDLGMNGR_INFO_UPDATECONTEXT_START
SRVMSG_NDLGMNGR_INFO_UPDATECONTEXT_SUCCESS
SRVMSG_NDLGMNGR_INFO_UPDATECONTEXT_FAIL
SRVMSG_NDLGMNGR_ERROR_INIT
SRVMSG_NDLGMNGR_ERROR_BAD_CONTEXT
SRVMSG_NDLGMNGR_INFO_CONTEXT_INSTALL
SRVMSG_NDLGMNGR_INFO_CONTEXT_DEINSTALL
SRVMSG_NDLGMNGR_WARNING_STATUSCHANGEINACTIVE
SRVMSG_NDLGMNGR_WARNING_STATUSCHANGEDEAD
SRVMSG_NDLGMNGR_INFO_DELETECONTEXT
SRVMSG_NDLGMNGR_WARNING_UPDATESCF
SRVMSG_NDLGMNGR_ERROR_READSCF
SRVMSG_NDLGMNGR_ERROR_NONETWARE
SRVMSG_NDLGMNGR_ERROR_LOGONPNT_IN_USE
SRVMSG_NDLGDISC_ERROR_INIT
SRVMSG_NDLGDISC_INFO_UPDATEPCF_START
SRVMSG_NDLGDISC_INFO_UPDATEPCF_SUCCESS SRVMSG_NDLGDISC_INFO_UPDATEPCF_FAIL
SRVMSG_NDLGDISC_ERROR_DATAPCFMISSING
SRVMSG_NDLGDISC_ERROR_WRITEPCF
SRVMSG_NDLGDISC_INFO_WROTEPCF
SRVMSG_NDLGDISC_INFO_CONTEXT_LIST
SRVMSG_NDLGDISC_WARNING_NONETWARE
SRVMSG_NDLGINST_ERROR_INIT
SRVMSG_NDLGINST_INFO_UPDATEPCF_START
SRVMSG_NDLGINST_INFO_UPDATEPCF_SUCCESS
SRVMSG_NDLGINST_INFO_UPDATEPCF_FAIL
SRVMSG_NDLGINST_ERROR_DATAPCFMISSING
SRVMSG_NDLGINST_ERROR_WRITEPCF
SRVMSG_NDLGINST_INFO_WROTEPCF
SRVMSG_NDLGINST_INFO_CONTEXT_LIST
SRVMSG_DISTMGR_INFO_START_PROCESSING_PKG SRVMSG_DISTMGR_INFO_PROCESSED_PKG SRVMSG_DISTMGR_ERROR_PROCESS_PKG
SRVMSG_DISTMGR_INFO_REFRESHED_DP SRVMSG_DISTMGR_INFO_RETRYING_PKG
SRVMSG_DISTMGR_ERROR_NO_PKG_SRC
SRVMSG_DISTMGR_ERROR_PKG_SRC_NOT_EXIST
SRVMSG_DISTMGR_ERROR_ACCESS_PKG_SRC
SRVMSG_DISTMGR_ERROR_REMOVE_OLD_COMPRESSED_PKG
SRVMSG_DISTMGR_ERROR_COMPRESS_PKG
SRVMSG_DISTMGR_INFO_COMPRESSED_PKG SRVMSG_DISTMGR_INFO_CREATED_PKG
SRVMSG_DISTMGR_ERROR_UPDATE_PKG
SRVMSG_DISTMGR_ERROR_REMOVE_PKG_DUE_TO_SHARE_CHANGE
SRVMSG_DISTMGR_INFO_REMOVED_PKG_DUE_TO_SHARE_CHANGE
SRVMSG_DISTMGR_INFO_DELETED_STORED_PKG SRVMSG_DISTMGR_ERROR_DELETE_STORED_PKG
SRVMSG_DISTMGR_INFO_REFRESH_PKG SRVMSG_DISTMGR_ERROR_NT_HIDDEN_SHARE
SRVMSG_DISTMGR_ERROR_BAD_COMPRESSED_PKG
SRVMSG_DISTMGR_ERROR_NOT_ENOUGH_DISK_SPACE_TO_DECOMPRESS
SRVMSG_DISTMGR_ERROR_DECOMPRESS_PKG
SRVMSG_DISTMGR_INFO_DECOMPRESSED_PKG
SRVMSG_DISTMGR_ERROR_INIT_NAL
SRVMSG_DISTMGR_ERROR_FIND_EXPORT
SRVMSG_DISTMGR_ERROR_CREATE_SUB_DIR
SRVMSG_DISTMGR_ERROR_SAVE_PKG_STATUS
SRVMSG_DISTMGR_ERROR_SAVE_PKG_INFO
SRVMSG_DISTMGR_ERROR_COPY_PKG
SRVMSG_DISTMGR_INFO_COPY_PKG SRVMSG_DISTMGR_INFO_DISTRIBUTED_PKG SRVMSG_DISTMGR_INFO_REMOVED_DISTRIBUTION_POINT SRVMSG_DISTMGR_ERROR_REMOVE_PKG_FILES
SRVMSG_DISTMGR_INFO_START_SENDING_PKG_TO_CHILD
SRVMSG_DISTMGR_INFO_CREATE_1X_INST_FOR_PKG SRVMSG_DISTMGR_INFO_SENT_PKG_TO_CHILD SRVMSG_DISTMGR_ERROR_CREATE_1X_INST_FOR_PKG
SRVMSG_DISTMGR_ERROR_SENT_PKG_TO_CHILD
SRVMSG_DISTMGR_INFO_CREATE_1X_INST_FOR_PKG_DEF
SRVMSG_DISTMGR_INFO_SENT_PKG_DEF_TO_CHILD
SRVMSG_DISTMGR_ERROR_CREATE_1X_INST_FOR_PKG_DEF
SRVMSG_DISTMGR_ERROR_SENT_PKG_DEF_TO_CHILD
SRVMSG_DISTMGR_INFO_START_PROCESSING_DP SRVMSG_DISTMGR_ERROR_NOT_ENOUGH_DISK_SPACE_TO_COPY
SRVMSG_DISTMGR_ERROR_CREATE_VIRTUAL_DIRECTORY
SRVMSG_DISTMGR_ERROR_REMOVE_VIRTUAL_DIRECTORY
SRVMSG_DISTMGR_ERROR_SMS_HIDDEN_SHARE
SRVMSG_DISTMGR_WARNING_RESTART_BITS_DP
SRVMSG_DISTMGR_ERROR_REFRESH_DP
SRVMSG_DISTMGR_ERROR_ENABLE_WEBDAV
SRVMSG_DISTMGR_INFO_SENT_PKG_FWD_TO_CHILD
SRVMSG_DISTMGR_WARNING_INVALID_PCK
SRVMSG_DISTMGR_ERROR_INVALID_PCK
SRVMSG_DISTMGR_ERROR_CONFIGURE_SMS_PORTS
SRVMSG_DISTMGR_ERROR_INVALID_BDP_STA
SRVMSG_DISTMGR_WARNING_NO_STANDARD_DP
SRVMSG_SMSDBMON_ERROR_XP_COPY
SRVMSG_SMSDBMON_WARNING_TASK_EXEC
SRVMSG_SMSDBMON_ERROR_CMD_EXEC
SRVMSG_SMSDBMON_INFO_DELETE_TASK
SRVMSG_SMSDBMON_INFO_INSTALL_TRIG
SRVMSG_SMSDBMON_INFO_DROP_TRIG
SRVMSG_SMSDBMON_ERROR_INSTALL_TRIG
SRVMSG_SMSDBMON_INFO_BEGIN_TASK
SRVMSG_SMSDBMON_INFO_DEL_COLL_FILES
SRVMSG_SMSDBMON_INFO_CREATE_INDEX
SRVMSG_SMSDBMON_INFO_DROP_INDEX
SRVMSG_SMSDBMON_INFO_ROLLING_KEY
SRVMSG_SMSDBMON_FILE_USAGE_SUMMARIZATION
SRVMSG_SMSDBMON_MONTHLY_USAGE_SUMMARIZATION
SRVMSG_SMSDBMON_CLEAR_UNDISC_CLIENT
SRVMSG_SMSDBMON_WARNING_BACKUP
SRVMSG_SMSDBMON_DELETE_INACTIVE_CLIENT_DISCOVERY_DATA
SRVMSG_SMSDBMON_DELETE_OBSOLETE_CLIENT_DISCOVERY_DATA
SRVMSG_SMSDBMON_CAL_USAGE_SUMMARIZATION
SRVMSG_SMSDBMON_TASK_MISSED_WINDOW
SRVMSG_SMSDBMON_RESET_AMT_PASSWORD_DATA SRVMSG_SMSDBMON_EVALUATE_PROV_CERT_DATA SRVMSG_COLLEVAL_ERROR_ENUM_COLL
SRVMSG_COLLEVAL_INFO_CREATE_ADC
SRVMSG_COLLEVAL_INFO_CREATE_UDC
SRVMSG_COLLEVAL_INFO_REPL_COLL
SRVMSG_COLLEVAL_WARNING_NO_COLL
SRVMSG_COLLEVAL_WARNING_RESET_COLL
SRVMSG_COLLEVAL_INFO_PARENT_CHANGE
SRVMSG_COLLEVAL_ERROR_DELETE_COLL
SRVMSG_COLLEVAL_INFO_NEW_SUBSITE
SRVMSG_COLLEVAL_WARNING_NO_DUE_DATE
SRVMSG_COLLEVAL_INFO_BEGIN_REFRESH
SRVMSG_COLLEVAL_ERROR_REFRESH_COLL
SRVMSG_COLLEVAL_ERROR_REPLICATE_COLL
SRVMSG_COLLEVAL_INFO_BEGIN_SETUP
SRVMSG_COLLEVAL_ERROR_SETUP_TABLE
SRVMSG_COLLEVAL_INFO_DONE_SETUP
SRVMSG_COLLEVAL_ERROR_SEND_FILE
SRVMSG_COLLEVAL_ERROR_MEMBER_SITE_LIST
SRVMSG_COLLEVAL_ERROR_ENUM_MEMBERS
SRVMSG_COLLEVAL_ERROR_INSERT_DIRECT_MEMBER
SRVMSG_COLLEVAL_ERROR_GET_COLL
SRVMSG_COLLEVAL_ERROR_INS_TFR_FILE_GEN
SRVMSG_COLLEVAL_ERROR_ENUM_RULES
SRVMSG_COLLEVAL_ERROR_INS_TFR_FILE_RULE
SRVMSG_COLLEVAL_ERROR_ENUM_SUBCOLLS
SRVMSG_COLLEVAL_ERROR_INS_TFR_FILE_SUBCOLL
SRVMSG_COLLEVAL_ERROR_READ_TFR_FILE_GEN
SRVMSG_COLLEVAL_WARNING_SUBCOLL_UNKNOWN
SRVMSG_COLLEVAL_ERROR_WRITE_MEMBER
SRVMSG_COLLEVAL_ERROR_WRITE_COLL
SRVMSG_COLLEVAL_ERROR_NO_SQL_CMD
SRVMSG_COLLEVAL_ERROR_GET_DISC_SRC
SRVMSG_COLLEVAL_ERROR_ENUM_DISC_ARCHS
SRVMSG_COLLEVAL_WARNING_LOCKED_COLL
SRVMSG_COLLEVAL_ERROR_NO_NAME
SRVMSG_COLLEVAL_INFO_TBL_CREATED
SRVMSG_COLLEVAL_INFO_REFRESH_SUCCEEDED SRVMSG_COLLEVAL_INFO_DIRECT_RULES_PROCESSED SRVMSG_COLLEVAL_INFO_RULES_PROCESSED
SRVMSG_COLLEVAL_INFO_DUPES_REMOVED
SRVMSG_COLLEVAL_INFO_NEW_RESULTS_READY SRVMSG_COLLEVAL_WARNING_CANT_EVALUATE_RULE
SRVMSG_COLLEVAL_WARNING_CANT_EVALUATE_COLLECTION
SRVMSG_COLLEVAL_INFO_NEW_RESULTS_READY2 SRVMSG_CEPHANDLER_INFO_NEW_CEP_PROCESSED SRVMSG_CEPHANDLER_INFO_CEPUPDATE_PROCESSED SRVMSG_CEPHANDLER_INFO_CEP_POLICY_REMOVED SRVMSG_CEPHANDLER_ERROR_PROCESSING_CEP_CHANGES
SRVMSG_CEPHANDLER_WARNING_PROCESSING_CEP
SRVMSG_CEPHANDLER_ERROR_PROCESSING_CEP
SRVMSG_CEPHANDLER_ERROR_CEP_FK
SRVMSG_CEPHANDLER_ERROR_PROCESS_CEP_REPLFILE
SRVMSG_MEPHANDLER_WARNING_PROCESSING_MEP
SRVMSG_MEPHANDLER_ERROR_PROCESSING_MEP_CHANGES
SRVMSG_DDM_ERROR_SYNC_DELETE
SRVMSG_DDM_ERROR_GET_DISC_SRC
SRVMSG_DDM_INFO_CLEAN_SITE SRVMSG_DDM_INFO_START_SEND_DB
SRVMSG_DDM_WARNING_SEND_DB_FAILURE
SRVMSG_DDM_ERROR_SEND_DB_FILE
SRVMSG_DDM_ERROR_SEND_DB_QUITTING
SRVMSG_DDM_INFO_SEND_DB_DONE SRVMSG_DDM_ERROR_SEND_FILE_TO_PARENT
SRVMSG_DDM_ERROR_ENUM_ARCHS
SRVMSG_DDM_ERROR_SET_DDR
SRVMSG_DDM_INFO_BEGIN_RULE_PROC
SRVMSG_DDM_ERROR_RULE_PROC
SRVMSG_DDM_ERROR_READ_SERIAL_NUM
SRVMSG_DDM_ERROR_READ_NEW_ITEM
SRVMSG_DDM_ERROR_PARSE_NEW_ITEM
SRVMSG_DDM_ERROR_INSERT_NEW_ITEM
SRVMSG_DDM_ERROR_WRITE_SERIAL_NUM
SRVMSG_DDM_ERROR_WRITE_ITEM_KEY
SRVMSG_DDM_ERROR_WRITE_ITEM
SRVMSG_DDM_ERROR_FORMAT_BUFFER
SRVMSG_DDM_ERROR_ENUM_PROPS
SRVMSG_DDM_ERROR_NO_NAME_PROPS
SRVMSG_DDM_ERROR_NO_LICENSES
SRVMSG_DDM_ERROR_READ_MASTER_NCF
SRVMSG_DDM_ERROR_READ_NCF
SRVMSG_DDM_ERROR_OPEN_NCF
SRVMSG_DDM_ERROR_READ_SCF
SRVMSG_DDM_WARNING_WRITE_NCF
SRVMSG_DDM_WARNING_COPY_NCF
SRVMSG_DDM_INFO_RULES_CHANGED
SRVMSG_DDM_ERROR_SEC_SITE_FILE_CREATE
SRVMSG_DDM_ERROR_NOTIFY_CONSUMERS
SRVMSG_DDM_ERROR_SEND_FILE_TO_SITE
SRVMSG_DDM_INFO_RULE_PROC_SUCCEEDED
SRVMSG_DDM_ERROR_BLANK_ARCH
SRVMSG_DDM_ERROR_WRITE_SOURCE
SRVMSG_DDM_INFO_UPD_STAT
SRVMSG_DDM_INFO_DELETING_ITEM
SRVMSG_DDM_INFO_ITEMS_OBSOLETED_HIDCHANGE
SRVMSG_DDM_INFO_ITEMS_OBSOLETED_SMSIDCHANGE
SRVMSG_DDM_ERROR_REGREQ_FAILED_EXISTINGITEM
SRVMSG_DDM_INFO_REGISTRATION_CONFLICT
SRVMSG_DATALDR_ERROR_CONVERT_DELTA
SRVMSG_DATALDR_ERROR_STOPPING_MIF_PROC
SRVMSG_DATALDR_WARNING_ORPHAN
SRVMSG_DATALDR_WARNING_BAD_MIF
SRVMSG_DATALDR_INFO_UPDATING_STATISTICS
SRVMSG_DATALDR_INFO_MIFS_DONE
SRVMSG_DATALDR_ERROR_INVUPD_ABANDON
SRVMSG_DATALDR_WARNING_INVUPD_RETRY
SRVMSG_DATALDR_INFO_INVUPD_BEGIN
SRVMSG_DATALDR_INFO_INIT_STAT
SRVMSG_DATALDR_INFO_INVUPD_ALREADY_COMPLETE
SRVMSG_DATALDR_INFO_INVUPD_USING_DIR
SRVMSG_DATALDR_ERROR_WRITE_MIF
SRVMSG_DATALDR_INFO_INVUPD_COMPLETE
SRVMSG_DATALDR_INFO_SENDING_RESYNC
SRVMSG_DATALDR_INFO_RESYNC_REQUEST
SRVMSG_DATALDR_INFO_WIDEN_COLUMN
SRVMSG_DATALDR_INFO_ADD_GROUP
SRVMSG_DATALDR_INFO_ADD_ARCH
SRVMSG_DATALDR_ERROR_FILE_SIZE
SRVMSG_DATALDR_WARNING_NO_RESYNC
SRVMSG_DATALDR_ERROR_MOFCOMP_FAILED
SRVMSG_DATALDR_INFO_SENDING_RESYNC_TO_MACHINE
SRVMSG_DATALDR_INFO_SENDING_RESYNC_REPORT_NO_KEY
SRVMSG_DATALDR_WARNING_SMSDEF_MOF_CONFLICT
SRVMSG_DATALDR_WARNING_SMSDEF_MOF_CONFLICT_SINGLETHREAD
SRVMSG_SITECTRL_INFO_PROCESSING_DELTA_SCF
SRVMSG_SITECTRL_INFO_PROCESSING_DELTA_SCF_SUCCESSFUL SRVMSG_SITECTRL_WARNING_PROCESSING_DELTA_SCF_NOT_DONE
SRVMSG_SITECTRL_WARNING_PROCESSING_DELTA_SCF_PARTIALLY_SUCCESSFUL
SRVMSG_SITECTRL_WARNING_PROCESSING_DELTA_SCF_ABORTED
SRVMSG_SITECTRL_WARNING_DELTA_CORRUPT
SRVMSG_SITECTRL_WARNING_DELTA_MISSING_ITEM
SRVMSG_SITECTRL_INFO_DELTA_RECORD_FROM_SDK_CLIENT
SRVMSG_SITECTRL_INFO_DELTA_RECORD_FROM_SERVER_COMPONENT
SRVMSG_SITECTRL_INFO_DELTA_FROM_SDK_CLIENT_IS_OLD
SRVMSG_SITECTRL_INFO_WROTE_TEMP_SCF
SRVMSG_SITECTRL_INFO_UPDATED_MASTER_SCF
SRVMSG_SITECTRL_INFO_UPDATED_BUT_NO_CHANGES
SRVMSG_SITECTRL_INFO_ITEM_ADD
SRVMSG_SITECTRL_INFO_ITEM_SET
SRVMSG_SITECTRL_INFO_ITEM_DELETE
SRVMSG_SITECTRL_ERROR_MASTER_SCF_IS_GONE
SRVMSG_SITECTRL_ERROR_NOT_RUNNING_ON_SITE_SERVER
SRVMSG_SITECTRL_ERROR_MISSING_ITEM
SRVMSG_SITECTRL_INFO_NUMBER_OF_HISTORY_FILES
SRVMSG_SITECTRL_INFO_WROTE_COPY_OF_MASTER_SCF
SRVMSG_SITECTRL_WARNING_WRITE_COPY_OF_MASTER_SCF
SRVMSG_SITECTRL_WARNING_FILEDEF_IS_NOT_DELTA
SRVMSG_SITECTRL_WARNING_FILEDEF_SITECODE_EMPTY
SRVMSG_SITECTRL_WARNING_FILEDEF_SITECODE_INVALID
SRVMSG_SITECTRL_WARNING_FILEDEF_DELTA_SITECODE_EMPTY
SRVMSG_SITECTRL_WARNING_FILEDEF_DELTA_COMPUTERNAME_EMPTY
SRVMSG_SITECTRL_WARNING_FILEDEF_DELTA_USERNAME_EMPTY
SRVMSG_SITECTRL_WARNING_FILEDEF_DELTA_COMPONENTNAME_EMPTY
SRVMSG_SITECTRL_WARNING_FILEDEF_SERVER_COMP_DIFFERENT_SITE
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SITETYPE_INVALID
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SITECODE_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SITECODE_INVALID
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SITENAME_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SITENAME_INVALID
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SITESERVERNAME_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SITESERVERNAME_INVALID
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SITESERVERDOMAIN_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SITESERVERDOMAIN_INVALID
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SITESERVERPLATFORM_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_INSTALLDIRECTORY_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_INSTALLDIRECTORY_INVALID
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SERVICEACCOUNTDOMAIN_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SERVICEACCOUNT_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SERVICEPLAINTEXTACCOUNT_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SERVICEACCOUNTPASSWORD_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SERVICEPUBLICKEY_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SERVICEPUBLICKEY_INVALID
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SERVICEACCOUNT_INVALID
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_ADDRESSPUBLICKEY_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SQLSERVERNAME_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SQLDATABASENAME_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SQLACCOUNT_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SQLACCOUNTPASSWORD_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SQLPUBLICKEY_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_SQLACCOUNT_INVALID
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_LICSQL_INVALID
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_LICSQL_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_LICSQLSERVERNAME_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_LICSQLDATABASENAME_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_LICSQLACCOUNT_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_LICSQLACCOUNTPASSWORD_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_LICSQLPUBLICKEY_EMPTY
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_LICSQLACCOUNT_INVALID
SRVMSG_SITECTRL_WARNING_SITEDEF_INVALID_NAL_CONNECT_ACCOUNTS
SRVMSG_SITECTRL_INFO_SUBMITTED_NON_HEARTBEAT_SCF_TO_HMAN
SRVMSG_SITECTRL_INFO_SUBMITTED_HEARTBEAT_SCF_TO_HMAN
SRVMSG_SITECTRL_INFO_SUBMITTED_HEARTBEAT_SCF_TO_HMAN2
SRVMSG_SITECTRL_WARNING_NO_MORE_HEARTBEATS
SRVMSG_SITECTRL_INFO_HEARTBEAT_SCHEDULE_CHANGED
SRVMSG_SITECTRL_WARNING_SITEDEF_DELTA_VERSION_OLD
SRVMSG_CIDM_ERROR_READ_INST_MAP
SRVMSG_CIDM_ERROR_READ_SCF
SRVMSG_CIDM_ERROR_CREATE_THREAD
SRVMSG_CIDM_ERROR_ESTABLISH_INBOX_SITESERVER
SRVMSG_CIDM_ERROR_ESTABLISH_INBOX_CAPSERVER
SRVMSG_CIDM_ERROR_DIRECTORY_NOT_FOUND
SRVMSG_CIDM_ERROR_FILE_NOT_FOUND
SRVMSG_CIDM_ERROR_INBOX_RULE_CREATE_COPY_FILES
SRVMSG_CIDM_WARNING_EMPTY_CAP_LIST
SRVMSG_CIDM_INFO_WRITING_CAP_LIST
SRVMSG_CIDM_ERROR_WRITING_CAP_LIST
SRVMSG_CIDM_INFO_WRITING_CLICFG_FILES
SRVMSG_CIDM_ERROR_WRITING_CLICFG_FILES
SRVMSG_CIDM_INFO_REMOVING_CLICOMP
SRVMSG_CIDM_INFO_CLICOMP_NOT_ACTIVE
SRVMSG_CIDM_INFO_CLICOMP_ACTIVE
SRVMSG_CIDM_ERROR_CREATING_CLICOMP_CFGFILE
SRVMSG_CIDM_ERROR_CREATING_CLICOMP_INBOX
SRVMSG_CIDM_ERROR_REFRESH_CLICOMP_OFFER_INFO
SRVMSG_CIDM_WARNING_OUT_OF_MEMORY
SRVMSG_CIDM_ERROR_UPGRADE_LEGACY_TOPAZ_CLIENTS
SRVMSG_CIDM_ERROR_UPGRADE_SP1_LEGACY_CLIENTS
SRVMSG_CCM_ERROR_READ_SCF
SRVMSG_CCM_ERROR_READ_REG_IDCFG
SRVMSG_CCM_WARNING_READ_REG_SITESERVER
SRVMSG_CCM_ERROR_GET_SERVER_ACCOUNT
SRVMSG_CCM_ERROR_READ_SCF_COMPITEM
SRVMSG_CCM_ERROR_CREATE_THREAD
SRVMSG_CCM_WARNING_ESTABLISH_INBOX_SITESERVER
SRVMSG_CCM_WARNING_ESTABLISH_INBOX_CAPSERVER
SRVMSG_CCM_WARNING_INBOX_RULE_DEF
SRVMSG_CCM_WARNING_CCRS_EXCEED_THRESHOLD
SRVMSG_CCM_WARNING_INSTALL_FAILING
SRVMSG_CCM_ERROR_CCR_TIME_EXPIRED
SRVMSG_CCM_ERROR_ACCOUNT_CLEARUP_OPERATON_FAILED
SRVMSG_CCM_WARNING_ACCOUNT_LIST_RESET
SRVMSG_CCM_WARNING_CANT_CONNECT_TO_CLIENT
SRVMSG_CCM_WARNING_CLIENT_IS_OFFLINE
SRVMSG_CCM_WARNING_CLIENT_WRONG_PLATFORM
SRVMSG_CCM_WARNING_CLIENT_IS_DC
SRVMSG_CCM_WARNING_NO_NETWORK_ACCESS_ACCOUNT
SRVMSG_CCM_WARNING_UNSUPPORTED_BY_ADVANCED_CLIENT
SRVMSG_NTPUSH_ERROR_INIT
SRVMSG_NTPUSH_ERROR_WAIT
SRVMSG_NTPUSH_ERROR_CREATE_CRR
SRVMSG_NTPUSH_INFO_CREATE_CCR
SRVMSG_NTPUSH_INFO_SUMMARY
SRVMSG_INVPROC_ERROR_PROCESS_MIF
SRVMSG_INVPROC_ERROR_PROCESS_RAW
SRVMSG_HMAN_ERROR_CIRCULAR_HIERARCHY
SRVMSG_HMAN_ERROR_NEW_LOCAL_SITE
SRVMSG_HMAN_ERROR_CHANGE_PARENT
SRVMSG_HMAN_ERROR_CONNECT_TO_SQL
SRVMSG_HMAN_ERROR_WRITE_TO_SITES_TABLE
SRVMSG_HMAN_ERROR_DUPLICATED_CHILD_SITE_CODE
SRVMSG_HMAN_INFO_PROCESSED_CT2
SRVMSG_HMAN_INFO_PROCESSED_DB
SRVMSG_HMAN_ERROR_REINSTALL_SITECOMP
SRVMSG_HMAN_INFO_REINSTALLED_SITECOMP
SRVMSG_HMAN_INFO_INSTALL_SEC_SITE
SRVMSG_HMAN_INFO_UPGRADE_SEC_SITE
SRVMSG_HMAN_INFO_DEINSTALL_SEC_SITE
SRVMSG_HMAN_WARNING_TASK_EXEC
SRVMSG_HMAN_ERROR_SQL7_IN_ADV_SEC
SRVMSG_HMAN_ERROR_DETECTED_NT_LOGON
SRVMSG_HMAN_ERROR_NT4DOM_IN_ADV_SEC
SRVMSG_HMAN_WARNING_ADD_MACHINE_ACCOUNT
SRVMSG_HMAN_WARNING_ADD_ADDRESS_ACCOUNT
SRVMSG_HMAN_ERROR_NEED_Q325804
SRVMSG_HMAN_ERROR_FAILED_DRW
SRVMSG_HMAN_INFO_SITE_SWITCHED_TO_NATIVE SRVMSG_HMAN_WARNING_DB_ROLE_REMOVAL
SRVMSG_HMAN_INFO_SITE_SWITCHED_TO_MIXED SRVMSG_HMAN_WARNING_SITE_PUBLIC_KEY_CHANGED
SRVMSG_SCHED_ERROR_NO_ADDRESS_DEFINED
SRVMSG_SCHED_WARNING_NO_ADDRESS_AVAILABLE
SRVMSG_SCHED_INFO_ROUTING_PKG
SRVMSG_SENDER_ERROR_LAN_CONNECTION
SRVMSG_SENDER_ERROR_RAS_CONNECTION
SRVMSG_SENDER_ERROR_MISSING_SERVER
SRVMSG_SENDER_ERROR_MISSING_SHARE
SRVMSG_SENDER_ERROR_NOT_NTFS
SRVMSG_SENDER_ERROR_CREATE_INI
SRVMSG_SENDER_ERROR_GET_CRYPTO_KEY
SRVMSG_SENDER_ERROR_QUERY_SVC
SRVMSG_SENDER_ERROR_STOP_SVC
SRVMSG_SENDER_ERROR_NT_VERSION
SRVMSG_SENDER_ERROR_ALREADY_SITE_SERVER
SRVMSG_SENDER_ERROR_COPY_BOOTSTRAP
SRVMSG_SENDER_ERROR_INSTALL_SVC
SRVMSG_SENDER_ERROR_START_SVC
SRVMSG_SENDER_INFO_INSTALL_SEC_SITE
SRVMSG_SENDER_INFO_UPGRADE_SEC_SITE
SRVMSG_SENDER_INFO_DEINSTALL_SEC_SITE
SRVMSG_SENDER_ERROR_WRITE_FILE
SRVMSG_SENDER_ERROR_CANNOT_START
SRVMSG_SENDER_ERROR_WINSOCK_SENDER_CONNECTION
SRVMSG_SENDER_ERROR_WINSOCK_RECEIVER_START
SRVMSG_SENDER_ERROR_WINSOCK_RECEIVER_CONNECTION
SRVMSG_SENDER_ERROR_BOOTSTRAP
SRVMSG_SENDER_INFO_SETUP_START_SEC_SITE SRVMSG_SENDER_ERROR_SETUP_START_SEC_SITE
SRVMSG_SENDER_INFO_SETUP_FINISH_SEC_SITE SRVMSG_SENDER_ERROR_SETUP_FINISH_SEC_SITE SRVMSG_SENDER_INFO_PKGDCOMP_SEC_SITE
SRVMSG_SENDER_INFO_BOOTSTRAP_FINISH_SEC_SITE SRVMSG_SENDER_WARNING_BACK_ADDRESS_SEC_SITE
SRVMSG_SENDER_ERROR_LAN_CONNECTION2
SRVMSG_SENDER_SENDING_PKG
SRVMSG_SENDER_WARNING_SENDING_PKG
SRVMSG_SENDER_SENT_PKG
SRVMSG_INBOXMGR_ERROR_REPLICATION
SRVMSG_INBOXMGR_ERROR_CREATE_INBOX_ON_SERVER
SRVMSG_INBOXMGR_ERROR_CREATE_INBOX_ON_CAP
SRVMSG_INBOXMGR_ERROR_CREATE_INBOX_ON_NAL
SRVMSG_INBOXMGR_ERROR_CONNECT_TO_SITE_SERVER
SRVMSG_INBOXMGR_ERROR_NO_PERM_SUPPORT
SRVMSG_INBOX_MONITOR_WARNING_CYCLE_TIME_EXCEEDED
SRVMSG_OUTBOX_MONITOR_WARNING_CYCLE_TIME_EXCEEDED
SRVMSG_SINVPROC_INFO_SINV_DONE SRVMSG_SINVPROC_WARNING_BAD_SINV
SRVMSG_SINVPROC_ERROR_STOPPING_SINV_PROC
SRVMSG_SINVPROC_INFO_SENDING_RESYNC
SRVMSG_SINVPROC_INFO_AGING_COLLECTED_FILE
SRVMSG_SINVPROC_INFO_UPDATING_STATISTICS
SRVMSG_SINVPROC_WARNING_FILECOL_RESOURCES
SRVMSG_SINVPROC_WARNING_ORPHAN_SINV
SRVMSG_SINVPROC_ERROR_FILE_SIZE
SRVMSG_SINVPROC_INFO_SENDING_RESYNC_REPORT_NO_KEY
SRVMSG_OFFER_SUMM_ERROR_QUEUE SRVMSG_OFFER_SUMM_ERROR_REPL_DATA SRVMSG_OFFER_SUMM_ERROR_REPL_OPEN SRVMSG_OFFER_SUMM_ERROR_DATASTORE SRVMSG_OFFER_SUMM_INFO_STATUS_MSG
SRVMSG_OFFER_SUMM_WARNING_OLD_DATA
SRVMSG_OFFER_SUMM_WARNING_REPL_FAIL SRVMSG_OFFER_SUMM_WARNING_INTERVAL SRVMSG_OFFER_SUMM_WARNING_NO_DATASTORE SRVMSG_OFFER_SUMM_WARNING_REPL_FILE SRVMSG_OFFER_SUMM_WARNING_FILE_CREATE SRVMSG_OFFER_SUMM_WARNING_DATASTORE_SEND SRVMSG_OFFER_SUMM_WARNING_INVALID_MESSAGE_ID_FROM_APM
SRVMSG_OFFER_SUMM_WARNING_MESSAGE_DOES_NOT_HAVE_OFFER_ID
SRVMSG_OFFER_SUMM_WARNING_INVALID_OFFER_ID_IN_MESSAGE
SRVMSG_OFFERMGR_INFO_OFFER_CREATED SRVMSG_OFFERMGR_INFO_OFFER_REMOVED SRVMSG_REPLMGR_INFO_JOB_CREATED
SRVMSG_REPLMGR_WARNING_THROWING_AWAY_FILES
SRVMSG_NTUSERGROUPDISC_ERROR_READING_REG
SRVMSG_NTUSERGROUPDISC_ERROR_READING_OUTBOX
SRVMSG_NTUSERGROUPDISC_INFO_STATUS SRVMSG_NTUSERGROUPDISC_FAILED_ENUMERATION
SRVMSG_NTUSERGROUPDISC_FAILED_TRUSTED_DOMAIN
SRVMSG_NTUSERGROUPDISC_FAILED_FIND_DC
SRVMSG_NTSERVERDISC_ERROR_READING_REG
SRVMSG_NTSERVERDISC_ERROR_READING_OUTBOX
SRVMSG_NTSERVERDISC_INFO_STATUS
SRVMSG_NTUSERDISC_ERROR_READING_REG
SRVMSG_NTUSERDISC_ERROR_READING_OUTBOX
SRVMSG_NTUSERDISC_INFO_STATUS SRVMSG_NTUSERDISC_FAILED_ENUMERATION
SRVMSG_NTUSERDISC_FAILED_TRUSTED_DOMAIN
SRVMSG_NTUSERDISC_FAILED_FIND_DC
SRVMSG_DESPOOLER_INFO_STORED_PKG SRVMSG_DESPOOLER_ERROR_BAD_COMPRESSED_PKG
SRVMSG_DESPOOLER_ERROR_COMPRESS_MERGE_FAILED
SRVMSG_DESPOOLER_ERROR_OPAL_CHILD_NOT_ALLOWED
SRVMSG_DESPOOLER_ERROR_NO_PUB_KEY_OK
SRVMSG_DESPOOLER_ERROR_NO_PUB_KEY
SRVMSG_DESPOOLER_ERROR_BAD_SIGNATURE
SRVMSG_DESPOOLER_INFO_RECEIVED_PKG SRVMSG_BASESUMM_INFO_REPLICATED SRVMSG_BASESUMM_INFO_REPL_CREATED SRVMSG_BASESUMM_INFO_REPL_INCOMING SRVMSG_BASESUMM_INFO_REPL_CORRUPT SRVMSG_BASESUMM_WARNING_BAD_SQL_INFO SRVMSG_BASESUMM_WARNING_SCF_SECTION_NOT_FOUND SRVMSG_BASESUMM_WARNING_SCF_OPEN_FAILED SRVMSG_BASESUMM_WARNING_SCF_READ_FAILED SRVMSG_BASESUMM_WARNING_SCF_EVENT_FAILED
SRVMSG_BASESUMM_WARNING_INBOX_EVENT_FAILED SRVMSG_BASESUMM_WARNING_QUEUE_FAILED SRVMSG_BASESUMM_WARNING_REPL_FAILED SRVMSG_BASESUMM_WARNING_OPEN_DATA_FAILED SRVMSG_BASESUMM_WARNING_READ_DATA_FAILED SRVMSG_BASESUMM_WARNING_WRITE_DATA_FAILED SRVMSG_BASESUMM_ERROR_INIT_FAILED SRVMSG_BASESUMM_ERROR_REG_FAILED SRVMSG_BASESUMM_ERROR_QUEUE_FAILED SRVMSG_BASESUMM_ERROR_HALT SRVMSG_BASESUMM_INFO_NO_TALLY_RESET SRVMSG_BASESUMM_INFO_TALLY_RESET SRVMSG_COMPSUMM_INFO_TALLY_CHANGED
SRVMSG_COMPSUMM_WARNING_BAD_THRESHOLD
SRVMSG_COMPSUMM_INFO_DISCOVERED_COMPONENT
SRVMSG_COMPSUMM_INFO_INFO_TALLY_CRITICAL
SRVMSG_COMPSUMM_INFO_WARN_TALLY_CRITICAL
SRVMSG_COMPSUMM_INFO_ERROR_TALLY_CRITICAL
SRVMSG_COMPSUMM_INFO_INFO_TALLY_WARN
SRVMSG_COMPSUMM_INFO_WARN_TALLY_WARN
SRVMSG_COMPSUMM_INFO_ERROR_TALLY_WARN
SRVMSG_COMPSUMM_INFO_STATUS_CRITICAL
SRVMSG_COMPSUMM_INFO_STATUS_WARN
SRVMSG_COMPSUMM_INFO_STATUS_OK
SRVMSG_COMPSUMM_WARNING_DEL_AGED_COMP
SRVMSG_COMPSUMM_WARNING_FOREIGN_MESSAGE
SRVMSG_COMPSUMM_INFO_RESET_ERROR_TALLY_FOR_SINCE_TIME
SRVMSG_COMPSUMM_INFO_RESET_ERROR_TALLY_FOR_SINCE_DAY_OF_WEEK
SRVMSG_COMPSUMM_INFO_RESET_ERROR_TALLY_FOR_SINCE_DAY_OF_MONTH
SRVMSG_COMPSUMM_INFO_RESET_ERROR_TALLY_FOR_SINCE_SITE_INSTALLATION
SRVMSG_COMPSUMM_INFO_RESET_ERROR_TALLY_FOR_SINCE_UNKNOWN_TOKEN
SRVMSG_COMPSUMM_INFO_RESET_WARNING_TALLY_FOR_SINCE_TIME
SRVMSG_COMPSUMM_INFO_RESET_WARNING_TALLY_FOR_SINCE_DAY_OF_WEEK
SRVMSG_COMPSUMM_INFO_RESET_WARNING_TALLY_FOR_SINCE_DAY_OF_MONTH
SRVMSG_COMPSUMM_INFO_RESET_WARNING_TALLY_FOR_SINCE_SITE_INSTALLATION
SRVMSG_COMPSUMM_INFO_RESET_WARNING_TALLY_FOR_SINCE_UNKNOWN_TOKEN
SRVMSG_COMPSUMM_INFO_RESET_INFO_TALLY_FOR_SINCE_TIME
SRVMSG_COMPSUMM_INFO_RESET_INFO_TALLY_FOR_SINCE_DAY_OF_WEEK
SRVMSG_COMPSUMM_INFO_RESET_INFO_TALLY_FOR_SINCE_DAY_OF_MONTH
SRVMSG_COMPSUMM_INFO_RESET_INFO_TALLY_FOR_SINCE_SITE_INSTALLATION
SRVMSG_COMPSUMM_INFO_RESET_INFO_TALLY_FOR_SINCE_UNKNOWN_TOKEN
SRVMSG_COMPSUMM_INFO_AVAILABILITY_STATE_ONLINE
SRVMSG_COMPSUMM_INFO_AVAILABILITY_STATE_FAILED
SRVMSG_COMPSUMM_INFO_AVAILABILITY_STATE_DEGRADED
SRVMSG_COMPSUMM_INFO_AVAILABILITY_STATE_OFFLINE
SRVMSG_COMPSUMM_INFO_AVAILABILITY_STATE_UNKNOWN
SRVMSG_SITESUMM_INFO_SO_NAL_PATH_UNAVAILABLE
SRVMSG_SITESUMM_INFO_SO_NAL_PATH_STILL_UNAVAILABLE
SRVMSG_SITESUMM_INFO_SO_NAL_PATH_NOW_AVAILABLE
SRVMSG_SITESUMM_INFO_SO_DB_UNAVAILABLE
SRVMSG_SITESUMM_INFO_SO_DB_STILL_UNAVAILABLE
SRVMSG_SITESUMM_INFO_SO_DB_NOW_AVAILABLE
SRVMSG_SITESUMM_INFO_SO_DBLOG_UNAVAILABLE
SRVMSG_SITESUMM_INFO_SO_DBLOG_STILL_UNAVAILABLE
SRVMSG_SITESUMM_INFO_SO_DBLOG_NOW_AVAILABLE
SRVMSG_SITESUMM_INFO_SO_NAL_PATH_STATUS_OK
SRVMSG_SITESUMM_INFO_SO_NAL_PATH_STATUS_WARNING
SRVMSG_SITESUMM_INFO_SO_NAL_PATH_STATUS_CRITICAL
SRVMSG_SITESUMM_INFO_SO_DB_STATUS_OK
SRVMSG_SITESUMM_INFO_SO_DB_STATUS_WARNING
SRVMSG_SITESUMM_INFO_SO_DB_STATUS_CRITICAL
SRVMSG_SITESUMM_INFO_SO_DBLOG_STATUS_OK
SRVMSG_SITESUMM_INFO_SO_DBLOG_STATUS_WARNING
SRVMSG_SITESUMM_INFO_SO_DBLOG_STATUS_CRITICAL
SRVMSG_SITESUMM_INFO_DELETED
SRVMSG_SITESUMM_INFO_SO_NAL_PATH_PDP_STATUS_CRITICAL
SRVMSG_SITESUMM_INFO_AVAILABILITY_STATE_ONLINE
SRVMSG_SITESUMM_INFO_AVAILABILITY_STATE_FAILED
SRVMSG_SITESUMM_INFO_AVAILABILITY_STATE_DEGRADED
SRVMSG_SITESUMM_INFO_AVAILABILITY_STATE_OFFLINE
SRVMSG_SITESUMM_INFO_AVAILABILITY_STATE_UNKNOWN
SRVMSG_NWSERVERDISC_ERROR_READING_REG
SRVMSG_NWSERVERDISC_ERROR_READING_OUTBOX
SRVMSG_NWSERVERDISC_INFO_STATUS
SRVMSG_SITECOMP_INFO_SERVER_COMPONENTS_DEINSTALL_STARTED SRVMSG_SITECOMP_INFO_SERVER_COMPONENTS_DEINSTALL_SUCCEEDED SRVMSG_SITECOMP_ERROR_SERVER_COMPONENTS_DEINSTALL_FAILED
SRVMSG_SITECOMP_ERROR_SERVER_COMPONENTS_DEINSTALL_FAILED_AND_ABORTED
SRVMSG_SITECOMP_INFO_PERF_COUNTERS_INSTALLED
SRVMSG_SITECOMP_ERROR_PERF_COUNTERS_NOT_INSTALLED
SRVMSG_SITECOMP_INFO_PERF_COUNTERS_DEINSTALLED
SRVMSG_SITECOMP_ERROR_PERF_COUNTERS_NOT_DEINSTALLED
SRVMSG_SITECOMP_INFO_COMP_COULD_NOT_ADD_MACHINEACCOUNT
SRVMSG_SITECOMP_CANNOT_FIND_SMS_AD_CONTAINER
SRVMSG_SITECOMP_SMS_AD_CONTAINER_CREATED
SRVMSG_SITECOMP_SMS_AD_OBJECT_CREATED SRVMSG_SITECOMP_CANNOT_UPDATE_AD_OBJECT
SRVMSG_SITECOMP_CANNOT_CREATE_AD_OBJECT
SRVMSG_SITECOMP_SMS_AD_OBJECT_DELETED SRVMSG_SITECOMP_CANNOT_DELETE_AD_OBJECT
SRVMSG_SITECOMP_CANNOT_UPDATE_MP_PERMISSIONS
SRVMSG_SITECOMP_SLP_CANNOT_CONNECT_TO_SQL
SRVMSG_SITECOMP_CANNOT_UPDATE_FQDN_AD_OBJECT
SRVMSG_SITECOMP_INFO_COM_ACCESS_REGISTRY_INSTALLED
SRVMSG_SITECOMP_ERROR_COM_ACCESS_REGISTRY_NOT_INSTALLED
SRVMSG_SITECOMP_INFO_COM_ACCESS_REGISTRY_DEINSTALLED
SRVMSG_SITECOMP_ERROR_COM_ACCESS_REGISTRY_NOT_DEINSTALLED
SRVMSG_SITECOMP_SHV_ERROR_STATUS SRVMSG_SITECOMP_WARNING_ADD_MACHINE_ACCOUNT
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_NO_IIS
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_MSI_ERROR
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_MISSING_FILES
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_RP_SETUP_ERROR
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_RP_OLD_INSTALL
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_NO_MSMQ
SRVMSG_SITECOMP_WARNING_COMP_BOOTSTRAP_REBOOT_REQUIRED
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_NO_BITS
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_NO_IIS_ANONYMOUS_ACT
SRVMSG_SITECOMP_WARNING_CANNOT_VALIDATE_SQL_SPN
SRVMSG_SITECOMP_ERROR_IIS_WEBSITE_STOPPED
SRVMSG_SITECOMP_ERROR_DTC_NOT_RUNNING
SRVMSG_SITECOMP_ERROR_TASK_SCHEDULER_NOT_RUNNING
SRVMSG_SITECOMP_ERROR_IIS_ACCOUNT_DISABLED
SRVMSG_SITECOMP_ERROR_SSL_IS_MISCONFIGURED
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_NO_IAS
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_LONGHORN
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_NO_WDS
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_NO_WSUS
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_WSUS_ERROR
SRVMSG_SITECOMP_ERROR_COMP_BOOTSTRAP_WEBDAV_ERROR
SRVMSG_BACKUP_ERROR_CONTROL_FILE_OPEN
SRVMSG_BACKUP_INFO_STOPPED_EXECUTABLE SRVMSG_BACKUP_ERROR_COULD_NOT_STOP_EXECUTABLE
SRVMSG_BACKUP_INFO_STARTED_EXECUTABLE SRVMSG_BACKUP_ERROR_COULD_NOT_START_EXECUTABLE
SRVMSG_BACKUP_INFO_STOPPED_SERVICE SRVMSG_BACKUP_ERROR_COULD_NOT_STOP_SERVICE
SRVMSG_BACKUP_INFO_STARTED_SERVICE
SRVMSG_BACKUP_ERROR_COULD_NOT_START_SERVICE
SRVMSG_BACKUP_INFO_FILESYSTEM_TASK_SUCCEEDED SRVMSG_BACKUP_WARNING_FILESYSTEM_TASK_FAILED
SRVMSG_BACKUP_INFO_REGISTRY_TASK_SUCCEEDED
SRVMSG_BACKUP_WARNING_REGISTRY_TASK_FAILED
SRVMSG_BACKUP_INFO_DBDUMP_TASK_SUCCEEDED
SRVMSG_BACKUP_WARNING_DBDUMP_TASK_FAILED
SRVMSG_BACKUP_INFO_CMD_LINE_TASK_SUCCEEDED SRVMSG_BACKUP_WARNING_CMD_LINE_TASK_FAILED
SRVMSG_BACKUP_ERROR_CONTROL_DATA_ENDS_UNEXPECTEDLY
SRVMSG_BACKUP_ERROR_CONTROL_DATA_IGNORING_LINE
SRVMSG_BACKUP_ERROR_CONTROL_DATA_IGNORING_SECTION
SRVMSG_BACKUP_INFO_STOPPED_SMS_CLIENT_APP SRVMSG_BACKUP_WARNING_SMS_CLIENT_APP_DID_NOT_RESPOND_TO_STOP
SRVMSG_BACKUP_ERROR_COULD_NOT_STOP_SMS_CLIENT_APP
SRVMSG_BACKUP_INFO_STARTED_SMS_CLIENT_APP SRVMSG_BACKUP_ERROR_COULD_NOT_START_SMS_CLIENT_APP
SRVMSG_BACKUP_ERROR_NO_BACKUP_DEST_DIR
SRVMSG_BACKUP_ERROR_INVALID_BACKUP_DEST_DIR
SRVMSG_BACKUP_ERROR_SYNTAX_ERRORS
SRVMSG_BACKUP_WARNING_UTILITY_UNAVAILAVAILBE
SRVMSG_BACKUP_WARNING_INSTALL_VERIFICATION
SRVMSG_BACKUP_WARNING_SLEEP_LIMIT
SRVMSG_BACKUP_WARNING_SYMBOL_REDEFINED
SRVMSG_BACKUP_ERROR_REGISTRY_TASK_FAILED
SRVMSG_BACKUP_ERROR_DBBACKUP_TASK_FAILED
SRVMSG_BACKUP_WARNING_COULD_NOT_START_EXECUTABLE
SRVMSG_BACKUP_INFO_COMPLETED_SUCCESSFULLY SRVMSG_BACKUP_INFO_ALREADY_STOPPED_SERVICE SRVMSG_BACKUP_INFO_ALREADY_STOPPED_EXECUTABLE SRVMSG_BACKUP_WARNING_MANUAL_STOP SRVMSG_BACKUP_WARNING_UTILITY_TERMINATION
SRVMSG_BACKUP_INFO_CMDFILE_SUCCEEDED SRVMSG_BACKUP_WARNING_CMDFILE_FAILED
SRVMSG_BACKUP_INFO_CMDFILE_NOTFOUND
SRVMSG_BACKUP_ERROR_FILESYSTEM_TASK_FAILED
SRVMSG_BACKUP_ERROR_VSS_INITIALIZATION_FAILED
SRVMSG_BACKUP_ERROR_SMSWRITER_NOTFOUND
SRVMSG_BACKUP_ERROR_GATHERWRITERMETADATA_FAILED SRVMSG_BACKUP_ERROR_CREATESNAPSHOT_FAILED SRVMSG_BACKUP_ERROR_BACKUPCOMPLETE_FAILED
SRVMSG_BACKUP_ERROR_CANNOT_READ_SQLREGISTRY
SRVMSG_BACKUP_ERROR_ENTRIES_MISSING_IN_SQLREGISTRY
SRVMSG_BACKUP_ERROR_SQLBACKUP_ALREADY_RUNNING
SRVMSG_BACKUP_ERROR_SQLBACKUP_FAILED
SRVMSG_BACKUP_ERROR_SQLBACKUP_DIDNOT_START
SRVMSG_BACKUP_INFO_SQLBACKUP_COMPLETED SRVMSG_BACKUP_INFO_STARTING_BACKUP
SRVMSG_BACKUP_INFO_STARTING_FILECOPY
SRVMSG_BACKUP_INFO_COMPLETED_FILECOPY SRVMSG_BACKUP_WARNING_SQL_BACKUP_PATH_EMPTY
SRVMSG_POLICYPROVIDER_INFO_SOFTWARE_POLICY_CREATED
SRVMSG_POLICYPROVIDER_INFO_SOFTWARE_POLICY_UPDATED
SRVMSG_POLICYPROVIDER_INFO_POLICY_REMOVED SRVMSG_POLICYPROVIDER_INFO_SETTINGS_POLICY_CREATED SRVMSG_POLICYPROVIDER_INFO_SETTINGS_POLICY_UPDATED SRVMSG_POLICYPROVIDER_INFO_METERING_POLICY_CREATED SRVMSG_POLICYPROVIDER_INFO_METERING_POLICY_UPDATED SRVMSG_POLICYPROVIDER_INFO_DP_POLICY_CREATED
SRVMSG_POLICYPROVIDER_INFO_DP_POLICY_UPDATED
SRVMSG_POLICYPROVIDER_INFO_DP_PKG_POLICY_CREATED SRVMSG_POLICYPROVIDER_INFO_DP_PKG_POLICY_UPDATED
SRVMSG_POLICYPROVIDER_INFO_SIGNING_CERT_NOT_FOUND SRVMSG_POLICYPROVIDER_INFO_SIGNING_CERT_WILL_EXPIRE
SRVMSG_POLICYPROVIDER_INFO_SIGNING_CERT_EXPIRED
SRVMSG_POLICYPROVIDER_INFO_SIGNING_CERT_CHANGED
SRVMSG_POLICYPROVIDER_INFO_SIGNING_FAILED
SRVMSG_POLICYPROVIDER_INFO_SIGNING_SUCCESS
SRVMSG_POLICYPROVIDER_INFO_HASHALG_CHANGED SRVMSG_POLICYPROVIDER_ERROR_DEPRECATED_PLATFORM
SRVMSG_ADSYSDISC_ERROR_READING_REG
SRVMSG_ADSYSDISC_ERROR_READING_OUTBOX
SRVMSG_ADSYSDISC_INFO_STATUS
SRVMSG_ADSYSDISC_WARNING_READING_OBJECTS
SRVMSG_ADSYSDISC_ERROR_BINDING_CONTAINER
SRVMSG_ADUSRDISC_ERROR_READING_REG
SRVMSG_ADUSRDISC_ERROR_READING_OUTBOX
SRVMSG_ADUSRDISC_INFO_STATUS
SRVMSG_ADUSRDISC_WARNING_READING_OBJECTS
SRVMSG_ADUSRDISC_ERROR_BINDING_CONTAINER
SRVMSG_ADSGDISC_ERROR_READING_REG
SRVMSG_ADSGDISC_ERROR_READING_OUTBOX
SRVMSG_ADSGDISC_INFO_STATUS
SRVMSG_ADSGDISC_WARNING_READING_OBJECTS
SRVMSG_ADSGDISC_ERROR_BINDING_CONTAINER
MPMSG_FDM_ERROR_CONNECT_TO_SITE_SERVER
MPMSG_FDM_ERROR_REPLICATION
MPMSG_CANNOT_READ_MP_CONFIGURATION
MPMSG_OUT_OF_MEMORY
MPMSG_UNEXPECTED_ERROR
MPMSG_DISCARDING_INVENTORY_REPORT
MPMSG_CANNOT_COMPLETE_PROCESSING
MPMSG_CANNOT_LOAD_HINV_MAP
MPMSG_NEED_TO_RELOAD_HINV_MAP
MPMSG_DISCARDING_MESSAGE
MPMSG_UNKNOWN_CLASSES
MPMSG_HINV_RETRY_LIMIT
MPMSG_CONNECT_DATABASE_FAILED
MPMSG_MP_REPAIRED
MPMSG_WINS_REGISTRATION_FAILED
MPMSG_WINS_UNREGISTRATION_FAILED
MPMSG_WRITE_TO_CCM_SETTINGS_FAILED
MPMSG_UPDATE_MP_SETTINGS_FAILED
MPMSG_START_ALL_MP_MANAGERS_FAILED
MPMSG_STOP_ALL_MP_MANAGERS_FAILED
MPMSG_HTTP_REQUEST_NONRESPONSIVE
MPMSG_HTTP_REQUEST_NLB_NONRESPONSIVE
MPMSG_HTTP_REQUEST_NONRESPONSIVE_ERROR
MPMSG_HTTP_REQUEST_NLB_NONRESPONSIVE_ERROR
MPMSG_CLIENT_PUBLICKEY_MISMATCH
MPMSG_CERTUPDATE_FAILURE_MP MPMSG_CERTUPDATE_SUCCESS_MP MPMSG_CLIENT_PUBLICKEY_MISMATCH_MP
MPMSG_CERT_REVOKED MPMSG_CERT_INVALID_CHAIN
MPMSG_CERT_EXPIRED MPMSG_CLIENT_NOT_APPROVED
MPMSG_HTTP_REQUEST_DMP_NONRESPONSIVE
MPMSG_HTTP_REQUEST_DMP_NONRESPONSIVE_ERROR
MPMSG_HTTP_REQUEST_NLB_NODE_NONRESPONSIVE
MPMSG_HTTP_REQUEST_NLB_NODE_NONRESPONSIVE_ERROR
MPMSG_NLB_NODE_AVAILABILITY_STATE_ONLINE
MPMSG_NLB_NODE_AVAILABILITY_STATE_DEGRADED
MPMSG_NLB_NODE_AVAILABILITY_STATE_OFFLINE
MPMSG_SQL_DB_CLR_DISABLED
SRVMSG_ADUPDATE_ERROR_READING_REG
SRVMSG_ADUPDATE_ERROR_READING_OUTBOX
SRVMSG_ADUPDATE_INFO_STATUS
SRVMSG_ADUPDATE_WARNING_READING_OBJECTS
SRVMSG_ADUPDATE_ERROR_BINDING_CONTAINER
SRVMSG_SWMPROC_ERROR_READING_REG
SRVMSG_SWMPROC_ERROR_CORRUPT_DATA_FILE
SRVMSG_SWMPROC_ERROR_RULE_CHANGE
SRVMSG_SWMPROC_ERROR_RULE_CHANGES
SRVMSG_SWMPROC_ERROR_RULE_CHANGE_CHILD
SRVMSG_SWMPROC_ERROR_RULE_CHANGE_PARENT
SRVMSG_SWMPROC_ERROR_SUMMARY_DATA_PARENT_REP
SRVMSG_SWMPROC_ERROR_PROCESS_SUMMARY_DATA_CHILD_REP
SRVMSG_SWMPROC_WARNING_DATA_RETRY_MOVE
SRVMSG_SWMPROC_INFORMATION_RULE_PROCESSED_ENABLED
SRVMSG_SWMPROC_INFORMATION_RULE_PROCESSED_DISABLED
SRVMSG_SWMPROC_INFORMATION_DELETED_FILES SRVMSG_SWMPROC_ERROR_PROCESS_USAGE_DATA_SS
SRVMSG_SWMPROC_ERROR_DATA_DISCARD_MOVE
SRVMSG_SWMPROC_ERROR_CORRUPT_DATA_FILE_BADTIME
SRVMSG_SWMPROC_ERROR_MOVED_FILE_TO_CORRUPT_DIRECTORY
SRVMSG_SWMPROC_WARNING_RESOURCE_MISSING_IN_SUMMARY_RETRY
SRVMSG_SWMPROC_ERROR_RESOURCE_MISSING_IN_SUMMARY_NORETRY
DMPMSG_ERROR_UNEXPECTED DMPMSG_WARNING_LOW_MEMORY DMPMSG_ERROR_BAD_DB_CONNECTION
DMPMSG_ERROR_CLIENT_AUTHENTICATION_FAILED DMPMSG_WARNING_UNDEFINED_MESSAGE DMPMSG_WARNING_UNAUTHORIZED_CLIENT DMPMSG_ERROR_BAD_POLL DMPMSG_ERROR_BAD_INST_REQUEST DMPMSG_ERROR_BAD_LOC_REQUEST DMPMSG_ERROR_BAD_STATUS_MESSAGE DMPMSG_ERROR_BAD_HINV_MESSAGE DMPMSG_ERROR_BAD_SINV_MESSAGE DMPMSG_ERROR_BAD_FILECOLL_MESSAGE DMPMSG_ERROR_BAD_REGISTRATION_MESSAGE DMPMSG_ERROR_DDR_PROBLEM DMPMSG_ERROR_HINV_PROBLEM DMPMSG_ERROR_SINV_PROBLEM DMPMSG_ERROR_FILE_COLL_PROBLEM DMPMSG_ERROR_STATUS_PROBLEM DMPMSG_ERROR_LOC_REQUEST_PROBLEM DMPMSG_ERROR_INST_REQUEST_PROBLEM DMPMSG_ERROR_REGISTRATION_REQUEST_PROBLEM DMPMSG_ERROR_BAD_POLL_RESPONSE DMPMSG_ERROR_BAD_INST_RESPONSE DMPMSG_ERROR_BAD_LOC_RESPONSE DMPMSG_ERROR_BAD_REGISTRATION_RESPONSE SRVMSG_CIAMGR_INFO_NEW_CIA_PROCESSED SRVMSG_CIAMGR_INFO_CIA_UPDATE_PROCESSED SRVMSG_CIAMGR_INFO_CIA_REMOVED
SRVMSG_CIAMGR_INFO_CIA_DELETED
SRVMSG_CIAMGR_ERROR_PROCESSING_CIA_CHANGES
SRVMSG_CIAMGR_WARNING_PROCESSING_CIA
SRVMSG_CIAMGR_ERROR_PROCESSING_CIA
SRVMSG_CIAMGR_ERROR_CIA_FK
SRVMSG_CIAMGR_ERROR_PROCESS_CIA_REPLFILE
SRVMSG_OBJREPLMGR_INFO_OBJECT_PROCESSED SRVMSG_OBJREPLMGR_INFO_OBJECT_UPDATE_PROCESSED SRVMSG_OBJREPLMGR_INFO_OBJECT_REMOVED
SRVMSG_OBJREPLMGR_ERROR_PROCESSING_OBJECT
SRVMSG_OBJREPLMGR_ERROR_PROCESSING_OBJECT_CHANGES
SRVMSG_OBJREPLMGR_ERROR_PROCESS_OBJECT_REPLFILE
SRVMSG_OBJREPLMGR_WARNING_PROCESSING_OBJECT
SRVMSG_OBJREPLMGR_ERROR_SMS_OBJECT_FK
SRVMSG_STATESYSTEM_ERROR_READING_REG
SRVMSG_STATESYSTEM_ERROR_PROCESSING_FILES
SRVMSG_STATESYSTEM_ERROR_TASK_FAILED
SRVMSG_STATESYSTEM_ERROR_BAD_FILE
SRVMSG_STATESYSTEM_ERROR_INVALID_RECORDS
SRVMSG_SMP_ERROR_READING_REG
SRVMSG_SMP_ERROR_SMPSTORE_MINIMUM_DISKSPACE_REACHED
SRVMSG_SMP_ERROR_SMPSTORE_MAXIMUM_CLIENTS_REACHED
SRVMSG_SMP_WARNING_SMPSTORE_CAPTURE_REQUEST_WHEN_STORE_EXISTS SRVMSG_SMP_WARNING_SMPSTORE_MINIMUM_DISKSPACE_REACHED
SRVMSG_SMP_INFO_STATE_STORE_REMOVED SRVMSG_SMP_ERROR_CLIENT_NOT_AUTHENTICATED
SMPMSG_HTTP_REQUEST_NONRESPONSIVE
SMPMSG_HTTP_REQUEST_NONRESPONSIVE_ERROR
SMPMSG_ERROR_STORE_NOT_ACCESSIBLE SMPMSG_ERROR_SIGNEDSERIALIZEDKEY_NOT_AVAILABLE
SRVMSG_NBS_ERROR_READING_REG
SRVMSG_NBS_ERROR_PROVIDER_INITIALIZE
SRVMSG_NBS_ERROR_PROVIDER_SHUTDOWN
SRVMSG_NBS_ERROR_INIT_PERFCOUNTERS
SRVMSG_NBS_ERROR_INIT_WORKER_THREADS
SRVMSG_NBS_ERROR_PROCESS_MESSAGE
SRVMSG_NBS_WARNING_PROVIDER_NOT_ACTIVE
SRVMSG_NBS_ERROR_DATABASE_LOOKUP
SRVMSG_NBS_ERROR_DATABASE_BOOTACTION
SRVMSG_NBS_ERROR_BOOT_IMAGE_NOT_AVAILABLE
SRVMSG_NBS_WARNING_BOOT_IMAGE_NOT_AVAILABLE
SRVMSG_NBS_INFO_DEVICE_BOOTED
SRVMSG_NBS_INFO_DEVICE_UNKNOWN
SRVMSG_NBS_INFO_DEVICE_ALREADY_HANDLED
SRVMSG_NBS_INFO_DEVICE_NO_ADVERTISEMENT
SRVMSG_NBS_ERROR_DATABASE_INIT
SRVMSG_NBS_ERROR_PXE_CERT_NOT_VALID
SRVMSG_NBS_WARNING_PXE_CERT_WILL_EXPIRE
SRVMSG_PXE_UPDATE_SETTINGS_FAILED
SRVMSG_PXE_REQUEST_NONRESPONSIVE_ERROR
SRVMSG_PXE_REQUEST_NONRESPONSIVE
SRVMSG_NBS_INFO_BOOTIMAGE_MISSING
SRVMSG_NBS_INFO_BOOTPROGRAM_MISSING
SRVMSG_COMPMON_WARNING_CYCLE_TIME_EXCEEDED
SRVMSG_WOL_ERROR_READING_SCF
SRVMSG_WOL_INFO_COMPONENTENABLED SRVMSG_WOL_INFO_COMPONENTDISABLED SRVMSG_WOL_INFO_COMPONENTSETTINGSCHANGE SRVMSG_WOL_INFO_STARTING_SENDING_PACKETS
SRVMSG_WOL_INFO_COMPLETED_SENDING_PACKETS
SRVMSG_WOL_INFO_SUCCEEDED_SENDING_PACKETS
SRVMSG_WOL_ERROR_SENDING_PACKETS
SRVMSG_WOL_ERROR_SENDING_PACKETS_HARDFAILURE
SRVMSG_WOL_ERROR_DBFAILED
SRVMSG_WOL_INFO_SUCCEEDED_PROCESSOBJECT
SRVMSG_WOL_ERROR_FAILED_PROCESSOBJECT
SRVMSG_WOL_INFO_MANAGEABILITY_RECOVERED
SRVMSG_WOL_ERROR_MANAGEABILITY_FAILED
SRVMSG_WCM_ERROR_REMOTE_CONFIG
SRVMSG_WCM_ERROR_GET_CATEGORIES
SRVMSG_WCM_ERROR_SUBSCRIBE
SRVMSG_WCM_ERROR_INVALID_API_INSTALL
SRVMSG_WCM_INFO_SWITCH_TO_PARENT
SRVMSG_WCM_WARNING_SWITCH_TO_WUMU
SRVMSG_WCM_WARNING_CLIENTPUB_WSUS_NOT_CONFIGURED
SRVMSG_WCM_ERROR_CLIENTPUB_PACKAGE_INFO SRVMSG_WCM_ERROR_CLIENT_PUBLISH
SRVMSG_WCM_ERROR_CLIENT_UNPUBLISH
SRVMSG_WCM_SUCCESS_CLIENT_PUBLISH
SRVMSG_WCM_SUCCESS_CLIENT_UNPUBLISH
SRVMSG_WCM_ERROR_CLIENT_UNPUBLISH_NOVERSION
SRVMSG_WCM_SUCCESS_CLIENT_UNPUBLISH_NOVERSION
SRVMSG_WSM_ERROR
SRVMSG_WSM_INFO_SYNC_STARTED SRVMSG_WSM_INFO_SYNC_DONE SRVMSG_WSM_ERROR_SYNC_FAILED
SRVMSG_WSM_INFO_PROGRESS_SYNC_WSUS
SRVMSG_WSM_INFO_PROGRESS_SYNC_SMS
SRVMSG_WSM_INFO_PROGRESS_SYNC_INF
SRVMSG_WSM_WARNING_CONTENT_OUT_OF_DATE
SRVMSG_INFO_SYNC_STARTED SRVMSG_INFO_SYNC_DONE SRVMSG_ERROR_SYNC_FAILED SRVMSG_SMSWRITER_ERROR_CONTROL_FILE_OPEN
SRVMSG_SMSWRITER_INFO_STOPPED_EXECUTABLE SRVMSG_SMSWRITER_ERROR_COULD_NOT_STOP_EXECUTABLE
SRVMSG_SMSWRITER_INFO_STARTED_EXECUTABLE SRVMSG_SMSWRITER_ERROR_COULD_NOT_START_EXECUTABLE
SRVMSG_SMSWRITER_INFO_STOPPED_SERVICE
SRVMSG_SMSWRITER_ERROR_COULD_NOT_STOP_SERVICE
SRVMSG_SMSWRITER_INFO_STARTED_SERVICE SRVMSG_SMSWRITER_ERROR_COULD_NOT_START_SERVICE
SRVMSG_SMSWRITER_INFO_STOPPED_SMS_CLIENT_APP SRVMSG_SMSWRITER_WARNING_SMS_CLIENT_APP_DID_NOT_RESPOND_TO_STOP
SRVMSG_SMSWRITER_ERROR_COULD_NOT_STOP_SMS_CLIENT_APP
SRVMSG_SMSWRITER_INFO_STARTED_SMS_CLIENT_APP SRVMSG_SMSWRITER_ERROR_COULD_NOT_START_SMS_CLIENT_APP
SRVMSG_SMSWRITER_ERROR_SYNTAX_ERRORS
SRVMSG_SMSWRITER_WARNING_UTILITY_UNAVAILAVAILBE
SRVMSG_SMSWRITER_WARNING_INSTALL_VERIFICATION
SRVMSG_SMSWRITER_WARNING_SLEEP_LIMIT
SRVMSG_SMSWRITER_WARNING_SYMBOL_REDEFINED
SRVMSG_SMSWRITER_ERROR_FILE_NOT_READABLE
SRVMSG_SMSWRITER_ERROR_REGISTRY_TASK_FAILED
SRVMSG_SMSWRITER_ERROR_CANNOT_CREATE_TEMPFILE
SRVMSG_SMSWRITER_INFO_ALREADY_STOPPED_SERVICE SRVMSG_SMSWRITER_INFO_ALREADY_STOPPED_EXECUTABLE SRVMSG_SMSWRITER_WARNING_MANUAL_STOP
SRVMSG_SMSWRITER_ERROR_INITIALIZATION_FAILED
SRVMSG_SMSWRITER_ERROR_SUBSCRIPTION_FAILED SRVMSG_SMSWRITER_ERROR_BUILDMETADATA_FAILED SRVMSG_SMSWRITER_WARNING_ALLCOMPS_NOTINCLUDED
SRVMSG_SMSWRITER_INFO_STOPPING_SERVICES SRVMSG_SMSWRITER_INFO_SNAPSHOT_CREATED SRVMSG_SMSWRITER_INFO_STARTEDSERVICES SRVMSG_SMSWRITER_WARNING_ABORTING_BACKUP SRVMSG_SMSWRITER_INFO_BACKUP_COMPLETE SRVMSG_FSP_ERROR_READING_REG
SRVMSG_FSP_ERROR_CLIENT_NOT_AUTHENTICATED
SRVMSG_FSP_WARNING_DISK_FULL
SRVMSG_FSP_ERROR_NO_TOPICS
SRVMSG_FSP_ERROR_NO_STAGING_FOLDER
SRVMSG_FSP_ERROR_COPY_FAILED
SRVMSG_WSUSCTRL_ERROR_PROXY_CONFIG
SRVMSG_WSUSCTRL_ERROR_WSUS_COMPONENTS
SRVMSG_WSUSCTRL_ERROR_WSUS_DATABASE
SRVMSG_WSUSCTRL_ERROR_MONITOR
SRVMSG_WSUSCTRL_ERROR_INVALID_SERVER_INSTALL
SRVMSG_MCS_ERROR_OPENING_SESSION
SRVMSG_MCS_HTTP_REQUEST_NONRESPONSIVE
SRVMSG_MCS_HTTP_REQUEST_NONRESPONSIVE_ERROR
SRVMSG_MCS_ERROR_CREATING_TRANSPORT_NAMESPACE
SRVMSG_MCS_ERROR_INITIALIZING_MULTICAST_SERVICE
SRVMSG_MCS_ERROR_INITIALIZING_MULTICAST_PROVIDER
SRVMSG_MCS_ERROR_INITIALIZING_ISAPI
SRVMSG_MCS_ERROR_FILE_ACCESS_NOT_GRANTED
SRVMSG_MCS_ERROR_SIGNEDSERIALIZEDKEY_NOT_AVAILABLE
SRVMSG_MCS_CLIENT_NOT_APPROVED SRVMSG_MCS_CERT_REVOKED SRVMSG_MCS_CERT_EXPIRED SRVMSG_MCS_SERVICE_INITIALIZATION_FAILED SRVMSG_AMTOM_ERROR_READING_NOTIFICATION_REGISTRY
SRVMSG_AMTOM_ERROR_INITIALIZING_INBOX
SRVMSG_AMTOM_INFO_STARTING_SENDING_PACKETS
SRVMSG_AMTOM_INFO_COMPLETED_SENDING_PACKETS
SRVMSG_AMTOM_ERROR_WINRMOOB_NOT_INSTALLED
SRVMSG_AMTOM_ERROR_HELLO_LISTENER_OCCUPYIED SRVMSG_AMTOM_ERROR_PROVISION_INCOMPLETE
SRVMSG_AMTOM_ERROR_OPERATION_INCOMPLETE
SRVMSG_AMTOM_ERROR_PROVISION_PROXY_BLOCKWSMAN
SRVMSG_AMTOM_ERROR_PROVISION_PROVCERT_MISS
SRVMSG_AMTOM_INFO_PROVISION_CERT_WILL_EXPIRE
SRVMSG_AMTOM_ERROR_PROVISION_CERT_WILL_EXPIRE
SRVMSG_AMTOM_ERROR_PROVISION_INCOMPLETE_NETWORKCONFIG_ERR
SRVMSG_AMTOM_ERROR_PROVISION_AUTHENTICATION_ERR
SRVMSG_AMTOM_ERROR_PROVISION_CERT_REVOCATION_CHKFAIL
SRVMSG_AMTOM_ERROR_PROVISION_CERT_INVALID SRVMSG_AMTOM_ERROR_OPERATION_INCOMPLETE_AUDITFULL
SRVMSG_AMTOM_WARN_IPV6FIRST
SRVMSG_AIUS_ERROR_INSTALL_FAILED
SRVMSG_SRSRP_ERROR_CONFIG SRVMSG_SRSRP_ERROR_INVALID_SRSSERVER_INSTALL SRVMSG_SRSRPCTRL_ERROR_MONITOR SRVMSG_SRSRPCTRL_ERROR_SRSSERVICE_NOTRUNNING SRVMSG_SRSRPCTRL_ERROR_SRSRP_SRSNOTINSTALLEDORCONFIGURED SRVMSG_SRSRPCTRL_ERROR_SRSRP_SRSROOTFOLDERNOTCONFIGURED SRVMSG_AI_KB_MANAGER_WARNING_PROCESSING_VARFILE
SRVMSG_AI_KB_MANAGER_ERROR_PROCESSING_VARFILE
SRVMSG_AI_KB_MANAGER_WARNING_PROCESSING_ARXFILE
SRVMSG_AMTCM_ERROR_NOPERMISSION_TO_REQUESTCERT
SRVMSG_AMTCM_ERROR_CAROOTCERTIFICATE_NOT_IN_CTL
SRVMSG_AMTCM_ERROR_AD_ADD_OBJECT
SRVMSG_AMTCM_ERROR_AD_REMOVE_OBJECT
SRVMSG_AMTCM_ERROR_AD_UPDATE_OBJECT
SRVMSG_AMTCM_WARNING_CERTREQUEST_IN_PENDING
SRVMSG_AMTCM_ERROR_REGISTER_PROVISION_SERVER
SRVMSG_AMTCM_ERROR_UNREGISTER_PROVISION_SERVER
SRVMSG_AMTCM_WARNING_PROXY_FILEREPLICATION_RETRY
SRVMSG_AMTCM_WARNING_PROXY_FILEREPLICATION_FAILED
MessageID 10000
Severity
ERROR
Message Source
Available Programs Agent
10001
ERROR
10002
INFORMATIONAL Available Programs Agent
10003
ERROR
10004
ERROR
10005
10006
ERROR
10007
ERROR
10008
10009
10010
ERROR
10011
ERROR
10012
10013
ERROR
10014
ERROR
10015
10016
10017
ERROR
10018
WARNING
10019
WARNING
10020
10021
ERROR
10022
10023 10024 10025
INFORMATIONAL Available Programs Agent INFORMATIONAL Available Programs Agent ERROR Available Programs Agent
10026
10027
10028
10029
10030
ERROR
10031
10034
10035
10036
10037
10038
10040
10041
10042
10043
10045
WARNING
10046
WARNING
10050
ERROR
10051
ERROR
10052
ERROR
10053
ERROR
10054
ERROR
10055
WARNING
10056
WARNING
10057
ERROR
10058
ERROR
10060
WARNING
10061
WARNING
10062
WARNING
10070
ERROR
10071
ERROR
10072
WARNING
10073
10074
ERROR
10075
10076
10077
10078
ERROR
10079
ERROR
10080
ERROR
10090 10091
INFORMATIONAL Available Programs Agent WARNING Available Programs Agent
10092
ERROR
10093
WARNING
10094
ERROR
10100
ERROR
Client Component Installation Manager
10101
ERROR
10102
WARNING
10103
WARNING
10104
WARNING
10105
ERROR
10106
ERROR
10107
ERROR
10108
WARNING
10109
INFORMATIONAL Client Component Installation Manager
10110
10200
10201
10202
10203
10204
10205
10206
10207
10208
10209
ERROR
10210
ERROR
10211
ERROR
10212
ERROR
10213
ERROR
10214
ERROR
10215
WARNING
10216
WARNING
10217
WARNING
10218
ERROR
10219
ERROR
10220
ERROR
10221
WARNING
10222
10223
WARNING
10224
10225 10226 10500
INFORMATIONAL Client Component Installation Manager WARNING Client Component Installation Manager
INFORMATIONAL Hardware Inventory Agent
10501
ERROR
Hardware Inventory Agent
10502
ERROR
10503
ERROR
10504
WARNING
10505
INFORMATIONAL Hardware Inventory Agent
10506
ERROR
10507
ERROR
10508
WARNING
10509
ERROR
10510
ERROR
10511
ERROR
10600
INFORMATIONAL Software Inventory Agent
10601
WARNING
Software Inventory Agent
10602
WARNING
10603
WARNING
10604
WARNING
10605
INFORMATIONAL Software Inventory Agent
10650
INFORMATIONAL File Collection
10651
WARNING
File Collection
10700 10701
INFORMATIONAL Remote Client Inventory Agent INFORMATIONAL Remote Client Inventory Agent
10702
WARNING
Remote Client Inventory Agent
10703 10704 10800 10801 10802 10803 10804
ERROR ERROR
Remote Client Inventory Agent Remote Client Inventory Agent
INFORMATIONAL Remote Client INFORMATIONAL Remote Client INFORMATIONAL Remote Client ERROR Remote Client
INFORMATIONAL Remote Client
10805
WARNING
Remote Client
10806 10807 10808
WARNING
Remote Client
INFORMATIONAL Remote Client ERROR Remote Client
10809 10810
INFORMATIONAL Remote Client WARNING Remote Client
10811
10812 10813 10814
ERROR
Remote Client
INFORMATIONAL Remote Client INFORMATIONAL Remote Client
10815
ERROR
Remote Client
10816
10817
ERROR
Remote Client
10818
ERROR
Remote Client
10819 10820
ERROR WARNING
Remote Client Remote Client
10821
ERROR
Remote Client
10822 10900
ERROR ERROR
Remote Client Software Metering Agent
10901 10902
ERROR WARNING
Software Metering Agent Software Metering Agent
10903
INFORMATIONAL Software Metering Agent
10904
WARNING
Software Metering Agent
10905 10906 10907 11000 11001 11002 11010 11011 11012 11020 11021 11030 11031 11032 11033 11034 11035 11036 11037 11070 11071 11072 11073 11074 11080 11081 11082
ERROR
Software Metering Agent
INFORMATIONAL Software Metering Agent INFORMATIONAL Software Metering Agent INFORMATIONAL ERROR ERROR INFORMATIONAL ERROR ERROR Device Client Device Client Device Client Device Client Device Client Device Client
INFORMATIONAL Device Client ERROR Device Client
INFORMATIONAL Device Client INFORMATIONAL Device Client ERROR Device Client
WARNING Device Client INFORMATIONAL Device Client INFORMATIONAL Device Client ERROR ERROR INFORMATIONAL ERROR INFORMATIONAL ERROR Device Client Device Client Device Client Device Client Device Client Device Client
INFORMATIONAL Device Client INFORMATIONAL Device Client ERROR Device Client INFORMATIONAL Device Client
11083 11084 11090 11091 11095 11096 11100 11101 11102 11103 11104 11105 11106 11107 11108 11109 11110 11111 11112 11113 11120 11121 11122
INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL ERROR INFORMATIONAL
Device Client Device Client Device Client Device Client Device Client Device Client
INFORMATIONAL OS Deployment Agent ERROR OS Deployment Agent
INFORMATIONAL OS Deployment Agent ERROR OS Deployment Agent ERROR ERROR OS Deployment Agent OS Deployment Agent
INFORMATIONAL OS Deployment Agent INFORMATIONAL OS Deployment Agent INFORMATIONAL OS Deployment Agent INFORMATIONAL OS Deployment Agent INFORMATIONAL OS Deployment Agent INFORMATIONAL OS Deployment Agent INFORMATIONAL OS Deployment Agent INFORMATIONAL OS Deployment Agent INFORMATIONAL Task Sequence Execution ERROR Task Sequence Execution
INFORMATIONAL Task Sequence Execution
11123 11124
INFORMATIONAL Task Sequence Execution INFORMATIONAL Task Sequence Execution
11125 11126 11127 11128 11129
WARNING ERROR
Task Sequence Execution Task Sequence Execution
INFORMATIONAL Task Sequence Execution INFORMATIONAL Task Sequence Execution ERROR Task Sequence Execution
11130
11131 11132
INFORMATIONAL Task Sequence Execution ERROR Task Sequence Execution
11133 11134
11135
ERROR
Task Sequence Execution
11136
11137
ERROR
Task Sequence Execution
11138 11139 11140 11141 11142 11143
WARNING ERROR
Task Sequence Execution Task Sequence Execution
INFORMATIONAL Task Sequence Execution ERROR Task Sequence Execution
11144 11169 11170
INFORMATIONAL Task Sequence Execution ERROR ERROR Task Sequence Manager Task Sequence Manager
11171 11200
INFORMATIONAL Task Sequence Manager ERROR Software Updates Installation Agent
11201
ERROR
Software Updates Installation Agent
11202
ERROR
11203
ERROR
11204
ERROR
11205
ERROR
11206
ERROR
11207
ERROR
11250
WARNING
11251
WARNING
11252 11253 11254
INFORMATIONAL Software Updates Installation Agent INFORMATIONAL Software Updates Installation Agent INFORMATIONAL Software Updates Installation Agent
11255
INFORMATIONAL Software Updates Installation Agent
11256
WARNING
11257
11258
11259
11261 11262 11263 11264
INFORMATIONAL Software Updates Installation Agent INFORMATIONAL Software Updates Installation Agent INFORMATIONAL Software Updates Installation Agent INFORMATIONAL Software Updates Installation Agent
11266
11267
11268 11269
INFORMATIONAL Software Updates Installation Agent INFORMATIONAL Software Updates Installation Agent
11270 11300
INFORMATIONAL Software Updates Installation Agent INFORMATIONAL Software Updates Installation Agent
11301
11302
ERROR
11303
WARNING
11304
11306
ERROR
11307
11308
11309
11310
11350 11351 11352 11353 11354
INFORMATIONAL Branch Distribution Point INFORMATIONAL Branch Distribution Point ERROR WARNING ERROR Branch Distribution Point Branch Distribution Point Branch Distribution Point
11355
ERROR
Branch Distribution Point
11356
ERROR
11357
ERROR
11358
ERROR
11359
ERROR
11360
ERROR
11361
ERROR
11362
ERROR
11363
INFORMATIONAL Branch Distribution Point
11364
WARNING
11365
ERROR
11366
ERROR
11367
WARNING
11368 11369 11370 11371
INFORMATIONAL Branch Distribution Point INFORMATIONAL Branch Distribution Point INFORMATIONAL Branch Distribution Point INFORMATIONAL Branch Distribution Point
11372 11373 11374 11375 11376 11377 11378 11379 11380 11381
INFORMATIONAL Branch Distribution Point INFORMATIONAL Branch Distribution Point INFORMATIONAL Branch Distribution Point ERROR Branch Distribution Point
INFORMATIONAL Branch Distribution Point ERROR ERROR Branch Distribution Point Branch Distribution Point
INFORMATIONAL Branch Distribution Point INFORMATIONAL Branch Distribution Point WARNING Branch Distribution Point
11401
ERROR
Software Updates Scan
11402
ERROR
11403 11404
ERROR ERROR
Software Updates Scan Software Updates Scan
11405
ERROR
11406 11408
ERROR
INFORMATIONAL Software Updates Scan
11409
WARNING
11410
ERROR
11411
ERROR
11412 11413 11414 11415 11416
ERROR ERROR ERROR
Software Updates Scan Software Updates Scan Software Updates Scan
INFORMATIONAL Software Updates Scan ERROR Software Updates Scan
11417 11418
INFORMATIONAL Software Updates Scan ERROR Software Updates Scan
11419
INFORMATIONAL Software Updates Scan
11420
ERROR
11421
ERROR
11422
ERROR
11423 11424
ERROR ERROR
Software Updates Scan Software Updates Scan
11425
ERROR
11426
WARNING
11450 11451 11452 11453 11454
ERROR ERROR ERROR ERROR ERROR
Software Updates Sync Software Updates Sync Software Updates Sync Software Updates Sync Software Updates Sync
11455
ERROR
Software Updates Sync
11456
ERROR
11457
INFORMATIONAL Software Updates Sync
11458
ERROR
11459
ERROR
11460
INFORMATIONAL Software Updates Sync
11461
ERROR
11462
ERROR
11500 11501 11502 11503 11504 11505
INFORMATIONAL Device Client Deployment INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment
INFORMATIONAL Device Client Deployment
11506 11507 11508 11510
INFORMATIONAL Device Client Deployment INFORMATIONAL Device Client Deployment INFORMATIONAL Device Client Deployment WARNING Device Client Deployment
11511
WARNING
Device Client Deployment
11512
WARNING
11520 11521 11522 11523 11524 11525
ERROR ERROR ERROR ERROR ERROR ERROR
Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment
11526 11527 11528 11529 11530 11540
ERROR ERROR ERROR ERROR ERROR ERROR
Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment
11541
ERROR
11542 11550 11551 11552 11553 11554 11555 11560 11561 11562 11563 11564 11565 11566
ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR
Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment
11567 11568 11570 11571
Device Client Deployment Device Client Deployment Device Client Deployment Device Client Deployment
11572
ERROR
11573 11600 11700
ERROR ERROR ERROR
Device Client Deployment System Health Software Update Manager
11701 11702 11703 11704
Software Update Manager Software Update Manager Software Update Manager Software Update Manager
11705
ERROR
Software Update Manager
11706 11707 11708 11709 11710
Software Update Manager Software Update Manager Software Update Manager Software Update Manager Software Update Manager
11711 11712 11713 11714
Software Update Manager Software Update Manager Software Update Manager Software Update Manager
11715
ERROR
11716
ERROR
11717
ERROR
11750 11751 11752 11753 11754 11755 11756 11757 11758 11759
ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR
Software Update Manager Software Update Manager Software Update Manager Software Update Manager Software Update Manager Software Update Manager Software Update Manager Software Update Manager Software Update Manager Software Update Manager
11760
ERROR
11800 11801
ERROR ERROR
Desired Configuration Manager Desired Configuration Manager
11802
ERROR
Desired Configuration Manager
11850 11851
ERROR ERROR
11852 11853 11854
ERROR ERROR
INFORMATIONAL Desired Configuration Manager
11855
INFORMATIONAL Desired Configuration Manager
11856
WARNING
11857
ERROR
11858 11859 11860 11861 11862 11863 11864 11865 11866 11867 11900
ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR
Desired Configuration Manager Desired Configuration Manager Desired Configuration Manager Desired Configuration Manager Desired Configuration Manager Desired Configuration Manager Desired Configuration Manager Desired Configuration Manager Desired Configuration Manager Desired Configuration Manager
INFORMATIONAL Task Sequence
11901
ERROR
Task Sequence
12000 12001
INFORMATIONAL Out-of-Band Management Agent ERROR Out-of-Band Management Agent
12100
INFORMATIONAL Virtual Application Management Agent
12101
ERROR
Virtual Application Management Agent
12102
12103
12104
ERROR
12105
12106 12107
ERROR
Message Text
A data integrity error was detected for advertisement "%1" (%2%1.ofr).%12 Possible cause: The advertisement (.ofr) file on this Client Access Point (CAP) is missing, corrupt, or lacking data. The advertisement will not be run or displayed to users. Solution: Modify the specified advertisement in the SMS Administrator console to force Offer Manager to update (rewrite) the advertisement files. Wait for Inbox Manager to replicate the change to the CAPs throughout the site before refreshing the list of advertised programs on the client (press F5 in the Advertised Programs Monitor). If the problem persists, check for disk problems on the CAP or for other external causes of file corruption.
A data integrity error was detected for package "%1" (%2%1.pkg).%12 Possible cause: The package (.pkg) or network location (.nal) file on this Client Access Point (CAP) is missing, corrupt, or lacking data. Advertisements for the package's programs will not be run or displayed to users until the file can be read successfully. Solution: Modify the specified package or one of its programs to force SMS Distribution Manager to update (rewrite) the package files. Wait for SMS Inbox Manager to replicate the change to the CAPs throughout the site before refreshing the list of advertised programs on the client (press F5 in the Advertised Programs Monitor). If the problem persists, check for disk problems on the CAP or for other external causes of file corruption.
Advertisement "%1" was received from site "%2".%12 The client passes any supported platform requirements and the SMS will add the advertisement's program to the list that will be displayed to users and/or run via assignment. If an advertisement is received but not displayed on a client, verify that the current time on the client is between the advertisement start and expiration times, and that the program specified in the advertisement is enabled.
An error occurred while preparing to run the program for advertisement "%1" ("%4" - "%5").%12Additional program properties: Command line: %2 Working directory: %3 Drive letter (? = any): %6 Possible cause: This message most commonly occurs when the program's command-line executable file could not be found, when a required drive letter connection to a distribution point could not be established, or when the program is configured to use the SMS Software Installation Account but the account is not specified, could not be found, or does not have the appropriate permissions. Solution: Check each of the items listed above. The program for advertisement "%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. Possible cause: This error can be caused by an invalid executable file specified in the command line (such as an Alpha-based executable file on an x86-based computer) or by a corrupt executable file. This error can also be caused if the program is executed from a remote session. Solution: Make sure that the executable file specified in the program's command line is valid for the computer it is attempting to run on. Also, manually verify that the specified command line can be executed from within the original content source directory. If necessary, modify the program properties, the content source files, or both. If changes to the content source files are required, use the Manage Distribution Points wizard to update all of the content's distribution points with the new version of the content source files before retrying execution on the client.
Program started for advertisement "%1" ("%4" - "%5").%12 Command line: %2 Working directory: %3 User context: %9
The program for advertisement "%1" failed ("%4" - "%5"). A failure exit code of %2 was returned. User context: %9%12 Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS 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. An exit code of %2 is considered a failure. Solution: For more information on the exit code, refer to the documentation for the program you are distributing. The program for advertisement "%1" failed ("%4" - "%5"). The failure description was "%3%7%8%9". User context: %2%12 Possible cause: The program generated an installation status Management Information Format (MIF) file with a status value of Failed. Solution: For more information about the failure, refer to the documentation for the program you are distributing. The program for advertisement "%1" completed successfully ("%4" - "%5"). User context: %9%12 Systems Management Server (SMS) determines status for each program it executes. If SMS 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. The program for advertisement "%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.
An error occurred while SMS Advertised Program Manager was preparing to run the uninstall program for advertisement "%1" ("%4" - "%5").%12 Additional program properties: Command line: %2 Working directory: %3 Drive letter (? = any): %6 Possible cause: SMS Advertised Program Manager is unable to find the uninstall command line executable file specified in the program's uninstall registry key. Solution: Verify that the uninstall command registered by the program's setup routines is valid for the client. The uninstall program for advertisement "%1" could not be executed ("%4" - "%5").%12 Additional properties: Command line: %2 Working directory: %3 Possible cause: The uninstall command line for the program cannot be executed successfully. This error can be caused by an invalid executable file specified in the uninstall command line (such as an Alpha executable file on an Intel computer) or by a corrupt executable file. Solution: Make sure that the executable file specified in the program's uninstall command line is valid for the computer running the advertisement. Uninstall started for advertisement "%1" ("%4" - "%5"). Command line: %2 Working directory: %3%12 The uninstall program for advertisement "%1" failed ("%4" "%5"). A non-zero exit code of %2 was returned.%12 Possible cause: SMS Advertised Program Manager (APM) determines status for each program it executes. If APM cannot find or correlate any install status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. A non-zero exit code is considered a failure. Solution: For more information about the exit code, refer to the documentation for the program you are distributing.
The uninstall program for advertisement "%1" failed ("%4" "%5"). The failure description was "%3".%12 Possible cause: The uninstall program generated an install status Management Information Format (MIF) file with a status value of Failed. Solution: For more information about the failure, refer to the documentation for the program you are distributing. The uninstall program for advertisement "%1" completed successfully ("%4" - "%5"). An exit code of zero was returned.%12 SMS Advertised Program Manager (APM) determines status for each program it executes. If APM cannot find or correlate any install status Management Information Format (MIF) files for the program, it uses the program's exit code program to determine status. An exit code of zero is considered successful.
The uninstall program for advertisement "%1" completed successfully ("%4" - "%5"). The success description was "%3".%12 The program generated an install status Management Information Format (MIF) file with a status value of Success. For more information, see the documentation for the program you are distributing. The uninstall for advertisement "%1" failed.%12 Possible cause: The removal key specified (%2) for the program in the advertisement ("%4" - "%5") cannot be found in the client registry or was found but did not contain either of the required uninstall command line entries (a UninstallString or a QuietUninstallString value). Solution: Verify that the removal key specified on the Advanced tab of the Program's Properties dialog box exists in the client's registry under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\Uninstall and that it contains one of the required uninstall command-line entries. If necessary, adjust the key specified in the program's properties. APM will retry the uninstall operation the next time the client's list of advertised programs is refreshed and a change in the program's properties is detected.
Advertisement "%1" from site "%2" was rejected because the client's platform is not supported.%12 Possible cause: The client received the advertisement but rejected it because the client's platform was not included in the list of supported platforms specified for the program. Solution: If the client should actually accept the advertisement, either disable supported platform checking or modify the list of supported platforms specified on the Requirements tab of the Program's Properties dialog box. Changes to the program properties will not be detected until the list of advertised programs is refreshed on the client.
Advertisement "%1" from site "%2" was rejected because the advertisement has expired.%12 Possible cause: The client received the advertisement but rejected it because the advertisement expiration date is past. Solution: If the client should accept the advertisement, you can extend the life of the advertisement by changing the expiration date and time or disabling expiration on the Schedule tab of the advertisement's properties. Changes to the Advertisement's Properties dialog box will not be detected until the list of advertised programs is refreshed on the client.
The program for advertisement "%1" ("%4" - "%5") will not be scheduled because the client is currently attached to the site with a slow network connection. Possible cause: The advertisement specified has the "Assignments are not mandatory over slow links" checkbox selected on its Schedule tab and the performance of the connection to the Client Access Point (CAP) has either been detected as below the configured threshold, could not be determined, or is a Remote Access Service (RAS) connection. Solution: The advertisement will be scheduled for execution when the client next attaches to the site with a fast network connection.
The program for advertisement "%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 Possible cause: The program performs a restart of the client computer when it completes, but the 'After running' setting in the program's properties is not set to Program restarts computer, or the client machine was restarted while the program was running. Solution: Verify the above. If the program does a restart when it completes, even if it only requires a restart in some cases, modify the program's properties and set 'After running' to 'Program restarts computer'. The program for advertisement "%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. Systems Management Server (SMS) determines status for each program it executes. Any program dependencies will not be executed until after the restart occurs. If SMS 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. Download of the content "%4" - "%2" has started. Download of the content "%4" - "%2" has completed successfully. Download of the content "%4" - "%2" has failed.%12. Possible cause: The content can not be found on the network, or the content could not be accessed. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters.
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. The cache size has been modified from %6 MB to %7 MB. The cache is located at %3. The contents of the cache have been cleared by user request. The cache is currently located at %3 and %7 MB of space is allocated. 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. 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. Possible causes: The content on the distribution point has been manually modified, or a local administrator on the computer has modified the content in the computer's hash. Solution: Refresh the content on the distribution point and retry the download. Download of the content "%4" - "%2" was cancelled. The download was cancelled because either a local distribution point was located, a user cancelled the download, or the advertisement associated with the download expired, was disabled or deleted. The program for the advertisement "%1" ("%4" - "%5") has been cancelled due to a user request.
The program for advertisement "%1 has not yet started because the content for the package "%4" - "%5" (version %2) has not been acquired. Possible cause: The content for this program must be downloaded into the computer's cache, or the content could not be located. Solution: If the program is being downloaded, no action is required. The program will start once the download has been successfully completed. If the content can not be located, ensure that a distribution point with this content is available for this computer. Distribution point availability can be affected by roaming boundary configuration which is used to determine whether distribution points are classified as local or remote, or by enabling distribution points as protected distribution points. Distribution point availability can also be affected if you are using branch distribution points and the advertisement is configured with the option Run program from distribution point instead of Download content from distribution point and run locally. This is because branch distribution points do not support advertisements that are configured to run directly from a distribution point.
The program for advertisement "%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. SMS will run this program once the user logon condition is satisfied. The program for advertisement "%1" has not been run yet ("%4" "%5"). SMS is currently running another program ("%2" - "%3") on this computer, and that program must complete before this one can begin. The program for advertisement "%1" has not been run yet ("%4" "%5"). Software Distribution is currently paused on this computer, and it has to be resumed before this program can begin. The program for advertisement "%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.
The program for advertisement "%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. The program for advertisement "%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. The program for advertisement "%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. The program for the advertisement "%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. Solution: Increase the size of the cache, or remove other content from the cache, or increase the amount of free disk space. This program will be retried. Windows Installer per-user elevation of this program ("%4" "%5") failed for advertisement "%1".%12This program was started. Please check the status of this program to determine whether or not it was completed sucessfully Possible causes: The version of Windows Installer on the computer is less than version 2.0, or the setup program does not support Windows Installer per-user elevated rights installations. Possible solutions: Update the version of Windows Installer on the computer to version 2.0 or later, or contact the software vendor that supplied the install program to determine if a version of setup that supports per-user elevated rights is available.
The program for the advertisement "%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. Solution: Increase the size of the cache. The content for "%4" - "%2" could not be located. This SMS client will no longer attempt to locate this content. Possible cause: The content source might not be available on any distribution servers, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Content source might not be available because the advertisement is configured with the option Run program from distribution point on one or more branch distribution points and is not available on a standard distribution point. Branch distribution points do not support advertisements that are configured with the option Run program from distribution point. Solution: Use the Manage Distribution Points wizard to distribute the content to a distribution point. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point. Use the Manage Distribution Points wizard to distribute the content to a standard distribution point if you want to use the option Run program from distribution point.
The program for the advertisement "%1" ("%4" - "%5") could not be run because the policy contains an invalid combination of requirements: %2. Possible cause: The program is set to run when no user is logged on, but is being advertised to a user. Solution: Examine the properties of the program to resolve the conflicting requirements. Possible cause: The program is set to require user input, but does not require that a user be logged on in order to run. Solution: Examine the properties of the program to resolve the conflicting requirements. Possible cause: The program requires content download, but no supported hash is available because the package was previously created by a version of SMS that did not support the required hash algorithms. Solution: Perform a package update to recalculate the hash and send policy to clients with the updated hash value.
The program for advertisement "%1 has failed because download of the content "%4" - "%2" has failed. Possible cause: The content can not be found on the network, or the content could not be accessed, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point.
The program for the advertisement "%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. Solution: Increase the size of the cache, or remove other content from the cache, or increase the amount of free disk space. This program will not be retried.
An error occurred while preparing to run the program for advertisement "%1" ("%4" - "%5").%12Additional program properties: Command line: %2 Working directory: %3 Drive letter (? = any): %6 Possible cause: This message most commonly occurs when the program's command-line executable file could not be found, when a required drive letter connection to a distribution point could not be established, or when the program is configured to use the SMS Software Installation Account but the account is not specified, could not be found, or does not have the appropriate permissions. Solution: Check each of the items listed above. This program will be retried. The program for advertisement "%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. Possible cause: This error can be caused by an invalid executable file specified in the command line (such as an Alpha-based executable file on an x86-based computer) or by a corrupt executable file. This error can also be caused if the program is executed from a remote session. Solution: Make sure that the executable file specified in the program's command line is valid for the computer on which it is attempting to run. Also, manually verify that the specified command line can be executed from within the original content source directory. If necessary, modify the program properties, the content source files, or both. If changes to the content source files are required, use the Manage Distribution Points wizard to update all of the content's distribution points with the new version of the content source files before retrying execution on the client. This program will be retried.
The program for advertisement "%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. Possible causes: The content on the distribution point has been manually modified, or a local administrator on the computer has modified the content in the computer's hash. Solution: Refresh the content on the distribution point and retry the download. The program for advertisement "%1 has failed because download of the content "%4" - "%2" has failed. Possible cause: The content can not be found on the network, or the content could not be accessed, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Content source might not be available because the advertisement is configured with the option Run program from distribution point on one or more branch distribution points and is not available on a standard distribution point. Branch distribution points do not support advertisements that are configured with the option Run program from distribution point. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point. Use the Manage Distribution Points wizard to distribute the content to a standard distribution point if you want to use the option Run program from distribution point.
The content for "%4" - "%2" can not be located. This SMS client will attempt to locate this content again. Possible cause: The content source might not be available on any distribution servers, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Content source might not be available because the advertisement is configured with the option Run program from distribution point on one or more branch distribution points and is not available on a standard distribution point. Branch distribution points do not support advertisements that are configured with the option Run program from distribution point. Solution: Use the Manage Distribution Points wizard to distribute the content to a distribution point. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point. Use the Manage Distribution Points wizard to distribute the content to a standard distribution point if you want to use the option Run program from distribution point.
The program for advertisement "%1 has failed because download of the content "%4" - "%2" has failed. Possible cause: The content can not be found on the network, or the content could not be accessed, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters. This operation will be retried. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point.
The program for advertisement "%1 has failed because download of the content "%4" - "%2" has failed. Possible cause: The content can not be found on the network, or the content could not be accessed, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Content source might not be available because the advertisement is configured with the option Run program from distribution point on one or more branch distribution points and is not available on a standard distribution point. Branch distribution points do not support advertisements that are configured with the option Run program from distribution point. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters. This operation will be retried. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point. Use the Manage Distribution Points wizard to distribute the content to a standard distribution point if you want to use the option Run program from distribution point.
The program for advertisement "%1" ("%4" - "%5") exceeded the maximum allowed run time of %2 minute(s). Systems Management Server (SMS) has stopped monitoring the program, and is unable to determine the status of the program. SMS will not automatically attempt to run this program again. Possible causes: The program might have taken longer to run than expected, or the program might have experienced problems while running. Possible solution: Make sure the maximum allowed run time specified for the program allows enough time for the program to finish running. If the program requires user input, ensure the program properties allow the user to interact with the program.
The program for advertisement "%1" ("%4" - "%5") could not be monitored. Systems Management Server has assumed this program failed and will attempt to run the program again. Possible cause: There is not enough memory available on the client to monitor this program.
The program for advertisement "%1" failed ("%4" - "%5"). A failure exit code of %2 was returned. User context: %9%12 Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS 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. An exit code of %2 is considered a failure. Solution: For more information on the exit code, refer to the documentation for the program you are distributing. This program will be retried. The program for advertisement "%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. Possible Cause: The duration for the maintenance window is shorter than the maximum runtime specified for this program. Solution: modify the duration of the maintenance window or add another maintenance window that is long enough in duration to accomodate the maximum runtime of this program. Possible Cause: The advertisement is not set to override maintenance window. Solution: Update the advertisement to override maintenance windows. Note: setting the override flag will cause the system to install the program at the mandatory assignment scheduled time and may cause the system to restart if required.
The program for advertisement "%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. Possible Cause: The duration for the maintenance window is shorter than the maximum runtime specified for this program. Solution: modify the duration of the maintenance window or add another maintenance window that is long enough in duration to accomodate the maximum runtime of this program. Possible Cause:There is only one maintenance window defined for this computer, and it is a one-time maintenance window that occurs in the past. Solution: You can delete the maintenance window if it is no longer applicable, or you can disable the maintenance window. You can also add another maintenance window for this computer, and allow the program to run according to the new maintenance window schedule. Possible Cause: The advertisement is not set to override maintenance window. Solution: Update the advertisement to override maintenance windows. Note: setting the override flag will cause the system to install the program at the mandatory assignment scheduled to An advertisement has completed and requires the machine time restart but the restart cannot be performed due to maintenance window restrictions. The restart is waiting for the next available maintenance window. 1An advertisement has completed and requires the machine to restart. The machine will restart now, and will not adhere to any maintenance window restrictions. 1The advertisement "%1" ("%4" - "%5") is waiting for package content from an Intranet-based Distribution Point. The system is Internet based and cannot run the advertised program directly from a UNC location over the internet. 1The advertisement "%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.
A restart is pending for an advertisement. There is no maintenance window available for this computer that will allow the restart to occur . Possible cause: the duration of the reboot countdown is longer than the duration of any maintenance windows defined for this computer. Solution: Increase the duration of the maintenance window available to this computer, add another maintenance window for that exceeds the duration of the restart countdown notfication length or reduce the duration of the restart countdown notification.
The program for advertisement "%1" failed ("%4" - "%5"). Operating System Deployment task sequences cannot run when the computer is on the Internet. The Windows Installer source paths have been successfully updated on this computer. The Windows Installer source paths on this computer failed to update. The failure was caused by error %12. The update will be retried. The Windows Installer source paths on this computer failed to update. The failure was caused by error %12. The update will not be retried. The Windows Installer source paths on this computer failed to update. SMS was unable to determine the correct locations for the Windows Installer program. Possible causes: The computer is unable to contact a Management Point to locate the program content; the content location request to the Management Point timed out. Solutions: Wait until the computer is connected to the network and able to contact the Management Point. The update will be retried. The Windows Installer source paths on this computer failed to update. SMS was unable to determine the correct locations for the Windows Installer program. Possible causes: The computer is unable to contact a Management Point to locate the program content; the content location request to the Management Point timed out. Solutions: Wait until the computer is connected to the network and able to contact the Management Point. The update will not be retried.
SMS Client Component Installation Manager (CCIM) encountered an error while attempting to use the file "%1".%12 Solution: Check for low disk space. Then, 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."
SMS Client Component Installation Manager (CCIM) cannot generate the client's heartbeat discovery data record (DDR) file, "%1".%12 Possible cause: Low disk space. Solution: Free up some disk space. SMS Client Component Installation Manager (CCIM) encountered an error while reading the site's client component offer data from "%1".%12 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. SMS Client Component Installation Manager (CCIM) encountered an error while trying to copy the site's client component data files from "%1".%12 Solution: Check the client account permissions to verify that the client has read permission to the Clifiles.box directory. SMS Client Component Installation Manager (CCIM) encountered an error while trying to copy the site's client component configuration files from "%1".%12 Solution: Check the client account permissions to verify that the client has read permission to the Clifiles.box directory.
SMS Client Component Installation Manager (CCIM) encountered an error while trying to get execution information from SMS Available Programs Manager (APM) for client component "%1", command "%2".%12 Possible cause: Either APM is not running or the inter-process communication (IPC) mechanism might not be working. 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." SMS Client Component Installation Manager (CCIM) encountered an error while trying to send client component "%1", command "%2" to SMS Available Programs Manager (APM).%12 Possible cause: Either APM is not running or the inter-process communication (IPC) mechanism might not be working. 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."
SMS Client Component Installation Manager (CCIM) encountered an error while trying to run the following client component command(s): %1 %12 Solution: See the SMS Available Programs Manager (APM) status messages for specific information. SMS Available Programs Manager (APM) has not executed the following SMS client component command(s) within the hour: %1 %12 Solution: See the APM status messages for specific information.
The following SMS client component(s) are scheduled to be upgraded: %1 %12
The following SMS client component(s) are scheduled to be verified: %1 %12 The basic SMS client services were successfully installed on this computer.%12 The SMS Client Component Installation Manager (CCIM) is now ready to install the optional client components. You can enable and disable the installation of these components by using Site Database -> Site Hierarchy -> site code - site name -> Client Agents in the SMS Administrator console. This computer is no longer assigned to any site as an SMS client.%12 SMS Client Component Installation Manager (CCIM) will now remove all SMS client components and services from this computer. This computer is now assigned to site "%1" as an SMS client.%12 You can control which computers are assigned to each site by configuring the Site Boundaries in the SMS Administrator console. This computer is no longer assigned to site "%1" as an SMS client.%12 You can control which computers are assigned to each site by configuring the Site Boundaries in the SMS Administrator console. SMS Client Component Installation Manager (CCIM) installed client component "%1" %2 on this computer.%12 SMS Client Component Installation Manager (CCIM) upgraded client component "%1" %2 on this computer.%12 SMS Client Component Installation Manager (CCIM) verified that client component "%1" %2 is correctly installed on this computer.%12 SMS Client Component Installation Manager (CCIM) removed client component "%1" from this computer.%12
SMS Client Component Installation Manager (CCIM) could not successfully install client component "%1" %2 on this computer. %12 The computer is configured in a way that prevented the component from completely installing. You can either ignore this message or reconfigure the computer to enable CCIM to automatically retry the installation approximately every 30 days. To force CCIM to retry the installation immediately, perform the following steps: 1. In Control Panel, double-click Systems Management. 2. Click Components. 3. Click "%1". 4. Click Repair Installation. For more information about troubleshooting this issue, refer to the SMS product documentation. SMS Client Component Installation Manager (CCIM) failed to install client component "%1" %2 on this computer.%12 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.
SMS Client Component Installation Manager (CCIM) failed to deinstall client component "%1" on this computer.%12 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.
SMS Client Component Installation Manager (CCIM) failed to upgrade client component "%1" %2 on this computer.%12 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.
SMS Client Component Installation Manager (CCIM) failed to verify the installation of client component "%1" %2 on this computer.%12 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. SMS Client Component Installation Manager (CCIM) encountered an error while attempting to use the file "%1".%12 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." SMS Client Component Installation Manager (CCIM) cannot generate the client's heartbeat discovery data record (DDR) file, "%1".%12 Possible cause: Low disk space. Solution: Free up some disk space on the client computer. SMS Client Component Installation Manager (CCIM) encountered an error while reading the site's client component offer data from "%1".%12 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. SMS Client Component Installation Manager (CCIM) encountered an error while trying to copy the site's client component data files from "%1".%12 Solution: Check the client account permissions to verify that the client has read permission to the Clifiles.box directory.
SMS Client Component Installation Manager (CCIM) encountered an error while trying to copy the site's client component configuration files from "%1".%12 Solution: Check the client account permissions to verify that the client has read permission to the Clicomp.box directory. SMS Client Component Installation Manager (CCIM) encountered an error while trying to get execution information from SMS Available Programs Manager (APM) for client component "%1", command "%2".%12 Possible cause: Either APM is not running or the inter-process communication (IPC) mechanism might not be working. 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." SMS Client Component Installation Manager (CCIM) encountered an error while trying to send client component "%1", command "%2" to SMS Available Programs Manager (APM).%12 Possible cause: Either APM is not running or the inter-process communication (IPC) mechanism might not be working. 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."
SMS Client Component Installation Manager (CCIM) encountered an error while trying to run the following client component command(s): %1 %12 Solution: See SMS Available Programs Manager (APM) status messages for specific information. SMS Available Programs Manager (APM) has not executed the following SMS client component command(s) within the hour: %1.%12 Solution: See APM status messages for specific information.
SMS Client Component Installation Manager (CCIM) has postponed client-agent maintenance operations on this client computer. The postponed operations include upgrades, verifications, and deinstallations of the current client agents. SMS Client Component Installation Manager (CCIM) has detected an earlier version of the SMS client (version 1.2 or earlier). SMS does not support automatic upgrade for this client. The client installation will proceed normally, but SMS will not remove the files for the previous version of the client. Although client functionality will be unaffected, remote control of this client may not work until you remove the old client files from the computer. Solution: Before deploying SMS 2003 in your organization, uninstall the files for earlier versions of the SMS client.
A new SMS GUID has been generated for this computer: %1. The previous GUID for this computer was: %2. The new GUID generated for this computer is: %3. SMS Client Component Installation Manager (CCIM) has successfully moved client %1 from site %2 to site %3. SMS Client Component Installation Manager (CCIM) failed to move client %1 from site %2 to site %3. SMS Hardware Inventory Agent successfully collected hardware inventory from this computer, created a Management Information Format (MIF) file representing the collected data, and instructed Copy Queue to move the MIF file to a client access point (CAP). The Inbox Manager or Inbox Manager Assistant will move the file from the Client Access Point to the site server. If this is a primary site, the Inventory Data Loader will store the data in the SMS site database. If this is a child site, the Inventory Data Loader will also replicate the data to the parent site. SMS Hardware Inventory Agent cannot connect to the Common Information Model Object Manager (CIM Object Manager).%12 Possible cause: Windows Management Instrumentation (Winmgmt) may not be running properly on the client. Solution: Verify that the WinMgmt service is installed and running on the client.
SMS Hardware Inventory Agent cannot open the "%1" namespace.%12 Possible cause: Windows Management Instrumentation (Winmgmt) might not be running properly on the client. Solution: Verify that the WinMgmt service is installed and running on the client. The "%1" namespace has been removed or has become corrupted.%12 Possible cause: The SMS Hardware Inventory Agent cannot continue to function in this state and might need to be reinstalled. Solution: Reinstall the Hardware Inventory Agent on this client. SMS 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 Possible cause: The Hardware Inventory Agent requires at least 3 MB of virtual memory and 500 KB of disk space to begin the inventory cycle. Solution: Add additional memory or disk space to the client. The SMS 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 SMS Hardware Inventory Agent cannot update the SMS Hardware Inventory Schema.%12 Possible cause: The Hardware Inventory Agent cannot compile either the new Managed Object Format (MOF) file from site "%1" or the default MOF file. The agent cannot continue to function in this state. A request to verify the installation of the agent has been issued. Solution: Reinstall the Hardware Inventory Agent.
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 Possible cause: If the file sms_def.mof was updated to change the SMS Inventory Schema, a syntax error might have been introduced. Solution: Verify the syntax of the MOF file by using Mofcomp tool with the -check flag parameter enabled. SMS Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12 Possible cause: This MIF file exceeds the maximum third-party MIF size. Solution: The maximum MIF file size is configurable and is provided to allow greater control over third-party MIF files. Decrease the size of your MIF file. SMS Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12 Possible cause: There might be an error in the MIF file. Solution: During parsing, the following error was reported - "%3". Fix the error on the reported line. SMS Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12 Possible cause: This MIF file is attempting to update the "System" or "Personal Computer" architectures, which are restricted to SMS. For security reasons, third-party MIF files are not permitted to update the "System" or "Personal Computer" architectures. Solution: Reconfigure the MIF file so that it will not attempt to update the "System" or "Personal Computer" architectures. SMS Hardware Inventory Agent is unable to locate the Windows Management Instrumentation (WinMgmt) service.%12 Solution: Verify that the WinMgmt service is installed and running on the client.
SMS Software Inventory Agent successfully collected software inventory from this computer, created a Software Inventory (SINV) file representing the collected data, and instructed Copy Queue to move the file to a client access point (CAP). The Inbox Manager or Inbox Manager Assistant will move the file from the CAP to the site server. If this is a primary site, the Software Inventory Processor will store the data in the SMS site database. If this is a child site, the Software Inventory Processor will also replicate the data to the parent site.%12
SMS 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 Possible cause: The Software Inventory Agent requires at least 3 MB of virtual memory and 500 KB of disk space to begin the inventory cycle. Solution: Add additional memory or disk space to the client. SMS Software Inventory Agent could not collect one or more files.%12 Possible cause: Software Inventory Agent needs to make a copy of each collected file before the files can be collected. There is insufficient disk space to allow this second copy to be made. As a result, some files that match the file collection criteria might not be collected on this inventory cycle. Either this client has insufficient disk space, or the file collection criteria specifies the collection of too many files. Solution: Increase disk space on the client, or specify that fewer files be collected. SMS 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 Possible cause: Software Inventory Agent is limited in the total collected file size. This limit has been reached. As a result, some files that match the file collection criteria might not be collected on this inventory cycle. Solution: Use the "Reconfigure the maximum data collected per client (MB)" option on the File Collection tab of the Software Inventory Client Agent Properties dialog box in the SMS Administrator console.
SMS Software Inventory Agent raised an exception while attempting to extract file version information from file "%1".%12 Possible cause: The exception was non-fatal, and the agent will continue processing. The file that caused the exception may be corrupt. Solution: Remove the file from this client to prevent further problems. SMS Software Inventory Agent successfully collected %1 files, totally %2 KB of data, from this computer. These files will be transfered to the SMS Site Server as part of the Software Inventory (SINV) file.%12 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 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 Inventory was collected successfully on this computer. The agent completed in %1 minutes, %2 seconds.%12 Inventory was collected successfully on this computer. The agent completed in %1 minutes, %2 seconds and generated inventory data report %3. %12 The agent encountered an error while querying WMI to collect data from this computer. The first query to fail was "%1".%12 The agent encountered an error while collecting data from this computer. The agent encountered an error while generating the inventory report (%1) for this computer.%12 The SMS Advanced client was installed. The current version is %1.%12 The SMS Advanced client was uninstalled.%12 The SMS Advanced client was upgraded. The current version is %1.%12 The client failed to download policy. The data transfer service returned "%2" (%1).%12 The SMS Advanced client was reassigned. The previous site code was "%1". The new site code is "%2".%12
The SMS Advanced 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 An attempt to assign the SMS Advanced client to site "%1" failed. The site code could not be verified.%12 The SMS Advanced client is already assigned to site "%1". The client site assignment was not changed.%12 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 The SMS Advanced client was repaired. The current version is %1.%12 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 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 The SMS Service Host (CCMEXEC) was unable to update certificate information in the Active Directory.%12 The SMS Service Host (CCMEXEC) successfuly updated certificate information in the Active Directory. %12 The SMS Advanced client was installed but may require a reboot for the installation to complete.%12
The SMS Service Host (CCMEXEC) encountered a failure (%1) when performing Certificate operations.%12 Possible cause: The ACLs on the Certificate store are incorrect. Solution: Verify that the ACLs on the Certificate store are correct. If not, fix the ACLs appropriately. Possible cause: Encryption is not supported on this version of the Operating System. Solution: Refer to the SMS Documentation on supported Operating Systems. Possible cause: The Certificate Store is corrupted. Solution: Refer to the Windows Documentation on troubleshooting this. The SMS Client generated a new SMS Unique Identifier. The old SMS Unique ID was %2. The new SMS Unique ID is %1.%12 The ConfigMgr Advanced Client rejected the site server signing certificate due to a revocation-related failure (%1).%12 The ConfigMgr Advanced Client rejected the site server signing certificate due to an expiration-related failure (%1).%12 The ConfigMgr Advanced Client rejected the site server signing certificate due to a trust-related failure (%1).%12 The ConfigMgr Advanced Client encounted an SSL-related failure (%1) when using BITS to access location %2.%12 The ConfigMgr Advanced Client received policy that could not be verified. For more information see PolicyAgent.log on the client machine.%12 The ConfigMgr Advanced Client encountered a certificate for Management Point %1 that could not be verified.%12 SMS 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 SMS Software Metering Agent failed to create %1 usage data file, error code %2.%12 SMS Software Metering Agent failed to upload %1 usage data file, error code %2. The agent will retry later to upload this file.%12 SMS Software Metering Agent successfully processed %1 usage data files.%12
SMS Software Metering Agent failed to download %1 rule file, error code %2. The agent will retry later to download this file.%12 SMS Software Metering Agent unable to open %1 rule file, error code %2.%12 SMS Software Metering Agent successfully processed %1 rule file.%12 SMS Software Metering Agent successfully received rule %1 for program %2, version %3.%12 Client agent settings policy received.%12 Invalid client agent settings policy received.%12 Client agent settings policy is not trusted.%12 Software Distribution Policy received for Advertisement %1 (Package %2).%12 Invalid Software Distribution Policy received for Advertisement %1 (Package %2).%12 Software Distribution Policy received for Advertisement %1 (Package %2) is not trusted.%12 Package Location response received for Advertisement %1 (Package %2).%12 Invalid Package Location response received for Advertisement %1 (Package %2).%12 Starting content download for package %1 (Advertisement %2).%12 Successfully downloaded content for package %1 (Advertisement %2).%12 Content download failed for package %1 (Advertisement %2).%12 Download aborted due to poor connectivity.%12 Attempting to execute command line %1.%12 The program for Advertisement %1 (Package %2) executed successfully.%12 The program for Advertisement %1 (Package %2) failed. A non zero exit code of %3 was returned.%12 Downloaded content for package %1 (Advertisement %2) but the package content's hash verification failed.%12 Hardware inventory initiated.%12 Hardware inventory failed.%12 Hardware inventory succeeded.%12 Device Client failed to refresh site server signing certificate (SSSC).%12 Device Client successfully refreshed site server signing certificate (SSSC).%12 Software inventory initiated.%12 Software inventory failed.%12 Software inventory succeeded.%12
Device Client is about to be upgraded.%12 Device Client is about to be uninstalled.%12 File collection initiated.%12 File collection succeeded.%12 File collection failed.%12 Registration of Device Client in Native Security Mode succeeded.%12 The OS Deployment agent successfully started the action %1.%12 The OS installation failed action %1 with exit code %2.%12 The OS installation has been completed successfully.%12 The OS installation failed to request distribution points from management point %1.%12 The OS installation failed because there are no distribution points available at this location.%12 The OS installation failed to connect to the distribution point %1.%12 The OS installation successfully started the Validation phase.%12 The OS installation successfully started the State Capture phase.%12 The OS installation successfully started the Preinstall phase.%12 The OS installation successfully started the Install phase.%12 The OS installation successfully started the Postinstall phase.%12 The OS installation successfully started the State Restore phase.%12 Package was succesfully downloaded from Multicast enabled DP.%12 Package failed to download from Multicast enabled DP. Error %1. Will try another DP. %12 The task sequence execution engine skipped the disabled group (%3).%12 The task sequence execution engine failed evaluating the condition for the group (%3). Error code %4.%12 The task sequence execution engine skipped the group (%3) because the condition was evaluated to be false.%12 The task sequence execution engine evaluated TRUE for the condition of the group (%3).%12 The task sequence execution engine started the group (%3).%12
The task sequence execution engine ignored execution failure in the group (%3).%12 The task sequence execution engine aborted execution for a failure in the group (%3).%12 The task sequence execution engine successfully completed the group (%3).%12 The task sequence execution engine skipped the disabled action (%2) in the group (%3).%12 The task sequence execution engine failed evaluating the condition for the action (%2) in the group (%3). Error code %4.%12 The task sequence execution engine skipped the action (%2) in the group (%3) because the condition was evaluated to be false.%12 The task sequence execution engine evaluated TRUE for the condition of the action (%2) in the group (%3).%12 The task sequence execution engine failed to start the action (%2) in the group (%3) with the win32 error code %4.%12 The task sequence execution engine successfully started the action (%2) in the group (%3).%12 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 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 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 The task sequence execution engine timeout in executing the action (%2) in the group (%3) Partial action output: %5%6%7%8.%12 The task sequence execution engine ignored execution failure of the action (%2) in the group (%3).%12 The task sequence execution engine aborted execution for a failure of the action (%2) in the group (%3).%12 The task sequence execution engine started execution of a task sequence.%12 The task sequence execution engine failed execution of a task sequence.%12 The task sequence execution engine performed a system reboot initiated by the action (%2) in the group (%3).%12 The task sequence execution engine successfully completed a task sequence.%12
The task sequence execution engine from a non-client started execution of a task sequence.%12 Task sequence version is not supported.%12 The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of %1 was returned.%12 The task sequence manager successfully completed execution of the task sequence.%12 Software updates evaluation failed: invalid syntax or value for the specified scheduled installation window (/l). Possible cause: Incorrect command line settings. Solution: Review the program command line settings. The valid range, in minutes, is from 5 minutes greater than the value of the timeout for unresponsive updates (/t) to a maximum of 8 hours.%12 Software updates evaluation failed: could not determine the advertisement assignment schedule. This is needed to calculate the correct begin and end times for the specified scheduled installation window (/l). Possible cause: Incorrect advertisement settings. Solution: Verify that the advertisement assignment schedule is correct and that users are not allowed to run the program independently of assignments.%12 Software updates evaluation failed: could not load software updates authorization list %1. Possible cause: authorization list not present or not valid. Solution: Verify that the authorization list, %1, is present in the package source folder and is a valid authorization list.%12
Software updates evaluation failed: could not locate the scan component of the specified software update inventory tool. The scan component advertisement might not have run on the client computer. Possible cause: Incorrect package and program name in the Scan.ini file. Solution: Verify that the package and program name specified in the scan.ini file are correct. Possible cause: Scan component was never run on client. Solution: Specify that the scan component is run in a program dependency of the software updates package. This will ensure that new client computers always run the scan component before software update installation is attempted.%12 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. Possible cause: The scan component was removed from the client cache. Solution: Re-run the advertisement for the scan component on the client computer. This will update the cache and might fix the problem. Possible cause: Unknown scan component failure. Solution: Review the status of the scan component of the specified software update inventory tool on this client.%12
Software updates evaluation failed: error loading Win32_PatchState class from WMI. Possible cause: This is most likely a transitory problem. Solution: None.%12 Software updates evaluation failed: error storing Win32_PatchState class into WMI. Possible cause: This is most likely a transitory problem. Solution: None.%12
Software updates evaluation failed: unable to load resource file. Possible cause: file not present. Solution: Verify that all files are present in the package and that distribution points have been successfully updated.%12
Software updates evaluation was ended due to a scheduled installation window violation (installation started too early.) Solution: Do nothing. The Software Updates Installation Agent will try again at the next advertisement recurrence.%12
Software updates evaluation was ended due to a scheduled installation window violation (installation started too late.) Solution: Do nothing. The Software Updates Installation Agent will try again at the next advertisement recurrence.%12
Software updates installation was rescheduled by the user.%12 Software updates installation was postponed by the user.%12 Software updates installation was automatically postponed: the user did not choose to install the updates and the grace period has not expired.%12 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
Software update installation failed: the scheduled installation window expired while software update installation was not complete. Possible cause: The scheduled installation window is not long enough. Solution: Verify that the specified scheduled installation window is long enough to accommodate the run times of all required updates in the package.%12
Software updates installation was postponed: the user rescheduled the required system restart. Possible cause: Previous installations might have replaced in-use files and are awaiting a system restart to complete installation. This restart was requested but the user of the computer has rescheduled it. Solution: Do nothing. Software update installation will be retried on the next scheduled cycle if the required restart has occurred.%12 Software updates installation was postponed: The user postponed the required pre-installation restart. Possible cause: Previous installations might have replaced in-use files and are awaiting a system restart to complete installation. This restart was requested but the user of the computer has postponed it. Solution: Restart the client computer or do nothing. Software update installation will be retried on the next scheduled cycle if the required restart has occurred.%12 Software updates installation was automatically postponed: a preinstallation restart was required, but the user did not choose to restart and the grace period has not expired. Possible cause: Previous installations might have replaced in-use files and are awaiting a system restart to complete installation. This restart was requested but the user of the computer did not allow it. Because the software updates in the current package were not yet required, the installation was postponed.%12
Software updates installation completed but the required restart was rescheduled by the user.%12 Software updates installation completed but the required restart was postponed by the user.%12 Software updates installation completed but the required restart was postponed automatically.%12 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 Software Updates Installation Agent completed successfully and suppressed the required system restart because the program was configured to suppress restarts for workstations.%12
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
Software Updates Installation Agent completed successfully and no restart was required.%12 Software update installation was postponed: awaiting system restart. Possible cause: Previous installations might have replaced in-use files and are awaiting a system restart to complete installation. Solution: Restart the client computer or do nothing. Software update installation will be retried on the next scheduled cycle if the required restart has occurred.%12 Restart of the computer is required in order for newly installed updates to take effect.%12 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 The software update was installed and a restart of the computer is required in order for the changes to take effect. Refer to the advertisement 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
The software update failed to install. Possible cause: Typically such failures are the result of internal errors within the software update itself. Solution: Review the log files generated by the software update on the client computer for additional details. Possible cause: The Software Updates Installation Agent was unable to start the software update installation program. Solution: Verify that the software update file is included in the package. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12 The software update installation did not complete within the allocated time and was stopped by the agent. Possible cause: The Software Update Installation Agent timeout settings for this package/program do not allow sufficient time for the installation. Solution: Check the command-line settings for the program and ensure that the timeout setting (/t) is sufficient. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12 The software update was started, but was cancelled during installation by the user of the computer. Solution: To prevent this, software updates can be configured with enforcement options. Consult the product documentation for details on the enforcement feature. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12 The software update installation was not attempted due to a low disk space condition. Possible cause: This software update was estimated to require %7MB, however only %8MB was available. Solution: Verify that enough disk space is available to install the updates. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12
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 The software update was installed and a restart of the computer is required in order for the changes to take effect. Refer to the advertisement 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 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 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 advertisement 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 Content download for the package "%1" - "%2" has been started.%12 Content download for the package "%1" - "%2" succeeded.%12 Content download for the package "%1" - "%2" failed.%12 Content download for the package "%1" - "%2" has been cancelled.%12 Content download for the package "%1" - "%2" failed. The download failed because the content downloaded to the client does not match the content specified in the package source.%12 Content download for the package "%1" - "%2" failed. The download failed because either there was not enough disk space to host the content or a disk was not found that satisfied the required properties.%12
Content download for the package "%1" - "%2" failed. The download failed because no NTFS partition is available. Please specify an NTFS partition to which to download the content.%12 Content download for the package "%1" - "%2" failed. The download failed because either there was not enough disk space to host the content or a disk was not found that satisfied the required properties.%12 Content download for the package "%1" - "%2" failed. The download failed because Branch DP was unable to create directory %3. The corresponding failure code is %4.%12 Content download for the package "%1" - "%2" has failed. The download failed because Branch DP was unable to create share %3. The corresponding failure code is %4.%12 Content download for the package "%1" - "%2" has failed. The download failed because Branch DP was unable to set the ACLs on share %3. The corresponding failure code is %4.%12 Content download for the package "%1" - "%2" has failed. The download failed because Branch DP was unable copy content to the directory %3. The corresponding failure code is %4.%12 Branch DP Package download policy is invalid %1. The policy may be invalid because one or more defined properties are in conflict or because one or more required properties are missing.%12 Content for the package "%1" - "%2" was not downloaded because the "Do Not Download flag" is set.%12 Content for the package was not downloaded because the content "%1" - "%2" already exists on the share %3.%12 An error was encountered while the STA file was being sent after hash matches were confirmed. The corresponding error code for this failure is %3.%12 The download did not complete successfully and the maximum number of retries (%3) has been exhausted.%12 Configuration of the background intelligent transfer service (BITS) policy will not be applied because BITS is not installed on this machine. BITS policy support is available in the BITS 2.0 and later releases. Please visit Microsoft.com for information on installing the most current version of BITS.%12
The content "%1" - "%2" is no longer available on the share %3.%12 The package "%1" - "%2" has been successfully provisioned on the share %3.%12 Maintenance Task for the package "%1" - "%2" was not started since the package is already in Active state.%12 Branch DP Agent detected a change in the BITS configuration setting. New settings have been applied.%12 Branch DP Agent detected that the BITS configuration setting has been deleted.%12 Starting package Maintenance Task for all packages.%12 Maintenance Task kicked off for the following packages: %3.%12 Maintenance Task for package "%1" was not started because the package policy does not exist.%12 The provisioning location for package "%1" - "%2" has changed from %3 share %4 to the %5 share %6.%12 The client is internet enabled, therefore can not be marked as a Branch DP.%12 The client is not domain joined, therefore can not be marked as a Branch DP.%12 The client has been enabled as a Branch DP .%12 The client has been disabled as a Branch DP .%12 The content "%1" - "%2" could not be deleted from the share %3. One or more files may be in use, or the system may not have permissions to remove the content.%12 Scan component failed: The client operating system version is not supported in this release. %2 or later is required. Type = %1.%12 Scan component failed: Cannot access cache folder or insufficient permissions to run the scan. Type = %1. Possible cause: The scanprogram may have been run without administrative rights or it cannot write to the folder %2. Solution: Verify the scan program is set torun with administrative rights using the program properties defined for this package%12
Scan component failed: Internet Explorer version is below IE5. IE 5 or later version is required. Type = %1.%12 Scan component failed: at least 10 MB free disk cache space is required. Cache location = %2. Type = %1.%12
Scan component failed: an unknown error was encountered in the scan component (type = %1). Inventory MOF results not generated. Solution: Review the relevant log files for this client computer.%12 Scan component failed (type = %1): probably due to a schema change or WMI error.%12 The software update status has been changed to installed. Possible cause: This can happen when a pending restart condition was resolved, but it can also occur if the user installed the software update independently. Solution: To determine the reason for this message, review other status messages for this software update from this client computer. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5%12 The software update status has been changed and is no longer reported as installed. Possible cause: This can happen when an update has been removed, or if the update has been re-issued and new detection rules show the old version of the update as not present. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5%12 Scan component failed(type = %1): An error was encountered while trying to read the configuration file.%12 Scan component failed(type = %1): One or more of the requirements specified for Package or Binary %2 could not be met. Type="%3", Name="%4", Condition="%5".%12 Scan component failed(type = %1): Error while trying to execute %2.%12 Scan component failed(type = %1): Error while trying to expand %2.%12 Scan component failed(type = %1): Scan.ini could not be found.%12 Scan started for scan component (type=%1).%12 Failed to launch scan component (type=%1). Possible reasons scan tool not registered with client.%12
Completed scanning with scan component (type=%1).%12 Scan component (type=%1) has been forcibly terminated for scan as scan didn't finish in the expected duration.%12 Scan component (type=%1) has not yet started because the scan tool content "%2" - "%3" has not been acquired. Possible cause: The content must be downloaded into the computer's cache, or the content could not be located. Solution: If the content is being downloaded, no action is required. Scanning will start once the download has been successfully completed. If the content can not be located, ensure that a distribution point with this content is available for this computer.%12 Scan component (type = %1) has failed because content download for scan tool content "%2" - "%3" has failed. Possible cause: The content can not be found on the network, or the content could not be accessed. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters.%12 Scan component (type=%1) requires content "%2" - "%3" to be downloaded, but the total cache size is smaller than the size of the content. The current cache size is %4 MB, and %5 MB of cache space is available. This program requires %6 MB to be available in the cache. Solution: Increase the size of the cache.%12 Scan component (type=%1) requires package content to be downloaded, but the cache does not have enough space. 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 scan component requires %5 MB to be available in the cache. Solution: Increase the size of the cache, or remove other content from the cache, or increase the amount of free disk space.%12
Scan component (type=%1) failed. A failure code of %2 was returned.%12 Scan component (type=%1) Update Source registration failed. A failure code of %2 was returned.%12
Scan component (type=%1) rejected a scan request because the existing scan agent is not supported. This version of the product only supports scanning by using the Windows Update Agent.%12 Scan component (type=%1) 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 Synchronization component failed: SMS Site Code is not specified. Type = %1.%12 Synchronization component failed: Package ID is not specified. Type = %1.%12 Synchronization component failed: SMS Site Name is not specified. Type = %1.%12 Synchronization component failed: package source folder is not specified. Type = %1.%12 Synchronization component failed: Unable to write to %2. Type = %1. Possible cause: Typically, this error results when the software update inventory tool synchronization component does not have network access to the package source folder for package ID %3. Solution: To prevent this, keep the package source folder on the same computer as the synchronization component.%12
Synchronization component failed: Unable to read from %2. Type = %1. Possible cause: Typically, this error results when the software update inventory tool synchronization component does not have network access to the package source folder for package ID %3. Solution: To prevent this, keep the package source folder on the same computer as the synchronization component.%12
Synchronization component failed: the synchronization component (type = %1) failed to download %2, error code: %3. Possible cause: Typically, this error results when the user account running the synchronization component does not have access to the Internet. Solution: Consider changing the proxy configuration to allow anonymous connections or specific IP addresses, or consult the product documentation on the use of the SMSPatchDownloader.ini file to configure specific proxy settings on the client computer that runs the catalog download.%12
Software update catalog (type = %1) sync operation completed successfully. Newer version of catalog was downloaded and updated on distribution points.%12 Synchronization component failed: the synchronization component failed to update the Distribution Points for the catalog (type = %1). Error code: %2. Solution: Consider the use of the /unattend command line option and a separate update schedule for this package.%12 Synchronization component failed: the synchronization component failed to update the Site Database for the catalog (type = %1). See the log file for details.%12 Software update catalog (type = %1) sync operation completed successfully. Newer version of catalog was not available.%12 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 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 Version of device client on attached device is newer. No action taken.%12 No device client action specified. No action taken.%12 Device client installation completed successfully.%12 Device client upgrade completed successfully.%12 Installed device client state verified and settings enforced.%12 Device client uninstallation completed successfully.%12
Device client installation completed successfully and certificate enrollment was not required.%12 Device client upgrade completed successfully and certificate enrollment was not required.%12 Installed Device client state verified, settings enforced and certificate enrollment was not required.%12 Device client installation completed successfully. Certificate installation and/or enrollment failed. Check DmInstaller.log on the Device Client for detailed error information.%12 Device client upgrade completed successfully. Certificate installation and/or enrollment failed. Check DmInstaller.log on the Device Client for detailed error information.%12 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 Device client deployment action failed. Failed to establish ActiveSync connection to device.%12 Device client deployment action failed. Invalid client settings file.%12 Device client deployment action failed. Error determining running directory for DmClientXfer.exe.%12 Device client deployment action failed. Required ActiveSync libraries missing.%12 Device client deployment action failed. Could not determine processor type of attached device.%12 Device client deployment action failed. Could not determine base operating system version of attached device.%12 Device client deployment action failed. Error determining client version for attached device.%12 Device client deployment action failed. Error creating client settings .ini file.%12 Device client deployment action failed. Failed copying files to attached device.%12 Device client deployment action failed. Failed executing client installer program on attached device.%12 Device client deployment action may have failed. Failed reading status information from device.%12 Device client deployment action failed. Error determining running directory for client installer program.%12 Device client deployment action failed. Error executing pre-install command line.%12
Device client deployment action failed. Error executing postinstall command line.%12 Device client installation or upgrade failed. Error during uninstallation of previous client.%12 Device client installation or upgrade failed. Invalid client settings file.%12 Device client installation or upgrade failed. Error installing client CAB file.%12 Device client installation or upgrade failed. Error starting client service.%12 Device client installation or upgrade failed. Error updating client settings.%12 Device Client Deployment failed with unknown error.%12 Device client verification or repair failed. Error during uninstallation of previous client.%12 Device client verification or repair failed. Invalid client settings file.%12 Device client verification or repair failed. Error installing client CAB file.%12 Device client verification or repair failed. Error starting client service.%12 Device client verification or repair failed. Error updating client settings.%12 Device client verification or repair failed. Error restoring required files.%12 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 Encountered unknown error installing the device client.%12 Device client setup failed to launch during install.%12 Device client uninstallation failed. Error using unload.exe to uninstall the existing client.%12 Device client install/upgrade failed. Error enforcing new client. Device rolled back to old client (if existed before).%12 Device client rollback failed during unsuccessful upgrade. Error enforcing old client. Need to freshly install the client.%12 Device client failed to perform post cab install actions. Device client installation failed.%12 The Component "%1" encountered an error %2 of category "%3" at %4.%12 Scan tool %2 for the update %1 not available.
Scan tool %2 for the update %1 failed.%12 The contents hash for the update %1 provided in policy does not match with the contents downloaded. The contents for update %1 could not be located.%12 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.
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. Failed to download contents for update %1.%12 Update %1 cannot be attempted due to invalid commandline = %2. Update %1 application failed with returned exit code = %2. Update %1 did not finish in allocated time %2 minutes. Creation of process failed for update %1.%12 Commandline = %2 Failed to get installer path for the update %1.%12 Failed to monitor process for update %1 after service restart.%12 SMS internal error occurred for the update %1.%12 Bundle update "%1" failed to get content for update "%2". Please check the enforcement status of update "%2" to get further details.%12 Bundle update "%1" failed to install update "%2". Please check the enforcement status of update "%2" to get further details.%12 Bundle update "%1" failed to evaluate the applicability of its leaf updates.%12
Update "%1" failed to install as no current or future maintenance window is available to accomodate this update with max runtime = %2.%12 Possible Cause: The duration for the maintenance window is shorter than the maximum runtime specified for this update. Solution: modify the duration of the maintenance window or add another maintenance window that is long enough in duration to accomodate the maximum runtime of this update. Possible Cause:There is only one maintenance window defined for this computer, and it is a one-time maintenance window that occurs in the past. Solution: You can delete the maintenance window if it is no longer applicable, or you can disable the maintenance window. You can also add another maintenance window for this computer, and allow the update to run according to the new maintenance window schedule. Possible Cause: The deployment is not set to override maintenance window. Solution: Update the deployment to override maintenance windows. Note: setting the override flag will cause the system to install the update at the deadline and may cause the system to restart if enforcement job failed for assignment %1.%12 Updates required. Updates failures occured during enforcement for assignment %1.%12 Some updates are still non-compliant after enforcemet completion of the assignment %1. Post restart updates compliance checking failed.%12 Failed to initiate enforcement of assignment %1.%12 Failed to initiate updates evaluation for assignment %1.%12 Updates evaluation job completed with failure for assignment %1.%12 Invalid policy received for assignment %1. Failed to initiate updates advance download for assignment %1.%12 Updates advance download job completed with failure for assignment %1.%12
No maintenance window is defined to accommodate at least one update in the deployment %1. Possible Cause:There is only one maintenance window defined for this computer, and it is a one-time maintenance window that occurs in the past. Solution: You can delete the maintenance window if it is no longer applicable, or you can disable the maintenance window. You can also add another maintenance window for this computer, and allow the update to run according to the new maintenance window schedule. Possible Cause: The deployment is not set to override maintenance window. Solution: Update the deployment to override maintenance windows. Note: setting the override flag will cause the system to install the update at the deadline and may cause the system to restart if required. %12 Failed to download baseline CI Id %1, version %2. The contents hash for baseline CI Id %1, version %2 provided in policy does not match with the contents downloaded. Cannot further process baseline CI Id %1, version %2. Managed client does not have the .Net framework version 2.0 installed. Failed to download baseline content %4 (%3), version %5. The contents hash for baseline content %4 (%3), version %5 provided in policy does not match with the contents downloaded. Failed to evaluate baseline content %4 (%3), version %5. %6.%12 Failed to report compliance state for baseline content %4 (%3), version %5.%12 Baseline content %4 (%3), version %5 which was previously noncompliant or had no prior discovery information is now compliant. Baseline content %4 (%3), version %5 which was previously compliant, had no prior discovery information, or a different noncompliance severity is now non-compliant with 'Informational' severity.
Baseline content %4 (%3), version %5 which was previously compliant, had no prior discovery information, or a different noncompliance severity is now non-compliant with 'Warning' severity Baseline content %4 (%3), version %5 which was previously compliant, had no prior discovery information, or a different noncompliance severity is now non-compliant with 'Critical' severity. Baseline CI Id %1, version %2 could not be decompressed. Baseline content %4 (%3), version %5 could not be decompressed. Internal error - cannot further process baselince CI Id %1, version %2. Internal error - cannot further process baseline content %4 (%3), version %5. Failed to launch discovery process for baseline content %4 (%3), version %5. Discovery process crashed for baseline content %4 (%3), version %5. Baseline content %4, version %5 has model violations. Baseline content %4, version %5 encountered one or more errors during discovery. Download of baseline CI Id %1, version %2 timed out. Download of baseline content %4 (%3), version %5 timed out. The task sequence execution engine successfully installed (%6) package (%5) for action (%2) in the group (%3) with exit code %4.%12.%12 The task sequence execution engine failed to install (%6) package (%5) for action (%2) in the group (%3) with exit code %4.%12.%12 The out-of-band management agent successfully started the configuration at (%4).%12.%12 The out-of-band management agent failed to start the configuration in action (%1) with error code %2(%3).%12.%12 The virtual application package %2 has been registered on the client successfully for advertisement %1. [SCCM package ID = %4] [Virtual app package GUID = %3] The virtual application package %2 failed to register on the client for advertisement %1. The error message is: [%5] and error code is: [%6]. [SCCM package ID = %4] [Virtual app package GUID = %3]
The virtual application package %2 is pending registration as the package is currently in use on the client. [Advertisement ID = %1] [SCCM package ID = %4] [Virtual app package GUID = %3] The virtual application package %1 has been deleted from the client successfully. [SCCM package ID = %3] [Virtual app package GUID = %2] The virtual application package %1 failed to be deleted from the client. The error message is: [%4] and error code is: [%5]. [SCCM package ID = %3] [Virtual app package GUID = %2] The virtual application package %1 is pending deletion, as the package is currently in use on the client. [SCCM package ID = %3] [Virtual app package GUID = %2] The virtual application %1 failed to launch on the client. The error message is: [%2] and error code is: [%3]. The softgrid client is not installed on this machine. The application virtualization management feature is disabled.
Symbolic Name
CLIMSG_APA_ERROR_OFFER_DATA_INTEGRITY
CLIMSG_APA_ERROR_PACKAGE_DATA_INTEGRITY
CLIMSG_APA_INFO_OFFER_RECEIVED
CLIMSG_APA_ERROR_BAD_ENVIRONMENT
CLIMSG_APA_ERROR_UNABLE_TO_EXECUTE_PROGRAM
CLIMSG_APA_INFO_PROGRAM_STARTED
CLIMSG_APA_ERROR_PROGRAM_ERROR
CLIMSG_APA_ERROR_PROGRAM_ERROR_STATUS
CLIMSG_APA_INFO_NO_PROGRAM_ERROR
CLIMSG_APA_INFO_NO_PROGRAM_ERROR_STATUS
CLIMSG_APA_ERROR_REMOVAL_BAD_ENVIRONMENT
CLIMSG_APA_ERROR_UNABLE_TO_EXECUTE_REMOVAL
CLIMSG_APA_INFO_REMOVAL_STARTED
CLIMSG_APA_ERROR_REMOVAL_ERROR
CLIMSG_APA_ERROR_REMOVAL_ERROR_STATUS
CLIMSG_APA_INFO_NO_REMOVAL_ERROR
CLIMSG_APA_INFO_NO_REMOVAL_ERROR_STATUS
CLIMSG_APA_ERROR_INVALID_REMOVAL_KEY
CLIMSG_APA_INFO_OFFER_REJECTED_PLATFORM
CLIMSG_APA_INFO_OFFER_REJECTED_EXPIRED
CLIMSG_APA_INFO_OFFER_DEFERRED_SLOWLINK
CLIMSG_APA_ERROR_PROGRAM_ERROR_RESTART
CLIMSG_APA_INFO_PRELIM_NO_PROGRAM_ERROR
CLIMSG_APA_INFO_DOWNLOAD_STARTED CLIMSG_APA_INFO_DOWNLOAD_COMPLETE CLIMSG_APA_ERROR_DOWNLOAD_FAILED
CLIMSG_APA_INFO_CONTENT_REMOVED
CLIMSG_APA_INFO_CACHE_SIZE_MODIFIED
CLIMSG_APA_INFO_CACHE_PURGED
CLIMSG_APA_INFO_CACHE_LOCATION_MODIFIED
CLIMSG_APA_ERROR_HASH_MISMATCH
CLIMSG_APA_INFO_DOWNLOAD_CANCELLED
CLIMSG_APA_INFO_PROGRAM_CANCELED
CLIMSG_APA_INFO_WAITING_FOR_CONTENT
CLIMSG_APA_INFO_WAITING_FOR_USER_ENVIRONMENT
CLIMSG_APA_INFO_WAITING_FOR_ANOTHER_PROGRAM
CLIMSG_APA_INFO_WAITING_PAUSED
CLIMSG_APA_INFO_PROGRAM_HAS_RUN_BEFORE_WITHOUT_FAILURE
CLIMSG_APA_INFO_PROGRAM_HAS_RUN_BEFORE_WITHOUT_SUCCESS
CLIMSG_APA_INFO_PROGRAM_HAS_RUN_BEFORE
CLIMSG_APA_INFO_PROGRAM_HAS_NOT_RUN_BEFORE
CLIMSG_APA_WARNING_INSUFFICIENT_CACHE
CLIMSG_APA_ERROR_NO_ELEVATED_MSI
CLIMSG_APA_ERROR_INSUFFICIENT_CACHE_SIZE
CLIMSG_APA_ERROR_NO_CONTENT
CLIMSG_APA_ERROR_INVALID_POLICY
CLIMSG_APA_ERROR_ADVERT_DOWNLOAD_FAILED
CLIMSG_APA_ERROR_INSUFFICIENT_CACHE
CLIMSG_APA_WARNING_BAD_ENVIRONMENT
CLIMSG_APA_WARNING_UNABLE_TO_EXECUTE_PROGRAM
CLIMSG_APA_ERROR_ADVERT_HASH_MISMATCH
CLIMSG_APA_ERROR_LOCATION_AND_DOWNLOAD_FAILED
CLIMSG_APA_WARNING_NO_CONTENT
CLIMSG_APA_WARNING_ADVERT_DOWNLOAD_FAILED
CLIMSG_APA_WARNING_LOCATION_AND_DOWNLOAD_FAILED
CLIMSG_APA_ERROR_MAX_RUN_TIME_EXCEEDED
CLIMSG_APA_ERROR_CANNOT_MONITOR
CLIMSG_APA_WARNING_PROGRAM_ERROR
CLIMSG_APA_INFO_WAITING_FOR_SERVICE_WINDOW
CLIMSG_APA_ERROR_PROGRAM_MAY_NEVER_RUN
CLIMSG_APA_INFO_REBOOT_WAITING_FOR_SERVICE_WINDOW
CLIMSG_APA_INFO_REBOOT_PERFORMED_OUTSIDE_OF_SERVICE_WINDOW
CLIMSG_APA_INFO_WAITING_CONTENT_AVAILABILITY_ON_LOCAL_DP
CLIMSG_APA_ERROR_INTERNET_BASED_CLIENT_CANNOT_RUN_FROM_NET
CLIMSG_APA_ERROR_SYSTEM_MAY_NEVER_REBOOT
CLIMSG_APA_ERROR_INTERNET_BASED_CLIENT_CANNOT_RUN_OSD_TS
CLIMSG_APA_INFO_MSI_SOURCE_UPDATE_SUCCESS CLIMSG_APA_WARNING_MSI_SOURCE_UPDATE_ERROR
CLIMSG_APA_ERROR_MSI_SOURCE_UPDATE_ERROR
CLIMSG_APA_WARNING_MSI_SOURCE_UPDATE_LS_ERROR
CLIMSG_APA_ERROR_MSI_SOURCE_UPDATE_LS_ERROR
CLIMSG_CCIM_ERROR_FILE_CORRUPTED
CLIMSG_CCIM_ERROR_HEARTBEAT_DDR
CLIMSG_CCIM_WARNING_SITE_OFFER_DATA_UPDATE
CLIMSG_CCIM_WARNING_SITE_DATA_FILES_UPDATE
CLIMSG_CCIM_WARNING_SITE_CFG_FILES_UPDATE
CLIMSG_CCIM_ERROR_GET_APM_INFO
CLIMSG_CCIM_ERROR_SEND_APM_INFO
CLIMSG_CCIM_ERROR_PROCESS_CLICOMP_OFFERS
CLIMSG_CCIM_WARNING_CLICOMP_PENDING
CLIMSG_CCIM_INFO_CLICOMP_UPGRADE
CLIMSG_CCIM_INFO_CLICOMP_VERIFY
CLIMSG_CCIM2_INFO_CLI_INSTALLED
CLIMSG_CCIM2_INFO_CLI_DEINSTALLED
CLIMSG_CCIM2_INFO_CLI_ASSIGNED
CLIMSG_CCIM2_INFO_CLI_UNASSIGNED
CLIMSG_CCIM2_INFO_CLICOMP_INSTALLED
CLIMSG_CCIM2_INFO_CLICOMP_UPGRADED
CLIMSG_CCIM2_INFO_CLICOMP_VERIFIED
CLIMSG_CCIM2_INFO_CLICOMP_DEINSTALLED
CLIMSG_CCIM2_INFO_CLICOMP_INSTALLED_NOT_AVAIL
CLIMSG_CCIM2_ERROR_CLICOMP_INSTALL_FAILED
CLIMSG_CCIM2_ERROR_CLICOMP_DEINSTALL_FAILED
CLIMSG_CCIM2_ERROR_CLICOMP_UPGRADE_FAILED
CLIMSG_CCIM2_ERROR_CLICOMP_VERIFY_FAILED
CLIMSG_CCIM2_ERROR_FILE_CORRUPTED
CLIMSG_CCIM2_ERROR_HEARTBEAT_DDR
CLIMSG_CCIM2_WARNING_SITE_OFFER_DATA_UPDATE
CLIMSG_CCIM2_WARNING_SITE_DATA_FILES_UPDATE
CLIMSG_CCIM2_WARNING_SITE_CFG_FILES_UPDATE
CLIMSG_CCIM2_ERROR_GET_APM_INFO
CLIMSG_CCIM2_ERROR_SEND_APM_INFO
CLIMSG_CCIM2_ERROR_PROCESS_CLICOMP_OFFERS
CLIMSG_CCIM2_WARNING_CLICOMP_PENDING
CLIMSG_CCIM2_INFO_CLICOMP_POSTPONED
CLIMSG_CCIM2_WARN_CLI1X_DETECTED
CLIMSG_CCIM2_INFO_GUID_CHANGED
CLIMSG_CCIM2_INFO_SITE_CHANGE CLIMSG_CCIM2_WARN_SITE_CHANGE CLIMSG_HINV_INFO_INVENTORY_COLLECTED_SUCCESSFULLY
CLIMSG_HINV_ERROR_CIMOM_CONNECTION
CLIMSG_HINV_ERROR_OPEN_NAMESPACE
CLIMSG_HINV_ERROR_CORRUPT_NAMESPACE
CLIMSG_HINV_WARNING_RESOURCES
CLIMSG_HINV_INFO_SCHEMA_UPDATE
CLIMSG_HINV_ERROR_SCHEMA_UPDATE_FATAL
CLIMSG_HINV_ERROR_SCHEMA_UPDATE
CLIMSG_HINV_WARNING_BAD_MIF_SIZE
CLIMSG_HINV_ERROR_BAD_MIF_SYNTAX
CLIMSG_HINV_ERROR_BAD_MIF_SECURITY
CLIMSG_HINV_ERROR_CIMOM_INSTALLED
CLIMSG_SINV_INFO_INVENTORY_COLLECTED_SUCCESSFULLY
CLIMSG_SINV_WARNING_RESOURCES
CLIMSG_SINV_WARNING_FILECOL_RESOURCES
CLIMSG_SINV_WARNING_FILECOL_MAXIMUM
CLIMSG_SINV_WARNING_FILEVER_EXCEPTION
CLIMSG_SINV_INFO_INVENTORY_COLLECTED_FILES_SUCCESSFULLY
CLIMSG_FILECOLLAGT_INFO_INVENTORY_COLLECTED_FILES_SUCCESSFULLY
CLIMSG_FILECOLLAGT_WARNING_FILECOL_MAXIMUM
CLIMSG_INVAGT_INFO_INVENTORY_COLLECTED_SUCCESSFULLY CLIMSG_INVAGT_INFO_GENERIC_COLLECTED_SUCCESSFULLY
CLIMSG_INVAGT_WARNING_QUERYFAILURE
CLIMSG_INVAGT_ERROR_WMIFAILURE CLIMSG_INVAGT_ERROR_REPORT_FAILURE CLIMSG_REMOTECLIENT_INFO_INSTALLED CLIMSG_REMOTECLIENT_INFO_UNINSTALLED CLIMSG_REMOTECLIENT_INFO_UPGRADED CLIMSG_REMOTECLIENT_POLICYAGENT_BITSPOLICYDOWNLOADFAILED CLIMSG_REMOTECLIENT_INFO_REASSIGNED
CLIMSG_REMOTECLIENT_POLICYAGENT_POLICYMISMATCH
CLIMSG_REMOTECLIENT_WARNING_CLIENTNOTASSIGNED CLIMSG_REMOTECLIENT_INFO_ASSIGNMENTUNCHANGED CLIMSG_REMOTECLIENT_POLICYAGENT_COMPILEFAILURE
CLIMSG_REMOTECLIENT_INFO_REPAIRED CLIMSG_REMOTECLIENT_WARNING_LOWMEMORYMODE_ENTER
CLIMSG_REMOTECLIENT_INFO_LOWMEMORYMODE_RECOVER
CLIMSG_REMOTECLIENT_CERTUPDATE_FAILURE CLIMSG_REMOTECLIENT_CERTUPDATE_SUCCESS CLIMSG_REMOTECLIENT_INFO_INSTALL_PENDINGREBOOT
CLIMSG_REMOTECLIENT_CERTIFICATEOPERATIONS_FAILURE
CLIMSG_REMOTECLIENT_NEW_SMSID_GENERATED
CLIMSG_REMOTECLIENT_ERROR_REVOKED_SITE_SIGNING_CERTIFICATE
CLIMSG_REMOTECLIENT_ERROR_EXPIRED_SITE_SIGNING_CERTIFICATE
CLIMSG_REMOTECLIENT_ERROR_UNTRUSTED_SITE_SIGNING_CERTIFICATE CLIMSG_REMOTECLIENT_ERROR_DATATRANSFERSERVICE_BITS_SECURE_FAILURE
CLIMSG_REMOTECLIENT_POLICYAGENT_ERROR_NATIVE_MODE_POLICY_AUTHORIZATION_FAILURE
CLIMSG_REMOTECLIENT_ERROR_MP_CROSS_SIGNATURE_VERIFICATION_FAILURE CLIMSG_SWMETER_ERROR_USAGE_WMIFAILURE
CLIMSG_SWMETER_ERROR_USAGE_CREATE_FAILED CLIMSG_SWMETER_WARNING_USAGE_UPLOAD_FAILED
CLIMSG_SWMETER_INFO_USAGE_PROCESSED
CLIMSG_SWMETER_WARNING_RULE_DOWNLOAD_FAILED
CLIMSG_SWMETER_ERROR_RULE_OPEN_FAILED CLIMSG_SWMETER_INFO_RULE_PROCESSED CLIMSG_SWMETER_INFO_RULE_RECEIVED CLIMSG_DEVICECLIENT_INFO_AGENT_SETTINGS_RECEIVED CLIMSG_DEVICECLIENT_ERROR_INVALID_AGENT_SETTINGS CLIMSG_DEVICECLIENT_ERROR_AGENT_SETTINGS_NOT_TRUSTED CLIMSG_DEVICECLIENT_INFO_SWDIST_POLICY_RECEIVED CLIMSG_DEVICECLIENT_ERROR_BAD_SWDIST_POLICY CLIMSG_DEVICECLIENT_ERROR_SWDIST_POLICY_NOT_TRUSTED CLIMSG_DEVICECLIENT_INFO_LOC_RESPONSE_RECEIVED CLIMSG_DEVICECLIENT_ERROR_BAD_LOC_RESPONSE CLIMSG_DEVICECLIENT_INFO_DOWNLOAD_START CLIMSG_DEVICECLIENT_INFO_DOWNLOAD_SUCCESS CLIMSG_DEVICECLIENT_ERROR_DOWNLOAD_FAIL CLIMSG_DEVICECLIENT_WARNING_DOWNLOAD_ABORTED CLIMSG_DEVICECLIENT_INFO_START_EXECUTION CLIMSG_DEVICECLIENT_INFO_EXECUTION_SUCCESS CLIMSG_DEVICECLIENT_ERROR_EXECUTION_FAIL CLIMSG_DEVICECLIENT_ERROR_HASH_VERIFICATION_FAIL CLIMSG_DEVICECLIENT_INFO_HINV_START CLIMSG_DEVICECLIENT_ERROR_HINV_FAIL CLIMSG_DEVICECLIENT_INFO_HINV_SUCCESS CLIMSG_DEVICECLIENT_ERROR_REFRESHING_SSSC CLIMSG_DEVICECLIENT_INFO_REFRESHING_SSSC CLIMSG_DEVICECLIENT_INFO_SINV_START CLIMSG_DEVICECLIENT_ERROR_SINV_FAIL CLIMSG_DEVICECLIENT_INFO_SINV_SUCCESS
CLIMSG_DEVICECLIENT_INFO_CLIENT_UPGRADE_START CLIMSG_DEVICECLIENT_INFO_CLIENT_UNINSTALL_START CLIMSG_DEVICECLIENT_INFO_FILECOLLECTION_START CLIMSG_DEVICECLIENT_INFO_FILECOLLECTION_SUCCESS CLIMSG_DEVICECLIENT_ERROR_FILECOLLECTION_FAIL CLIMSG_DEVICECLIENT_INFO_REGISTRATION_SUCCESS CLIMSG_OSDEPLOYMENT_INFO_ACTION_START CLIMSG_OSDEPLOYMENT_ERROR_ACTION_FAIL CLIMSG_OSDEPLOYMENT_INFO_INSTALLATION_COMPLETE CLIMSG_OSDEPLOYMENT_ERROR_DPREQUEST_FAIL CLIMSG_OSDEPLOYMENT_ERROR_NODP CLIMSG_OSDEPLOYMENT_ERROR_CONNECTTODP_FAIL CLIMSG_OSDEPLOYMENT_INFO_VALIDATION_START CLIMSG_OSDEPLOYMENT_INFO_STATECAPTURE_START CLIMSG_OSDEPLOYMENT_INFO_PREINSTALL_START CLIMSG_OSDEPLOYMENT_INFO_INSTALL_START CLIMSG_OSDEPLOYMENT_INFO_POSTINSTALL_START CLIMSG_OSDEPLOYMENT_INFO_STATERESTORE_START CLIMSG_OSDEPLOYMENT_INFO_MULTICAST_DOWNLOAD_SUCCESS CLIMSG_OSDEPLOYMENT_INFO_MULTICAST_DOWNLOAD_FAILED CLIMSG_TSEXECUTION_INFO_SKIP_DISABLED_GROUP CLIMSG_TSEXECUTION_ERROR_CONDITION_FAIL_FOR_GROUP CLIMSG_TSEXECUTION_INFO_SKIP_GROUP_CONDITION_FALSE
CLIMSG_TSEXECUTION_INFO_GROUP_CONDITION_TRUE CLIMSG_TSEXECUTION_INFO_GROUP_START
CLIMSG_TSEXECUTION_WARNING_GROUP_IGNORE_FAILURE CLIMSG_TSEXECUTION_ERROR_GROUP_ABORT_EXECUTION CLIMSG_TSEXECUTION_INFO_GROUP_COMPLETE CLIMSG_TSEXECUTION_INFO_SKIP_DISABLED_ACTION CLIMSG_TSEXECUTION_ERROR_CONDITION_FAIL_FOR_ACTION
CLIMSG_TSEXECUTION_INFO_SKIP_ACTION_CONDITION_FALSE
CLIMSG_TSEXECUTION_INFO_ACTION_CONDITION_TRUE CLIMSG_TSEXECUTION_ERROR_ACTION_FAIL_START
CLIMSG_TSEXECUTION_INFO_ACTION_START CLIMSG_TSEXECUTION_INFO_ACTION_COMPLETE
CLIMSG_TSEXECUTION_ERROR_ACTION_FAIL
CLIMSG_TSEXECUTION_INFO_RECEIVE_EXTERNAL_SHUTDOWN
CLIMSG_TSEXECUTION_ERROR_ACTION_TIMEOUT
CLIMSG_TSEXECUTION_WARNING_ACTION_IGNORE_FAILURE CLIMSG_TSEXECUTION_ERROR_ACTION_ABORT_EXECUTION CLIMSG_TSEXECUTION_INFO_TASK_SEQUENCE_START CLIMSG_TSEXECUTION_ERROR_TASK_SEQUENCE_FAIL CLIMSG_TSEXECUTION_INFO_TASK_SEQUENCE_REBOOT CLIMSG_TSEXECUTION_INFO_TASK_SEQUENCE_SUCCESS
CLIMSG_TSEXECUTION_INFO_TASK_SEQUENCE_START_FROM_NON_CLIENT CLIMSG_TSMANAGER_ERROR_TASK_SEQUENCE_XML_VERSION CLIMSG_TSMANAGER_ERROR_TASK_SEQUENCE_FAIL
CLIMSG_TSMANAGER_INFO_TASK_SEQUENCE_SUCCESS CLIMSG_SUIAGENT_ERROR_INVALID_CHANGEWINDOW_CMDLINE
CLIMSG_SUIAGENT_ERROR_NO_ASSIGNMENT_SCHEDULE
CLIMSG_SUIAGENT_ERROR_AUTHORIZATION_LIST
CLIMSG_SUIAGENT_ERROR_NO_SCAN_PATH
CLIMSG_SUIAGENT_ERROR_SCAN_FAILED
CLIMSG_SUIAGENT_ERROR_LOAD_PATCHSTATE
CLIMSG_SUIAGENT_ERROR_STORE_PATCHSTATE
CLIMSG_SUIAGENT_ERROR_LOAD_RESOURCE_DLL
CLIMSG_SUIAGENT_WARNING_EARLY_START
CLIMSG_SUIAGENT_WARNING_LATE_START
CLIMSG_SUIAGENT_INFO_USER_RESCHEDULED_INSTALL CLIMSG_SUIAGENT_INFO_USER_POSTPONED_INSTALL CLIMSG_SUIAGENT_INFO_AUTO_POSTPONED_INSTALL
CLIMSG_SUIAGENT_INFO_INSTALL_SUMMARY
CLIMSG_SUIAGENT_WARNING_WINDOW_EXPIRED_INSTALL
CLIMSG_SUIAGENT_INFO_USER_RESCHEDULED_PREINST_REBOOT
CLIMSG_SUIAGENT_INFO_USER_POSTPONED_PREINST_REBOOT
CLIMSG_SUIAGENT_INFO_AUTO_POSTPONED_PREINST_REBOOT
CLIMSG_SUIAGENT_INFO_USER_RESCHEDULED_REBOOT CLIMSG_SUIAGENT_INFO_USER_POSTPONED_REBOOT CLIMSG_SUIAGENT_INFO_AUTO_POSTPONED_REBOOT CLIMSG_SUIAGENT_INFO_INITIATED_REBOOT
CLIMSG_SUIAGENT_INFO_SUPPRESSED_REBOOT_WS
CLIMSG_SUIAGENT_INFO_SUPPRESSED_REBOOT_SVR
CLIMSG_SUIAGENT_INFO_NO_REBOOT_REQUIRED CLIMSG_SUIAGENT_INFO_PREINST_REBOOT_REQUIRED
CLIMSG_SUIAGENT_INFO_REBOOT_REQUIRED CLIMSG_SUIAGENT_INFO_UPDATE_SUCCEEDED
CLIMSG_SUIAGENT_INFO_UPDATE_SUCCEEDED_REBOOT
CLIMSG_SUIAGENT_ERROR_UPDATE_FAILED
CLIMSG_SUIAGENT_WARNING_UPDATE_TIME_EXPIRED
CLIMSG_SUIAGENT_INFO_UPDATE_CANCELLED
CLIMSG_SUIAGENT_ERROR_LOW_DISK_SPACE
CLIMSG_SUIAGENT_INFO_UPDATE_SUCCEEDED_OPTIONAL
CLIMSG_SUIAGENT_INFO_UPDATE_SUCCEEDED_REBOOT_OPTIONAL
CLIMSG_SUIAGENT_INFO_UPDATE_SUCCEEDED_MANDATORY
CLIMSG_SUIAGENT_INFO_UPDATE_SUCCEEDED_REBOOT_MANDATORY
CLIMSG_PDP_PKG_DOWNLOAD_STARTED CLIMSG_PDP_PKG_DOWNLOAD_SUCCEEDED CLIMSG_PDP_PKG_DOWNLOAD_FAILED CLIMSG_PDP_PKG_DOWNLOAD_CANCELLED CLIMSG_PDP_HASH_MISMATCH
CLIMSG_PDP_NO_DISKSPACE
CLIMSG_PDP_NO_NTFS
CLIMSG_PDP_DISK_NOT_FOUND
CLIMSG_PDP_CREATE_DIR_FAIL
CLIMSG_PDP_CREATE_SHARE_FAIL
CLIMSG_PDP_SET_ACL_FAIL
CLIMSG_PDP_MOVE_COPY_FAIL
CLIMSG_PDP_INVALID_POLICY
CLIMSG_PDP_DO_NOT_DOWNLOAD
CLIMSG_PDP_PKG_EXISTS
CLIMSG_PDP_ERR_STA
CLIMSG_PDP_MAX_RETRY
CLIMSG_PDP_NO_BITS20
CLIMSG_PDP_PKG_DELETE CLIMSG_PDP_PKG_PROVISION_SUCCESS CLIMSG_PDP_PKG_UNABLE_START_MAINTENANCE CLIMSG_PDP_BITS_CONFIG_CHANGED
CLIMSG_PDP_BITS_CONFIG_DELETED CLIMSG_PDP_START_MAINTENANCE_ALL CLIMSG_PDP_PKG_MAINTENANCE_LIST CLIMSG_PDP_MAINTENANCE_PKG_NOT_EXISTS CLIMSG_PDP_PKG_SHARE_MOVED CLIMSG_PDP_INTERNET_CLIENT CLIMSG_PDP_NON_DOMAIN_CLIENT CLIMSG_PDP_AGENT_ENABLED CLIMSG_PDP_AGENT_DISABLED CLIMSG_PDP_PKG_DELETE_FAIL
CLIMSG_UPDATESSCAN_ERROR_OS_UNSUPPORTED
CLIMSG_UPDATESSCAN_ERROR_NON_ADMIN
CLIMSG_UPDATESSCAN_ERROR_IE_UNSUPPORTED CLIMSG_UPDATESSCAN_ERROR_DISK_SPACE
CLIMSG_UPDATESSCAN_ERROR_INV_RES
CLIMSG_UPDATESSCAN_ERROR_SCAN_FAILED CLIMSG_UPDATESSCAN_INFO_STATUS_CHANGE
CLIMSG_UPDATESSCAN_WARNING_STATUS_REMOVED
CLIMSG_UPDATESSCAN_ERROR_READ_CONFIGFILE
CLIMSG_UPDATESSCAN_ERROR_REQUIREMENTS
CLIMSG_UPDATESSCAN_ERROR_EXECUTION CLIMSG_UPDATESSCAN_ERROR_EXPANSION CLIMSG_UPDATESSCAN_ERROR_SCAN_INI CLIMSG_UPDATESCAN_STARTED CLIMSG_UPDATESCAN_UNABLE_TO_START
CLIMSG_UPDATESCAN_COMPLETED_SUCCESSFUL CLIMSG_UPDATESCAN_TIMEOUT
CLIMSG_UPDATESCAN_WAIT_CONTENT
CLIMSG_UPDATESCAN_ERROR_DOWNLOAD_FAILED
CLIMSG_UPDATESCAN_ERROR_INSUFFICIENT_CACHE_SIZE
CLIMSG_UPDATESCAN_ERROR_INSUFFICIENT_CACHE
CLIMSG_UPDATESCAN_ERROR_FAILED CLIMSG_UPDATESCAN_ERROR_UPDATESOURCE_REGISTRATION_FAILED
CLIMSG_UPDATESSCAN_ERROR_LEGACY_SCANNER_NOT_SUPPORTED
CLIMSG_UPDATESSCAN_WARNING_SCAN_SUCCEEDED_WITH_ERRORS
CLIMSG_UPDATESSYNC_ERROR_NO_SITECODE CLIMSG_UPDATESSYNC_ERROR_NO_PACKAGEID CLIMSG_UPDATESSYNC_ERROR_NO_SITENAME CLIMSG_UPDATESSYNC_ERROR_NO_TARGET CLIMSG_UPDATESSYNC_ERROR_NO_WRITE_ACCESS
CLIMSG_UPDATESSYNC_ERROR_NO_READ_ACCESS
CLIMSG_UPDATESSYNC_ERROR_SYNC_FAILED
CLIMSG_UPDATESSYNC_INFO_SYNC_SUCCEEDED
CLIMSG_UPDATESSYNC_ERROR_UPDATE_DP
CLIMSG_UPDATESSYNC_ERROR_UPDATE_CATALOG
CLIMSG_UPDATESSYNC_INFO_SYNC_NOUPDATE_SUCCEEDED
CLIMSG_UPDATESSYNC_INFO_ERROR_CONTENT_NOTRUST
CLIMSG_UPDATESSYNC_INFO_ERROR_DUPLICATE_TOOL
DMCLIENTDEPLOYMENT_INFO_NEWER_CLIENT DMCLIENTDEPLOYMENT_INFO_NO_ACTION DMCLIENTDEPLOYMENT_INFO_INSTALL_SUCCESS DMCLIENTDEPLOYMENT_INFO_UPGRADE_SUCCESS DMCLIENTDEPLOYMENT_INFO_VERIFY_SUCCESS DMCLIENTDEPLOYMENT_INFO_UNINSTALL_SUCCESS
DMCLIENTDEPLOYMENT_INFO_INSTALL_SUCCESS_CERTIFICATE_ENROLLMENT_NOT_REQUIRED DMCLIENTDEPLOYMENT_INFO_UPGRADE_SUCCESS_CERTIFICATE_ENROLLMENT_NOT_REQUIRED DMCLIENTDEPLOYMENT_INFO_VERIFY_SUCCESS_CERTIFICATE_ENROLLMENT_NOT_REQUIRED DMCLIENTDEPLOYMENT_WARN_INSTALL_SUCCESS_CERT_FAILED
DMCLIENTDEPLOYMENT_WARN_UPGRADE_SUCCESS_CERT_FAILED
DMCLIENTDEPLOYMENT_WARN_VERIFY_SUCCESS_CERT_FAILED
DMCLIENTDEPLOYMENT_ERROR_NO_CONNECTION DMCLIENTDEPLOYMENT_ERROR_INVALID_SETTINGS DMCLIENTDEPLOYMENT_ERROR_CLIXFER_DIR DMCLIENTDEPLOYMENT_ERROR_NO_RAPI DMCLIENTDEPLOYMENT_ERROR_BAD_PROC DMCLIENTDEPLOYMENT_ERROR_BAD_OS
DMCLIENTDEPLOYMENT_ERROR_BAD_CLI_VER DMCLIENTDEPLOYMENT_ERROR_BAD_SETTINGS DMCLIENTDEPLOYMENT_ERROR_COPY DMCLIENTDEPLOYMENT_ERROR_CAB_INSTALL DMCLIENTDEPLOYMENT_ERROR_NO_STATUS DMCLIENTDEPLOYMENT_ERROR_INSTALLER_DIR
DMCLIENTDEPLOYMENT_ERROR_PRECOMMAND
DMCLIENTDEPLOYMENT_ERROR_POSTCOMMAND DMCLIENTDEPLOYMENT_ERROR_INSTALL_UNINSTALL_PREV DMCLIENTDEPLOYMENT_ERROR_INSTALL_BAD_SETTINGS DMCLIENTDEPLOYMENT_ERROR_INSTALL_CAB_INSTALL DMCLIENTDEPLOYMENT_ERROR_INSTALL_START_CLIENT DMCLIENTDEPLOYMENT_ERROR_INSTALL_UPDATE_SETTINGS DMCLIENTDEPLOYMENT_ERROR_UNKNOWN_FAILURE DMCLIENTDEPLOYMENT_ERROR_VERIFY_UNINSTALL_PREV DMCLIENTDEPLOYMENT_ERROR_VERIFY_BAD_SETTINGS DMCLIENTDEPLOYMENT_ERROR_VERIFY_CAB_INSTALL DMCLIENTDEPLOYMENT_ERROR_VERIFY_START_CLIENT DMCLIENTDEPLOYMENT_ERROR_VERIFY_UPDATE_SETTINGS DMCLIENTDEPLOYMENT_ERROR_VERIFY_RESTORE_FILES DMCLIENTDEPLOYMENT_ERROR_INSTALL_PRIVILEGED_CERTIFICATE
DMCLIENTDEPLOYMENT_ERROR_GENERIC DMCLIENTDEPLOYMENT_ERROR_LAUNCH_CLIENT_SETUP DMCLIENTDEPLOYMENT_ERROR_CLIENT_UNINSTALL DMCLIENTDEPLOYMENT_ERROR_ENFORCING_NEW_CLIENT
DMCLIENTDEPLOYMENT_ERROR_ENFORCING_OLD_CLIENT
DMCLIENTDEPLOYMENT_ERROR_PERFORMING_POST_CAB_INSTALL_STEPS CLIMSG_SMSNAP_ERROR_CLIENT_FRAGILITY CLIMSG_SUMAGENT_ERROR_NO_SCAN_FOUND
CLIMSG_SUMAGENT_ERROR_SCAN_FAILED CLIMSG_SUMAGENT_ERROR_HASH_MISMATCH CLIMSG_SUMAGENT_ERROR_NO_CONTENT CLIMSG_SUMAGENT_ERROR_INSUFFICIENT_CACHE
CLIMSG_SUMAGENT_ERROR_INSUFFICIENT_CACHE_SIZE
CLIMSG_SUMAGENT_ERROR_DOWNLOAD_FAILED CLIMSG_SUMAGENT_ERROR_INVALID_COMMANDLINE CLIMSG_SUMAGENT_ERROR_UPDATE_FAILED CLIMSG_SUMAGENT_WARNING_UPDATE_TIME_EXPIRED CLIMSG_SUMAGENT_ERROR_CREATE_PROCESS
CLIMSG_SUMAGENT_ERROR_INSTALLER_PATH CLIMSG_SUMAGENT_ERROR_RESUME_PROCESS CLIMSG_SUMAGENT_ERROR_INTERNAL CLIMSG_SUMAGENT_ERROR_BUNDLE_FAILED_CONTENT
CLIMSG_SUMAGENT_ERROR_BUNDLE_FAILED_EXECUTE
CLIMSG_SUMAGENT_ERROR_BUNDLE_FAILED_EVALUATE
CLIMSG_SUMAGENT_ERROR_NO_SERVICEWINDOW
CLIMSG_SUMAGENT_ERROR_ENFORCEMENT_JOB CLIMSG_SUMAGENT_ERROR_ENFORCEMENT_UPDATES_FAILURE CLIMSG_SUMAGENT_ERROR_ENFORCEMENT_NON_COMPLIANCE CLIMSG_SUMAGENT_ERROR_ENFORCEMENT_DETECT_POSTRESTART CLIMSG_SUMAGENT_ERROR_ENFORCEMENT_INITIATE CLIMSG_SUMAGENT_ERROR_EVALUATION_INITIATE CLIMSG_SUMAGENT_ERROR_EVALUATION_JOB CLIMSG_SUMAGENT_ERROR_INVALID_POLICY CLIMSG_SUMAGENT_ERROR_ADVANCE_DOWNLOAD_INITIATE CLIMSG_SUMAGENT_ERROR_ADVANCE_DOWNLOAD_JOB
CLIMSG_SUMAGENT_ERROR_ENFORCEMENT_NO_SERVICEWINDOW
CLIMSG_DCMAGENT_CI_DOWNLOAD_FAILED CLIMSG_DCMAGENT_CI_HASH_MISMATCH
CLIMSG_DCMAGENT_DOTNETMISSING
CLIMSG_DCMAGENT_SDM_DOWNLOAD_FAILED CLIMSG_DCMAGENT_SDM_HASH_MISMATCH
CLIMSG_DCMAGENT_SDM_EVAL_FAILED CLIMSG_DCMAGENT_SDM_REPORTING_FAILED CLIMSG_DCMAGENT_SDM_COMPLIANT
CLIMSG_DCMAGENT_SDM_NONCOMPLIANT_INFO
CLIMSG_DCMAGENT_SDM_NONCOMPLIANT_WARN
CLIMSG_DCMAGENT_SDM_NONCOMPLIANT_ERROR
CLIMSG_DCMAGENT_CI_DECOMPRESSION_FAILED CLIMSG_DCMAGENT_SDM_DECOMPRESSION_FAILED CLIMSG_DCMAGENT_CI_INTERNAL_FAILED CLIMSG_DCMAGENT_SDM_INTERNAL_FAILED CLIMSG_DCMAGENT_DISC_LAUNCH_FAILED CLIMSG_DCMAGENT_DISC_PROCESS_FAILED CLIMSG_DCMAGENT_MODEL_VIOLATIONS CLIMSG_DCMAGENT_DISCOVERY_VIOLATIONS CLIMSG_DCMAGENT_CI_DOWNLOAD_TIMEOUT CLIMSG_DCMAGENT_SDM_DOWNLOAD_TIMEOUT CLIMSG_SMSSWD_INFO_DYNAMIC_SW_INSTALL_SUCCESS
CLIMSG_SMSSWD_ERROR_DYNAMIC_SW_INSTALL_FAIL
CLIMSG_AMTAGENT_INFO_STARTCONFIG_SUCCESS CLIMSG_AMTAGENT_ERROR_STARTCONFIG_FAILURE
CLIMSG_VIRTUALAPP_INFO_PACKAGEADD_SUCCESS
CLIMSG_VIRTUALAPP_ERROR_PACKAGEADD_FAILURE
CLIMSG_VIRTUALAPP_INFO_PACKAGEADD_PENDING
CLIMSG_VIRTUALAPP_INFO_PACKAGEDELETE_SUCCESS
CLIMSG_VIRTUALAPP_ERROR_PACKAGEDELETE_FAILURE
CLIMSG_VIRTUALAPP_INFO_PACKAGEDELETE_PENDING
CLIMSG_VIRTUALAPP_ERROR_LAUNCH_FAILURE CLIMSG_VIRTUALAPP_INFO_NOSOFTGRID
MessageID 30000 30001 30002 30003 30004 30005 30006 30007
Severity
Message Source
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider
30008 30009 30010 30011 30012 30013 30014 30015 30016 30017 30018 30019
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider
30020 30021 30022
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider
30023 30024 30025 30026 30027 30028 30029 30030
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider
30031
INFORMATIONAL SMS Provider
30032
30033 30034 30035 30036 30037 30038 30039 30040 30041 30042 30043 30044
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider
30045 30046 30047 30048 30049 30050 30051 30052 30053 30054 30055 30056 30057
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL SMS Provider SMS Provider SMS Provider SMS Provider SMS Provider SMS Provider SMS Provider
30058
30059
30060
30061
30062
30063
30064 30065 30066 30067 30068 30069 30070 30071 30072 30073 30074 30075 30076 30077 30078 30079 30080 30081 30082 30083 30084 30085
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL SMS Provider SMS Provider SMS Provider SMS Provider SMS Provider
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider WARNING SMS Provider
30086
WARNING
SMS Provider
30087
WARNING
SMS Provider
30088
WARNING
SMS Provider
30089
WARNING
SMS Provider
30090 30091 30092
30093 30094
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider
30095
30096 30097 30098 30099 30100 30101 30102 30103 30104 30105
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider
30106 30107 30108 30109
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider
30110
30111
30112
30113 30114 30115 30116 30117 30118 30119
INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL
SMS Provider SMS Provider SMS Provider SMS Provider SMS Provider SMS Provider
30120 30121
30122
30123
30124
30125 30126 30127 30128 30129 30130 30131 30132 30133 30134 30135 30136 30137 30138 30139 30140 30152
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider
30153
30154
30155
30156
30157
30158
30159
30160
30161
30162
30163
30164
30165
30166
30167
30168
30169
30170
30171
30172
30173 30180 30181 30183
30185
30186
30187
30188
30189
30190
30191
30192 30193
30194
30195
30196
30197
30198
30199
30200
30201
30202
30203
30204
30205
30206
30207
30208
30209
30210
30211
30212
30213
30214 30215 30216 30217 30218 30219
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider
30220
30221
30222 30223 30224 30225
30226 30227 30228 30300 30301 30302 30303 30304 30305 30306 30307 30308 30309 30310
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider ERROR SMS Provider
INFORMATIONAL SMS Provider ERROR SMS Provider
30311
ERROR
SMS Provider
30312
ERROR
SMS Provider
30313
ERROR
SMS Provider
30314
ERROR
SMS Provider
30315
ERROR
SMS Provider
30316
ERROR
SMS Provider
30317 30318 30319 30320 30321 30322 30323 30324 30325 30400 30401 30402 30403 30404 30405 30406 30407 30408 30409 39997 39998 39999
ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR
SMS Provider SMS Provider SMS Provider SMS Provider SMS Provider SMS Provider SMS Provider SMS Provider SMS Provider
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL SMS Provider SMS Provider SMS Provider SMS Provider
INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider INFORMATIONAL SMS Provider WARNING SMS Provider ERROR SMS Provider
Message Text
User "%1" created a package named "%5 %3 %4 %6" (%2).%12 User "%1" modified the Package Properties of a package named "%5 %3 %4 %6" (%2).%12 User "%1" deleted a package named "%5 %3 %4 %6" (%2).%12 User "%1" created a program named "%2" that belongs to a package with package ID %3.%12 User "%1" modified a program named "%2" that belongs to a package with package ID %3.%12 User "%1" deleted a program named "%2" that belongs to a package with package ID %3.%12 User "%1" created an advertisement named "%3" (%2) advertising program "%4".%12 User "%1" modified the advertisement properties of an advertisement named "%3" (%2) advertising program "%4".%12 User "%1" deleted an advertisement named "%3" (%2) advertising program "%4".%12 User "%1" targeted a package with package ID %2 to a distribution point on %5 at site "%4 - %6".%12 User "%1" modified a distribution point on %5 at site "%4 - %6" for a package with package ID %2.%12 User "%1" removed a package with package ID %2 from a distribution point on %5 at site "%4 - %6".%12 User "%1" created secondary site "%3 - %2".%12 User "%1" upgraded or removed secondary site "%3 - %2".%12 User "%1" deleted (removed all records from the SMS site database) secondary site "%3 - %2".%12 User "%1" created a collection named "%3" (%2).%12 User "%1" modified the Collection Properties for a collection named "%3" (%2).%12 User "%1" deleted a collection named "%3" (%2).%12 User "%1" created address of type "%6" connecting site %3 to %7 on %8 with priority %9.%12 User "%1" modified the address properties for an address of type "%6" connecting site %3 to %7 on %8 with priority %9.%12 User "%1" deleted address of type "%6" connecting site %3 to %7 on %8 with priority %9.%12 User "%1" created file definition "%5" at secondary site %3.%12 User "%1" modified file definition "%5" at secondary site %3.%12
User "%1" deleted file definition "%5" at secondary site %3.%12 User "%1" created the property "%5" in the site control file at site %3.%12 User "%1" modified the property "%5" in the site control file at site %3.%12 User "%1" deleted the property "%5" in the site control file at site %3.%12 User "%1" created the property list "%5" in the site control file at site %3.%12 User "%1" modified the property list "%5" in the site control file at site %3.%12 User "%1" deleted the property list "%5" in the site control file at site %3.%12 User "%1" created site definition information in the site control file for site "%3 - %6" (Parent Site Code="%7").%12 User "%1" modified site definition information in the site control file for site "%3 - %6" (Parent Site Code="%7").%12 User "%1" deleted site definition information in the site control file for site "%3 - %6" (Parent Site Code="%7").%12 User "%1" created component "%7" on %6 in the site control file at site %3.%12 User "%1" modified component "%7" on %6 in the site control file at site %3.%12 User "%1" deleted component "%7" on %6 in the site control file at site %3.%12 User "%1" added the role of %7 to the %6 "%8" in the site control file at site %3.%12 User "%1" modified the role of the %6 "%8" as a %7 in the site control file at site %3.%12 User "%1" deleted the role of the %6 "%8" as a %7 in the site control file at site %3.%12 User "%1" created a configuration for the "%5" component in the site control file at site %3.%12 User "%1" modified the configuration of the "%5" component in the site control file at site %3.%12 User "%1" deleted the configuration of the "%5" component in the site control file at site %3.%12 User "%1" created client component "%5" in the site control file at site %3.%12 User "%1" modified client component "%5" in the site control file at site %3.%12 User "%1" deleted client component "%5" in the site control file at site %3.%12
User "%1" created client configuration "%5" in the site control file at site %3.%12 User "%1" modified client configuration "%5" in the site control file at site %3.%12 User "%1" deleted client configuration "%5" in the site control file at site %3.%12 User "%1" created SQL command "%5" at site %3.%12 User "%1" modified SQL command "%5" at site %3.%12 User "%1" deleted SQL command "%5" at site %3.%12 User "%1" created SQL Task "%5" at site %3.%12 User "%1" modified SQL Task "%5" at site %3.%12 User "%1" deleted SQL Task "%5" at site %3.%12 User "%1" added the site boundaries record to the site control file of site %3.%12 User "%1" modified the site boundaries of site %3.%12 User "%1" deleted the site boundaries record in the site control file of site %3.%12 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 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 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 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 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 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 User "%1" created a query named "%3" (%2) targeting the "%4" class.%12
User "%1" modified a query named "%3" (%2) targeting the "%4" class.%12 User "%1" deleted a query named "%3" (%2) targeting the "%4" class.%12 User "%1" deleted a discovered resource named "%3" (%2).%12 User "%1" deleted all of the resources that belong to collection "%3" (%2).%12 User "%1" updated a package named "%5 %3 %4 %6" (%2) to the site distribution points.%12 User "%1" at "%2" initiated a Remote Tools session with "%3".%12 User "%1" at "%2" ended a Remote Tools session with "%3".%12 User "%1" at "%2" initiated Remote Execute with "%3".%12 User "%1" at "%2" ended Remote Execute with %3.%12 User "%1" at "%2" Remote Rebooted "%3".%12 User "%1" at "%2" initiated File Transfer with "%3".%12 User "%1" at "%2" ended File Transfer with "%3".%12 User "%1" at "%2" initiated Remote Control with "%3".%12 User "%1" at "%2" ended Remote Control with "%3".%12 User "%1" at "%2" initiated Remote Diagnostics with "%3".%12 User "%1" at "%2" ended Remote Diagnostics with "%3".%12 User "%1" at "%2" initiated Remote Chat with "%3".%12 User "%1" at "%2" ended Remote Chat with "%3".%12 User "%1" at "%2" initiated Remote Tools Ping with "%3".%12 User "%1" at "%2" ended Remote Tools Ping with "%3".%12 User "%1" at "%2" started a Remote Tools session with "%3".%12 User "%1" at "%2" failed to start a Remote Tools session with "%3".%12 Solution: Verify that the Remote Tools Client Agent is installed on the client. If the agent is installed and you cannot start a Remote Tools session, use the "Show Status" command on Control Panel, Remote Tools on the client to verify that the Remote Control Agent is listening on the right protocol.
User "%1" at "%2" failed to start a Remote Tools session with "%3" due to insufficient security credentials.%12 Solution: Verify that the logged on user is a member of a group that is listed in the Permitted viewers list on the Security tab of the Remote Tools Client Agent Properties dialog box. User "%1" at "%2" failed to start a Remote Tools session with "%3".%12 Solution: Confirm that another Remote Tools session is not already in progress on the client.%12 User "%1" at "%2" lost a Remote Tools connection with "%3".%12 Possible cause: When Remote.exe has an open connection to a client, it background polls the connection to verify that the client is still connected. The connection can fail because the network cable is unplugged, the client machine is turned off, or the client stops responding. Solution: Check the security credentials of logged on user "%1". Verify that the client is turned on and is still plugged into the network. If the client is a Windows NT client, verify that the SMS Remote Control Agent service is still running on the client. Then, retry the Remote Tools operation.%12
User "%1" at "%2" lost a Remote Tools connection with "%3".%12 Possible cause: When Remote.exe has an open connection to a client, it background polls the connection to verify that the client is still connected. The connection can fail because the network cable is unplugged, the client machine is turned off, or the client quits responding. Solution: Check the security credentials of logged on user "%1". Verify that the client is turned on and is still plugged into the network. If the client is a Windows NT client, verify that the SMS Remote Control Agent service is still running on the client. Then, retry the Remote Tools operation.%12
User "%1" at "%2" is ending a Remote Tools session with "%3".%12 User "%1" created a report named "%3" (%2).%12 User "%1" modified a report named "%3" (%2).%12
User "%1" deleted a report named "%3" (%2).%12 User "%1" created a meter rule named "%7" (%3) for file "%4" with a product version of "%6" and Language ID of "%5".%12 User "%1" modified a meter rule named "%7" (%3) for file "%4" with a product version of "%6" and Language ID of "%5".%12 User "%1" added the roaming boundaries record to the site control file of site %3.%12 User "%1" modified the roaming boundaries of site %3.%12 User "%1" deleted the roaming boundaries record in the site control file of site %3.%12 User "%1" created Maintenance Task "%5" at site %3.%12 User "%1" modified Maintenance Task "%5" at site %3.%12 User "%1" deleted Maintenance Task "%5" at site %3.%12 User "%2" from computer "%3" created a session using application [%4] version [%5].%12 User "%2" from computer "%3" released its session using application [%4] version [%5].%12 User "%1" requested that the membership be refreshed for collection "%3" (%2).%12 User "%1" deleted a meter rule named "%7" (%3) for file "%4" with a product version of "%6" and Language ID of "%5".%12 User "%1" requested that the CCRs be generated for query named "%3" (%2) targeting the "%4" class.%12 User "%1" requested that the CCRs be generated for collection "%3" (%2).%12 User "%1" requested that the CCR be generated for Machine "%2" (%3).%12 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. Possible cause: Some system resources are not assigned to the current site, And you chose to install clients only on system resources that are assigned to current site. Another possible cause: some system resources do not have Microsoft Windows NT operating system or above installed. %12
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. Possible cause: some system resources are not assigned to the current site, and you chose to install clients only on system resources that are assigned to current site. Another possible cause: Some system resources do not have Microsoft Windows NT operating system or above installed. %12 User "%1" requested that the CCR be generated for resource "%3". But no CCR is generated. Possible cause: this is not a system resource, this is not assigned to current site if you choose to install client on system resource that are assigned to current site, or the system resource does not have Microsoft Windows NT operating system or above installed.%12 User "%1" has authorized a software update. Details: ID = %2, QNumbers = %3, Product = %4, Title = %5, Locale = %6.%12 User "%1" created a folder named "%3" (%2).%12 User "%1" modified a folder named "%3" (%2).%12 User "%1" deleted a folder named "%3" (%2).%12 User "%1" added %3 of %4 to folder "%2".%12 User "%1" moved %3 of %4 out of folder "%2".%12 User "%1" added software update "%2" to program "%4" in package "%3", package version "%5".%12 User "%1" changed the link information for software update "%2" in program "%4" and package "%3", package version "%5".%12 User "%1" removed software update "%2" from program "%4" in package "%3", package version "%5".%12 User "%1" created software update with CI_ID "%2". Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12 User "%1" modified software update with CI_ID "%2". Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12 User "%1" deleted software update with CI_ID "%2". Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12
User "%1" has authorized software update "%2". Details: ID = "%3", QNumbers = "%5", Product = "%6", Title = "%4", Locale = "%7".%12 User "%1" added new distribution points to a package named "%5 %3 %4 %6" (%2).%12 User "%1" created device hardware inventory translation "%2".%12 User "%1" modified device hardware inventory translation "%2".%12 User "%1" deleted device hardware inventory translation "%2".%12 User "%1" created device discovery translation "%2".%12 User "%1" modified device discovery translation "%2".%12 User "%1" deleted device discovery translation "%2".%12 User "%1" created an instance of SMS_DeviceFQDN "%2".%12 User "%1" modified an instance of SMS_DeviceFQDN "%2".%12 User "%1" deleted an instance of SMS_DeviceFQDN "%2".%12 User "%1" created relation "%3" between software update "%2" and software update "%4".%12 User "%1" changed relation "%3" between software update "%2" and software update "%4".%12 User "%1" removed relation "%3" between software update "%2" and software update "%4".%12 User "%1" has created an instance of SMS_ScanTool. SMSScanToolID =%2 ToolName=%3.%12 User "%1" has modified an instance of SMS_ScanTool. SMSScanToolID =%2 ToolName=%3.%12 User "%1" has deleted an instance of SMS_ScanTool. SMSScanToolID =%2 ToolName=%3.%12 User "%1" created configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12 User "%1" modified configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12 User "%1" deleted configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12
User "%1" enforced configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12 User "%1" unenforced configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12 User "%1" accepted the EULA for configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12 User "%1" declined the EULA for configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12 User "%1" created a CategoryInstance "%2" (CategoryInstance_UniqueID=%3, CategoryTypeName=%4). .%12 User "%1" modified a CategoryInstance "%2" (CategoryInstance_UniqueID=%3, CategoryTypeName=%4). .%12 User "%1" deleted CategoryInstance "%2" (CategoryInstance_UniqueID=%3, CategoryTypeName=%4). .%12 User "%1" created a SDMPackage "%2" (SDMPackageName=%3, SDMPackageVersion=%4). .%12 User "%1" modified a SDMPackage "%2 (SDMPackageName=%3, SDMPackageVersion=%4)". .%12 User "%1" deleted SDMPackage "%2" (SDMPackageName=%3, SDMPackageVersion=%4). .%12 User "%1" created a EulaContent "%2" (EULAContentUniqueID=%3). .%12
User "%1" modified a EulaContent "%2" (EULAContentUniqueID=%3). .%12 User "%1" deleted EulaContent "%2" (EULAContentUniqueID=%3). .%12 User "%1" resend configuration item "%2" (CI_UniqueID=%3, CIVersion=%4) to all child sites. .%12 User "%1" resend a CategoryInstance "%2" (CategoryInstance_UniqueID=%3, CategoryTypeName=%4) to all child sites. .%12 User "%1" resend a SDMPackage "%2" (SDMPackageName=%3, SDMPackageVersion=%4) to all child sites. .%12 User "%1" resend a EulaContent "%2" (EULAContentUniqueID=%3) to all child sites. .%12 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 User "%1" has resend an instance of SMS_ScanTool to all child sites. SMSScanToolID =%2 ToolName=%3.%12 User "%1" created a state association between sourceclient (%2) and restoreclient (%3).%12 User "%1" deleted a state association between sourceclient (%2) and restoreclient (%3).%12 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 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
User "%1" created the SUM deployment template with TemplateUniqueID "%2" (Name = "%3"). .%12 User "%1" modified the SUM deployment template with TemplateUniqueID "%2" (Name = "%3"). .%12 User "%1" deleted the SUM deployment template with TemplateUniqueID "%2" (Name = "%3"). .%12 User "%1" added content with ContentID %2 to PackageID "%3" (ContentVersionInPkg = %4). .%12 User "%1" modified content with ContentID %2 in PackageID "%3 (ContentVersionInPkg = %4)". .%12 User "%1" removed content with ContentID %2 from PackageID "%3". .%12 User "%1" initiated a package change notification for Package named "%5 %3 %4 %6" (%2).%12 User "%1" created CI assignment %2 (%3). .%12 User "%1" modified CI assignment %2 (%3). .%12 User "%1" deleted CI assignment %2 (%3). .%12 User "%1" created updates assignment %2 (%3). .%12 User "%1" modified updates assignment %2 (%3). .%12 User "%1" deleted updates assignment %2 (%3). .%12
User "%1" created an instance of SMS_DeviceSettingItem %2 (Name = %3, Type = %4, Version = %5). .%12 User "%1" modified an instance of SMS_DeviceSettingItem %2 (Name = %3, Type = %4, Version = %5). .%12 User "%1" deleted an instance of SMS_DeviceSettingItem %2 (Name = %3, Type = %4, Version = %5). .%12 User "%1" created an instance of SMS_DeviceSettingPackage %2 (Name = %3, PlatformType = %4, Version = %5). .%12 User "%1" modified an instance of SMS_DeviceSettingPackage %2 (Name = %3, PlatformType = %4, Version = %5). .%12 User "%1" deleted an instance of SMS_DeviceSettingPackage %2 (Name = %3, PlatformType = %4, Version = %5). .%12 User "%1" created an instance of SMS_DeviceSettingPackageItem (DeviceSettingPkgID = %2, DeviceSettingItemID = %3). .%12 User "%1" modified an instance of SMS_DeviceSettingPackageItem (DeviceSettingPkgID = %2, DeviceSettingItemID = %3). .%12 User "%1" deleted an instance of SMS_DeviceSettingPackageItem (DeviceSettingPkgID = %2, DeviceSettingItemID = %3). .%12 User "%1" modified summary task (%2) (RunInterval=%3 Enabled=%4 TaskParameter=%5). .%12
User "%1" requested to execute summary task (%2). .%12 User "%1" created an user account (ItemName = %5). .%12 User "%1" modified an user account (ItemName = %5). .%12 User "%1" deleted an user account (ItemName = %5). .%12 User "%1" imported machine at site "%3 - %2" (NetbiosName=%4, MACAddress=%5, SMBIOSGUID=%6).%12 User "%1" submitted a registration record at site "%3 - %2" (SMSID=%4).%12 User "%1" received policies for Task Sequence %3 using Advertisement "%2".%12 User "%1" received client configuration policies.%12 User "%1" changed the Approved Status to %2 for %3 clients. ResourceIDs (%4).%12 User "%1" changed the Allowed Status to %2 for %3 clients. ResourceIDs (%4).%12 User "%1" created authorization list "%2" (CI_UniqueID=%3, CIVersion=%4). .%12 User "%1" modified authorization list "%2" (CI_UniqueID=%3, CIVersion=%4). .%12 User "%1" deleted authorization list "%2" (CI_UniqueID=%3, CIVersion=%4). .%12 User "%1" created per-computer settings for %3 (ResourceID %2).%12 User "%1" modified per-computer settings for %3 (ResourceID %2).%12 User "%1" changed the Block Status to %2 for Certificate (SMSID=%3).%12 User "%1" resolved the pending registration record (SMSID=%2, FQDN=%3, ConflictSMSID=%4, Action=%5).%12
User "%1" created a virtual App named %4 (VirtualAppID = %2) for the Package(%3).%12 User "%1" modified a virtual App named %4 (VirtualAppID = %2) for the Package(%3).%12 User "%1" deleted a virtual App named %4 (VirtualAppID = %2) for the Package(%3).%12 User "%1" at "%2" started an OOB Console session to "%3".%12 User "%1" at "%2" attempt to disconnect from "%3". Success.%12 User "%1" at "%2" attempt to perform a status information query from "%3". Success.%12 User "%1" at "%2" attempt to perform a system inventory query from "%3". Success.%12 User "%1" at "%2" attempt to perform a power control command to "%3". Success.%12 User "%1" at "%2" attempt to perform a serial over lan session to "%3". Success.%12 User "%1" at "%2" attempt to perform a IDE-R session to "%3". Success.%12 User "%1" at "%2" attempt to unprovision "%3". Success.%12 User "%1" at "%2" has no permission to connect "%3". Success.%12 User "%1" at "%2" attempt to connect to "%3".%12 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 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 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 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 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 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 User "%1" at "%2" failed to unprovision "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12
User "%1" at "%2" failed to disconnect from "%3".%12 User "%1" at "%2" failed to connect to "%3".%12 User "%1" at "%2" failed to connect to special resource %3 in this site.%12 User "%1" at "%2" failed to perform a status information query from "%3". Internal exception occurs.%12 User "%1" at "%2" failed to perform a system inventory query from "%3". Internal exception occurs.%12 User "%1" at "%2" failed to perform a power control command to "%3". Internal exception occurs.%12 User "%1" at "%2" failed to perform a serial over lan session to "%3". Internal exception occurs.%12 User "%1" at "%2" failed to perform a IDE-R session to "%3". Internal exception occurs.%12 User "%1" at "%2" failed to unprovision "%3". Internal exception occurs.%12 User "%1" changed the AMT Status to %2 for AMT Certificate (CertID=%3).%12 User "%1" initiated "Power on" command on "%3" (%2) .%12 User "%1" initiated "Restart" command on "%3" (%2).%12 User "%1" initiated "Shut down" command on "%3" (%2).%12 User "%1" enabled Audit Log on "%3" (%2).%12 User "%1" disabled Audit Log on "%3" (%2).%12 User "%1" cleared Audit Log on "%3" (%2).%12 User "%1" updates the provision data on machine "%3" (%2).%12 User "%1" unprovisioned machine "%3" (%2).%12 User "%1" initiated "Discover" command on "%3" (%2).%12 %1%12%2%3%4%5%6%7%8%9%10 %1%12%2%3%4%5%6%7%8%9%10 %1%12%2%3%4%5%6%7%8%9%10
Symbolic Name
PROVMSG_SMSPROV_INFO_CREATED_PACKAGE PROVMSG_SMSPROV_INFO_MODIFIED_PACKAGE PROVMSG_SMSPROV_INFO_DELETED_PACKAGE PROVMSG_SMSPROV_INFO_CREATED_PROGRAM PROVMSG_SMSPROV_INFO_MODIFIED_PROGRAM PROVMSG_SMSPROV_INFO_DELETED_PROGRAM PROVMSG_SMSPROV_INFO_CREATED_ADVERT PROVMSG_SMSPROV_INFO_MODIFIED_ADVERT
PROVMSG_SMSPROV_INFO_DELETED_ADVERT PROVMSG_SMSPROV_INFO_CREATED_DISTPOINT PROVMSG_SMSPROV_INFO_MODIFIED_DISTPOINT PROVMSG_SMSPROV_INFO_DELETED_DISTPOINT PROVMSG_SMSPROV_INFO_CREATED_SITE PROVMSG_SMSPROV_INFO_MODIFIED_SITE PROVMSG_SMSPROV_INFO_DELETED_SITE PROVMSG_SMSPROV_INFO_CREATED_COLLECTION PROVMSG_SMSPROV_INFO_MODIFIED_COLLECTION PROVMSG_SMSPROV_INFO_DELETED_COLLECTION PROVMSG_SMSPROV_INFO_CREATED_SCI_ADDRESS PROVMSG_SMSPROV_INFO_MODIFIED_SCI_ADDRESS
PROVMSG_SMSPROV_INFO_DELETED_SCI_ADDRESS PROVMSG_SMSPROV_INFO_CREATED_SCI_FILEDEFINITION PROVMSG_SMSPROV_INFO_MODIFIED_SCI_FILEDEFINITION
PROVMSG_SMSPROV_INFO_DELETED_SCI_FILEDEFINITION PROVMSG_SMSPROV_INFO_CREATED_SCI_PROPERTY PROVMSG_SMSPROV_INFO_MODIFIED_SCI_PROPERTY PROVMSG_SMSPROV_INFO_DELETED_SCI_PROPERTY PROVMSG_SMSPROV_INFO_CREATED_SCI_PROPERTYLIST PROVMSG_SMSPROV_INFO_MODIFIED_SCI_PROPERTYLIST PROVMSG_SMSPROV_INFO_DELETED_SCI_PROPERTYLIST PROVMSG_SMSPROV_INFO_CREATED_SCI_SITEDEFINITION
PROVMSG_SMSPROV_INFO_MODIFIED_SCI_SITEDEFINITION
PROVMSG_SMSPROV_INFO_DELETED_SCI_SITEDEFINITION
PROVMSG_SMSPROV_INFO_CREATED_SCI_COMPONENT PROVMSG_SMSPROV_INFO_MODIFIED_SCI_COMPONENT PROVMSG_SMSPROV_INFO_DELETED_SCI_COMPONENT PROVMSG_SMSPROV_INFO_CREATED_SCI_SYSRESUSE PROVMSG_SMSPROV_INFO_MODIFIED_SCI_SYSRESUSE PROVMSG_SMSPROV_INFO_DELETED_SCI_SYSRESUSE PROVMSG_SMSPROV_INFO_CREATED_SCI_CONFIGURATION PROVMSG_SMSPROV_INFO_MODIFIED_SCI_CONFIGURATION PROVMSG_SMSPROV_INFO_DELETED_SCI_CONFIGURATION PROVMSG_SMSPROV_INFO_CREATED_SCI_CLIENTCOMP PROVMSG_SMSPROV_INFO_MODIFIED_SCI_CLIENTCOMP PROVMSG_SMSPROV_INFO_DELETED_SCI_CLIENTCOMP
PROVMSG_SMSPROV_INFO_CREATED_SCI_CLIENTCONFIG PROVMSG_SMSPROV_INFO_MODIFIED_SCI_CLIENTCONFIG PROVMSG_SMSPROV_INFO_DELETED_SCI_CLIENTCONFIG PROVMSG_SMSPROV_INFO_CREATED_SCI_SQLCMD PROVMSG_SMSPROV_INFO_MODIFIED_SCI_SQLCMD PROVMSG_SMSPROV_INFO_DELETED_SCI_SQLCMD PROVMSG_SMSPROV_INFO_CREATED_SCI_SQLTASK PROVMSG_SMSPROV_INFO_MODIFIED_SCI_SQLTASK PROVMSG_SMSPROV_INFO_DELETED_SCI_SQLTASK PROVMSG_SMSPROV_INFO_CREATED_SCI_SITEASSIGNMENT PROVMSG_SMSPROV_INFO_MODIFIED_SCI_SITEASSIGNMENT PROVMSG_SMSPROV_INFO_DELETED_SCI_SITEASSIGNMENT PROVMSG_SMSPROV_INFO_CREATED_SECURITYUSER
PROVMSG_SMSPROV_INFO_MODIFIED_SECURITYUSER
PROVMSG_SMSPROV_INFO_DELETED_SECURITYUSER
PROVMSG_SMSPROV_INFO_CREATED_SECURITYINSTANCE
PROVMSG_SMSPROV_INFO_MODIFIED_SECURITYINSTANCE
PROVMSG_SMSPROV_INFO_DELETED_SECURITYINSTANCE
PROVMSG_SMSPROV_INFO_CREATED_QUERY
PROVMSG_SMSPROV_INFO_MODIFIED_QUERY PROVMSG_SMSPROV_INFO_DELETED_QUERY PROVMSG_SMSPROV_INFO_DELETED_RESOURCE PROVMSG_SMSPROV_INFO_DELETEDRESOURCES_COLLECTION PROVMSG_SMSPROV_INFO_UPDATEDISTPOINTS_PACKAGE PROVMSG_SMSPROV_INFO_REMOTE_TOOLS_START PROVMSG_SMSPROV_INFO_REMOTE_TOOLS_END PROVMSG_SMSPROV_INFO_REMOTE_EXECUTE_START PROVMSG_SMSPROV_INFO_REMOTE_EXECUTE_END PROVMSG_SMSPROV_INFO_REMOTE_REBOOT_START PROVMSG_SMSPROV_INFO_REMOTE_FILETRANSFER_START PROVMSG_SMSPROV_INFO_REMOTE_FILETRANSFER_END PROVMSG_SMSPROV_INFO_REMOTE_CONTROL_START PROVMSG_SMSPROV_INFO_REMOTE_CONTROL_END PROVMSG_SMSPROV_INFO_REMOTE_DIAGNOSTICS_START PROVMSG_SMSPROV_INFO_REMOTE_DIAGNOSTICS_END PROVMSG_SMSPROV_INFO_REMOTE_CHAT_START PROVMSG_SMSPROV_INFO_REMOTE_CHAT_END PROVMSG_SMSPROV_INFO_REMOTE_PING_START PROVMSG_SMSPROV_INFO_REMOTE_PING_END PROVMSG_SMSPROV_INFO_REMOTE_CONNECT PROVMSG_SMSPROV_INFO_REMOTE_CONNECT_FAILED
PROVMSG_SMSPROV_INFO_REMOTE_CONNECT_FAILED_ACCESS_DENIED
PROVMSG_SMSPROV_INFO_REMOTE_CONNECT_FAILED_BUSY
PROVMSG_SMSPROV_INFO_REMOTE_CONNECT_FAILED_LOST_CONNECTION
PROVMSG_SMSPROV_INFO_REMOTE_CONNECT_FAILED_LOST_CONNECTION_ACCESS_DENIED
PROVMSG_SMSPROV_INFO_REMOTE_SHUTTING_DOWN PROVMSG_SMSPROV_INFO_CREATED_REPORT PROVMSG_SMSPROV_INFO_MODIFIED_REPORT
PROVMSG_SMSPROV_INFO_DELETED_REPORT PROVMSG_SMSPROV_INFO_CREATED_MTRRULE
PROVMSG_SMSPROV_INFO_MODIFIED_MTRRULE
PROVMSG_SMSPROV_INFO_CREATED_SCI_ROAMINGBOUNDARY PROVMSG_SMSPROV_INFO_MODIFIED_SCI_ROAMINGBOUNDARY PROVMSG_SMSPROV_INFO_DELETED_SCI_ROAMINGBOUNDARY PROVMSG_SMSPROV_INFO_CREATED_SCI_MAINTENANCETASK PROVMSG_SMSPROV_INFO_MODIFIED_SCI_MAINTENANCETASK PROVMSG_SMSPROV_INFO_DELETED_SCI_MAINTENANCETASK PROVMSG_SMSPROV_INFO_CONNECTED_UI_SiteControl PROVMSG_SMSPROV_INFO_RELEASED_UI_SiteControl PROVMSG_SMSPROV_INFO_REFRESHMEMBERSHIP_COLLECTION PROVMSG_SMSPROV_INFO_DELETED_MTRRULE
PROVMSG_SMSPROV_INFO_QUERY_INSTALL_CLIENT PROVMSG_SMSPROV_INFO_COLLECTION_INSTALL_CLIENT PROVMSG_SMSPROV_INFO_RESOURCE_INSTALL_CLIENT PROVMSG_SMSPROV_INFO_QUERY_INSTALL_CLIENT_PARTIAL
PROVMSG_SMSPROV_INFO_COLLECTION_INSTALL_CLIENT_PARTIAL
PROVMSG_SMSPROV_INFO_RESOURCE_INSTALL_CLIENT_NONE
PROVMSG_SMSPROV_INFO_PATCH_AUTHORIZE
PROVMSG_SMSPROV_INFO_CREATED_FOLDER PROVMSG_SMSPROV_INFO_MODIFIED_FOLDER PROVMSG_SMSPROV_INFO_DELETED_FOLDER PROVMSG_SMSPROV_INFO_CREATED_FOLDERMEMBER PROVMSG_SMSPROV_INFO_DELETED_FOLDERMEMBER PROVMSG_SMSPROV_INFO_CREATED_UPDATEPACKAGE PROVMSG_SMSPROV_INFO_MODIFIED_UPDATEPACKAGE
PROVMSG_SMSPROV_INFO_DELETED_UPDATEPACKAGE PROVMSG_SMSPROV_INFO_CREATED_UPDATE
PROVMSG_SMSPROV_INFO_MODIFIED_UPDATE
PROVMSG_SMSPROV_INFO_DELETED_UPDATE
PROVMSG_SMSPROV_INFO_PATCH_AUTHORIZE2
PROVMSG_SMSPROV_INFO_ADDDISTPOINTS_PACKAGE PROVMSG_SMSPROV_INFO_CREATED_DEVICEHINVTRANSLATION PROVMSG_SMSPROV_INFO_MODIFIED_DEVICEHINVTRANSLATION PROVMSG_SMSPROV_INFO_DELETED_DEVICEHINVTRANSLATION PROVMSG_SMSPROV_INFO_CREATED_DEVICEDISCOVERYTRANSLATION PROVMSG_SMSPROV_INFO_MODIFIED_DEVICEDISCOVERYTRANSLATION PROVMSG_SMSPROV_INFO_DELETED_DEVICEDISCOVERYTRANSLATION PROVMSG_SMSPROV_INFO_CREATED_DEVICEFQDN PROVMSG_SMSPROV_INFO_MODIFIED_DEVICEFQDN PROVMSG_SMSPROV_INFO_DELETED_DEVICEFQDN PROVMSG_SMSPROV_INFO_CREATED_UPDATERELATION PROVMSG_SMSPROV_INFO_MODIFIED_UPDATERELATION PROVMSG_SMSPROV_INFO_DELETED_UPDATERELATION PROVMSG_SMSPROV_INFO_CREATED_SCANTOOL PROVMSG_SMSPROV_INFO_MODIFIED_SCANTOOL PROVMSG_SMSPROV_INFO_DELETED_SCANTOOL PROVMSG_SMSPROV_INFO_CREATED_CONFIGURATIONITEM
PROVMSG_SMSPROV_INFO_MODIFIED_CONFIGURATIONITEM
PROVMSG_SMSPROV_INFO_DELETED_CONFIGURATIONITEM
PROVMSG_SMSPROV_INFO_ENFORCE_CONFIGURATIONITEM
PROVMSG_SMSPROV_INFO_UNENFORCE_CONFIGURATIONITEM
PROVMSG_SMSPROV_INFO_ACCEPT_EULA
PROVMSG_SMSPROV_INFO_DECLINE_EULA
PROVMSG_SMSPROV_INFO_CREATED_CATEGORY
PROVMSG_SMSPROV_INFO_MODIFIED_CATEGORY
PROVMSG_SMSPROV_INFO_DELETED_CATEGORY
PROVMSG_SMSPROV_INFO_CREATED_SDMPACKAGE
PROVMSG_SMSPROV_INFO_MODIFIED_SDMPACKAGE
PROVMSG_SMSPROV_INFO_DELETED_SDMPACKAGE
PROVMSG_SMSPROV_INFO_CREATED_EULACONTENT
PROVMSG_SMSPROV_INFO_MODIFIED_EULACONTENT
PROVMSG_SMSPROV_INFO_DELETED_EULACONTENT
PROVMSG_SMSPROV_INFO_RESEND_CONFIGURATIONITEM
PROVMSG_SMSPROV_INFO_RESEND_CATEGORY
PROVMSG_SMSPROV_INFO_RESEND_SDMPACKAGE
PROVMSG_SMSPROV_INFO_RESEND_EULACONTENT
PROVMSG_SMSPROV_RESEND_UPDATE
PROVMSG_SMSPROV_INFO_RESEND_SCANTOOL PROVMSG_SMSPROV_INFO_CREATED_STATEASSOCIATION PROVMSG_SMSPROV_INFO_DELETED_STATEASSOCIATION PROVMSG_SMSPROV_DOWNLOAD_CONTENT
PROVMSG_SMSPROV_IMPORT_CONTENT
PROVMSG_SMSPROV_INFO_CREATED_TEMPLATE
PROVMSG_SMSPROV_INFO_MODIFIED_TEMPLATE
PROVMSG_SMSPROV_INFO_DELETED_TEMPLATE
PROVMSG_SMSPROV_INFO_CREATED_PACKAGECONTENT_RELATION
PROVMSG_SMSPROV_INFO_MODIFIED_PACKAGECONTENT_RELATION
PROVMSG_SMSPROV_INFO_DELETED_PACKAGECONTENT_RELATION
PROVMSG_SMSPROV_INFO_CHANGE_NOTIFICATION_PACKAGE PROVMSG_SMSPROV_INFO_CREATED_CI_ASSIGNMENT
PROVMSG_SMSPROV_INFO_MODIFIED_CI_ASSIGNMENT
PROVMSG_SMSPROV_INFO_DELETED_CI_ASSIGNMENT
PROVMSG_SMSPROV_INFO_CREATED_UPDATES_ASSIGNMENT
PROVMSG_SMSPROV_INFO_MODIFIED_UPDATES_ASSIGNMENT
PROVMSG_SMSPROV_INFO_DELETED_UPDATES_ASSIGNMENT
PROVMSG_SMSPROV_INFO_CREATED_DEVICESETTINGITEM
PROVMSG_SMSPROV_INFO_MODIFIED_DEVICESETTINGITEM
PROVMSG_SMSPROV_INFO_DELETED_DEVICESETTINGITEM
PROVMSG_SMSPROV_INFO_CREATED_DEVICESETTINGPACKAGE
PROVMSG_SMSPROV_INFO_MODIFIED_DEVICESETTINGPACKAGE
PROVMSG_SMSPROV_INFO_DELETED_DEVICESETTINGPACKAGE
PROVMSG_SMSPROV_INFO_CREATED_DEVICESETTINGPACKAGEITEM
PROVMSG_SMSPROV_INFO_MODIFIED_DEVICESETTINGPACKAGEITEM
PROVMSG_SMSPROV_INFO_DELETED_DEVICESETTINGPACKAGEITEM
PROVMSG_SMSPROV_INFO_MODIFIED_SUMMARYTASK
PROVMSG_SMSPROV_INFO_RUN_SUMMARYTASK
PROVMSG_SMSPROV_INFO_CREATED_SCI_USERACCOUNT
PROVMSG_SMSPROV_INFO_MODIFIED_SCI_USERACCOUNT
PROVMSG_SMSPROV_INFO_DELETED_SCI_USERACCOUNT
PROVMSG_SMSPROV_INFO_SITE_IMPORTMACHINE
PROVMSG_SMSPROV_INFO_SUBMIT_REGISTRATION_RECORD PROVMSG_SMSPROV_INFO_QUERY_TS_POLICY PROVMSG_SMSPROV_INFO_QUERY_CLIENTCONFIG_POLICY PROVMSG_SMSPROV_INFO_APPROVE_CLIENTS PROVMSG_SMSPROV_INFO_BLOCK_CLIENTS PROVMSG_SMSPROV_INFO_CREATED_AUTHLIST
PROVMSG_SMSPROV_INFO_MODIFIED_AUTHLIST
PROVMSG_SMSPROV_INFO_DELETED_AUTHLIST
PROVMSG_SMSPROV_INFO_CREATED_MACHINEEXTPROP PROVMSG_SMSPROV_INFO_MODIFIED_MACHINEEXTPROP PROVMSG_SMSPROV_INFO_BLOCK_CERTIFICATE PROVMSG_SMSPROV_INFO_RESOLVE_PENDING_REGISTRATION_RECORD
PROVMSG_SMSPROV_INFO_CREATED_VIRTUALAPP PROVMSG_SMSPROV_INFO_MODIFIED_VIRTUALAPP PROVMSG_SMSPROV_INFO_DELETED_VIRTUALAPP PROVMSG_SMSPROV_INFO_OOBCONSOLE_CONNECT PROVMSG_SMSPROV_INFO_OOBCONSOLE_DISCONNECT_AMT PROVMSG_SMSPROV_INFO_OOBCONSOLE_QUERY_STATUS PROVMSG_SMSPROV_INFO_OOBCONSOLE_QUERY_INVENTORY PROVMSG_SMSPROV_INFO_OOBCONSOLE_POWER_CONTROL PROVMSG_SMSPROV_INFO_OOBCONSOLE_SESSION_SOL PROVMSG_SMSPROV_INFO_OOBCONSOLE_SESSION_IDER PROVMSG_SMSPROV_INFO_OOBCONSOLE_UNPROVISION PROVMSG_SMSPROV_ERROR_OOBCONSOLE_NO_PERMISSION PROVMSG_SMSPROV_INFO_OOBCONSOLE_CONNECT_AMT PROVMSG_SMSPROV_ERROR_OOBCONSOLE_DUPLICATE_IDER
PROVMSG_SMSPROV_ERROR_OOBCONSOLE_QUERY_STATUS
PROVMSG_SMSPROV_ERROR_OOBCONSOLE_QUERY_INVENTORY
PROVMSG_SMSPROV_ERROR_OOBCONSOLE_POWER_CONTROL
PROVMSG_SMSPROV_ERROR_OOBCONSOLE_SESSION_SOL
PROVMSG_SMSPROV_ERROR_OOBCONSOLE_SESSION_IDER
PROVMSG_SMSPROV_ERROR_OOBCONSOLE_UNPROVISION
PROVMSG_SMSPROV_ERROR_OOBCONSOLE_DISCONNECT_AMT PROVMSG_SMSPROV_ERROR_OOBCONSOLE_CONNECT_AMT PROVMSG_SMSPROV_ERROR_OOBCONSOLE_CONNECT_AMT_WMI PROVMSG_SMSPROV_ERROR_OOBCONSOLE_QUERY_STATUS_EXCEPTION PROVMSG_SMSPROV_ERROR_OOBCONSOLE_QUERY_INVENTORY_EXCEPTION PROVMSG_SMSPROV_ERROR_OOBCONSOLE_POWER_CONTROL_EXCEPTION PROVMSG_SMSPROV_ERROR_OOBCONSOLE_SESSION_SOL_EXCEPTION PROVMSG_SMSPROV_ERROR_OOBCONSOLE_SESSION_IDER_EXCEPTION PROVMSG_SMSPROV_ERROR_OOBCONSOLE_UNPROVISION_EXCEPTION PROVMSG_SMSPROV_INFO_BLOCK_AMT_CERTIFICATE PROVMSG_SMSPROV_INFO_OOBSP_WAKEUP PROVMSG_SMSPROV_INFO_OOBSP_RESTART PROVMSG_SMSPROV_INFO_OOBSP_SHUTDOWN PROVMSG_SMSPROV_INFO_OOBSP_ENABLEAUDIT PROVMSG_SMSPROV_INFO_OOBSP_DISABLEAUDIT PROVMSG_SMSPROV_INFO_OOBSP_CLEARAUDIT PROVMSG_SMSPROV_INFO_OOBSP_REPROVISION PROVMSG_SMSPROV_INFO_OOBSP_UNPROVISION PROVMSG_SMSPROV_INFO_OOBSP_DISCOVER PROVMSG_SMSPROV_INFO_USER_MESSAGE PROVMSG_SMSPROV_WARNING_USER_MESSAGE PROVMSG_SMSPROV_ERROR_USER_MESSAGE
MessageID 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 500 501
Severity
SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS INFORMATIONAL INFORMATIONAL
Message Source
Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic
502 503
INFORMATIONAL Generic INFORMATIONAL Generic
504 505 506 507 508 509 510 511 512 513 514 515
INFORMATIONAL Generic ERROR INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL Generic Generic Generic Generic Generic Generic Generic Generic Generic
516 517 518 519 520 521 522 523 524 525 526 527 528 529
INFORMATIONAL Generic WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic
530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546
ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR
Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic
INFORMATIONAL Generic INFORMATIONAL Generic ERROR ERROR Generic Generic
547
ERROR
Generic
548 549 550 551
ERROR ERROR
Generic Generic
INFORMATIONAL Generic ERROR Generic
552
ERROR
Generic
553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569
INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic WARNING WARNING WARNING Generic Generic Generic
INFORMATIONAL Generic INFORMATIONAL Generic WARNING WARNING WARNING WARNING Generic Generic Generic Generic
570 571 572 573
WARNING WARNING WARNING WARNING
Generic Generic Generic Generic
574 575 576 577 578 579 580 581 582 583
WARNING ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR
Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic
584 585 586 587 588 589 590 591 592 593 594 595 596 597 598
Generic Generic Generic Generic Generic
INFORMATIONAL Generic INFORMATIONAL INFORMATIONAL INFORMATIONAL INFORMATIONAL Generic Generic Generic Generic
INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic
599 600
ERROR ERROR
Generic Generic
601 602 603 604 605 606 607 608 609 610 611 612 613 614 615
ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR
Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic Generic
INFORMATIONAL Generic
616
WARNING
Generic
617
ERROR
Generic
618
619
WARNING
Generic
620
ERROR
Generic
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
INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic
646 647
648 649 650 651 652 653 654 655 656
INFORMATIONAL Generic INFORMATIONAL Generic INFORMATIONAL Generic WARNING WARNING ERROR ERROR ERROR ERROR Generic Generic Generic Generic Generic Generic
657
ERROR
Generic
658
ERROR
Generic
659
ERROR
Generic
660
ERROR
Generic
661
ERROR
Generic
662
ERROR
Generic
663
664
665
666
WARNING
Generic
667
ERROR
Generic
668
WARNING
Generic
669
ERROR
Generic
Message Text
Package ID Advertisement ID Collection ID User Name Distribution Point Policy ID Policy Assignment ID Software Metering Rule ID Client SMS Unique ID Site Code Package Version Time Key Unique Update ID Product ID CI Assignment ID Object ID Object Type Sdm Type Id Sdm Type Version UpdateSourceUniqueID Collection Extended Properties ID Wake On LAN Object Type Wake On LAN Batch ID Machine Extended Properties ID Wake On LAN Number of Requests Unknown Machine MAC Addresses SMBIOS ID This component started. 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. This component stopped. 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.
This component was signalled to resume processing by an administrator. Server %1 is unreachable or down.%12%2%3%4%5%6%7%8%9%10 Copied file "%1" to "%2".%12%3%4%5%6%7%8%9%10 Moved file "%1" to "%2".%12%3%4%5%6%7%8%9%10 Deleted file "%1".%12%2%3%4%5%6%7%8%9%10 Locked file "%1".%12%2%3%4%5%6%7%8%9%10 Unlocked file "%1".%12%2%3%4%5%6%7%8%9%10 Created directory "%1".%12%2%3%4%5%6%7%8%9%10 Removed directory "%1".%12%2%3%4%5%6%7%8%9%10 Set the current directory for this process to "%1".%12%2%3%4%5%6%7%8%9%10 Opened a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10 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 Closed the change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10 Could not open file "%1" for reading.%12%2%3%4%5%6%7%8%9%10 Could not open file "%1" for reading and writing.%12%2%3%4%5%6%7%8%9%10 Could not read from file "%1".%12%2%3%4%5%6%7%8%9%10 Could not write to file "%1".%12%2%3%4%5%6%7%8%9%10 Could not copy file "%1" to "%2".%12%3%4%5%6%7%8%9%10 Could not move file "%1" to "%2".%12%3%4%5%6%7%8%9%10 Could not delete file "%1".%12%2%3%4%5%6%7%8%9%10 Could not lock file "%1".%12%2%3%4%5%6%7%8%9%10 Could not create directory "%1".%12%2%3%4%5%6%7%8%9%10 Could not remove directory "%1".%12%2%3%4%5%6%7%8%9%10 Could not set the current directory for this process to "%1".%12%2%3%4%5%6%7%8%9%10 Could not open a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10 Could not wait on a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10
Could not open file "%1" for reading.%12%2%3%4%5%6%7%8%9%10 Could not open file "%1" for reading and writing.%12%2%3%4%5%6%7%8%9%10 Could not read from file "%1".%12%2%3%4%5%6%7%8%9%10 Could not write to file "%1".%12%2%3%4%5%6%7%8%9%10 Could not copy file "%1" to "%2".%12%3%4%5%6%7%8%9%10 Could not move file "%1" to "%2".%12%3%4%5%6%7%8%9%10 Could not delete file "%1".%12%2%3%4%5%6%7%8%9%10 Could not lock file "%1".%12%2%3%4%5%6%7%8%9%10 Could not create directory "%1".%12%2%3%4%5%6%7%8%9%10 Could not remove directory "%1".%12%2%3%4%5%6%7%8%9%10 Could not set the current directory for this process to "%1".%12%2%3%4%5%6%7%8%9%10 Could not open a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10 Could not wait on a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10 Parsed site control file "%1", serial number %2.%12%3%4%5%6%7%8%9%10 Wrote delta site control file "%1".%12%2%3%4%5%6%7%8%9%10 Could not read site control file "%1".%12%2%3%4%5%6%7%8%9%10 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 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 Site control file "%1" does not contain a "File Definition" item.%12%2%3%4%5%6%7%8%9%10 Could not write delta site control file "%1".%12%2%3%4%5%6%7%8%9%10 Parsed installation map "%1".%12%2%3%4%5%6%7%8%9%10 Could not read installation map "%1".%12%2%3%4%5%6%7%8%9%10
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 Read registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Wrote registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Deleted registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Read registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Wrote registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Deleted registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Opened a change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Closed the change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not connect to registry hive %1 on computer %2.%12%3%4%5%6%7%8%9%10 Could not open registry key "%1" on computer %2 for reading.%12%3%4%5%6%7%8%9%10 Could not create or open registry key "%1" on computer %2 for reading and writing.%12%3%4%5%6%7%8%9%10 Could not read registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not write registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not delete the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not enumerate the subkeys of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not open a change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 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 Could not read the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not write the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not delete the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not enumerate the values of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10
The registry value "%1" on computer %2 contains invalid data.%12%3%4%5%6%7%8%9%10 Could not connect to registry hive %1 on computer %2.%12%3%4%5%6%7%8%9%10 Could not open registry key "%1" on computer %2 for reading.%12%3%4%5%6%7%8%9%10 Could not create or open registry key "%1" on computer %2 for reading and writing.%12%3%4%5%6%7%8%9%10 Could not read registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not write registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not delete the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not enumerate the subkeys of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not open a change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 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 Could not read the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not write the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not delete the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10 Could not enumerate the values of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10 The registry value "%1" on computer %2 contains invalid data.%12%3%4%5%6%7%8%9%10 Creating "%1" trigger for "%2".%12%3%4%5%6%7%8%9%10 Dropping trigger "%1".%12%2%3%4%5%6%7%8%9%10 Creating table "%1".%12%2%3%4%5%6%7%8%9%10 Dropping table "%1".%12%2%3%4%5%6%7%8%9%10 Creating index "%1" on table "%2".%12%3%4%5%6%7%8%9%10 Dropping index "%1".%12%2%3%4%5%6%7%8%9%10 Creating stored procedure "%1".%12%2%3%4%5%6%7%8%9%10 Dropping stored procedure "%1".%12%2%3%4%5%6%7%8%9%10 Creating view "%1".%12%2%3%4%5%6%7%8%9%10 Dropping view "%1".%12%2%3%4%5%6%7%8%9%10
SQL Login data is incomplete.%12%1%2%3%4%5%6%7%8%9%10 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 Failed to execute SQL command: "%1". Check messages from SQL Server.%12%2%3%4%5%6%7%8%9%10 The following SQL operation has timed out: "%1".%12%2%3%4%5%6%7%8%9%10 Failed to get new table name.%12%1%2%3%4%5%6%7%8%9%10 Failed to create table "%1".%12%2%3%4%5%6%7%8%9%10 Failed to rename table "%1" to "%2".%12%3%4%5%6%7%8%9%10 Failed to add columns to table "%1".%12%3%4%5%6%7%8%9%10 Failed to drop table "%1".%12%2%3%4%5%6%7%8%9%10 Failed to create index "%1" on table "%2".%12%3%4%5%6%7%8%9%10 Failed to create procedure "%1".%12%2%3%4%5%6%7%8%9%10 Failed to create view "%1".%12%2%3%4%5%6%7%8%9%10 Failed to create trigger "%1".%12%2%3%4%5%6%7%8%9%10 Failed to drop procedure "%1".%12%2%3%4%5%6%7%8%9%10 Failed to drop view "%1".%12%2%3%4%5%6%7%8%9%10 Failed to drop trigger "%1".%12%2%3%4%5%6%7%8%9%10 Microsoft SQL Server reported SQL error %1, severity %2: %3%12 Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. Microsoft SQL Server reported SQL error %1, severity %2: %3%12 Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information.
Microsoft SQL Server reported SQL error %1, severity %2: %3%12 Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. Microsoft SQL Server reported SQL message %1, severity %2: %3%12 Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. Microsoft SQL Server reported SQL message %1, severity %2: %3%12 Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. Microsoft SQL Server reported SQL message %1, severity %2: %3%12 Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. 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 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 Created the "%1" inbox definition. The inbox will exist on the Client Access Points with the relative path "%2".%12%3%4%5%6%7%8%9%10 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 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 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 Read the existing "%1" inbox definition. The inbox should exist on the Client Access Points with the relative path "%2".%12%3%4%5%6%7%8%9%10
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 Deleted the "%1" inbox definition.%12%4%5%6%7%8%9%10 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 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 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 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 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 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 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 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 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
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 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 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 Deleted the inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10 Deleted the inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10 Deleted the inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10 Deleted the inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10 Deleted the inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10 Deleted the inbox rule to mirror "%1" directories from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10 Resolved the "%1" inbox to "%2".%12%3%4%5%6%7%8%9%10 Waiting for the "%1" inbox to be defined.%12%2%3%4%5%6%7%8%9%10 Waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%12%2%3%4%5%6%7%8%9%10 Still waiting for the "%1" inbox to be defined.%12%2%3%4%5%6%7%8%9%10 Still waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%12%2%3%4%5%6%7%8%9%10 Still waiting for the "%1" inbox to be defined.%12%2%3%4%5%6%7%8%9%10 Still waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%12%2%3%4%5%6%7%8%9%10 Could not connect to the "%1" inbox source on computer %2.%12%3%4%5%6%7%8%9%10 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
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 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 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 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 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 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 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 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 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 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 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 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
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 Additional information: %7%12%8%9%10
Symbolic Name
GENMSG_ATTR_PACKAGE_ID GENMSG_ATTR_OFFER_ID GENMSG_ATTR_COLLECTION_ID GENMSG_ATTR_USER_NAME GENMSG_ATTR_DIST_POINT GENMSG_ATTR_POLICY_ID GENMSG_ATTR_POLICY_ASSIGNMENT_ID GENMSG_ATTR_METER_RULE_ID GENMSG_ATTR_CLIENT_GUID GENMSG_ATTR_SITE_CODE GENMSG_ATTR_PACKAGE_VERSION GENMSG_ATTR_TIME_KEY GENMSG_ATTR_UNIQUE_UPDATE_ID GENMSG_ATTR_PRODUCT_ID GENMSG_ATTR_UNIQUE_CIA_ID GENMSG_ATTR_UNIQUE_OBJECT_ID GENMSG_ATTR_OBJECT_TYPE GENMSG_ATTR_SDM_TYPE_ID GENMSG_ATTR_SDM_TYPE_VERSION GENMSG_ATTR_UPDATESOURCE_UNIQUE_ID GENMSG_ATTR_UNIQUE_CEP_ID GENMSG_ATTR_WOL_OBJ_TYPE GENMSG_ATTR_WOL_BATCH_ID GENMSG_ATTR_UNIQUE_MEP_ID GENMSG_ATTR_WOL_COUNT GENMSG_ATTR_UNKNOWN_MACHINE GENMSG_ATTR_MAC_ADDRESSES GENMSG_ATTR_SMBIOS GENMSG_INFO_COMP_STARTED GENMSG_INFO_COMP_IS_STOPPING
GENMSG_INFO_COMP_STOPPED GENMSG_INFO_COMP_PAUSED
GENMSG_INFO_COMP_RESUMED GENMSG_ERROR_NETWORK_SERVER_IS_DOWN GENMSG_INFO_FILE_COPY GENMSG_INFO_FILE_MOVE GENMSG_INFO_FILE_DELETE GENMSG_INFO_FILE_LOCK GENMSG_INFO_FILE_UNLOCK GENMSG_INFO_DIRECTORY_CREATE GENMSG_INFO_DIRECTORY_REMOVE GENMSG_INFO_DIRECTORY_SET_CURRENT GENMSG_INFO_DIRECTORY_CHANGE_NOTIFICATION_OPENED GENMSG_INFO_DIRECTORY_CHANGE_NOTIFICATION_REMOTE
GENMSG_INFO_DIRECTORY_CHANGE_NOTIFICATION_CLOSED GENMSG_WARNING_FILE_OPEN_READ GENMSG_WARNING_FILE_OPEN_READ_WRITE GENMSG_WARNING_FILE_READ GENMSG_WARNING_FILE_WRITE GENMSG_WARNING_FILE_COPY GENMSG_WARNING_FILE_MOVE GENMSG_WARNING_FILE_DELETE GENMSG_WARNING_FILE_LOCK GENMSG_WARNING_DIRECTORY_CREATE GENMSG_WARNING_DIRECTORY_REMOVE GENMSG_WARNING_DIRECTORY_SET_CURRENT GENMSG_WARNING_DIRECTORY_CHANGE_NOTIFICATION_OPEN GENMSG_WARNING_DIRECTORY_CHANGE_NOTIFICATION_WAIT
GENMSG_ERROR_FILE_OPEN_READ GENMSG_ERROR_FILE_OPEN_READ_WRITE GENMSG_ERROR_FILE_READ GENMSG_ERROR_FILE_WRITE GENMSG_ERROR_FILE_COPY GENMSG_ERROR_FILE_MOVE GENMSG_ERROR_FILE_DELETE GENMSG_ERROR_FILE_LOCK GENMSG_ERROR_DIRECTORY_CREATE GENMSG_ERROR_DIRECTORY_REMOVE GENMSG_ERROR_DIRECTORY_SET_CURRENT GENMSG_ERROR_DIRECTORY_CHANGE_NOTIFICATION_OPEN GENMSG_ERROR_DIRECTORY_CHANGE_NOTIFICATION_WAIT GENMSG_INFO_SCF_PARSED GENMSG_INFO_SCF_WROTE_DELTA GENMSG_ERROR_SCF_READ_FAILED GENMSG_ERROR_SCF_IS_CORRUPT
GENMSG_ERROR_SCF_NO_EOF_MARKER
GENMSG_ERROR_SCF_NO_FILE_DEFINITION GENMSG_ERROR_SCF_WRITE_FAILED GENMSG_INFO_INSTMAP_PARSED GENMSG_ERROR_INSTMAP_READ_FAILED
GENMSG_ERROR_INSTMAP_IS_CORRUPT
GENMSG_INFO_REGISTRY_KEY_READ GENMSG_INFO_REGISTRY_KEY_WRITE GENMSG_INFO_REGISTRY_KEY_DELETE GENMSG_INFO_REGISTRY_VALUE_READ GENMSG_INFO_REGISTRY_VALUE_WRITE GENMSG_INFO_REGISTRY_VALUE_DELETE GENMSG_INFO_REGISTRY_KEY_CHANGE_NOTIFICATION_OPENED GENMSG_INFO_REGISTRY_KEY_CHANGE_NOTIFICATION_CLOSED GENMSG_WARNING_REGISTRY_CONNECT GENMSG_WARNING_REGISTRY_KEY_OPEN_READ GENMSG_WARNING_REGISTRY_KEY_OPEN_READ_WRITE GENMSG_WARNING_REGISTRY_KEY_READ GENMSG_WARNING_REGISTRY_KEY_WRITE GENMSG_WARNING_REGISTRY_KEY_DELETE GENMSG_WARNING_REGISTRY_KEY_ENUMERATE GENMSG_WARNING_REGISTRY_KEY_CHANGE_NOTIFICATION GENMSG_WARNING_REGISTRY_KEY_IS_INVALID
GENMSG_WARNING_REGISTRY_VALUE_READ GENMSG_WARNING_REGISTRY_VALUE_WRITE GENMSG_WARNING_REGISTRY_VALUE_DELETE GENMSG_WARNING_REGISTRY_VALUE_ENUMERATE
GENMSG_WARNING_REGISTRY_VALUE_IS_INVALID GENMSG_ERROR_REGISTRY_CONNECT GENMSG_ERROR_REGISTRY_KEY_OPEN_READ GENMSG_ERROR_REGISTRY_KEY_OPEN_READ_WRITE GENMSG_ERROR_REGISTRY_KEY_READ GENMSG_ERROR_REGISTRY_KEY_WRITE GENMSG_ERROR_REGISTRY_KEY_DELETE GENMSG_ERROR_REGISTRY_KEY_ENUMERATE GENMSG_ERROR_REGISTRY_KEY_CHANGE_NOTIFICATION GENMSG_ERROR_REGISTRY_KEY_IS_INVALID
GENMSG_ERROR_REGISTRY_VALUE_READ GENMSG_ERROR_REGISTRY_VALUE_WRITE GENMSG_ERROR_REGISTRY_VALUE_DELETE GENMSG_ERROR_REGISTRY_VALUE_ENUMERATE GENMSG_ERROR_REGISTRY_VALUE_IS_INVALID GENMSG_INFO_CREATING_TRIGGER GENMSG_INFO_DROPPING_TRIGGER GENMSG_INFO_CREATING_TABLE GENMSG_INFO_DROPPING_TABLE GENMSG_INFO_CREATING_INDEX GENMSG_INFO_DROPPING_INDEX GENMSG_INFO_CREATING_PROCEDURE GENMSG_INFO_DROPPING_PROCEDURE GENMSG_INFO_CREATING_VIEW GENMSG_INFO_DROPPING_VIEW
GENMSG_ERROR_SQL_LOGIN_DATA GENMSG_ERROR_SQL_CONNECT
GENMSG_ERROR_SQL_CMD GENMSG_ERROR_SQL_TIMEOUT GENMSG_ERROR_SQL_NEW_TABLE_NAME GENMSG_ERROR_SQL_CREATE_TABLE GENMSG_ERROR_SQL_RENAME_TABLE GENMSG_ERROR_SQL_ALTER_TABLE GENMSG_ERROR_DROP_TABLE GENMSG_ERROR_SQL_CREATE_INDEX GENMSG_ERROR_SQL_CREATE_PROCEDURE GENMSG_ERROR_SQL_CREATE_VIEW GENMSG_ERROR_SQL_CREATE_TRIGGER GENMSG_ERROR_SQL_DROP_PROCEDURE GENMSG_ERROR_SQL_DROP_VIEW GENMSG_ERROR_SQL_DROP_TRIGGER GENMSG_INFO_SQL_ERR
GENMSG_WARNING_SQL_ERR
GENMSG_ERROR_SQL_ERR
GENMSG_INFO_SQL_MSG
GENMSG_WARNING_SQL_MSG
GENMSG_ERROR_SQL_MSG
GENMSG_INFO_INBOX_DEF_CREATE_ON_SITESERVER
GENMSG_INFO_INBOX_DEF_CREATE_ON_SQLSERVER
GENMSG_INFO_INBOX_DEF_CREATE_ON_CAP
GENMSG_INFO_INBOX_DEF_CREATE_ON_EXPORT
GENMSG_INFO_INBOX_DEF_READ_ON_SITESERVER
GENMSG_INFO_INBOX_DEF_READ_ON_SQLSERVER
GENMSG_INFO_INBOX_DEF_READ_ON_CAP
GENMSG_INFO_INBOX_DEF_READ_ON_EXPORT
GENMSG_INFO_INBOX_DEF_DELETE GENMSG_INFO_INBOX_RULE_CREATE_COPY_FILES
GENMSG_INFO_INBOX_RULE_CREATE_COPY_DIRECTORIES
GENMSG_INFO_INBOX_RULE_CREATE_MOVE_FILES
GENMSG_INFO_INBOX_RULE_CREATE_MOVE_DIRECTORIES
GENMSG_INFO_INBOX_RULE_CREATE_MIRROR_FILES
GENMSG_INFO_INBOX_RULE_CREATE_MIRROR_DIRECTORIES
GENMSG_INFO_INBOX_RULE_READ_COPY_FILES
GENMSG_INFO_INBOX_RULE_READ_COPY_DIRECTORIES
GENMSG_INFO_INBOX_RULE_READ_MOVE_FILES
GENMSG_INFO_INBOX_RULE_READ_MOVE_DIRECTORIES
GENMSG_INFO_INBOX_RULE_READ_MIRROR_FILES
GENMSG_INFO_INBOX_RULE_READ_MIRROR_DIRECTORIES
GENMSG_INFO_INBOX_RULE_DELETE_COPY_FILES GENMSG_INFO_INBOX_RULE_DELETE_COPY_DIRECTORIES GENMSG_INFO_INBOX_RULE_DELETE_MOVE_FILES GENMSG_INFO_INBOX_RULE_DELETE_MOVE_DIRECTORIES
GENMSG_INFO_INBOX_RULE_DELETE_MIRROR_FILES GENMSG_INFO_INBOX_RULE_DELETE_MIRROR_DIRECTORIES
GENMSG_INFO_INBOX_READ GENMSG_INFO_INBOX_DEF_READ_FAILED GENMSG_INFO_INBOX_READ_FAILED GENMSG_WARNING_INBOX_DEF_READ_FAILED GENMSG_WARNING_INBOX_READ_FAILED GENMSG_ERROR_INBOX_DEF_READ_FAILED GENMSG_ERROR_INBOX_READ_FAILED GENMSG_ERROR_INBOX_SOURCE_CONNECT GENMSG_ERROR_INBOX_DEF_CREATE_FAILED
GENMSG_ERROR_INBOX_RULE_CREATE_COPY_FILES
GENMSG_ERROR_INBOX_RULE_CREATE_COPY_DIRECTORIES
GENMSG_ERROR_INBOX_RULE_CREATE_MOVE_FILES
GENMSG_ERROR_INBOX_RULE_CREATE_MOVE_DIRECTORIES
GENMSG_ERROR_INBOX_RULE_CREATE_MIRROR_FILES
GENMSG_ERROR_INBOX_RULE_CREATE_MIRROR_DIRECTORIES
GENMSG_INFO_FILE_REPLICATION_LOW
GENMSG_INFO_FILE_REPLICATION_NORMAL
GENMSG_INFO_FILE_REPLICATION_HIGH
GENMSG_WARNING_FILE_REPLICATION
GENMSG_ERROR_FILE_REPLICATION
GENMSG_WARNING_OUT_OF_MEMORY
GENMSG_ERROR_UNHANDLED_EXCEPTION
You may notice the escape sequences in the message text of the status messages like %1, %2, etc. These correspond to the insertion string #1, #2, etc. %1 - Insertion string #1. %2 - Insertion string #2. %3 - Insertion string #3. %4 - Insertion string #4. %5 - Insertion string #5. %6 - Insertion string #6. %7 - Insertion string #7. %8 - Insertion string #8. %9 - Insertion string #9. %10 - Insertion string #10. %12 - The last insertion string, which is replaced by error message for Win32ErrorCode. For a given messageID, these insertion strings can be found in the corresponding records of v_StatMsgInsStrings. Now, in that case, the InsStrIndex field is 0-based so %1 would correspond to InsStrIndex = 0, %2 would correspond to InsStrIndex = 1, and so on. NOTE: Many message strings are formatted like this: [Message string, including insertion strings]%12 However, some message strings have unused insertion strings appended to the end like this: [Message string, including insertion strings]%12[unused insertion strings]

CM2007 SP2 StatusMessages v2

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CM2007 SP2 StatusMessages v2

Uploaded by

Copyright:

Available Formats

MessageID 1001

System Health Validator

System Health Validator

System Health Validator

System Health Validator

System Health Validator

System Health Validator

System Health Validator System Health Validator

INFORMATIONAL Site Component Manager

1014 1015 1016

INFORMATIONAL Site Component Manager

1018 1019 1020

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager ERROR Site Component Manager

Site Component Manager

INFORMATIONAL Site Component Manager INFORMATIONAL Site Component Manager

Site Component Manager

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager

Site Component Manager

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager

Site Component Manager

Site Component Manager

Site Component Manager

Site Component Manager

Site Component Manager

Site Component Manager

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager

Site Component Manager

Site Component Manager

Site Component Manager

Site Component Manager

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager

Site Component Manager

Site Component Manager

Site Component Manager

INFORMATIONAL Site Component Manager

Site Component Manager

INFORMATIONAL Site Component Manager

Site Component Manager

Site Component Manager

Site Component Manager

INFORMATIONAL Site Component Manager

Site Component Manager

INFORMATIONAL Site Component Manager

Site Component Manager

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager

Site Component Manager

INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager INFORMATIONAL Site Component Manager

INFORMATIONAL Site Component Manager

Site Component Manager

Site Component Manager

Site Component Manager