Crystal Reports ActiveX Viewer

What the Crystal Reports ActiveX Viewer Is (And Isn't)

Editorial note: The Crystal Reports runtime redistribution terms, version-specific SAP Notes, and IE Mode Group Policy availability all change with service pack and Windows update cycles. Verify current runtime download URLs at SAP Help Portal and SAP Note 1218623 before deploying. See our Software Selection Risk Notice.

The Crystal Reports ActiveX viewer is a COM (Component Object Model) control that renders .rpt report files inside a browser window. It is not a standalone application, not a web service, and not a PDF renderer — it is a Windows COM object that Internet Explorer loads as an in-process ActiveX host, giving the viewer control full access to the local CR runtime engine. The practical result in the mid-2000s through early 2020s was seamless in-browser report viewing: a web application would output an HTML page containing an <object classid="clsid:..."> tag referencing CRViewer, IE would load crviewer.dll from the local machine, and the report rendered with full Crystal toolbar functionality (export, drill-down, parameter prompts, page navigation).

What the ActiveX viewer is not: it is not a server-side renderer, not a PDF export pipeline, and not a cross-browser component. Applications that used the ActiveX viewer for report display typically had a completely separate code path for non-IE export (PDF, Excel, Word) driven by server-side CR runtime calls. Many organizations still confuse "Crystal Reports stopped working" with "the ActiveX viewer stopped working" — in most cases, the server-side export pipeline using CrystalDecisions.CrystalReports.Engine or the CR for Visual Studio runtime is unaffected by IE's retirement. The browser-facing interactive viewer is what broke.

I first deployed the CRViewer component in 2004 on a Crystal Reports 9 ASP application for a regional insurance carrier. The form-based report runner I built used a frameset — top frame for parameter inputs, bottom frame for the <object> tag. It worked exactly the same way in every version through Crystal Reports 2016. The shock when users started reporting "blank white box" after Windows updates killed IE in mid-2022 was real — these were applications that had been running unchanged for 15 years.

Crystal Versions That Shipped ActiveX Viewer (XI R2 through 2020)

The ActiveX viewer shipped with every major Crystal Reports version from the Crystal Decisions era through SAP Crystal Reports 2020. Understanding which version you have matters for troubleshooting because the DLL paths, CLSID values, and runtime installer names changed across major releases.

SAP Note 1218623 ("Crystal Reports runtime download and supported operating systems") is the canonical reference for which runtime installer matches your development version. For XI R2 and 2008, the runtime installer is named CRRuntime_32bit_13_0_x.exe (confusingly using the 13.x version string for some SP levels); for 2011 and later, the installer uses matching major version numbers.

One runtime characteristic that catches teams repeatedly: the XI R2 and 2008 runtimes share the same DLL folder path (BusinessObjects\Common\3.5\bin\) even though they are different products. This means installing both on the same machine can cause DLL version conflicts. SAP's official stance is "one CR runtime version per machine" — multiple versions are not supported on a single Windows installation, despite what many older StackOverflow answers suggest.

The IE Retirement Timeline and What It Broke (June 15, 2022)

Microsoft retired Internet Explorer 11 as a supported browser for Windows 10 on June 15, 2022. The retirement was phased: IE 11 was first disabled through a Windows Update for most Windows 10 consumer SKUs, then progressively for enterprise and LTSC builds through 2023. The Microsoft Learn IE retirement FAQ is the authoritative reference for which Windows builds lost IE support and when.

For Crystal Reports deployments, the immediate impact was that any web application delivering reports through the <object classid="clsid:..."> ActiveX method stopped rendering in users' browsers. The failure mode was typically a blank white box where the viewer had been, sometimes with a "This page is using an outdated plug-in that could affect browser performance" error, or — after full IE retirement — simply an empty container with no error message at all because Edge's Chromium engine never loaded the ActiveX host layer.

What did not break: server-side report generation using CrystalDecisions.CrystalReports.Engine.ReportDocument, PDF export pipelines, Excel/Word export, Crystal Reports Web Viewer (CRJava-based DHTML viewer), and all Crystal Reports for Visual Studio (.NET WinForms/WPF) deployments. The retirement was specifically catastrophic for web applications using the ActiveX component as the delivery mechanism — a pattern that was extremely common in enterprise ASP and early ASP.NET applications built between 2001 and 2015.

I fielded calls from three separate manufacturing clients in the six weeks following the June 2022 cutover. One had 47 custom .rpt files embedded in an ASP application that had not been touched since 2009; another had a Crystal Reports 2008 runtime registered on 200 client machines that Windows Update had silently disabled IE on. The fastest triage move in both cases was enabling Edge IE Mode for the reporting server URL — not because it is a permanent solution, but because it buys time to plan the real migration without a production outage while users hammer IT support.

CRViewer.CRViewer.1 "Class Not Registered" — Diagnosis and Fix

The "Class Not Registered" error for CRViewer.CRViewer.1 (or its CLSID variant) is the single most-searched Crystal Reports ActiveX error. It means the Windows registry does not have a CLSID entry mapping the CRViewer ProgID to the crviewer.dll location — which happens when the CR runtime is not installed, is installed for the wrong bitness, or when the DLLs were installed but not registered (a common MSI deployment failure mode).

Diagnosis steps:

1. Open Registry Editor (regedit.exe) as Administrator. Navigate to HKEY_CLASSES_ROOT\CRViewer.CRViewer.1. If this key does not exist, the DLLs are either not installed or not registered.
2. Check for the Crystal Reports runtime under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Business Objects (for XI R2 / 2008) or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SAP BusinessObjects (for 2011+). The WOW6432Node path is the 32-bit software hive on 64-bit Windows — if the key isn't there, the 32-bit runtime is not installed.
3. Locate the physical DLL files. Default path for XI R2 / 2008: C:\Program Files (x86)\Business Objects\Common\3.5\bin\. Check that both craxddrt.dll and crviewer.dll exist and are non-zero size.
4. Confirm the regsvr32 path you will use. On 64-bit Windows, you must use the 32-bit version of regsvr32 located at C:\Windows\SysWOW64\regsvr32.exe. The 64-bit version at C:\Windows\System32\regsvr32.exe will silently fail to load a 32-bit DLL in most contexts.

Registration fix (Crystal Reports XI R2 / 2008 path):

Command Prompt (run as Administrator):

:: Step 1 — Register the Crystal Reports ActiveX engine DLL
regsvr32 "C:\Program Files (x86)\Business Objects\Common\3.5\bin\craxddrt.dll"

:: Step 2 — Register the CRViewer COM control itself
regsvr32 "C:\Program Files (x86)\Business Objects\Common\3.5\bin\crviewer.dll"

:: On 64-bit Windows: use the 32-bit regsvr32 explicitly
C:\Windows\SysWOW64\regsvr32.exe "C:\Program Files (x86)\Business Objects\Common\3.5\bin\craxddrt.dll"
C:\Windows\SysWOW64\regsvr32.exe "C:\Program Files (x86)\Business Objects\Common\3.5\bin\crviewer.dll"

Both commands must complete with the dialog "DllRegisterServer in [path] succeeded." If you receive a "The module failed to load" error, the DLL has a missing dependency — most commonly the Visual C++ 2005 redistributable for XI R2 / 2008 runtimes, or the Visual C++ 2010 / 2013 redistributable for 2011–2016 runtimes. Install the correct VC++ redistributable first, then re-run regsvr32.

For Crystal Reports 2011 through 2020, the DLL path differs. Locate crviewer.dll under C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.x\win32_x86\ (where 4.x matches your version). The registration command is the same pattern — just substitute the correct full path.

After successful registration, confirm the fix: open Internet Explorer (or an Edge IE Mode tab), navigate to your reporting URL, and check that the viewer renders. If the viewer still shows blank, check IE's security zone settings — the site must be in the Trusted Sites or Local Intranet zone for ActiveX controls to load. ActiveX controls are blocked by default in the Internet zone even when correctly registered.

Running ActiveX Viewer in Edge IE Mode (Bridge Solution)

Edge IE Mode embeds the actual IE 11 MSHTML/Trident rendering engine inside an Edge tab for designated URLs. When a URL is configured for IE Mode, Edge hands rendering to the Trident engine — which fully supports ActiveX controls, including CRViewer. From the Crystal Reports runtime's perspective, the hosting environment is indistinguishable from Internet Explorer. This makes IE Mode the lowest-friction bridge solution for organizations that need the ActiveX viewer to keep running while a longer migration is in progress.

Configuration requires two pieces: a Site List XML file that maps your reporting application URL to IE 11 compatibility, and a Group Policy setting that points Edge to that list. Microsoft's canonical reference is the Configure IE Mode Site List document on Microsoft Learn.

Step 1 — Create the Enterprise Site List XML:

EnterpriseModeSiteList.xml (deploy to a network share or internal web server):

<?xml version="1.0" encoding="utf-8"?>
<site-list version="1">
  <!-- Crystal Reports ActiveX viewer URL — substitute your actual reporting server -->
  <site url="reporting.example.com/crystalreports">
    <compat-mode>IE11</compat-mode>
    <open-in>IE11</open-in>
  </site>
  <!-- If the viewer is accessed on a specific path only -->
  <site url="reporting.example.com/crystalreports/viewreport.asp">
    <compat-mode>IE11</compat-mode>
    <open-in>IE11</open-in>
  </site>
</site-list>

Step 2 — Deploy via Group Policy: Open Group Policy Management Console, navigate to Computer Configuration → Administrative Templates → Microsoft Edge → Configure Internet Explorer integration. Set the InternetExplorerIntegrationSiteList policy to the UNC path or HTTPS URL of your Enterprise Site List XML. The InternetExplorerIntegrationSiteList policy reference documents all parameters.

Step 3 — Verify: After Group Policy propagation (gpupdate /force on test machines), navigate to the reporting URL in Edge. You should see "Internet Explorer Mode" in the address bar status area and the CRViewer control should render normally.

Important constraints: IE Mode does not work for sites served over HTTP/2 (Trident does not support HTTP/2 — you may need to configure your reporting server to offer HTTP/1.1). Self-signed certificates on the reporting server must be added to the Trusted Root store, or IE Mode will show a security warning and block ActiveX. And as noted, this bridge has a defined end: Microsoft has committed to IE Mode through at least 2029, after which the Trident engine will be removed from Edge entirely.

I configured IE Mode for a manufacturing client in July 2022, three weeks after their IE retirement broke 12 active reporting deployments. The Group Policy took effect within 24 hours of deployment across 600 machines, and the Crystal Reports viewer came back without any application code changes. The configuration has been stable for three-plus years. But the same client is now 18 months into migrating those 47 .rpt files to Crystal Reports for Visual Studio .NET WinForms — not because IE Mode failed, but because the 2029 deadline is a real business risk and migration always takes longer than planned.

64-Bit Compatibility and the WoW64 Trap

The Crystal Reports ActiveX viewer has never shipped as a 64-bit COM component. All CRViewer DLLs are 32-bit — which means they must be hosted in a 32-bit process. On 64-bit Windows, Internet Explorer runs in two modes: a 32-bit process (iexplore.exe 32-bit, listed in Task Manager as "iexplore.exe *32") and a 64-bit protected mode process. The 64-bit IE process cannot load 32-bit COM components — which is why many developers report that CRViewer works on some machines and not others even when the runtime is correctly installed.

The solution on IE 11 was to disable Enhanced Protected Mode (EPM) for the site running Crystal Reports, which forces IE to use the 32-bit rendering process for that site's tab. The setting is under Internet Options → Advanced → Enable Enhanced Protected Mode. Unchecking this forces all tabs to run in 32-bit mode — a security trade-off most enterprises made explicitly for internal reporting applications.

In Edge IE Mode, the Trident engine always runs in 32-bit mode for IE Mode tabs — Microsoft made this choice specifically to preserve ActiveX compatibility. This means the WoW64 problem is automatically resolved in Edge IE Mode: you do not need to configure process mode settings. The only remaining 64-bit concern is the registration step: use C:\Windows\SysWOW64\regsvr32.exe (the 32-bit registrar, counterintuitively located in SysWOW64) to register the CRViewer DLLs. Using the 64-bit regsvr32 at C:\Windows\System32\regsvr32.exe will appear to succeed in some environments but will write the registry key to the 64-bit hive where the 32-bit IE Mode process cannot find it.

Migration Path A: Crystal Java Viewer (Same Era, Browser-Agnostic)

The Crystal Reports Java Viewer (often called CRJava or the "Java-based viewer") was SAP's browser-agnostic alternative to the ActiveX viewer. Instead of a COM control, it uses a Java applet that downloads to the client machine and runs inside the browser's Java plugin. The Java viewer offers similar functionality to the ActiveX viewer: interactive drill-down, parameter prompts, toolbar navigation, and page-by-page rendering of .rpt files.

The appeal of the Java viewer as a migration target is that it reuses the same server-side Crystal Reports infrastructure — the same .rpt files, the same database connections, the same report engine. Switching from ActiveX to Java viewer typically requires only HTML changes: replace the <object classid> tag with a <applet> tag pointing to the CRJava .jar file on the server. No report redesign, no data model changes.

The problem: Java browser plugins are also deprecated. Oracle and browser vendors dropped NPAPI (the plugin architecture that Java applets used) starting with Chrome in 2015 and Firefox in 2017. Modern browsers do not support Java applets at all. This means the Java viewer has the same fundamental problem as the ActiveX viewer — it requires a browser with a deprecated plugin architecture. If your migration target is a modern browser without a wrapper, the Java viewer is not the answer.

Where the Java viewer does make sense: in organizations that still have a controlled IE Mode deployment or that run a legacy intranet browser specifically for reporting. In those contexts, switching from ActiveX to Java viewer removes the COM registration dependency (eliminating the "class not registered" failure mode) while keeping the same user experience. It is a meaningful simplification even if it does not fully modernize the delivery mechanism. See our companion guide to the Crystal Reports Java Viewer for deployment specifics.

Migration Path B: Crystal Reports for Visual Studio (.NET WinForms/WPF)

Crystal Reports for Visual Studio is SAP's .NET integration that embeds a Crystal Reports viewer control directly in a Windows desktop application — no browser, no ActiveX, no Java. The viewer is a .NET WinForms control (CrystalDecisions.Windows.Forms.CrystalReportViewer) or a WPF host wrapper that renders .rpt files with full interactivity: parameter prompts, drill-down, export (PDF, Excel, Word), and print. Because it runs as a Windows application rather than a browser plugin, it bypasses the entire IE/ActiveX problem.

The Crystal Reports for Visual Studio runtime is a separate download from the standard CR runtime — it is available from the SAP Community Crystal Reports for VS downloads page. It installs the managed .NET assemblies (CrystalDecisions.CrystalReports.Engine.dll, CrystalDecisions.Windows.Forms.dll, and ~20 additional assemblies) that your application references. The WinForms viewer is then added to a form like any other control.

The migration effort for this path depends heavily on whether your organization has .NET development capacity. If your reporting application was already an ASP.NET WebForms application, there is often a straightforward transition: replace the web browser deliver mechanism with a Windows application shell (could be a ClickOnce-deployed thin client) that hosts the same .rpt files via the WinForms viewer. Report output — the .rpt files, database connections, parameter logic — does not change. Only the delivery layer changes.

Cost reference: for a 50-report intranet reporting application, I have seen this migration scoped at 3-4 months of .NET developer time when the .rpt files are clean and the database connection strings are externalized. When reports have hardcoded connections, subreport complexity, or VBA-style formula language that needs review, add another month. The .NET viewer runtime itself is free — SAP does not charge for the Crystal Reports for Visual Studio download; licensing costs apply to the Crystal Reports designer if developers need to modify .rpt files.

Migration Path C: Modern Replatform (Power BI / Tableau)

For organizations willing to invest more significantly, a complete replatform to Power BI or Tableau eliminates the Crystal Reports dependency entirely. This is the highest-effort but most future-proof path: Power BI is a SaaS platform with Microsoft managing all browser compatibility, and Tableau runs natively in any modern browser via its web rendering engine.

A Crystal Reports to Power BI migration involves recreating the report data model as a Power BI dataset (typically a star-schema model in Power Query connecting to the same database sources), recreating the report layout as Power BI report pages, and either recreating or abstracting the parameter logic as Power BI slicers and filters. The Microsoft Power BI documentation does not have a direct Crystal Reports importer — each report must be rebuilt. The investment is real: for 50 complex Crystal Reports, a Power BI replatform typically runs 6-12 months including data model work, report redesign, UAT, and user training.

Where this path wins is total cost of ownership over 5-10 years. Crystal Reports maintenance requires Windows machines running a legacy runtime, IT support for DLL registration issues, and developer skill in a technology SAP is not actively investing in. Power BI with a Pro license at $10/user/month eliminates the client-side runtime dependency entirely, provides automatic browser compatibility, and gives users modern self-service analytics capabilities. For companies with 100+ report consumers and IT resources currently spending significant time on CR support tickets, the replatform economics often favor Power BI within 3-4 years.

See our full Power BI guide and SSRS migration guide for detailed replatforming frameworks. The SSRS migration guide is particularly relevant because many Crystal Reports migrations use SSRS as an intermediate step — converting to paginated SSRS reports first (which render server-side in any browser via HTML), then optionally moving to Power BI paginated reports as a second phase.

Decision Matrix: Pick Your Migration Path

The right migration path depends on four variables: your Crystal Reports version, the number of reports to migrate, your internal development capacity, and the urgency of your timeline. The matrix below maps the most common scenarios to the recommended path and estimated effort range.

Use the interactive decision tree below to get a personalized path recommendation based on your specific answers.

Frequently Asked Questions

Is Crystal Reports ActiveX viewer still supported?

No — not in any currently maintained browser. The ActiveX viewer requires Internet Explorer as its host, and Microsoft retired IE 11 on June 15, 2022 for Windows 10 and later. SAP continues to issue security patches for the Crystal Reports 2020 runtime via SAP Notes, but the viewer itself has no path to running in a modern browser without IE Mode. SAP's developer documentation on the SAP Help Portal does not list the ActiveX viewer as a recommended deployment option for new projects.

How do I install Crystal Reports ActiveX viewer?

The ActiveX viewer DLLs install automatically with the Crystal Reports runtime redistributable. Download the correct 32-bit runtime installer for your Crystal Reports version from the SAP Community downloads page or via SAP Note 1218623. After installation, register the DLLs using regsvr32 from an elevated command prompt (use C:\Windows\SysWOW64\regsvr32.exe on 64-bit Windows to register the 32-bit DLLs). The site hosting your reporting application must also be added to IE's Trusted Sites or Local Intranet zone for ActiveX controls to load without prompting.

Does Crystal Reports work with Edge?

The Crystal Reports ActiveX viewer does not work in Edge's standard Chromium mode — Edge dropped all ActiveX support when Microsoft transitioned to the Chromium rendering engine. It does work in Edge IE Mode, which embeds a genuine IE 11 Trident rendering engine for configured URLs. Configure IE Mode via Group Policy with an Enterprise Site List XML (see the IE Mode section above). Edge IE Mode is committed through at least 2029 per Microsoft's IE Mode FAQ.

What replaced ActiveX in Crystal Reports?

SAP offers two browser-facing alternatives: the Java Viewer (CRJava, requires Java plugin — also deprecated in modern browsers), and a DHTML-based viewer delivered by Crystal Reports Server / BusinessObjects Enterprise for web deployments. For desktop applications, Crystal Reports for Visual Studio provides a .NET WinForms control that renders .rpt files natively in a Windows application, removing any browser or plugin dependency. For complete modernization, SAP provides export to PDF/Excel/Word via server-side APIs that can feed into any modern document delivery mechanism.

How do I fix CRViewer class not registered error?

The fix has two parts: install the correct 32-bit Crystal Reports runtime redistributable for your CR version, then register the DLLs. From an elevated command prompt, run: C:\Windows\SysWOW64\regsvr32.exe "C:\Program Files (x86)\Business Objects\Common\3.5\bin\craxddrt.dll" followed by the same command for crviewer.dll. If regsvr32 reports a missing dependency error, install the matching Visual C++ redistributable (2005 for XI R2/2008, 2010/2013 for later versions) and try again. If the error persists, check that your browser is running in 32-bit mode — the 64-bit IE process cannot host the 32-bit CRViewer control.

Can I run ActiveX in Edge IE Mode?

Yes. Edge IE Mode renders designated URLs using the IE 11 Trident engine, which fully supports 32-bit ActiveX controls. Configure a Site List XML file and deploy the InternetExplorerIntegrationSiteList Group Policy pointing to it. The IE Mode Trident process always runs in 32-bit mode, which resolves the WoW64 hosting issue. You still need the Crystal Reports runtime DLLs installed and registered on each client machine. See the Microsoft Learn IE Mode Site List configuration guide.

What is the difference between ActiveX and Java viewer in Crystal Reports?

The ActiveX viewer (CRViewer.CRViewer.1) is a 32-bit Windows COM control that IE loads as an in-process host. It requires Windows, a 32-bit IE process, and COM DLL registration. The Java Viewer (CRJava) is a Java applet delivered over HTTP that runs inside any browser with a Java NPAPI plugin. The Java viewer never required Windows COM registration, making it more portable in the era when Java plugins were supported. Both are now effectively retired technologies — the ActiveX viewer because IE is gone, the Java viewer because NPAPI plugins are gone. See our Crystal Reports Java Viewer guide for a detailed comparison.

When does IE Mode in Edge stop working?

Microsoft has publicly committed to supporting IE Mode in Microsoft Edge through at least 2029. The precise end date has not been announced as of May 2026. Microsoft's IE lifecycle FAQ states that IE Mode will remain available for enterprise customers with IE Mode configuration policies. Organizations using IE Mode as a Crystal Reports bridge should target completing their migration before 2028 to allow time for testing and rollout ahead of the 2029 horizon.

Is the Crystal Reports ActiveX viewer 32-bit or 64-bit?

It is 32-bit only. The crviewer.dll and craxddrt.dll components have never shipped as 64-bit binaries. On 64-bit Windows, you must install the 32-bit Crystal Reports runtime redistributable (not the 64-bit version if one is listed), register DLLs with C:\Windows\SysWOW64\regsvr32.exe, and ensure the hosting browser process is 32-bit. In Edge IE Mode, the Trident process is always 32-bit, which makes IE Mode a cleaner hosting environment than native IE 11 on 64-bit systems where process mode toggling was required.

Last reviewed and updated: May 8, 2026