When a Host Integration Server client tries to use the CryptAcquireContext function, the function fails and NTE_PROV_TYPE_NO_MATCH is returned under certain conditions
This problem occurs because a wrong provider type is specified, as in the following example:
CryptAcquireContext ( & hProv, NULL, MS_ENH_RSA_AES_PROV, PROV_RSA_FULL, CRYPT_NEWKEYSET) error: 8009 001B
If the first call to the CryptAcquireContext function fails (returns as false) and the NTE_BAD_KEYSET error is returned, a second request is sent that uses CRYPT_NEWKEYSET. However, this second call uses the wrong provider type.
In this case, you may receive the following error message:
Provider type does not match registered value.
The fix that resolves this problem is included in the following cumulative updates for Host Integration Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology Microsoft uses to describe software updates.