2.10.3 System Configuration Corruption and Other Internal Failures
A participant in the system could detect an unrecoverable internal state during its lifetime due to corruption of its configuration data, or due to the system that is under high resource load. In such scenarios, if the system participant that experiences this problem determines that it cannot continue to process the specific type of future requests or any communication with any other entities, it can send an error to abort the call. If the operation originates from this participant, for example the server, then the operation will be attempted again after appropriate changes have been made to repair the internal error, such as by resetting the configuration data. If the operation originates from another participant, for example the client, that participant will retry the specific operation after the internal error is resolved.
For details about how each protocol handles system errors, see [MS-WMI] section 2.2.11, [MS-WSMV] section 2.2.4.39, and also [MS-WSMAN] section 2.2.4.1.