Direct answer

Start with the token, then check the signer

A DSC not detected error is normally caused by one of five points: the USB token is not connected properly, its middleware is missing, Windows cannot read the smart card, the certificate is not visible, or the local signing utility is not ready. Complete the checks below in order. Do not change the XML or filing data until DSC detection is working.

Step 1

Check the USB token and port

  • 1Remove the DSC token, wait a few seconds, and reconnect it directly to another USB port. Avoid an external USB hub while testing.
  • 2If an older token is unstable on a USB 3.0 port, test a USB 2.0 port. This depends on the token model and driver, so treat it as a diagnostic check rather than a fixed rule.
  • 3Check whether the token light turns on. No light on multiple ports usually points to a USB port, token, or hardware problem.
  • 4If possible, test the token on another authorised Windows computer. This helps separate a token fault from a computer configuration problem.
Step 2

Install or repair the token middleware

The USB token needs its correct middleware or token manager. Common brands include ePass2003, ProxKey, WD Pro, eMudhra, and PantaSign, but the correct package depends on the token issued to you.

  1. Open the token's virtual CD drive or use the installer supplied by the authorised DSC provider.
  2. Close browsers and signing applications before running the setup.
  3. If an old or incorrect driver is installed, uninstall it from Windows Apps or Control Panel, restart the computer, and install the correct version.
  4. Open the token manager and confirm that it shows the certificate holder name and certificate validity.

Security note: download token middleware only from the token vendor, DSC provider, or your authorised Company/Agent. Avoid driver files shared through unknown links.

Step 3

Start the Windows Smart Card service

  1. Press Windows + R, type services.msc, and press Enter.
  2. Find Smart Card in the service list.
  3. If it is stopped, select Start. If it is already running, select Restart.
  4. On a company-managed computer, ask the IT administrator before changing the startup type. If the service repeatedly stops, the system policy or security software may need review.

Reconnect the token after the service starts, then reopen the token manager.

Step 4

Confirm that Windows can see the certificate

  1. Search Windows for Internet Options.
  2. Open Content and select Certificates.
  3. Check that the DSC certificate appears under the relevant personal certificate list.
  4. Confirm the certificate holder, validity dates, and expiry status.

If the token manager shows the certificate but Windows does not, restart the token middleware and computer. If the certificate is expired, revoked, or belongs to the wrong authorised user, software changes will not make it valid.

Clear browser cache only when the token works locally but a specific portal page is stale or failing. Running the browser as Administrator should not be a routine DSC fix.

Step 5

Start and activate EximSign Signer Utility

EximSign signing requires the EximSign Signer Utility on the Windows computer where the DSC token is connected. The utility communicates locally through port 4949.

  1. Install EximSign Signer Utility using the setup provided during onboarding.
  2. Open the utility and allow the local connection if Windows Firewall or approved antivirus software asks for permission.
  3. Enter the activation code supplied by your authorised Company/Agent.
  4. Wait for successful activation. Signing will remain unavailable until the code is accepted.
  5. Keep the utility running while selecting the certificate and signing the file.

The activation code can be issued only by the Company/Agent responsible for the EximSign account. Do not publish the code, include it in screenshots, or share it with an unknown caller.

For a technical port check, open Command Prompt and run netstat -ano | findstr :4949. A listening entry indicates that a local process is using the port. If EximSign Signer Utility still reports a port error, restart the utility and contact the authorised support team instead of closing unknown Windows processes.

Step 6

Run a test before the filing deadline

  1. Restart the computer after a driver or middleware change.
  2. Connect the DSC token and confirm the certificate in the token manager.
  3. Start EximSign Signer Utility and confirm that activation is complete.
  4. Open the EximSign workflow and perform a test signing check.
  5. Use the final validated XML or document only after the test succeeds.

If the token is visible but signing fails, note the exact message. A certificate selection error, wrong PIN, expired certificate, blocked port, invalid activation, and invalid XML are different issues and need different fixes.

Quick diagnosis

Match the symptom to the next check

  • !No token light: test another USB port and computer; the issue is likely hardware or USB related.
  • !Token manager is missing or blank: install or repair the correct token middleware.
  • !Certificate is not visible: check Smart Card service, middleware, certificate validity, and authorised user.
  • !Signer utility is not ready: start EximSign Signer Utility and check local port 4949.
  • !Activation is requested: obtain the code from the authorised Company/Agent and complete activation.
  • !Token is visible but signing fails: record the exact error and check certificate selection, PIN, activation, port, and file validity separately.