A token request was received for an application with the Uniform Resource Locator (URL) '%1', but the request could not be fulfilled because the URL does not identify any known application. URL: %1 This request will be failed. User Action If this URL should be handled, verify that it matches the URL for the application in the Federation Service trust policy. Hypertext Transfer Protocol (HTTP) URLs are matched according to a set of rules in the HTTP specification. Host names are case insensitive, but the path portion of the URL is matched in a case-sensitive manner. Additional Data Refer to Request for Comments (RFC) 2616 for HTTP URL matching rules.
A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. ...
A TLN or Exclusion record with the specified name exists on the trust but it's type does not match the switch used. Ensure ...
A TLS server certificate was found for SMTP virtual server instance '%1' with thumbprint %2. TLS will be available for this ...
A token request was received for a resource partner with the Uniform Resource Identifier (URI) '%1', but the request could ...
A token request was received for an application with the Uniform Resource Locator (URL) '%1', but the request could not be ...
A Token Ring Lobe Wire Fault has occurred. Verify cable connections. The network adapter will continue to try to reinsert ...
A torn-write was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. This ...
A torn-write was detected during soft recovery in logfile %4. The failing checksum record is located at position %5. The ...
A torn-write was detected while restoring from backup in logfile %4 of the backup set. The failing checksum record is located ...