locked
Crystal Reports ActiveX Designer: Failed to open document

    Question

  • I got the following error message on the line that declared a ReportDocument.  In addition, when I tried to open any Crystal Reports that I created in Visual Studio 2005, I got "Crystal Reports ActiveX Designer:  Failed to open document." and "Microsoft Visual Studio:  Failed to create the Crystal Query Engine." error message.

    I uninstalled and reinstalled Visual Studio 2005.  I had some problem during the uninstallation and installation process.  After I finally got VS installed, things seemed to work fine for a short while.  When I rebuilt my Setup project for the third time, I got this same error message again.

    Is there any way that I can fix this problem?  Thanks.

     

    Retrieving the COM class factory for component with CLSID {11BD5260-15B6-412D-80DB-12BB60B8FE50} failed due to the following error: 80040154.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {11BD5260-15B6-412D-80DB-12BB60B8FE50} failed due to the following error: 80040154.

    Source Error:

    Line 16:         ' ***** Load a report to ReportDocument Object.
    Line 17:         'Dim rptBatchCoverPage As ReportDocument = New ReportDocument
    Line 18:         Dim rptBatchCoverPage As ReportDocument = New ReportDocument
    Line 19:         Dim strReportFilePath As String = Server.MapPath("..\Reports\crBatchCoverPage.rpt")
    Line 20:         rptBatchCoverPage.Load(strReportFilePath)

    Source File: C:\Inetpub\wwwroot\CFSP\Batch\BatchCoverPage.aspx.vb    Line: 18

    Stack Trace:

    [COMException (0x80040154): Retrieving the COM class factory for component with CLSID {11BD5260-15B6-412D-80DB-12BB60B8FE50} failed due to the following error: 80040154.]
       CrystalDecisions.CrystalReports.Engine.ReportDocument..cctor() +182
    
    [TypeInitializationException: The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception.]
       CrystalDecisions.CrystalReports.Engine.ReportDocument..ctor() +0
       BatchCoverPage.ConfigureCrystalReports(Object sender, EventArgs e) in C:\Inetpub\wwwroot\CFSP\Batch\BatchCoverPage.aspx.vb:18
       BatchCoverPage.Page_Init(Object sender, EventArgs e) in C:\Inetpub\wwwroot\CFSP\Batch\BatchCoverPage.aspx.vb:12
       System.Web.UI.Control.OnInit(EventArgs e) +98
       System.Web.UI.Page.OnInit(EventArgs e) +9
       System.Web.UI.Control.InitRecursive(Control namingContainer) +371
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2029
    

    Friday, May 26, 2006 10:26 PM

Answers

  •  Error is coming as dlls required to run Crystal report are not registered in the m/c. Because of this reason only, Busiobj recommends to create websetup for crystal report deployment.

    Instead of going for this long process, i would recommend to create one windows application with one single form, in that drag one crystalreportviewer. Add one setup project in the same solution. In the setup, right click on its properties and add merge module files [ crystal11_net_embeddedreporting.msm and crystalreports11_maps.msm] and in the keycode of firstone add licence key.

    Run this msi file on the machine where the error is coming up. As this merge module will register the dlls which is required for your web app. [Or create full web setup program for your app]

     

     

     

     

     

    Thursday, March 15, 2007 4:37 PM

All replies

  • Try running the boot strapper for Crystal Reports. The one that comes with VS2005 is located here (if you installed to C:)

    C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\CrystalReports\CRRedist2005_x86.msi

     

    Tuesday, March 13, 2007 1:50 PM
  •  Error is coming as dlls required to run Crystal report are not registered in the m/c. Because of this reason only, Busiobj recommends to create websetup for crystal report deployment.

    Instead of going for this long process, i would recommend to create one windows application with one single form, in that drag one crystalreportviewer. Add one setup project in the same solution. In the setup, right click on its properties and add merge module files [ crystal11_net_embeddedreporting.msm and crystalreports11_maps.msm] and in the keycode of firstone add licence key.

    Run this msi file on the machine where the error is coming up. As this merge module will register the dlls which is required for your web app. [Or create full web setup program for your app]

     

     

     

     

     

    Thursday, March 15, 2007 4:37 PM
  • Thank you, Bhawnach and Youssef Abou-Kewik, for your help.  I really appreciate it.
    Thursday, March 15, 2007 6:13 PM
  • Hi all, I've the same problem...

    I ran \...\...\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\CrystalReports\CRRedist2005_x86.msi file but it didn't seem to solve anything.

    Then I've tried to follow Bhawnach's instructions but when I create a new Project and I drag into this a new Crystal Report component, I get the same error ("Unable to open file") and then VS2005 crashes without saving anything!!

    have you got any ideas??



    Lorenzo
    Monday, June 16, 2008 4:03 PM
  • Hello,
       Same problem here too and no luck with the above possible solution.
     I will be grateful if any one has the solution.

    Thanks and Regards,
    Prashanth Kumar Ganathe.
    prashanthganathe@gmail.com

    kumar
    Tuesday, August 05, 2008 7:00 AM
  • Ok guys im having the same problem ... funny thing is it was working yesterday, then out of the blue it gives me this exception . I advise MS followers to please dont use any ms product, please make our lives better by using an open source language. Every time i get an error , there are no solutions in the forums and when there is actually a solution it usually involves: please re-install this, delete and start all over, register that, browse to the registry and find that needle. What kind of product is this ? a pretty bad one i'd say. yeah lets restart a production server every week , maybe that helps with productivity. if you really like MS then u like being in the dark about how things really work in the background and spend contless hours learning a programming model than in the end it will change in a few years to a total different scheme ...
    Wednesday, August 13, 2008 3:49 PM
  • Why this issue didn't have solution for a long time ?
    Anyone can help ?
    Wednesday, April 22, 2009 1:37 AM
  • I also got the same error, I had two versions of CR and I was using CR2005  with VS2008
    myReportDocument = new CrystalDecisions.CrystalReports.Engine.ReportDocument();

    It was throwing COM error: 80040154. but then I used VS2005 with CR2005 and it worked fine.

    This com issue is mainly due to the CR versioning with Visual Studio, since VS2008 has its own CR2007, web.congif file is mapped with CR2005 but after installation of VS2008, CR2007 updated my GAC settings.


    - You can check your GAC { run >type: assembly } whether you posses  multiple versions.
    - If your VS2005 is crashing check out event viewer for the details.
    - Dude, replying to your post; it worked one day and didnt worked afterward because you changed some settings which was reflected after the computer  restarted.

    I hope this will resolve your problem. 


    MCP
    • Proposed as answer by Talha Ekram Monday, May 25, 2009 6:51 AM
    Monday, May 25, 2009 6:49 AM
  • Hi,

    Even I faced this problem. It was working fine yesterday and today it gave the error "Failed to open document".

    Actually to clear some space in my C drive, I have uninstalled the setup of the application on which I am working. And then when I opened a report on that application, it started giving this error.

    I uninstalled and reinstalled VS 2005, but all efforts were in vain.

    But to my surprise, it got rectified when I installed the setup of the application again.

    Please try doing it, if you have the setup of any VS2005 application which has crystal reports (and thus merge module) attached to it.

    All the Best.
    Tuesday, May 26, 2009 6:29 AM
  • Hi friends, I figure it out ,
    Fist I downloaded Business Objects Merge modules
    http://resources.businessobjects.com/support/additional_downloads/runtime.asp#07

    The I did the following

    If you need the Installer .msi, just send me an email michaelfallas@gmail.com, subject Crystal

    Hope this helps

    <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} @font-face {font-family:"Century Schoolbook"; mso-font-alt:Century; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:647 0 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman"; mso-ansi-language:EN-US; mso-fareast-language:EN-US;} h1 {mso-style-next:Normal; margin-top:12.0pt; margin-right:0cm; margin-bottom:3.0pt; margin-left:0cm; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:1; font-size:16.0pt; font-family:Arial; mso-font-kerning:16.0pt; mso-ansi-language:EN-US; mso-fareast-language:EN-US;} h2 {mso-style-next:"Text\: Body"; margin-top:0cm; margin-right:0cm; margin-bottom:12.0pt; margin-left:0cm; mso-pagination:widow-orphan lines-together; page-break-after:avoid; mso-outline-level:2; font-size:12.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-bidi-font-family:"Times New Roman"; color:#5F7BA4; letter-spacing:-.2pt; mso-font-kerning:14.0pt; mso-ansi-language:EN-US; mso-fareast-language:EN-US; font-weight:normal; mso-bidi-font-weight:bold;} h3 {mso-style-next:"Text\: Body"; margin-top:6.0pt; margin-right:0cm; margin-bottom:10.0pt; margin-left:36.0pt; mso-pagination:widow-orphan; page-break-after:avoid; mso-outline-level:3; font-size:10.0pt; font-family:Arial; mso-bidi-font-family:"Times New Roman"; color:#5F7BA4; mso-ansi-language:EN-US; mso-fareast-language:EN-US; mso-bidi-font-weight:normal;} p.MsoToc2, li.MsoToc2, div.MsoToc2 {mso-style-update:auto; mso-style-noshow:yes; mso-style-next:Normal; margin-top:0cm; margin-right:0cm; margin-bottom:0cm; margin-left:10.0pt; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; mso-bidi-font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman"; font-variant:small-caps; mso-ansi-language:EN-US; mso-fareast-language:EN-US;} p.MsoToc3, li.MsoToc3, div.MsoToc3 {mso-style-update:auto; mso-style-noshow:yes; mso-style-next:Normal; margin-top:0cm; margin-right:0cm; margin-bottom:0cm; margin-left:20.0pt; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; mso-bidi-font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman"; mso-ansi-language:EN-US; mso-fareast-language:EN-US; font-style:italic;} p.MsoHeader, li.MsoHeader, div.MsoHeader {margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; tab-stops:center 234.0pt right 468.0pt; font-size:8.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; color:blue; mso-ansi-language:EN-US; mso-fareast-language:EN-US; font-weight:bold; mso-bidi-font-weight:normal;} p.MsoFooter, li.MsoFooter, div.MsoFooter {margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; tab-stops:center 234.0pt right 468.0pt; font-size:8.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; color:blue; mso-ansi-language:EN-US; mso-fareast-language:EN-US; font-weight:bold; mso-bidi-font-weight:normal;} p.MsoBodyText3, li.MsoBodyText3, div.MsoBodyText3 {margin:0cm; margin-bottom:.0001pt; text-align:justify; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-ansi-language:EN-US; mso-fareast-language:EN-US;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} p.TextBody, li.TextBody, div.TextBody {mso-style-name:"Text\: Body"; margin-top:0cm; margin-right:0cm; margin-bottom:12.0pt; margin-left:36.0pt; text-align:justify; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-ansi-language:EN-US; mso-fareast-language:EN-US;} p.TitleMain, li.TitleMain, div.TitleMain {mso-style-name:"Title\: Main"; mso-style-parent:"Título 1"; mso-style-next:"Title\: Sub"; margin-top:6.0pt; margin-right:0cm; margin-bottom:6.0pt; margin-left:0cm; mso-pagination:widow-orphan; page-break-after:avoid; font-size:18.0pt; mso-bidi-font-size:10.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman"; color:#5F7BA4; mso-font-kerning:14.0pt; mso-ansi-language:EN-US; mso-fareast-language:EN-US; font-weight:bold;} p.TitleSub, li.TitleSub, div.TitleSub {mso-style-name:"Title\: Sub"; mso-style-next:"Text\: Body"; margin-top:0cm; margin-right:0cm; margin-bottom:12.0pt; margin-left:0cm; mso-pagination:widow-orphan; border:none; mso-border-bottom-alt:dotted windowtext .5pt; padding:0cm; mso-padding-alt:0cm 0cm 14.0pt 0cm; font-size:14.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; mso-ansi-language:EN-US; mso-fareast-language:EN-US;} p.FirstPageFooter, li.FirstPageFooter, div.FirstPageFooter {mso-style-name:"First Page Footer"; mso-style-parent:"Pie de página"; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; tab-stops:center 234.0pt right 468.0pt; font-size:8.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; color:blue; mso-ansi-language:EN-US; mso-fareast-language:EN-US; font-weight:bold; mso-bidi-font-weight:normal;} p.FirstPageHeader, li.FirstPageHeader, div.FirstPageHeader {mso-style-name:"First Page Header"; mso-style-parent:Encabezado; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; tab-stops:center 234.0pt right 468.0pt; font-size:8.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman"; color:blue; mso-ansi-language:EN-US; mso-fareast-language:EN-US; font-weight:bold; mso-bidi-font-weight:normal;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 63.0pt 72.0pt 54.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-page-numbers:1; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:68505481; mso-list-type:hybrid; mso-list-template-ids:-295960506 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;} @list l0:level1 {mso-level-text:"%1\)"; mso-level-tab-stop:72.0pt; mso-level-number-position:left; margin-left:72.0pt; text-indent:-18.0pt;} @list l1 {mso-list-id:625160322; mso-list-type:hybrid; mso-list-template-ids:-682490846 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;} @list l1:level1 {mso-level-text:"%1\)"; mso-level-tab-stop:72.0pt; mso-level-number-position:left; margin-left:72.0pt; text-indent:-18.0pt;} @list l2 {mso-list-id:933128122; mso-list-type:hybrid; mso-list-template-ids:563766136 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;} @list l2:level1 {mso-level-text:"%1\)"; mso-level-tab-stop:72.0pt; mso-level-number-position:left; margin-left:72.0pt; text-indent:-18.0pt;} @list l3 {mso-list-id:1537889501; mso-list-type:hybrid; mso-list-template-ids:-502255196 2042397364 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l3:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:108.0pt; mso-level-number-position:left; margin-left:108.0pt; text-indent:-18.0pt; mso-ansi-font-size:8.0pt; mso-bidi-font-size:8.0pt; font-family:Symbol;} @list l4 {mso-list-id:1687632600; mso-list-type:hybrid; mso-list-template-ids:1339582890 2042397364 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;} @list l4:level1 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:108.0pt; mso-level-number-position:left; margin-left:108.0pt; text-indent:-18.0pt; mso-ansi-font-size:8.0pt; mso-bidi-font-size:8.0pt; font-family:Symbol;} @list l4:level3 {mso-level-number-format:bullet; mso-level-text:; mso-level-tab-stop:180.0pt; mso-level-number-position:left; margin-left:180.0pt; text-indent:-18.0pt; font-family:Wingdings;} ol {margin-bottom:0cm;} ul {margin-bottom:0cm;} -->

    Crystal Reports for .NET Framework 2.0

    Deployment Using Merge Modules

     

    Overview

     

    This document provides a detailed description of how to perform a deployment using the Crystal Reports for .NET Framework 2.0 merge modules.

     

     

    System Requirements .. 2

    Dependencies .. 2

    Walkthroughs .. 3

    X86 Deployments. 3

    IA64 Deployments. 5

    X64 Deployments. 7


     

    System Requirements

    Michael Hidalgo Fallas

    Tuesday, July 07, 2009 2:38 PM
  • Hi friends, I figure it out ,

    Fist I downloaded Business Objects Merge modules
    http://resources.businessobjects.com/support/additional_downloads/runtime.asp#07

    I created an MSI installer

    If you need the Installer .msi, just send me an email michaelfallas@gmail.com, subject Crystal

    Hope this helps


    Michael Hidalgo Fallas
    Costa Rica.
    Tuesday, July 07, 2009 2:38 PM