SmartCard device is disconnected from ICA after 60s .Users smart card connection is timed out while renewing the certificates on Smart card

SmartCard device is disconnected from ICA after 60s .Users smart card connection is timed out while renewing the certificates on Smart card

book

Article ID: CTX269693

calendar_today

Updated On:

Description

When users are using SmartCard device to Launch Desktop or Application, the have noticed that  after logging to ICA session (Citrix Virtual Apps & desktops version 7.15 CU2 LTSR on Windows Server 2016)  all user's certificates checked with special application. If a certificate is not valid/expired, this special application works with SmartCard and deletes/issues & saves new certificate. This process sometimes takes more than 60s,  After 60s connection to SmartCard device is lost and following exception is thrown.

[2019-06-05 17:02:52.126E4FC1 PID=0000DC98 TID=0002FE30] L(02) MPMD_VerifyMPSignature 0x0 [2019-06-05 17:02:53.126E535B PID=0000DC98 TID=00023460] L(00) DLL_THREAD_DETACH [2019-06-05 17:02:55.126E5CB2 PID=0000DC98 TID=00030930] L(00) DLL_THREAD_DETACH [2019-06-05 17:03:04.126E7FCA PID=0000DC98 TID=00011884] L(00) DLL_THREAD_DETACH [2019-06-05 17:03:11.126E9B9F PID=0000DC98 TID=00001D9C] L(00) DLL_THREAD_DETACH [2019-06-05 17:03:11.126E9B9F PID=0000DC98 TID=0002F564] L(00) DLL_THREAD_DETACH [2019-06-05 17:03:11.126E9B9F PID=0000DC98 TID=0002D47C] L(00) DLL_THREAD_DETACH [2019-06-05 17:03:16.126EAEC9 PID=0000DC98 TID=0002A06C] L(00) DLL_THREAD_DETACH [2019-06-05 17:03:24.126ECF80 PID=0000DC98 TID=000088F0] L(00) DLL_THREAD_DETACH [2019-06-05 17:03:52.126F3A21 PID=0000DC98 TID=0002FE30] ER L(02) SCardTransmit !ERR 0x8010001d

Issue is not reproducible,at all time.  

Resolution

Create the following registry  DWORD value named  VcResponseTimeoutValue"

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Citrix\SmartCard

DWORD value named "VcResponseTimeoutValue"

with value 120 or 300 on the client machine.

Problem Cause

This is a Microsoft problem, and customer needs involve Microsoft for the fix. However, they can  get around the problem by setting the above  registry  key