System Center Configuration Manager 2012 R2

  1. Syncml(424): The chunked object was received, but the size of the received object did not match the size declared within ...
  2. Syncml(425): The requested command failed because the sender does not have adequate access control permissions (ACL) on the ...
  3. Syncml(502): The recipient, while acting as a gateway or proxy, received an invalid response from the upstream recipient ...
  4. Syncml(503): The recipient is currently unable to handle the request due to a temporary overloading or maintenance of the ...
  5. Syncml(504): The recipient, while acting as a gateway or proxy, did not receive a timely response from the upstream recipient ...
  6. Syncml(505): The recipient does not support or refuses to support the specified version of SyncML DTD used in the request ...
  7. Syncml(508): An error occurred that necessitates a refresh of the current synchronization state of the client with the server. ...
  8. Syncml(510): An error occurred while processing the request. The error is related to a failure in the recipient data store. ...
  9. Syncml(513): The recipient does not support or refuses to support the specified version of the SyncML Synchronization Protocol ...
  10. Syncml(514): The SyncML command was not completed successfully, since the operation was already cancelled before processing ...
  11. System Center Operations Manager might generate alerts when a device installs a software update. To avoid receiving alerts ...
  12. System Center Operations Manager might generate alerts when these software updates runs. To avoid receiving alerts for this ...
  13. System Center Operations Manager might generate alerts when this program runs. To avoid receiving alerts for this planned ...
  14. Systems that do not have the Configuration Manager client installed. Systems require the Configuration Manager client before ...
  15. Task sequence '%s' will run on this computer in %s seconds. Windows could be installed on this computer and all data on this ...
  16. Task Sequence: %1!s! has failed with the error code ( 2!08lX!). For more information, contact your system administrator or ...
  17. The "%1" item in a site configuration change request in delta site control file %2 does not identify the change request as ...
  18. The "%1" item in a site configuration change request in delta site control file %2 does not specify a site code. This site ...
  19. The "%1" item in a site configuration change request in delta site control file %2 does not specify a site name. This site ...
  20. The "%1" item in a site configuration change request in delta site control file %2 does not specify the domain of the site ...
  21. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the service ...
  22. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site ...
  23. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site ...
  24. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL administrator ...
  25. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL Server ...
  26. The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the ...
  27. The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the ...
  28. The "%1" item in a site configuration change request in delta site control file %2 does not specify the plain text name of ...
  29. The "%1" item in a site configuration change request in delta site control file %2 does not specify the public key for decrypting ...
  30. The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server installation ...
  31. The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server's platform. ...
  32. The "%1" item in a site configuration change request in delta site control file %2 does not specify which component submitted ...
  33. The "%1" item in a site configuration change request in delta site control file %2 does not specify which computer submitted ...
  34. The "%1" item in a site configuration change request in delta site control file %2 does not specify which site should receive ...
  35. The "%1" item in a site configuration change request in delta site control file %2 does not specify which site submitted ...
  36. The "%1" item in a site configuration change request in delta site control file %2 does not specify which user submitted ...
  37. The "%1" item in a site configuration change request in delta site control file %2 specifies a site code (%3) that does not ...
  38. The "%1" item in a site configuration change request in delta site control file %2 specifies a site name ("%3") that does ...
  39. The "%1" item in a site configuration change request in delta site control file %2 specifies a site server domain (%3) that ...
  40. The "%1" item in a site configuration change request in delta site control file %2 specifies a site server installation directory ...
  41. The "%1" item in a site configuration change request in delta site control file %2 specifies a site server name ("%3") that ...
  42. The "%1" item in a site configuration change request in delta site control file %2 specifies a site type that does not match ...
  43. The "%1" item in a site configuration change request in delta site control file %2 specifies a SQL administrator account ...
  44. The "%1" item in a site configuration change request in delta site control file %2 specifies an invalid public key for decrypting ...
  45. The "%1" item in a site configuration change request in delta site control file %2 specifies an service account name and/or ...
  46. The "%1" item in a site configuration change request in delta site control file %2 specifies that the change request should ...
  47. The "%1" item in a site configuration change request in delta site control file %2 was submitted by a server component at ...
  48. The "%1" item in a site configuration change request in delta site control file %2contains a full version that's older than ...
  49. The "%1" item in a site configuration change request in delta site control file %2does not specify the domain of the service ...
  50. The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting ...
  51. The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting ...
  52. 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, ...
  53. The "%1" namespace has been removed or has become corrupted.%12 Possible cause: The Hardware Inventory Agent cannot continue ...
  54. The %1 ConfigMgr client application on the local computer did not respond to Site Backup's stop request.%12 Possible cause: ...
  55. The %1 ConfigMgr client application on the local computer did not respond to SMS Writer's stop request.%12 Possible cause: ...
  56. The /NoUserInput and /Deinstall switch cannot be used together to uninstall a Primary Site or Central Administration Site. ...
  57. The Active Directory (AD) Cache Client failed to search the AD Forest for NAP-related Configuration Manager Health Information. ...
  58. The Active Directory forest designed to store the Configuration Manager health state references has not been extended with ...
  59. The actual site control file %1 does not contain a "%2" item.%12 Solution: The Configuration Manager Server Components cannot ...
  60. The actual site control file %1 does not exist.%12 Solution: The Configuration Manager Server Components cannot function ...
  61. The address to distribution point server "%1" is invalid.%12 Possible cause: The destination distribution point share name ...
  62. The address to distribution point server "{0}" is invalid. Possible cause: The destination distribution point share name ...
  63. The address to site "%1" is invalid.%12 Possible cause: The destination share name is missing. Solution: Define a valid address ...
  64. The address to site "%1" is invalid.%12 Possible cause: The destination site server name is missing. Solution: Define a valid ...
  65. The advertised program is currently marked as disabled so its advertisements will not be displayed or run. Do you want to ...
  66. The Advertised Programs client agent has not been enabled for this ConfigMgr site so advertisements to clients at this site ...
  67. The agent encountered an error while querying WMI to collect data from this computer. The first query to fail was "%1".%12%0 ...
  68. The agent failed to resume Bitlocker after a require system restart. The error returned from the resume operation was: %1.%0 ...
  69. The agent has not collected files matching the file name "%1" or the path "%2" from this computer because the files exceed ...
  70. The allowed client connections setting is automatically configured and is displayed for information only. The value is determined ...
  71. The AMT Provisioning Removal Account removes the provisioning data from an AMT-based computer. This action can only occur ...
  72. The AMT Proxy Manager failed %2 times while replicating file %1 to out of band service point. The file has been moved to ...
  73. 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 ...
  74. The APNs account cert has expired, follow the Request Apple Notification Service CSR process to request a new APNs account ...
  75. The App-V package has already installed higher version by another deployment type so we cannot install a lower version of ...