System Center Configuration Manager 2012

  1. Synchronization component failed: Unable to write to %2. Type = %1. Possible cause: Typically, this error results when the ...
  2. Syncml(202): Accepted for processing. The request to either run a remote execution of an application or to alert a user or ...
  3. Syncml(203): Non-authoritative response. The request is being responded to by an entity other than the one targeted. The ...
  4. Syncml(204): The request was successfully completed but no data is being returned. The response code is also returned in ...
  5. Syncml(205): The source SHOULD update their content. The originator of the request is being told that their content SHOULD ...
  6. Syncml(206): The response indicates that only part of the command was completed. If the remainder of the command can be completed ...
  7. Syncml(207): Conflict resolved with merge. The response indicates that the request created a conflict; which was resolved ...
  8. Syncml(208): Conflict resolved with client's command "winning". The response indicates that there was an update conflict; ...
  9. Syncml(209): Conflict resolved with duplicate. The response indicates that the request created an update conflict; which ...
  10. Syncml(210): Delete without archive. The response indicates that the requested data was successfully deleted, but that it ...
  11. Syncml(212): Authentication accepted. No further authentication is needed for the remainder of the synchronization session. ...
  12. Syncml(214): Operation cancelled. The SyncML command completed successfully, but no more commands will be processed within ...
  13. Syncml(413): The recipient is refusing to perform the requested command because the requested item is larger than the recipient ...
  14. Syncml(414): The requested command failed because the target URI is too long for what the recipient is able or willing to ...
  15. Syncml(424): The chunked object was received, but the size of the received object did not match the size declared within ...
  16. Syncml(425): The requested command failed because the sender does not have adequate access control permissions (ACL) on the ...
  17. Syncml(502): The recipient, while acting as a gateway or proxy, received an invalid response from the upstream recipient ...
  18. Syncml(503): The recipient is currently unable to handle the request due to a temporary overloading or maintenance of the ...
  19. Syncml(504): The recipient, while acting as a gateway or proxy, did not receive a timely response from the upstream recipient ...
  20. Syncml(505): The recipient does not support or refuses to support the specified version of SyncML DTD used in the request ...
  21. Syncml(508): An error occurred that necessitates a refresh of the current synchronization state of the client with the server. ...
  22. Syncml(510): An error occurred while processing the request. The error is related to a failure in the recipient data store. ...
  23. Syncml(513): The recipient does not support or refuses to support the specified version of the SyncML Synchronization Protocol ...
  24. Syncml(514): The SyncML command was not completed successfully, since the operation was already cancelled before processing ...
  25. Syncml: An error occurred that necessitates a refresh of the current synchronization state of the client with the server. ...
  26. Syncml: The chunked object was received, but the size of the received object did not match the size declared within the first ...
  27. Syncml: The recipient does not support or refuses to support the specified version of SyncML DTD used in the request SyncML ...
  28. Syncml: The recipient does not support or refuses to support the specified version of the SyncML Synchronization Protocol ...
  29. Syncml: The recipient is currently unable to handle the request due to a temporary overloading or maintenance of the recipient. ...
  30. Syncml: The recipient is refusing to perform the requested command because the requested item is larger than the recipient ...
  31. Syncml: The recipient, while acting as a gateway or proxy, did not receive a timely response from the upstream recipient ...
  32. Syncml: The recipient, while acting as a gateway or proxy, received an invalid response from the upstream recipient it accessed ...
  33. Syncml: The requested command failed because the sender does not have adequate access control permissions (ACL) on the recipient. ...
  34. Syncml: The requested command failed because the target URI is too long for what the recipient is able or willing to process. ...
  35. Syncml: The SyncML command was not completed successfully, since the operation was already cancelled before processing the ...
  36. System Center Operations Manager might generate alerts when a device installs a software update. To avoid receiving alerts ...
  37. System Center Operations Manager might generate alerts when these software updates runs. To avoid receiving alerts for this ...
  38. System Center Operations Manager might generate alerts when this program runs. To avoid receiving alerts for this planned ...
  39. Systems that do not have the Configuration Manager client installed. Systems require the Configuration Manager client before ...
  40. Task sequence '%s' will run on this computer in %s seconds. Windows could be installed on this computer and all data on this ...
  41. Task Sequence: %1!s! has failed with the error code ( 2!08lX!). For more information, contact your system administrator or ...
  42. The "%1" item in a site configuration change request in delta site control file %2 does not identify the change request as ...
  43. The "%1" item in a site configuration change request in delta site control file %2 does not specify a site code. This site ...
  44. The "%1" item in a site configuration change request in delta site control file %2 does not specify a site name. This site ...
  45. The "%1" item in a site configuration change request in delta site control file %2 does not specify the domain of the site ...
  46. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the service ...
  47. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site ...
  48. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site ...
  49. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL administrator ...
  50. The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL Server ...
  51. The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the ...
  52. The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the ...
  53. The "%1" item in a site configuration change request in delta site control file %2 does not specify the plain text name of ...
  54. The "%1" item in a site configuration change request in delta site control file %2 does not specify the public key for decrypting ...
  55. The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server installation ...
  56. The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server's platform. ...
  57. The "%1" item in a site configuration change request in delta site control file %2 does not specify which component submitted ...
  58. The "%1" item in a site configuration change request in delta site control file %2 does not specify which computer submitted ...
  59. The "%1" item in a site configuration change request in delta site control file %2 does not specify which site should receive ...
  60. The "%1" item in a site configuration change request in delta site control file %2 does not specify which site submitted ...
  61. The "%1" item in a site configuration change request in delta site control file %2 does not specify which user submitted ...
  62. The "%1" item in a site configuration change request in delta site control file %2 specifies a site code (%3) that does not ...
  63. The "%1" item in a site configuration change request in delta site control file %2 specifies a site name ("%3") that does ...
  64. The "%1" item in a site configuration change request in delta site control file %2 specifies a site server domain (%3) that ...
  65. The "%1" item in a site configuration change request in delta site control file %2 specifies a site server installation directory ...
  66. The "%1" item in a site configuration change request in delta site control file %2 specifies a site server name ("%3") that ...
  67. The "%1" item in a site configuration change request in delta site control file %2 specifies a site type that does not match ...
  68. The "%1" item in a site configuration change request in delta site control file %2 specifies a SQL administrator account ...
  69. The "%1" item in a site configuration change request in delta site control file %2 specifies an invalid public key for decrypting ...
  70. The "%1" item in a site configuration change request in delta site control file %2 specifies an service account name and/or ...
  71. The "%1" item in a site configuration change request in delta site control file %2 specifies that the change request should ...
  72. The "%1" item in a site configuration change request in delta site control file %2 was submitted by a server component at ...
  73. The "%1" item in a site configuration change request in delta site control file %2contains a full version that's older than ...
  74. The "%1" item in a site configuration change request in delta site control file %2does not specify the domain of the service ...
  75. The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting ...