COM class factory component CLSID failed 8007007e

jb_bryant (23 posts)
May 31, 2019 11:45 AM
Accepted Answer

Please see attached log for Inventory Valuation report - note, I've modified license, IPs, DB name, and login credentials for security.

The Crystal Report runs fine from Crystal... and was running fine before 4/1/19

Report Commander 2.5.0.0 32-bit
2019-05-01 04:00:01Z
2019-05-01 00:00:01 Debug Report Commander 2.5.0.0
2019-05-01 00:00:01 Verbose Using license 1234567-01-abcdefg
2019-05-01 00:00:01 Info Processing report Inventory Valuation
2019-05-01 00:00:01 Debug Using ReportDoc engine
2019-05-01 00:00:02 Error An error occurred while processing the project: The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception.: Retrieving the COM class factory for component with CLSID {4DB2E2BB-78E6-4AEA-BEFB-FDAAB610FD1B} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E).
Exception detail: System.TypeInitializationException: The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception. ---> System.IO.FileNotFoundException: Retrieving the COM class factory for component with CLSID {4DB2E2BB-78E6-4AEA-BEFB-FDAAB610FD1B} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E).
   at CrystalDecisions.CrystalReports.Engine.ReportDocument..cctor()
   --- End of inner exception stack trace ---
   at CrystalDecisions.CrystalReports.Engine.ReportDocument..ctor()
   at #Lwd.#Kwd.#Gh(String )
   at ArcanaDevelopment.ReportCommander.Engine.ProcessingEngine.#ek(Report )
   at ArcanaDevelopment.ReportCommander.Engine.ProcessingEngine.#5xd(Boolean )

 

Thanks

Attachments

  • Inventory Valuation Report.log (72.7kb) (pending moderator review)
Bill Staff (603 posts)
May 31, 2019 12:04 PM
Accepted Answer

Two main possibilities:

  1. You installed a Crystal Reports product update, and that updated the runtime components that Report Commander uses to a version it doesn't expect.
  2. Something corrupted the Crystal Reports runtime installation.

Check in Add/Remove Programs to see what version of "SAP Crystal Reports runtime engine for .NET Framework" is installed. For Report Commander 2.5, it should be 13.0.20.x.

If it's later than that, then it's case 1. Download and install Report Commander 2.6 to update Report Commander to use the 13.0.24 version of the runtime.

If the installed runtime is earlier or the same, then something has reinstalled the runtime or corrupted it. In that case it's a good idea to figure out what else on the computer is using the runtime and causing the conflict, so they don't keep breaking each other. Then uninstall both Report Commander and the Crystal Reports runtime, and reinstall Report Commander 2.5 or 2.6. Be sure to install the 32-bit version--that's what you're using now.

Replies are disabled for this topic.