DSC Rejected or Not Working During LLP Filing? Here’s How to Fix It

Last Updated on September 23, 2026

If your DSC is rejected or not working during LLP annual filing, first verify that the DSC is correctly associated with your MCA V3 Business User profile, the certificate is valid, and that the latest emBridge utility is installed and running. MCA guidance also requires the DSC to meet the applicable class requirements and be associated before signing forms that require a DSC.

A rejected or missing Digital Signature Certificate is one of the most common roadblocks during LLP filing on the MCA portal. The form is ready, the details are correct, but the signing step simply won’t go through, and the error message rarely explains what’s actually wrong.

This is especially common for designated partners who last filed on the older MCA V2 system, since the signing mechanism changed completely when the portal moved to V3. If you’re newly stepping into this role, our guide on the procedure for appointment of a designated partner in an LLP covers the DPIN and consent steps that precede this stage.

This guide explains why DSC errors happen during LLP filing and how to fix them quickly, without guessing your way through it.

Why Do DSC Errors Happen During LLP Filing?

Common Causes

• emSigner not installed, or installed but not running in the background.
• DSC never associated with your Business User account on MCA V3.
• PAN or name on the DSC doesn’t match your MCA profile.
• Outdated USB token drivers.
• Trying to reuse a DSC that only worked on the old V2 portal.
• Expired or revoked Class 3 DSC certificate. If your certificate has actually expired (not just failed to associate), no amount of re-association or driver updates will fix it; an expired DSC must be renewed with your certifying authority before it can be used again for any MCA filing.”
• Browser compatibility issues with older or unsupported browsers.

The V2-to-V3 migration is the single biggest source of confusion. V2 relied on a Java applet for signing, which most professionals had running for years without ever needing to touch it again. V3 dropped Java entirely and now uses a separate utility called emSigner, installed once and kept running in the background whenever you’re filing. A DSC that worked perfectly on V2 will not work on V3 until it’s associated again through the new system, no matter how valid the certificate itself still is.

Mac users: emSigner is a Windows utility with no native Mac version. Designated partners on macOS typically need a Windows virtual machine (via Parallels or similar) or a Windows PC to complete DSC association and signing.

If your certificate has expired rather than simply failed to associate, see our guide to renewing an expired Digital Signature Certificate for the full renewal process before attempting to file again.

Getting the Basic Setup Right

Before Filing Any LLP Form, Confirm

• emSigner is downloaded from the MCA portal’s Help & FAQ section and actively running; check your system tray, not just installed. You’re using a supported browser; Chrome or Edge are recommended; Firefox has been reported to cause compatibility issues with the V3 portal’s signing components and is best avoided if you’re troubleshooting a DSC error.
• Install emSigner with administrator rights on shared, corporate, or IT-managed laptops; a standard user account can silently block the utility from running correctly, even though installation appears to succeed.
• Your USB DSC token has the latest drivers from the manufacturer’s website.
• The DSC is a valid Class 3 certificate from a licensed certifying authority such as eMudhra, Sify, or nCode.
• You’re using a supported browser, Chrome, Edge, or Firefox.

How to Associate Your DSC on MCA V3?

Step 1. Log In and Navigate

Log in to your MCA V3 Business User account, go to MCA Services, then DSC Services.

Step 2. Select Associate DSC

Choose Associate DSC from the available options.

Step 3. Choose the Correct Role

Select Designated Partner for LLP filings, not Director or Authorised Representative, unless that’s genuinely your role.

Step 4. Enter Required Details

Enter your DPIN and other requested details exactly as they appear on your MCA profile.

Step 5. Connect and Select the Certificate

Plug in your token, select the certificate from the list emSigner displays, and confirm.

Step 6. Confirm Success

A success message confirms the DSC is now associated and usable for LLP forms.

Fixing Specific DSC Errors

1. DSC Not Detected

Check that emSigner is running, the token drivers are current, and the USB token is properly connected. This covers the vast majority of detection failures.

If the token drivers are current and emSigner is running but the certificate still isn’t detected, try reinstalling the DSC into your system’s certificate store directly (via the token’s management software) rather than relying on emSigner to detect it automatically. This resolves a meaningful share of persistent detection failures that drivers alone don’t fix.

2. Invalid Certificate

This usually means the PAN on the DSC doesn’t match your MCA profile. The details need to be identical, not just close.

3. Screen Freezes on “Associate DSC”

Change the PIN on your token and retry after refreshing. If that doesn’t work, go to Profile Upgrade, change your hint question, and try again.

4. “Customer Already Exists” (Error e7002)

This means the DSC is already linked to the same user ID. Check your existing associations under Profile Upgrade before trying again.

5. DSC Worked on V2 But Fails on V3

This needs a fresh association on V3. V2 associations don’t carry over automatically, even if the certificate itself is still valid and unexpired.

6. Session Times Out Mid-Signing

If the portal logs you out or the signing window closes unexpectedly, it’s often a slow connection or an idle browser tab. Refresh the page, log back in, and complete the association or signing step again without switching tabs midway.

Quick Reference: Error and Fix

Error or Symptom	Likely Cause	Fix
DSC not detected	emSigner not running, outdated driver, token unplugged	Install and run emSigner, update drivers, reconnect token
Invalid certificate	PAN on DSC doesn’t match MCA profile	Verify PAN matches exactly; reissue DSC if needed
Screen freezes on Associate DSC	Token or session glitch	Change token PIN, refresh; change hint question if unresolved
Customer already exists (e7002)	DSC already linked to this user ID	Check existing associations under Profile Upgrade
DSC worked on V2, fails on V3	No fresh V3 association	Re-associate DSC through MCA Services on V3
Session times out mid-signing	Slow connection or idle browser tab	Refresh, log back in, avoid switching tabs during signing

Common Mistakes to Avoid

• Assuming a DSC that worked on V2 will carry over to V3 automatically.
• Selecting the wrong role during association, Director instead of Designated Partner.
• Leaving emSigner installed but not actually running during filing.
• Using an unsupported or outdated browser.
• Not verifying the DSC’s PAN and name match the MCA profile before signing.
• Waiting until the filing deadline to discover and fix the DSC issue.

Penalty Risk If You Don’t Fix It in Time

LLP filings like Form 8 and Form 11 carry late filing penalties calculated per day of delay. A DSC issue eating into your remaining time before the deadline doesn’t excuse the penalty once it applies, regardless of how avoidable the underlying cause turns out to be. Testing your DSC setup well ahead of the due date, rather than on the day itself, avoids this entirely.

A practical way to test early: attempt the DSC association step on the portal at least a week before any real filing is due, independent of the actual form you need to file. This surfaces setup issues with time to fix them, rather than during a deadline-bound submission.

Benefits of Getting Your DSC Setup Right

• Faster Filing- Forms get signed and submitted without repeated attempts.
• No Late Penalties- Avoids delays that push you past the filing deadline.
• Fewer Rejections- Correctly matched DSC details reduce association and signing errors.
• Less Downtime- A working setup means less time lost to troubleshooting on filing day.
• Peace of Mind- One-time correct setup means fewer surprises on future filings.

Example

A designated partner tries to sign an LLP annual return using a DSC that worked fine on the old V2 portal for years. On V3, the certificate doesn’t appear at all, and the first instinct is to assume the certificate itself has expired. After checking the basics, it turns out emSigner was never installed on that particular system, since filings had always been done from a different laptop in the past. Once emSigner is installed and running, the token is detected immediately, but the DSC still needs to be freshly associated with the Business User account, since V2 associations don’t transfer over. The fix takes only a few minutes once the actual cause is identified, though the confusion beforehand often eats up far more time than the fix itself.

Where Things Stand Now

MCA completed its full migration to V3 by mid-2025, with the last batch of forms, including major annual filing forms, moved over that July. LLP forms shifted to V3 much earlier, back in March 2022, so most designated partners have already been through this transition once. V2 is fully retired at this point; there’s no fallback to the old signing method regardless of what used to work before, and support queries referencing the old system are no longer actionable on the current portal.

How Kanakkupillai Can Help?

Kanakkupillai handles LLP registration to filings, including setting up and troubleshooting DSC association issues before they become a deadline problem. We help configure emSigner correctly, verify DSC details against MCA records, and resolve association errors for designated partners switching systems, replacing tokens, or renewing certificates.

Conclusion

A rejected or non-functioning DSC during LLP filing is almost always a setup issue, not a problem with the certificate itself. Working through the checklist in order emSigner, association, PAN match, usually identifies the cause within minutes. Testing your setup before a deadline is looming saves the scramble entirely.

Get hassle-free LLP filing and DSC troubleshooting support from Kanakkupillai.

FAQs

1. Why does my DSC that worked on MCA V2 not work on V3?

V3 uses the emSigner utility instead of the old Java applet, so every DSC needs fresh association with your Business User account on V3. This is the most common reason a DSC appears rejected.

2. What should I do if my DSC isn’t detected at all?

Confirm emSigner is installed and running, your token drivers are updated, and the USB token is properly connected. These three checks resolve most detection failures.

3. What does the “customer already exists” error mean?

It means the DSC is already linked to the same user ID on the MCA portal. Check your existing DSC associations under Profile Upgrade before trying to add it again.

4. What type of DSC is required for LLP filings on MCA V3?

A Class 3 Digital Signature Certificate from a licensed certifying authority, with the PAN and name matching your MCA profile exactly. Lower-class certificates aren’t accepted for MCA filings.

5. Will a DSC problem excuse a late LLP filing penalty?

No. Form 8 and Form 11 penalties accrue per day of delay regardless of the reason. It’s best to test your DSC setup well before the filing deadline.