Site Control Manager aborted the processing of delta site control file %1.%12 Possible cause: The delta site control file ...

%11Site 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 a ConfigMgr 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 Configuration Manager Console), 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, 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 Hierarchy Manager at the site that submitted the file using the Configuration Manager Service Manager application. Hierarchy Manager will continue to submit new delta site control files until all outstanding site configuration change requests have been made.%0