Skip to Content
avatar image
Former Member

Crystal Reports 2010 .NET 4.0 COM class factory 80000003 error

I am having the following error occur on a PDF generated by Crystal Reports via an ASP.NET 4.0 web page when deployed to the server:

Retrieving the COM class factory for component with CLSID {F734A321-8381-4FFD-A614-139E8906DC83} failed due to the following error: 80000003 One or more arguments are invalid (Exception from HRESULT: 0x80000003).

The offending code is:

ReportDocument reportdoc = new ReportDocument();

I am using the following DLLS:



These are both version 13.0.2000.0 and I'm also referencing CrystalDecisions.Web and CrystalReports.ReportSource in the project (also the same version 13.0.2000.0).

I am targeting the project to build as an x86 per suggestions as well.

I have installed the CRRuntime_32bit_13_0 to the server (running Windows Server 2008 and IIS 7) and have verified that there is only one .config on the web app, yet I still receive this error. I have tried reinstalling the runtime multiple times. I have not seen any installation log files generated (not sure where to look)

Please advise.


Edited by: travis.burgess on Feb 10, 2012 5:52 PM

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Feb 10, 2012 at 05:54 PM

    The GIUD resolves to clientdoc.dll.

    Did you get any errors re. registering clientdoc.dll , etc., when you were installing the CR runtime?

    Are you able to manually register the clientdoc.dll using regsvr32?

    The dll is in C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\clientdoc.dll.


    Follow us on Twitter

    Got Enhancement ideas? Try the [SAP Idea Place|]

    Add comment
    10|10000 characters needed characters exceeded

    • 😊

      reason it was not answered is that the query was posted to the Crystal reports (design) "discussion forum". I moved it to the SAP Crystal Reports, version for Visual Studio forum now and will get to it in a minute. This move to the new platform has it's pain points. Where to put the queries is one of those pain points (it's quite confusing), but we are working on making these more clear.

      - Ludek