COM Error Codes (Security and Setup)
The following table provides a list of error codes used by COM-based APIs.
If you are experiencing difficulty with an application you are installing or running, contact customer support for the software that is displaying the error message. To obtain support for a Microsoft product, go to https://support.microsoft.com.
| Constant/value | Description |
|---|---|
|
The specified event is currently not being audited. |
|
The SID filtering operation removed all SIDs. |
|
Business rule scripts are disabled for the calling application. |
|
The packaging API has encountered an internal error. |
|
The file is not a valid package because its contents are interleaved. |
|
The file is not a valid package because it contains OPC relationships. |
|
The file is not a valid package because it is missing a manifest or block map, or missing a signature file when the code integrity file is present. |
|
The package's manifest is invalid. |
|
The package's block map is invalid. |
|
The package's content cannot be read because it is corrupt. |
|
The computed hash value of the block does not match the one stored in the block map. |
|
The requested byte range is over 4GB when translated to byte range of blocks. |
|
The SIP_SUBJECTINFO structure used to sign the package didn't contain the required data. |
|
The app didn't start in the required time. |
|
The app didn't start. |
|
This app failed to launch because of an issue with its license. Please try again in a moment. |
|
Bad UID. |
|
Bad Hash. |
|
Bad Key. |
|
Bad Length. |
|
Bad Data. |
|
Invalid Signature. |
|
Bad Version of provider. |
|
Invalid algorithm specified. |
|
Invalid flags specified. |
|
Invalid type specified. |
|
Key not valid for use in specified state. |
|
Hash not valid for use in specified state. |
|
Key does not exist. |
|
Insufficient memory available for the operation. |
|
Object already exists. |
|
Access denied. |
|
Object was not found. |
|
Data already encrypted. |
|
Invalid provider specified. |
|
Invalid provider type specified. |
|
Provider's public key is invalid. |
|
Keyset does not exist |
|
Provider type not defined. |
|
Provider type as registered is invalid. |
|
The keyset is not defined. |
|
Keyset as registered is invalid. |
|
Provider type does not match registered value. |
|
The digital signature file is corrupt. |
|
Provider DLL failed to initialize correctly. |
|
Provider DLL could not be found. |
|
The Keyset parameter is invalid. |
|
An internal error occurred. |
|
A base error occurred. |
|
Provider could not perform the action since the context was acquired as silent. |
|
The security token does not have storage space available for an additional container. |
|
The profile for the user is a temporary profile. |
|
The key parameters could not be set because the CSP uses fixed parameters. |
|
The supplied handle is invalid. |
|
The parameter is incorrect. |
|
The buffer supplied to a function was too small. |
|
The requested operation is not supported. |
|
No more data is available. |
|
The supplied buffers overlap incorrectly. |
|
The specified data could not be decrypted. |
|
An internal consistency check failed. |
|
This operation requires input from the user. |
|
The cryptographic provider does not support HMAC. |
|
The device that is required by this cryptographic provider is not ready for use. |
|
The dictionary attack mitigation is triggered and the provided authorization was ignored by the provider. |
|
The validation of the provided data failed the integrity or signature validation. |
|
Incorrect password. |
|
Encryption failed. |
|
Not enough memory is available to complete this request |
|
The handle specified is invalid |
|
The function requested is not supported |
|
The specified target is unknown or unreachable |
|
The Local Security Authority cannot be contacted |
|
The requested security package does not exist |
|
The caller is not the owner of the desired credentials |
|
The security package failed to initialize, and cannot be installed |
|
The token supplied to the function is invalid |
|
The security package is not able to marshal the logon buffer, so the logon attempt has failed |
|
The per-message Quality of Protection is not supported by the security package |
|
The security context does not allow impersonation of the client |
|
The logon attempt failed |
|
The credentials supplied to the package were not recognized |
|
No credentials are available in the security package |
|
The message or signature supplied for verification has been altered |
|
The message supplied for verification is out of sequence |
|
No authority could be contacted for authentication. |
|
The function completed successfully, but must be called again to complete the context |
|
The function completed successfully, but CompleteToken must be called |
|
The function completed successfully, but both CompleteToken and this function must be called to complete the context |
|
The logon was completed, but no network authority was available. The logon was made using locally known information |
|
The requested security package does not exist |
|
The context has expired and can no longer be used. |
|
The context has expired and can no longer be used. |
|
The supplied message is incomplete. The signature was not verified. |
|
The credentials supplied were not complete, and could not be verified. The context could not be initialized. |
|
The buffers supplied to a function was too small. |
|
The credentials supplied were not complete, and could not be verified. Additional information can be returned from the context. |
|
The context data must be renegotiated with the peer. |
|
The target principal name is incorrect. |
|
There is no LSA mode context associated with this context. |
|
The clocks on the client and server machines are skewed. |
|
The certificate chain was issued by an authority that is not trusted. |
|
The message received was unexpected or badly formatted. |
|
An unknown error occurred while processing the certificate. |
|
The received certificate has expired. |
|
The specified data could not be encrypted. |
|
The specified data could not be decrypted. |
|
The client and server cannot communicate, because they do not possess a common algorithm. |
|
The security context could not be established due to a failure in the requested quality of service (e.g. mutual authentication or delegation). |
|
A security context was deleted before the context was completed. This is considered a logon failure. |
|
The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply. |
|
Unable to accomplish the requested task because the local machine does not have any IP addresses. |
|
The supplied credential handle does not match the credential associated with the security context. |
|
The crypto system or checksum function is invalid because a required function is unavailable. |
|
The number of maximum ticket referrals has been exceeded. |
|
The local machine must be a Kerberos KDC (domain controller) and it is not. |
|
The other end of the security negotiation is requires strong crypto but it is not supported on the local machine. |
|
The KDC reply contained more than one principal name. |
|
Expected to find PA data for a hint of what etype to use, but it was not found. |
|
The client certificate does not contain a valid UPN, or does not match the client name in the logon request. Please contact your administrator. |
|
Smartcard logon is required and was not used. |
|
A system shutdown is in progress. |
|
An invalid request was sent to the KDC. |
|
The KDC was unable to generate a referral for the service requested. |
|
The encryption type requested is not supported by the KDC. |
|
An unsupported preauthentication mechanism was presented to the Kerberos package. |
|
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. |
|
Client's supplied SSPI channel bindings were incorrect. |
|
The received certificate was mapped to multiple accounts. |
|
SEC_E_NO_KERB_KEY |
|
The certificate is not valid for the requested usage. |
|
The system cannot contact a domain controller to service the authentication request. Please try again later. |
|
The smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log. |
|
An untrusted certificate authority was detected While processing the smartcard certificate used for authentication. Please contact your system administrator. |
|
The revocation status of the smartcard certificate used for authentication could not be determined. Please contact your system administrator. |
|
The smartcard certificate used for authentication was not trusted. Please contact your system administrator. |
|
The smartcard certificate used for authentication has expired. Please contact your system administrator. |
|
The Kerberos subsystem encountered an error. A service for user protocol request was made against a domain controller which does not support service for user. |
|
An attempt was made by this server to make a Kerberos constrained delegation request for a target outside of the server's realm. This is not supported, and indicates a misconfiguration on this server's allowed to delegate to list. Please contact your administrator. |
|
The revocation status of the domain controller certificate used for smartcard authentication could not be determined. There is additional information in the system event log. Please contact your system administrator. |
|
An untrusted certificate authority was detected while processing the domain controller certificate used for authentication. There is additional information in the system event log. Please contact your system administrator. |
|
The domain controller certificate used for smartcard logon has expired. Please contact your system administrator with the contents of your system event log. |
|
The domain controller certificate used for smartcard logon has been revoked. Please contact your system administrator with the contents of your system event log. |
|
A signature operation must be performed before the user can authenticate. |
|
One or more of the parameters passed to the function was invalid. |
|
Client policy does not allow credential delegation to target server. |
|
Client policy does not allow credential delegation to target server with NLTM only authentication. |
|
The recipient rejected the renegotiation request. |
|
The required security context does not exist. |
|
The PKU2U protocol encountered an error while attempting to utilize the associated certificates. |
|
The identity of the server computer could not be verified. |
|
The returned buffer is only a fragment of the message. More fragments need to be returned. |
|
Only https scheme is allowed. |
|
The function completed successfully, but must be called again to complete the context. Early start can be used. |
|
An error occurred while performing an operation on a cryptographic message. |
|
Unknown cryptographic algorithm. |
|
The object identifier is poorly formatted. |
|
Invalid cryptographic message type. |
|
Unexpected cryptographic message encoding. |
|
The cryptographic message does not contain an expected authenticated attribute. |
|
The hash value is not correct. |
|
The index value is not valid. |
|
The content of the cryptographic message has already been decrypted. |
|
The content of the cryptographic message has not been decrypted yet. |
|
The enveloped-data message does not contain the specified recipient. |
|
Invalid control type. |
|
Invalid issuer and/or serial number. |
|
Cannot find the original signer. |
|
The cryptographic message does not contain all of the requested attributes. |
|
The streamed cryptographic message is not ready to return data. |
|
The streamed cryptographic message requires more data to complete the decode operation. |
|
The protected data needs to be re-protected. |
|
The length specified for the output data was insufficient. |
|
An error occurred during encode or decode operation. |
|
An error occurred while reading or writing to a file. |
|
Cannot find object or property. |
|
The object or property already exists. |
|
No provider was specified for the store or object. |
|
The specified certificate is self signed. |
|
The previous certificate or CRL context was deleted. |
|
Cannot find the requested object. |
|
The certificate does not have a property that references a private key. |
|
Cannot find the certificate and private key for decryption. |
|
Cannot find the certificate and private key to use for decryption. |
|
Not a cryptographic message or the cryptographic message is not formatted correctly. |
|
The signed cryptographic message does not have a signer for the specified signer index. |
|
Final closure is pending until additional frees or closes. |
|
The certificate is revoked. |
|
No Dll or exported function was found to verify revocation. |
|
The revocation function was unable to check revocation for the certificate. |
|
The revocation function was unable to check revocation because the revocation server was offline. |
|
The certificate is not in the revocation server's database. |
|
The string contains a non-numeric character. |
|
The string contains a non-printable character. |
|
The string contains a character not in the 7 bit ASCII character set. |
|
The string contains an invalid X500 name attribute key, oid, value or delimiter. |
|
The dwValueType for the CERT_NAME_VALUE is not one of the character strings. Most likely it is either a CERT_RDN_ENCODED_BLOB or CERT_RDN_OCTET_STRING. |
|
The Put operation cannot continue. The file needs to be resized. However, there is already a signature present. A complete signing operation must be done. |
|
The cryptographic operation failed due to a local security option setting. |
|
No DLL or exported function was found to verify subject usage. |
|
The called function was unable to do a usage check on the subject. |
|
Since the server was offline, the called function was unable to complete the usage check. |
|
The subject was not found in a Certificate Trust List (CTL). |
|
None of the signers of the cryptographic message or certificate trust list is trusted. |
|
The public key's algorithm parameters are missing. |
|
An object could not be located using the object locator infrastructure with the given name. |
|
OSS Certificate encode/decode error code base See asn1code.h for a definition of the OSS runtime errors. The OSS error values are offset by CRYPT_E_OSS_ERROR. |
|
OSS ASN.1 Error: Output Buffer is too small. |
|
OSS ASN.1 Error: Signed integer is encoded as an unsigned integer. |
|
OSS ASN.1 Error: Unknown ASN.1 data type. |
|
OSS ASN.1 Error: Output buffer is too small, the decoded data has been truncated. |
|
OSS ASN.1 Error: Invalid data. |
|
OSS ASN.1 Error: Invalid argument. |
|
OSS ASN.1 Error: Encode/Decode version mismatch. |
|
OSS ASN.1 Error: Out of memory. |
|
OSS ASN.1 Error: Encode/Decode Error. |
|
OSS ASN.1 Error: Internal Error. |
|
OSS ASN.1 Error: Invalid data. |
|
OSS ASN.1 Error: Invalid data. |
|
OSS ASN.1 Error: Unsupported BER indefinite-length encoding. |
|
OSS ASN.1 Error: Access violation. |
|
OSS ASN.1 Error: Invalid data. |
|
OSS ASN.1 Error: Invalid data. |
|
OSS ASN.1 Error: Invalid data. |
|
OSS ASN.1 Error: Internal Error. |
|
OSS ASN.1 Error: Multi-threading conflict. |
|
OSS ASN.1 Error: Invalid data. |
|
OSS ASN.1 Error: Invalid data. |
|
OSS ASN.1 Error: Invalid data. |
|
OSS ASN.1 Error: Encode/Decode function not implemented. |
|
OSS ASN.1 Error: Trace file error. |
|
OSS ASN.1 Error: Function not implemented. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Trace file error. |
|
OSS ASN.1 Error: Trace file error. |
|
OSS ASN.1 Error: Invalid data. |
|
OSS ASN.1 Error: Invalid data. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: Program link error. |
|
OSS ASN.1 Error: System resource error. |
|
OSS ASN.1 Error: Trace file error. |
|
ASN1 Certificate encode/decode error code base. The ASN1 error values are offset by CRYPT_E_ASN1_ERROR. |
|
ASN1 internal encode or decode error. |
|
ASN1 unexpected end of data. |
|
ASN1 corrupted data. |
|
ASN1 value too large. |
|
ASN1 constraint violated. |
|
ASN1 out of memory. |
|
ASN1 buffer overflow. |
|
ASN1 function not supported for this PDU. |
|
ASN1 bad arguments to function call. |
|
ASN1 bad real value. |
|
ASN1 bad tag value met. |
|
ASN1 bad choice value. |
|
ASN1 bad encoding rule. |
|
ASN1 bad unicode (UTF8). |
|
ASN1 bad PDU type. |
|
ASN1 not yet implemented. |
|
ASN1 skipped unknown extension(s). |
|
ASN1 end of data expected |
|
The request subject name is invalid or too long. |
|
The request does not exist. |
|
The request's current status does not allow this operation. |
|
The requested property value is empty. |
|
The certification authority's certificate contains invalid data. |
|
Certificate service has been suspended for a database restore operation. |
|
The certificate contains an encoded length that is potentially incompatible with older enrollment software. |
|
The operation is denied. The user has multiple roles assigned and the certification authority is configured to enforce role separation. |
|
The operation is denied. It can only be performed by a certificate manager that is allowed to manage certificates for the current requester. |
|
Cannot archive private key. The certification authority is not configured for key archival. |
|
Cannot archive private key. The certification authority could not verify one or more key recovery certificates. |
|
The request is incorrectly formatted. The encrypted private key must be in an unauthenticated attribute in an outermost signature. |
|
At least one security principal must have the permission to manage this CA. |
|
The request contains an invalid renewal certificate attribute. |
|
An attempt was made to open a Certification Authority database session, but there are already too many active sessions. The server may need to be configured to allow additional sessions. |
|
A memory reference caused a data alignment fault. |
|
The permissions on this certification authority do not allow the current user to enroll for certificates. |
|
The permissions on the certificate template do not allow the current user to enroll for this type of certificate. |
|
The contacted domain controller cannot support signed LDAP traffic. Update the domain controller or configure Certificate Services to use SSL for Active Directory access. |
|
The request was denied by a certificate manager or CA administrator. |
|
An enrollment policy server cannot be located. |
|
The requested certificate template is not supported by this CA. |
|
The request contains no certificate template information. |
|
The request contains conflicting template information. |
|
The request is missing a required Subject Alternate name extension. |
|
The request is missing a required private key for archival by the server. |
|
The request is missing a required SMIME capabilities extension. |
|
The request was made on behalf of a subject other than the caller. The certificate template must be configured to require at least one signature to authorize the request. |
|
The request template version is newer than the supported template version. |
|
The template is missing a required signature policy attribute. |
|
The request is missing required signature policy information. |
|
The request is missing one or more required signatures. |
|
One or more signatures did not include the required application or issuance policies. The request is missing one or more required valid signatures. |
|
The request is missing one or more required signature issuance policies. |
|
The UPN is unavailable and cannot be added to the Subject Alternate name. |
|
The Active Directory GUID is unavailable and cannot be added to the Subject Alternate name. |
|
The DNS name is unavailable and cannot be added to the Subject Alternate name. |
|
The request includes a private key for archival by the server, but key archival is not enabled for the specified certificate template. |
|
The public key does not meet the minimum size required by the specified certificate template. |
|
The EMail name is unavailable and cannot be added to the Subject or Subject Alternate name. |
|
One or more certificate templates to be enabled on this certification authority could not be found. |
|
The certificate template renewal period is longer than the certificate validity period. The template should be reconfigured or the CA certificate renewed. |
|
The certificate template requires too many RA signatures. Only one RA signature is allowed. |
|
The certificate template requires renewal with the same public key, but the request uses a different public key. |
|
The key is not exportable. |
|
You cannot add the root CA certificate into your local store. |
|
The key archival hash attribute was not found in the response. |
|
An unexpected key archival hash attribute was found in the response. |
|
There is a key archival hash mismatch between the request and the response. |
|
Signing certificate cannot include SMIME extension. |
|
A system-level error occurred while verifying trust. |
|
The certificate for the signer of the message is invalid or not found. |
|
One of the counter signatures was invalid. |
|
The signature of the certificate cannot be verified. |
|
The timestamp signature and/or certificate could not be verified or is malformed. |
|
The digital signature of the object did not verify. |
|
A certificate's basic constraint extension has not been observed. |
|
The certificate does not meet or contain the Authenticode(tm) financial extensions. |
|
Tried to reference a part of the file outside the proper range. |
|
Could not retrieve an object from the file. |
|
Could not find the head table in the file. |
|
The magic number in the head table is incorrect. |
|
The offset table has incorrect values. |
|
Duplicate table tags or tags out of alphabetical order. |
|
A table does not start on a long word boundary. |
|
First table does not appear after header information. |
|
Two or more tables overlap. |
|
Too many pad bytes between tables or pad bytes are not 0. |
|
File is too small to contain the last table. |
|
A table checksum is incorrect. |
|
The file checksum is incorrect. |
|
The signature does not have the correct attributes for the policy. |
|
The file did not pass the hints check. |
|
The file is not an OpenType file. |
|
Failed on a file operation (open, map, read, write). |
|
A call to a CryptoAPI function failed. |
|
There is a bad version number in the file. |
|
The structure of the DSIG table is incorrect. |
|
A check failed in a partially constant table. |
|
Some kind of structural error. |
|
The requested credential requires confirmation. |
|
Unknown trust provider. |
|
The trust verification action specified is not supported by the specified trust provider. |
|
The form specified for the subject is not one supported or known by the specified trust provider. |
|
The subject is not trusted for the specified action. |
|
Error due to problem in ASN.1 encoding process. |
|
Error due to problem in ASN.1 decoding process. |
|
Reading / writing Extensions where Attributes are appropriate, and visa versa. |
|
Unspecified cryptographic failure. |
|
The size of the data could not be determined. |
|
The size of the indefinite-sized data could not be determined. |
|
This object does not read and write self-sizing data. |
|
No signature was present in the subject. |
|
A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. |
|
The validity periods of the certification chain do not nest correctly. |
|
A certificate that can only be used as an end-entity is being used as a CA or visa versa. |
|
A path length constraint in the certification chain has been violated. |
|
A certificate contains an unknown extension that is marked 'critical'. |
|
A certificate being used for a purpose other than the ones specified by its CA. |
|
A parent of a given certificate in fact did not issue that child certificate. |
|
A certificate is missing or has an empty value for an important field, such as a subject or issuer name. |
|
A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. |
|
A certificate chain could not be built to a trusted root authority. |
|
Generic trust failure. |
|
A certificate was explicitly revoked by its issuer. |
|
The certification path terminates with the test root which is not trusted with the current policy settings. |
|
The revocation process could not continue - the certificate(s) could not be checked. |
|
The certificate's CN name does not match the passed value. |
|
The certificate is not valid for the requested usage. |
|
The certificate was explicitly marked as untrusted by the user. |
|
A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider. |
|
The certificate has invalid policy. |
|
The certificate has an invalid name. The name is not included in the permitted list or is explicitly excluded. |
|
A non-empty line was encountered in the INF before the start of a section. |
|
A section name marker in the INF is not complete, or does not exist on a line by itself. |
|
An INF section was encountered whose name exceeds the maximum section name length. |
|
The syntax of the INF is invalid. |
|
The style of the INF is different than what was requested. |
|
The required section was not found in the INF. |
|
The required line was not found in the INF. |
|
The files affected by the installation of this file queue have not been backed up for uninstall. |
|
The INF or the device information set or element does not have an associated install class. |
|
The INF or the device information set or element does not match the specified install class. |
|
An existing device was found that is a duplicate of the device being manually installed. |
|
There is no driver selected for the device information set or element. |
|
The requested device registry key does not exist. |
|
The device instance name is invalid. |
|
The install class is not present or is invalid. |
|
The device instance cannot be created because it already exists. |
|
The operation cannot be performed on a device information element that has not been registered. |
|
The device property code is invalid. |
|
The INF from which a driver list is to be built does not exist. |
|
The device instance does not exist in the hardware tree. |
|
The icon representing this install class cannot be loaded. |
|
The class installer registry entry is invalid. |
|
The class installer has indicated that the default action should be performed for this installation request. |
|
The operation does not require any files to be copied. |
|
The specified hardware profile does not exist. |
|
There is no device information element currently selected for this device information set. |
|
The operation cannot be performed because the device information set is locked. |
|
The operation cannot be performed because the device information element is locked. |
|
The specified path does not contain any applicable device INFs. |
|
No class installer parameters have been set for the device information set or element. |
|
The operation cannot be performed because the file queue is locked. |
|
A service installation section in this INF is invalid. |
|
There is no class driver list for the device information element. |
|
The installation failed because a function driver was not specified for this device instance. |
|
There is presently no default device interface designated for this interface class. |
|
The operation cannot be performed because the device interface is currently active. |
|
The operation cannot be performed because the device interface has been removed from the system. |
|
An interface installation section in this INF is invalid. |
|
This interface class does not exist in the system. |
|
The reference string supplied for this interface device is invalid. |
|
The specified machine name does not conform to UNC naming conventions. |
|
A general remote communication error occurred. |
|
The machine selected for remote communication is not available at this time. |
|
The Plug and Play service is not available on the remote machine. |
|
The property page provider registry entry is invalid. |
|
The requested device interface is not present in the system. |
|
The device's co-installer has additional work to perform after installation is complete. |
|
The device's co-installer is invalid. |
|
There are no compatible drivers for this device. |
|
There is no icon that represents this device or device type. |
|
A logical configuration specified in this INF is invalid. |
|
The class installer has denied the request to install or upgrade this device. |
|
One of the filter drivers installed for this device is invalid. |
|
The driver selected for this device does not support this version of Windows. |
|
The driver selected for this device does not support Windows. |
|
The third-party INF does not contain digital signature information. |
|
An invalid attempt was made to use a device installation file queue for verification of digital signatures relative to other platforms. |
|
The device cannot be disabled. |
|
The device could not be dynamically removed. |
|
Cannot copy to specified target. |
|
Driver is not intended for this platform. |
|
Operation not allowed in WOW64. |
|
The operation involving unsigned file copying was rolled back, so that a system restore point could be set. |
|
An INF was copied into the Windows INF directory in an improper manner. |
|
The Security Configuration Editor (SCE) APIs have been disabled on this Embedded product. |
|
An unknown exception was encountered. |
|
A problem was encountered when accessing the Plug and Play registry database. |
|
The requested operation is not supported for a remote machine. |
|
The specified file is not an installed OEM INF. |
|
One or more devices are presently installed using the specified INF. |
|
The requested device install operation is obsolete. |
|
A file could not be verified because it does not have an associated catalog signed via Authenticode(tm). |
|
Authenticode(tm) signature verification is not supported for the specified INF. |
|
The INF was signed with an Authenticode(tm) catalog from a trusted publisher. |
|
The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted. |
|
The publisher of an Authenticode(tm) signed catalog was not established as trusted. |
|
The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version. |
|
The file may only be validated by a catalog signed via Authenticode(tm). |
|
One of the installers for this device cannot perform the installation at this time. |
|
A problem was encountered while attempting to add the driver to the store. |
|
The installation of this device is forbidden by system policy. Contact your system administrator. |
|
The installation of this driver is forbidden by system policy. Contact your system administrator. |
|
The specified INF is the wrong type for this operation. |
|
The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering. |
|
A problem was encountered while attempting to delete the driver from the store. |
|
An unrecoverable stack overflow was encountered. |
|
No installed components were detected. |
|
An internal consistency check failed. |
|
The action was canceled by an SCardCancel request. |
|
The supplied handle was invalid. |
|
One or more of the supplied parameters could not be properly interpreted. |
|
Registry startup information is missing or invalid. |
|
Not enough memory available to complete this command. |
|
An internal consistency timer has expired. |
|
The data buffer to receive returned data is too small for the returned data. |
|
The specified reader name is not recognized. |
|
The user-specified timeout value has expired. |
|
The smart card cannot be accessed because of other connections outstanding. |
|
The operation requires a Smart Card, but no Smart Card is currently in the device. |
|
The specified smart card name is not recognized. |
|
The system could not dispose of the media in the requested manner. |
|
The requested protocols are incompatible with the protocol currently in use with the smart card. |
|
The reader or smart card is not ready to accept commands. |
|
One or more of the supplied parameters values could not be properly interpreted. |
|
The action was canceled by the system, presumably to log off or shut down. |
|
An internal communications error has been detected. |
|
An internal error has been detected, but the source is unknown. |
|
An ATR obtained from the registry is not a valid ATR string. |
|
An attempt was made to end a non-existent transaction. |
|
The specified reader is not currently available for use. |
|
The operation has been aborted to allow the server application to exit. |
|
The PCI Receive buffer was too small. |
|
The reader driver does not meet minimal requirements for support. |
|
The reader driver did not produce a unique reader name. |
|
The smart card does not meet minimal requirements for support. |
|
The Smart card resource manager is not running. |
|
The Smart card resource manager has shut down. |
|
An unexpected card error has occurred. |
|
No Primary Provider can be found for the smart card. |
|
The requested order of object creation is not supported. |
|
This smart card does not support the requested feature. |
|
The identified directory does not exist in the smart card. |
|
The identified file does not exist in the smart card. |
|
The supplied path does not represent a smart card directory. |
|
The supplied path does not represent a smart card file. |
|
Access is denied to this file. |
|
The smartcard does not have enough memory to store the information. |
|
There was an error trying to set the smart card file object pointer. |
|
The supplied PIN is incorrect. |
|
An unrecognized error code was returned from a layered component. |
|
The requested certificate does not exist. |
|
The requested certificate could not be obtained. |
|
Cannot find a smart card reader. |
|
A communications error with the smart card has been detected. Retry the operation. |
|
The requested key container does not exist on the smart card. |
|
The Smart card resource manager is too busy to complete this operation. |
|
The smart card PIN cache has expired. |
|
The smart card PIN cannot be cached. |
|
The smart card is read only and cannot be written to. |
|
The reader cannot communicate with the smart card, due to ATR configuration conflicts. |
|
The smart card is not responding to a reset. |
|
Power has been removed from the smart card, so that further communication is not possible. |
|
The smart card has been reset, so any shared state information is invalid. |
|
The smart card has been removed, so that further communication is not possible. |
|
Access was denied because of a security violation. |
|
The card cannot be accessed because the wrong PIN was presented. |
|
The card cannot be accessed because the maximum number of PIN entry attempts has been reached. |
|
The end of the smart card file has been reached. |
|
The action was canceled by the user. |
|
No PIN was presented to the smart card. |
|
The requested item could not be found in the cache. |
|
The requested cache item is too old and was deleted from the cache. |
|
The new cache item exceeds the maximum per-item size defined for the cache. |
|
Authentication target is invalid or not configured correctly. |
|
Your application cannot get the Online Id properties due to the Terms of Use accepted by the user. |
Requirements
| Requirement | Value |
|---|---|
| Header |
|