How to Use Viewer ActiveX Control in Modern Browsers

Viewer ActiveX Control: Troubleshooting Common Errors

1. Installation fails or control not registered

• Problem: OCX/DLL not registered; control doesn’t appear in app.
• Fixes:
  • Run Command Prompt as Administrator and register manually:
    • 32-bit on 32-bit OS or 64-bit on 64-bit OS:
      regsvr32 C:\Path\To\ViewerCtl.ocx

    • 32-bit control on 64-bit OS:
      %windir%\SysWOW64\regsvr32 C:\Path\To\ViewerCtl.ocx

  • Ensure the file permissions allow SYSTEM/Administrators read & execute.
  • Confirm dependent DLLs are present (use Dependency Walker or dumpbin).

2. “Control can’t create object” or ActiveX not listed

• Problem: ProgID/CLSID registration missing or registry keys corrupted.
• Fixes:
  • Re-register the control (see above).
  • Check registry under HKEY_CLASSES_ROOT\CLSID and HKEY_CLASSES_ROOT\ProgID for the control’s entries.
  • Repair or reinstall the application that installs the control.

3. Permission / security prompts block use

• Problem: Browser or Windows blocks ActiveX or prompts repeatedly.
• Fixes:
  • For Internet Explorer: add site to Trusted Sites and enable ActiveX initialization in Security settings.
  • For local apps: run the host application as Administrator.
  • Ensure the control is signed with a valid code-signing certificate; unsigned controls trigger warnings.

4. Compatibility issues with modern browsers / 64-bit

• Problem: Most modern browsers dropped NPAPI/ActiveX support; 64-bit vs 32-bit mismatch.
• Fixes:
  • Use Internet Explorer (32-bit) or an ActiveX-compatible host.
  • If possible, migrate to a modern alternative (e.g., WebAssembly, native app, or a signed COM server).
  • Ensure you use the correct bitness version of the control matching the host process.

5. Runtime errors or crashes in the control

• Problem: Exceptions, memory access violations, or unstable behavior.
• Fixes:
  • Update to the latest control version with bug fixes.
  • Check event logs (Windows Event Viewer) for faulting module name and stack.
  • Run the host under a debugger (Visual Studio) or use Application Verifier to catch heap issues.
  • Verify input parameters and file formats passed to the control; sanitize inputs.

6. Licensing or trial limitation errors

• Problem: Control reports license missing or in demo mode.
• Fixes:
  • Ensure license file or registry licensing keys are installed per vendor instructions.
  • Re-run vendor installer as Administrator.
  • Contact vendor for license activation steps or replacement license.

7. Rendering / display problems (blank, distorted)

• Problem: Viewer shows blank area or rendering artifacts.
• Fixes:
  • Confirm graphic/rendering dependencies (DirectX/OpenGL) and update drivers.
  • Check DPI/scaling settings and test with system scale set to 100%.
  • Test with hardware acceleration disabled if the control supports it.

8. Slow performance or high CPU

• Problem: Viewer is sluggish or consumes CPU.
• Fixes:
  • Profile the host process to identify hotspots.
  • Reduce update/redraw frequency or lower rendering quality settings.
  • Ensure multithreading model is used correctly; avoid heavy work on UI thread.

9. Networking / licensing server connection errors

• Problem: Control fails to fetch remote resources or validate license.
• Fixes:
  • Verify firewall/antivirus rules allow the control’s network traffic.
  • Ensure correct proxy settings or add exceptions.
  • Test connectivity to the license/asset server from the host machine.

10. General troubleshooting checklist

1. Confirm control file present and registered.
2. Match bitness between control and host process.
3. Run host as Administrator to rule out permission issues.
4. Check Event Viewer and application logs for error codes.
5. Update control and host application to latest versions.
6. Verify dependencies (DLLs, runtimes, drivers).
7. Test on a clean VM to reproduce and isolate environment issues.
8. Contact vendor with logs, version numbers, and reproduction steps if unresolved.

If you want, tell me the exact error message, host application, Windows version, and whether the control is 32- or 64-bit — I’ll give targeted next steps.