Most MCA V3 login and DSC failures come down to four root causes: trying to register a DSC as a "Registered User" instead of a "Business User" (only Business Users can associate a DSC), a stale or missing emBridge signing-bridge install, a duplicate V2/V3 profile sharing the same PAN or email after migration, or a missed portal deadline — 15 days to upload the DSC-affixed PDF after SRN generation, then payment within 7 days of that upload or "due date + 2 days," whichever is earlier. Miss that window and the SRN auto-cancels, forcing a fresh filing at full fee.
The portal has been shakier than usual since the 5 June 2026 MCA data-centre fire forced a disaster-recovery-site switchover — MCA has responded with fee-relief circulars rather than a formal all-clear, so intermittent slowness into late July 2026 is not unusual. If a filing is stuck and the deadline is close, CapEasy handles the ROC filing end to end — including chasing the MCA helpdesk when the portal itself is the problem.
Since the 5 June 2026 data-centre fire: MCA has issued two relief circulars — General Circular 02/2026 (19 June, waiving DPT-3 additional fees to 31 July 2026) and General Circular 03/2026 (8 July, extending the CCFS-2026 amnesty to 31 August 2026, since pushed to 15 September 2026 by General Circular 04/2026 of 31 August) — and separately moved name-reservation and e-form resubmission deadlines that fell between 21–30 June 2026 out to 10 July 2026 as a one-time administrative relief.
Why MCA V3 login and DSC association fail
- Registered User instead of Business User — a Registered User account cannot register a DSC at all; the account must first be upgraded to Business User.
- An old or missing emBridge install — V3 signs through emBridge, not the old V2-era emSigner alone. A stale install after a browser update is a common cause of silent signing failures.
- Duplicate V2/V3 profiles on the same PAN or email — left over from the V2-to-V3 migration, this throws a "user already exists" error on Business User upgrade.
- The DSC is already registered to a different MCA user ID — a DSC can belong to only one user ID at a time, so it must be dissociated from the other ID first.
- A generic USB-token driver instead of the token-brand-specific one (ProxKey, Watchdata, ePass, eMudhra) — generic drivers often fail without any error message.
- Name or date-of-birth mismatch between the form, the PAN record and the DSC certificate — the DSC has to be reissued in that case, not edited.
How to fix the common DSC and login errors
- Check your account type first. Log in and look at the profile — if it says "Registered User," go to Profile → Upgrade to Business User, supply PAN and DIN/membership number, and verify by OTP.
- If the upgrade fails with "user already exists," a duplicate profile is sharing your PAN or email. If your old V2 ID is still editable, change its email and re-migrate; otherwise raise an MCA helpdesk ticket to merge or deactivate the duplicate.
- Reinstall the signing software. Download the current emBridge from the MCA homepage (not a saved V2-era emSigner installer), add the driver specific to your token brand, then restart the machine before reinserting the token.
- Associate the DSC from the Business User account: MCA Services → FO/LLP Service → Associate DSC → select the certificate → enter the PIN → Register. "DSC already registered with another user" means dissociating it from that other ID first; "Customer already exists" (error e7002) usually means it is already tied to your own ID — check via Profile Upgrade → Show DSC before re-registering.
- For a PAN/DIN link error, correct the identification number under Profile Upgrade — the DSC links to it automatically without re-registering the certificate.
- For OTPs that never arrive, especially on foreign mobile numbers, try the registered email OTP as a fallback; MCA runs an IVR-based OTP channel for foreign-jurisdiction numbers on DIR-3 KYC.
The SRN and resubmission deadlines that trip up filings
| Stage | Window | Miss it and |
|---|---|---|
| DSC-affixed PDF upload | 15 days from SRN generation | the SRN auto-cancels; file and pay again from scratch |
| Payment after upload | 7 days from upload, or due date + 2 days, whichever is earlier | same — the SRN cancels and fees are lost |
| Resubmission (RSUB) correction | 15 days from the resubmission flag, no extra fee for a timely fix | the SRN goes "Invalid"; a fresh eForm at full fee is the only option |
If a payment fails for a technical reason while the SRN still shows "Not Paid"/"Pending for Payment," use Track SRN/Transaction Status → Cancel SRN rather than letting the window lapse — that lets you re-attempt cleanly instead of losing the SRN outright.
Upload rejections that look like DSC errors but aren’t
- Filenames with special characters get silently rejected at upload.
- PDFs not generated via "Microsoft Print to PDF" sometimes fail the portal’s validation, even when they open fine.
- Files over 2MB are rejected outright — split or re-scan at a lower resolution.
- An expired DSC, or one simply not yet associated with the V3 user account, throws the same generic signing error as a genuine mismatch.
How to escalate to the MCA helpdesk
- Raise a service request (SR) from the portal’s grievance/helpdesk section, describing the exact error message and the SRN if one exists.
- For Name Reservation or Incorporation-linked tickets unresolved after 2 working days, escalate by email to CRC.Escalation@mca.gov.in, quoting the SR number.
- For DSC association or Business User issues, reference the specific error code (for example e7002) in your ticket — it speeds up routing.
- If a cancelled SRN falls inside the fire-relief window (21–30 June 2026), request reopening under the one-time administrative relief rather than filing fresh.
- Track the SR status in your V3 dashboard; MCA’s stated resolution timelines vary by category, so don’t assume silence means rejection.
- If nothing moves after 30 days, file a grievance on CPGRAMS (pgportal.gov.in) — this sits outside MCA and tends to get a faster written response.
- For a field or jurisdiction-specific problem, ask your regional ROC/RD office directly rather than the generic helpdesk — check current contact details on the mca.gov.in "Contact Us" page, since helpline numbers change.
Primary sources
The dates and fees on this page are read off the statute and the MCA’s own published forms, not copied from other guides. You can check every one of them:
- General Clauses Act, 1897 — section 9 (commencement and termination of time)
- Companies Act, 2013 — full text (India Code)
- MCA — company forms and downloads
- MCA — official portal
Verified against the Companies Act, 2013 / LLP Act, 2008, MCA rules and circulars as of 31 July 2026. Your exact position depends on your entity and any notifications or circulars issued since — we confirm it for you, and always recommend checking the official MCA portal. CapEasy is a private consultancy and is not affiliated with any government authority. This page is a guide, not legal advice.