32-bit machine: C: Program Files SAP BusinessObjects Crystal Reports for.NET Framework 4.0 Common SAP BusinessObjects Enterprise XI 4.0 win32x86 64-bit machine: C: Program Files (x86) SAP BusinessObjects Crystal Reports for.NET Framework 4.0 Common SAP BusinessObjects Enterprise XI 4.0 win32x86 64-bit edition DLLs: 32-bit machine: N A. We made a project with Visual Studio 2010 and.NET 4.0 using Crystal Reports. But if we publish it on the server, it won't work. I remember that with Visual Studio 2008 you just downloaded an installer for the server, but I can't seem to find one for this version. Crystal Reports for Visual Studio 2010. Note The log file extension created by Crystal for Visual Studio 2010 is.GLF. Windows Registry Editor Version 5.00 HKEYLOCALMACHINESOFTWARESAP BusinessObjectsCrystal Reports for.NET Framework 4.0Crystal ReportsLogging.
Symptom
Error 1904. Module C:Program FilesSAP BusinessObjectsCrystal Reports for .NET Framework 4.0CommonSAP BusinessObjects Enterprise XI 4.0win32_x86crtslv.dll failed to register. HRESULT -2147010895. Contact your support personnel.
Environment
- Crystal Reports Developer for Visual Studio Service Pack 9 ( Supports Visual Studio 2013 and Windows 8.1 )
- Windows 8.1
- Windows Servers
- Windows 7
- Visual Studio 2013
Module C:Program Files (x86)SAP BusinessObjectsCrystal Reports for.NET Framework 4.0CommonSAP BusinessObjects Enterprise XI 4.0win32x86crtslv.dll failed to register. Contact your support personnel.”, this can be caused by missing prerequisite(s) including.NET Framework 3.5. Feb 28, 2018 The other is SAP Crystal Reports runtime engine for.NET Framework that is installed when the application is deployed on server machine. SAP Crystal Reports in Visual Studio 2017 is now planned for Service Pack/Support Pack 21 (as of Apr 04'2017).
Cause
1904 error is typically due to some third party missing dependency.
Microsoft provided two methods to redistribute the VC++ runtime files: a set of merge modules, or one self-extracting vcredist.exe file. The two methods are designed to affect the same result once installed. CR Developer for VS installers have been using the merge modules to deliver the VC++ runtimes files since the first release, such that each CR Developer for VS installer is self-contained and does not require pre-installation of any other software except .NET Framework 2.0 or later. Namely, we handle pre-requisite check and installing of the required runtime. The version of the VC++ runtimes in CR Developer for VS installers is 8.0.50727.4053, which is identical to those installed by 'Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update' (internal version is 8.0.50727.4053).
This issue was escalated with ADAPT01723743 and resulted are in the Resolution section.
Resolution
1. Manually download and install the VC Redist package before installing CR Developer for VS.
2. If this does not resolve the issue then due to some issue on Microsoft’s part, the error as reported in this ADAPT could happen to some machines, as detailed in this Microsoft KBase article. The official fix to the problem is for customers to contact Microsoft to get the hotfix; Microsoft does not provide any download link for the hotfix. The hotfix is to be applied to a machine that encounters this error only. The KBase article does not provide any way to prevent the problem from happening.
The suggestion of pre-installing “'Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update” may help some customers, however there is no endorsement from Microsoft to guarantee that it always works (this post actually reported that it could trigger the error on some machines). Getting help from Microsoft is the best way. Please note that the Kbase article only applies to customers who are reporting error “HRESULT: 0x80073715” ( 2147956501 )
Keywords
1904, Failed to register a SAP component, HRESULT -2147010895, HRESULT: 0x80073715, CRforVS, crystal reports for Visual studio , KBA , BI-DEV-NET-SDK , .NET SDK / COM SDK , Problem