Posts

Showing posts from 2023

Embridge signer is not working on HRMS portal with M-Toke Crypto driver

While utilizing HRMS APAR with EMBridge Signer, we encountered an issue where the signer functionality was not working as expected. To address this, we took the following steps in an attempt to resolve the problem: We attempted to update the EMBridge Software to ensure that we were using the latest version, hoping that it might contain bug fixes or improvements. We also installed CA Certificates from our signing vendor, as this is essential for ensuring secure and trusted digital signatures. Despite these efforts, the issue persisted, and the EMBridge Signer remained non-functional. Subsequently, we explored alternative solutions to rectify the problem. It was during this process that we came across the Crypto Signer Software, available for download from the following link: Link to Crypto Signer Software https://prospectlegal.in/download-mtoken-driver-for-windows-10-32bit-64-bit/ After installing the Crypto Signer Software from the provided source, we were pleased to find that it effec

E-office and PARICHAY Digital Signer troubleshooting guide

Image
  E-office and PARICHAY Digital Signer troubleshooting guide Recently it is observed while Gazetted Officers signing for their APAR and IPR with DSC Signer 4.0 which is recommended for Digital signing any document/page in E-office/SPPARROW is not working properly and tossing different error, whereas it was working fine before. So we recommended to process using e-hastakshar method for APAR signing but IPR page was still causing errors in few cases. After few tests/tweaks we observed below 1.      DSC Signer 4.0 & 4.1 is working fine if anyone is only using E-Office as signing application ( existing known method) Available signer and method on below URL’s  https://tinyurl.com/eofficembdiv http://tinyurl.com/moradabaddivision https://mbdiv.blogspot.com/ 2.      E-office has release a DSC Signer Version 4.1.7 which is working fine for E-Office as well as SPPARROW signing once recommended method is followed. It is now suggested to uninstall 4.0 or 4.1 and use 4.1.