The session setup from computer '%1' failed because the security database does not contain a trust account '%2' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and '%2' is a legitimate machine account for the computer '%1' then '%1' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: If '%2' is a legitimate machine account for the computer '%1', then '%1' should be rejoined to the domain. If '%2' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that '%2' is not a legitimate account, the following action should be taken on '%1': If '%1' is a Domain Controller, then the trust associated with '%2' should be deleted. If '%1' is not a Domain Controller, it should be disjoined from the domain.
The session ended due to an internal error. Try to connect again. If the problem persists, contact your system administrator. ...
The session has been disconnected due to a decompression failure. Try to connect again. If the problem persists, contact ...
The session has been disconnected due to a network error. Try to connect again. If the problem persists, contact your network ...
The session is busy. You will be connected to the session as soon as it is available. To cancel the Enter-PSSession command, ...
The session setup from computer '%1' failed because the security database does not contain a trust account '%2' referenced ...
The session setup from the computer %1 failed to authenticate. The name(s) of the account(s) referenced in the security database ...
The session setup to the Windows Domain Controller %1 for the domain %2 failed because %1 does not support signing or sealing ...
The session setup to the Windows Domain Controller %1 for the domain %2 failed because the computer %3 does not have a local ...
The session setup to the Windows Domain Controller %1 for the domain %2 failed because the Domain Controller did not have ...