Windows 10
- I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data. ...
- I64i! bytes could not be recovered because of bad clusters on the backup image. You can retry the recovery operation using ...
- I64i! bytes could not be written to the recovered volume because of bad clusters on the volume (%2). Run CHKDSK /R on the ...
- Iashlpr initialization failed: %1, so DHCP server cannot talk to NPS server. It could be that IAS service is not started. ...
- ICACLS name /save aclfile /T /C /L /Q stores the DACLs for the files and folders that match the name into aclfile for later ...
- ICACLS name /save aclfile /T /C stores the DACLs for the files and folders that match the name into aclfile for later use ...
- ICC profile information: size = %1 bytes, version = %2, class = '%3', data color space = '%4', profile connection space = ...
- Id = %1; ClientMachine = %2; User = %3; ClientProcessId = %4; Component = %5; Operation = %6; ResultCode = %7; PossibleCause ...
- ID Process is the unique identifier of this process. ID Process numbers are reused, so they only identify a process for the ...
- Id that is globally unique to each instance of each adapter. This is the value reported by the MSiSCSI_HBAInformation class. ...
- ID Thread is the unique identifier of this thread. ID Thread numbers are reused, so they only identify a thread for the lifetime ...
- ID1004: The sign-in session is being terminated because the ticket is expired. Current time: '{0}' Expiration time: '{1}' ...
- ID1005: The format of the data is incorrect. The signature length is negative: '{0}'. The cookie may have been truncated. ...
- ID1013: The format of the data is incorrect. The signature is larger than the corresponding data. The cookie may have been ...
- ID1020: The security token received at the relying party is not a bearer token. The security token service must be configured ...
- ID1022: The value cannot be negative, it is used to specify a TimeSpan. Check where this value is set and ensure it is not ...
- ID1025: Cannot find a unique certificate that matches the criteria. StoreName: '{0}' StoreLocation: '{1}' X509FindType: '{2}' ...
- ID1029: The custom type is not suitable because it does not extend the correct base class. CustomType: '{0}' BaseClass: '{1}' ...
- ID1032: At least one 'audienceUri' must be specified in the SamlSecurityTokenRequirement when the AudienceUriMode is set ...
- ID1035: The SAML Assertion did not contain any AudienceRestrictionConditions. To accept assertions without AudienceRestrictionConditions, ...
- ID1037: The AudienceRestrictionCondition was not valid because it contains multiple Audiences none of which is present in ...
- ID1038: The AudienceRestrictionCondition was not valid because the specified Audience is not present in AudienceUris. Audience: ...
- ID1039: The certificate's private key could not be accessed. Ensure the access control list (ACL) on the certificate's private ...
- ID1044: An encrypted security token was received at the relying party which could not be decrypted. Configure the relying ...
- ID1045: A valid STS address is not provided for performing passive redirects from the WSFederationAuthenticationModule. Set ...
- ID1046: A valid relying party realm is not provided for performing passive redirects from the WSFederationAuthenticationModule. ...
- ID1047: A valid STS address is not configured on the WSFederationAuthenticationModule for creating WS-Federation passive ...
- ID1048: A valid relying party realm is not provided for performing passive redirects from the WSFederationAuthenticationModule. ...
- ID1050: The value specified for the Freshness property on the WSFederationAuthenticationModule is not valid. If specified, ...
- ID1053: The IClaimsIdentity contained multiple UPN Claims. The automatic Windows identity mapping feature does not support ...
- ID1054: The IClaimsIdentity did not contain a valid UPN Claim. The automatic Windows identity mapping feature requires exactly ...
- ID1056: The RequireHttps attribute is set to true but Issuer URI scheme is not https. Change the Issuer URI scheme to https ...
- ID1057: The RequireHttps attribute is set to true but Reply URI scheme is not https. Change the Reply URI scheme to https ...
- ID1058: A valid STS address is not configured on the WSFederationAuthenticationModule for creating WS-Federation passive ...
- ID1059: Cannot authenticate the user because the URL scheme is not https and requireSsl is set to true in the configuration, ...
- ID1068: The decompressed cookie exceeds the maximum size of '{0}' bytes. If this is expected, increase the MaxDecompressedSize ...
- ID1069: The ClaimsAuthorizationModule cannot be used without at least one other module such as a WSFederationAuthenticationModule, ...
- ID1071: The sign-in session is being terminated because the ticket is not yet valid. Current time: '{0}' ValidFrom: '{1}' ...
- ID1072: The security token cannot be added to the replay cache because it has an infinite lifetime. Either the token must ...
- ID1073: A CryptographicException occurred when attempting to decrypt the cookie using the ProtectedData API (see inner exception ...
- ID1074: A CryptographicException occurred when attempting to encrypt the cookie using the ProtectedData API (see inner exception ...
- ID2002: The AppliesTo address of the relying party was not a valid absolute URI. Override the SecurityTokenService.GetScope() ...
- ID2003: SecurityTokenService.SecurityTokenDescriptor was null. Initialize the SecurityTokenDescriptor on the STS in your ...
- ID2004: IAsyncResult must be the AsyncResult instance returned from the Begin call. The runtime is expecting '{0}', and the ...
- ID2013: SecurityTokenService.GetScope returned null. Return a suitable Scope instance from SecurityTokenService.GetScope ...
- ID2015: DefaultTokenType must be supported by the existing TokenHandlers. Try to add a TokenHandler which can handle '{0}' ...
- ID2018: The card image file name '{0}' is not valid. The specified file does not have a valid image format or GDI+ does not ...
- ID2029: The Information Card only supports mex over https. To fix this, make sure that the given mexAddress starts with https. ...
- ID2037: The GenerateScopedClaimTypes method on the scope provider needs to be implemented so that it will return a list of ...
- ID2039: The DisplayToken must have at least one DisplayClaim. To fix this, make sure the given DisplayClaim list is not empty. ...
- ID2041: X509CertificateCredentials can support only the following SecurityKeyIdentifierClause types: X509ThumbprintKeyIdentifierClause, ...
- ID2042: The Information Card image format must be either Bmp, Gif, Jpeg, Png or Tiff. To fix this, use the CardImage.CreateFromBaseImage ...
- ID2048: The given IUserCredential.CredentialType must match the one configured on the TokenServiceEndpoint. The credential ...
- ID2049: The Information card requires mex over https. To fix this, make sure that the TokenServiceEndpoint contains a valid ...
- ID2050: When the KeyType is bearer, it is not valid to have a KeySize element with a value other than zero in the request. ...
- ID2055: The RelyingPartyParameters property on the RequestSecurityToken instance must not contain another RelyingPartyParameters. ...
- ID2059: The request has a KeySizeInBits that has no value. If you have overridden SecurityTokenService.ValidateRequest, make ...
- ID2064: The object passed as parameter named 'elementValue' must be of type 'RequestSecurityToken' when 'elementName' is ...
- ID2072: The RequestSecurityToken contains an element with name '{0}' that cannot be processed. You will need to provide a ...
- ID2073: SecurityTokenServiceConfiguration.SecurityTokenService is either null or does not have a base type of SecurityTokenService. ...
- ID2075: The computed lifetime has a creation time of '{0}' and an expiration time of '{1}'. The expiration time is before ...
- ID2076: The computed lifetime has a creation time of '{0}' and an expiration time of '{1}'. This creation time is more that ...
- ID2077: The computed lifetime has a creation time of '{0}' and an expiration time of '{1}'. The expiration time is before ...
- ID2078: The computed lifetime has a creation time of '{0}' and an expiration time of '{1}'. This produces a time span greater ...
- ID2079: SecurityTokenService.SecurityTokenDescriptor.SigningCredentials is null. Specify a valid credential to sign the issued ...
- ID2080: Cannot resolve the SecurityKeyIdentifier to a SecurityKey with the given SecurityTokenResolver. SecurityTokenResolver: ...
- ID2081: SecurityTokenService does not implement asynchronous behavior. Override BeginGetOutputClaimsIdentity/EndGetOutputClaimsIdentity ...
- ID2083: IssuerName cannot be null or empty. Create SecurityTokenServiceConfiguration with a valid TokenIssuerName or override ...
- ID2084: Cannot create EncryptingCredentials from the specified proof encryption token '{0}'. Override SecurityTokenServi ...
- ID3002: WSTrustServiceContract could not create a SecurityTokenService instance from WSTrustServiceContract.SecurityTokenServiceConfiguration. ...
- ID3013: Cannot write element '{0}' of type '{1}'. Add your custom WSTrustResponseSerializer in SecurityTokenServiceConfiguration ...
- ID3017: The token contained in the UseKey object is not recognized as a writeable token by any of the configured SecurityTokenHandlers. ...
- ID3019: Cannot create RSTR from the given message. The message must be a SignInResponseMessage and must contain a wresult ...
- ID3022: The WSTrustServiceContract only supports receiving RequestSecurityToken messages. If you need to support more message ...
- ID3023: The WSTrustServiceContract only supports receiving RequestSecurityToken messages asynchronously. If you need to support ...