What does this error mean?
The browser or signing workflow cannot communicate correctly with the PKI component used for the digital certificate.
PKIPKI Errors
PKI component error
The browser or signing workflow cannot communicate correctly with the PKI component used for the digital certificate.
Why does this happen?
- The PKI or signer utility is not running.
- The browser cannot reach the local signing service.
- Token middleware, browser permissions, or security software is blocking communication.
How to fix this error
- Restart the PKI or signer utility.
- Confirm that the DSC token certificate is visible in Windows.
- Check the browser, local service port, and security software before retrying.
Who should resolve it?
Filing User / IT Team
Send the exact error, filing reference, date, time, and supporting source document to the responsible team.
Related errors
Check these messages if the first fix does not match
Improve this guide
Was this solution helpful?
Your response helps EximSign prioritise unclear or incomplete error guides.
Practical guidance
These solutions are operational guidance, not a replacement for current ICEGATE instructions, customs orders, GST rules, bank requirements, or advice from the responsible authority.
PKI FAQ
Questions users ask after seeing this error
What does PKI mean?
The browser or signing workflow cannot communicate correctly with the PKI component used for the digital certificate.
Can I refile after fixing this error?
Refiling depends on the transaction. First confirm whether the original submission failed, is pending, or already created an acknowledgement.
Who should resolve this issue?
Filing User / IT Team should review the relevant source record or system step.
Is this always an ICEGATE system problem?
No. The cause may be source data, a carrier filing, GST or bank validation, DSC setup, user access, Customs processing, or the ICEGATE service.
Should I contact Customs?
Contact Customs when the record is waiting for officer action, assessment, approval, or a customs query. Technical and source-data issues should go to the responsible team first.
How long does resolution usually take?
There is no fixed time. A local data or DSC issue may be corrected quickly, while carrier, bank, GST, or Customs processing depends on the responsible organisation.