System Center Configuration Manager 2012
- Synchronization component failed: Unable to write to %2. Type = %1. Possible cause: Typically, this error results when the ...
- Syncml(202): Accepted for processing. The request to either run a remote execution of an application or to alert a user or ...
- Syncml(203): Non-authoritative response. The request is being responded to by an entity other than the one targeted. The ...
- Syncml(204): The request was successfully completed but no data is being returned. The response code is also returned in ...
- Syncml(205): The source SHOULD update their content. The originator of the request is being told that their content SHOULD ...
- Syncml(206): The response indicates that only part of the command was completed. If the remainder of the command can be completed ...
- Syncml(207): Conflict resolved with merge. The response indicates that the request created a conflict; which was resolved ...
- Syncml(208): Conflict resolved with client's command "winning". The response indicates that there was an update conflict; ...
- Syncml(209): Conflict resolved with duplicate. The response indicates that the request created an update conflict; which ...
- Syncml(210): Delete without archive. The response indicates that the requested data was successfully deleted, but that it ...
- Syncml(212): Authentication accepted. No further authentication is needed for the remainder of the synchronization session. ...
- Syncml(214): Operation cancelled. The SyncML command completed successfully, but no more commands will be processed within ...
- Syncml(413): The recipient is refusing to perform the requested command because the requested item is larger than the recipient ...
- Syncml(414): The requested command failed because the target URI is too long for what the recipient is able or willing to ...
- Syncml(424): The chunked object was received, but the size of the received object did not match the size declared within ...
- Syncml(425): The requested command failed because the sender does not have adequate access control permissions (ACL) on the ...
- Syncml(502): The recipient, while acting as a gateway or proxy, received an invalid response from the upstream recipient ...
- Syncml(503): The recipient is currently unable to handle the request due to a temporary overloading or maintenance of the ...
- Syncml(504): The recipient, while acting as a gateway or proxy, did not receive a timely response from the upstream recipient ...
- Syncml(505): The recipient does not support or refuses to support the specified version of SyncML DTD used in the request ...
- Syncml(508): An error occurred that necessitates a refresh of the current synchronization state of the client with the server. ...
- Syncml(510): An error occurred while processing the request. The error is related to a failure in the recipient data store. ...
- Syncml(513): The recipient does not support or refuses to support the specified version of the SyncML Synchronization Protocol ...
- Syncml(514): The SyncML command was not completed successfully, since the operation was already cancelled before processing ...
- Syncml: An error occurred that necessitates a refresh of the current synchronization state of the client with the server. ...
- Syncml: The chunked object was received, but the size of the received object did not match the size declared within the first ...
- Syncml: The recipient does not support or refuses to support the specified version of SyncML DTD used in the request SyncML ...
- Syncml: The recipient does not support or refuses to support the specified version of the SyncML Synchronization Protocol ...
- Syncml: The recipient is currently unable to handle the request due to a temporary overloading or maintenance of the recipient. ...
- Syncml: The recipient is refusing to perform the requested command because the requested item is larger than the recipient ...
- Syncml: The recipient, while acting as a gateway or proxy, did not receive a timely response from the upstream recipient ...
- Syncml: The recipient, while acting as a gateway or proxy, received an invalid response from the upstream recipient it accessed ...
- Syncml: The requested command failed because the sender does not have adequate access control permissions (ACL) on the recipient. ...
- Syncml: The requested command failed because the target URI is too long for what the recipient is able or willing to process. ...
- Syncml: The SyncML command was not completed successfully, since the operation was already cancelled before processing the ...
- System Center Operations Manager might generate alerts when a device installs a software update. To avoid receiving alerts ...
- System Center Operations Manager might generate alerts when these software updates runs. To avoid receiving alerts for this ...
- System Center Operations Manager might generate alerts when this program runs. To avoid receiving alerts for this planned ...
- Systems that do not have the Configuration Manager client installed. Systems require the Configuration Manager client before ...
- Task sequence '%s' will run on this computer in %s seconds. Windows could be installed on this computer and all data on this ...
- Task Sequence: %1!s! has failed with the error code ( 2!08lX!). For more information, contact your system administrator or ...
- The "%1" item in a site configuration change request in delta site control file %2 does not identify the change request as ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify a site code. This site ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify a site name. This site ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the domain of the site ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the service ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL administrator ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL Server ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the plain text name of ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the public key for decrypting ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server installation ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server's platform. ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify which component submitted ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify which computer submitted ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify which site should receive ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify which site submitted ...
- The "%1" item in a site configuration change request in delta site control file %2 does not specify which user submitted ...
- The "%1" item in a site configuration change request in delta site control file %2 specifies a site code (%3) that does not ...
- The "%1" item in a site configuration change request in delta site control file %2 specifies a site name ("%3") that does ...
- The "%1" item in a site configuration change request in delta site control file %2 specifies a site server domain (%3) that ...
- The "%1" item in a site configuration change request in delta site control file %2 specifies a site server installation directory ...
- The "%1" item in a site configuration change request in delta site control file %2 specifies a site server name ("%3") that ...
- The "%1" item in a site configuration change request in delta site control file %2 specifies a site type that does not match ...
- The "%1" item in a site configuration change request in delta site control file %2 specifies a SQL administrator account ...
- The "%1" item in a site configuration change request in delta site control file %2 specifies an invalid public key for decrypting ...
- The "%1" item in a site configuration change request in delta site control file %2 specifies an service account name and/or ...
- The "%1" item in a site configuration change request in delta site control file %2 specifies that the change request should ...
- The "%1" item in a site configuration change request in delta site control file %2 was submitted by a server component at ...
- The "%1" item in a site configuration change request in delta site control file %2contains a full version that's older than ...
- The "%1" item in a site configuration change request in delta site control file %2does not specify the domain of the service ...
- The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting ...