The COM class factory for the component with CLSID... - SAP Community
source link: https://community.sap.com/t5/technology-q-a/the-com-class-factory-for-the-component-with-clsid-f734a321-8381-4ffd-a614/qaq-p/13596794
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Tuesday
We have a new Windows Server 2019 data center (64 bit). We have installed Crystal Report Runtime version 13.0.31.4010. Our application (32 bit) was created in Visual Studio 2019 with Crystal Reports for Visual Studio version 13.0.31.4010. When we try to start the app we get this error:
The COM class factory for the component with CLSID {F734A321-8381-4FFD-A614-139E8906DC83} could not be obtained due to the following error: 8007007f The specified procedure was not found. (Exception from HRESULT: 0x8007007F).
Everything runs on another server with the same configuration.
- SAP Managed Tags:
- SAP Crystal Reports, version for Visual Studio
Accepted Solutions (0)
Answers (3)
3 hours ago
Did you set your project to x86 and not leave the default for AnyCPU?
SP 31 is old I suggest upgrading to the latest SP 35, SP 31 did have video monitor issues.
https://help.sap.com/docs/SUPPORT_CONTENT/crystalreports/3354091173.html
Check the Install log, you may need to run the MSI again using a command line and enable logging, check MS's site on how to enable logging for msiexec.exe
It could be and likely is a missing dependency.
ProcessMonitor may be able to find the missing parts. Ignore the missing registry errors, CR has defaults built in so it's just looking to see if an override in the registry is available.
I assume this is a Desktop application and not a WEB App? If it is a WEB app make to AppPool for this app is set to x86.
And check your AV and Firewall setting, could be one of those are blocking access to the runtime.
Try starting the app by right clicking on your EXE and selecting Run as Administrator, could be a local permission issue.
Thursday
Did you install the 32-bit or the 64-bit SDK runtime? You need the 32-bit version because that's the architecture of your application even though the server is 64-bit.
-Dell
Wednesday
When the runtime was installed, were you logged in to the server with Administrator privileges? If not, you need to be because the install makes changes to the Windows Registry.
-Dell
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK