Crystal reports XI R2 and Visual Studio 2005 issues

Crystal reports XI R2 and Visual Studio 2005 issues

• The Developer-X

  I'm getting the same error. It even happens if you run the wizard to cretae a new crystal report application. A crystal error no doubt, they do my head in :).
  
  If I work out how to fix it I'll post the solution. Just thought I'd let you know your not the only one Crystal are fustrating!
  

• ruben@usa

  mciv34

  I am glad I am not the only one out there having this problem. I to am talking to Business Objects Tech Support. No answer yet and I will definately post once the answer is found. I agree we need to keep this post going. Thanks for the post.

  
  
  

• Aparrel

  jwalling

  This is a completely reloaded machine with only WinXP Pro all the updates, VS2005, and CRXIr2. So this would not be the problem but I do appretiate your fix reply.

  
  
  

• WilliamPen

  Well called up Business Objects on this. I could open a trouble ticket for $195 or explain the problem and they said they would look into it. Keeping my fingers crossed last time I waited 3 monthes and they put out a service pack.

  Ok I tried one more time to uninstall everything clean out the registry, Program files, common files, everything. I can not get this to work:

  Dim crReport0 As rptCDMediaLabelTop
  crReport0 = New rptCDMediaLabelTop
  crReport0.SetDataSource(dsReport)
  CrystalReportViewer1.ReportSource = crReport0

  I keep getting "Type 'rptCDMediaLabelTop' is not defined" it then say "Change 'rptCDMediaLabelTop' to 'frmCDMediaLabelTop'."

  This is on every report. I have checked all the file versions, Reference versions, etc. At this point I think I am going to uninstall CRXI r2 and use v10 that comes along with VS2005 and wait for a stable version or CRXI r2 to get released. I will use VMWare to load up VS2003 with CRXI none r2 to do all my programming that is pre VS2005.

  If anyone out there can please send me a basic examples that uses VS2005 with CRXI r2 that they have got to work correctly I would appretiate it. The examples that come with CRXI r2 do not work for me so I would like a tested basic example that I know works.

  
  
  

• Wizard_SHill

  WE are also having this problem with VS2005 and XI r2.  We created a simple test report and can edit it in the designer but it will not run. Same message Load report Failed.  I am in the process of working with business objects tech support, I will let you know if we find a solution. We need to keep this post going until someone finds something. I think your right iamtgo3 not many are using VS2005 and CRXI R2
  

• Steven_Gr3y_B3ard

  Has anyone came acrossed this or found a fix for this yet..
  
  

• lgemcor

  I would suggest checking your project references. I'm willing to bet that you had VS2003 installed on this PC at some point, because the references you listed are pointing to the .Net1.1 version of Crystal:

  CrystalDecisions.CrystalReports.Engine - v2.0.50526
  CrystalDecisions.Enterprise.Framework - v1.1.4322
  CrystalDecisions.Enterprise.InfoStore - v1.1.4322
  CrystalDecisions.ReportSource - v2.0.50526
  CrystalDecisions.Shared - v2.0.50526
  CrystalDecisions.Windows.Forms - v2.0.50526

  When you install a new instance of Crystal, the old assemblies still exist on your PC and are duplicated. Check to see if you have above assemblies that are flagged in red as a v2.0.xxxx in your reference list and use those instead.

  
  

• CMcGuire

  GeoffMF
  

  I am glad to see I am not the only one having this problem. Either others have not installed it or have not found this post. This is definately a bug on someones part. Plus the CRXI R2 examples do not even run correctly <F5>.

  
  
  

• Harel Moshe

  espeir
  That is a good observation but not the case here. This is a fresh install of XPPRO SP2, VS2005 and CRXIR2 being the only thing installed on my machine. I am still hashing it out with CR tech Support. They are a little stumped on this. They sent me an exact example of what I created local here to my machine. They created there example on a machine there that worked. This is the really odd part it worked on my machine perfectly. So I tried recreating that same example here and it errored out. Now that is very odd.

  I think I have narrowed the problem down to this folder My Project which contains the following files:

  Application.Designer.vb, Application.myapp, AssemblyInfo.vb, Resources.Designer.vb, Resources.resx, Settings.Designer.vb and Settings.settings

  When I create and exact copy of the program they sent me name and all. I run it it does not work. Once I replace My Project contents of the non working one with the contents of the My Project working one it works. So what seems to be the issue hmmm.

  
  
  

• Matt Wyncoop

  I have not found anything yet. I reloaded my system completely ran windows updates till there were no more. Then installed VS2005 and next CRXIr2. This is all I have loaded on the dev system. No matter how I create a project "Crystal reports Project" or "Windows App Project" in VB.NET. None of my projects will run. I have ruled out everything other then CRXIr2 is buggy and needs a patch big time.

  Here is my latest Errors / Bugs with creating a Crystal Reports Application from scratch and using SQL Server as my datasource.

  System.InvalidOperationException was unhandled
    Message="An error occurred creating the form. See Exception.InnerException for details.  The error is: The type initializer for 'CrystalDecisions.ReportSource.ReportSourceFactory' threw an exception."
    Source="CrystalReportsApplication1"
    StackTrace:
         at CrystalReportsApplication1.My.MyProject.MyForms.Create__Instance__[T](T Instance) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 190
         at CrystalReportsApplication1.My.MyProject.MyForms.get_Form1()
         at CrystalReportsApplication1.My.MyApplication.OnCreateMainForm() in C:\Documents and Settings\testuser\My Documents\Visual Studio 2005\Projects\CrystalReportsApplication1\CrystalReportsApplication1\My Project\Application.Designer.vb:line 34
         at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
         at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
         at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
         at CrystalReportsApplication1.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81
         at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
         at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
         at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
         at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
         at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
         at System.Threading.ThreadHelper.ThreadStart()

  
  
  

• roeschda

  I'm porting an enterprise application to vs2005 and and I experiences similar problem

  the type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception.

  ...
  -  InnerException {"Retrieving the COM class factory for component with CLSID {5EFA39FA-B2C4-4A6E-84D6-C3333D1A3D07} failed due to the following error: 80040154."} System.Exception

  loading a report in a winservice hosted in a windows 2003 enterprise server x64.

  I deployed the application with the

  C:\Programmi\File comuni\Merge Modules\CrystalReports11_5_NET_2005.msm

  I think that BO need to release a BIG PATCH!!
  

  
  

• MMcNamara

  After much research, we found our problem.  We had an old version(8) of Crystal on the systems we were having problems with.  As soon as we uninstalled that and reinstalled XI Release2 it started working without the out of memory error.  Could you be having conflicts like these
  
  

• PravinD

    You are correct in that we had VS 2003 on the machine but our Assemblies are pointing to the correct path

    <add assembly="CrystalDecisions.Web, Version=11.5.3700.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

                          <add assembly="CrystalDecisions.Shared, Version=11.5.3700.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>

                          <add assembly="CrystalDecisions.ReportSource, Version=11.5.3700.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>

                          <add assembly="CrystalDecisions.Enterprise.Framework, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>

                          <add assembly="CrystalDecisions.Enterprise.Desktop.Report, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>

                          <add assembly="CrystalDecisions.ReportAppServer.Controllers, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>

                          <add assembly="CrystalDecisions.CrystalReports.Engine, Version=11.5.3700.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>

                          <add assembly="CrystalDecisions.Enterprise.InfoStore, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>

                          <add assembly="CrystalDecisions.Enterprise.Viewing.ReportSource, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/><add assembly="CrystalDecisions.ReportAppServer.ClientDoc, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/></assemblies></compilation>

  
  

• Tyraslin

  We are seeing the same error as you are iamtgo3. The problem is only on the non-developer machines where we used the Crystal msm in the install.  The reports run fine on the dev machines which have the full version of CR XII R2 installed.

  This is a Winforms app that we are having the problem with.

  We have tried a number of things to no avail.  Has anyone come up with anything since this has been posted

  Thanks,

  Joe

   

  
  
  
• Crystal reports XI R2 and Visual Studio 2005 issues