Crystal Reports for Visual Studio 2022 Error 1904 CRAXDDRT.DLL Failed to Register

[andrew_hayes]

Trying to install CR for VS x64 SP34 on a Windows 10 Enterprise OS (21H2 19044.3570) with VS 2022, and getting the above mentioned error during the "registering modules" section of the installation process.

I've checked the following:

• Missing VS 2005 C++ Security runtime. Installed, along with 2012, 2013 and 2015-2022.
• Run As Administrator. Yes.
• Using ignore isn't suitable as I need the report designer in VS.
• Get the same error on Windows 11 Enterprise (22H2 22621.2428)
• Already have the SAP Crystal Reports runtime engine for .NET Framework (64-bit) 13.0.31.4010 installed.
• Same question that Gordon Kenyon asked Nov 25, 2020, and which doesn't have an answer.
• Same question that Daniele Pedruzzi asked Apr 28, 2021, and which doesn't have an answer.

Given this problem has existed for many years with no suitable answer, I'm not holding out for a solution to this question, but I certainly won't get an answer if I don't ask.

SAP are releasing new versions of the CR for VS every year, so surely it must be usable. Just what are the exact pre-requisites required?

[DonWilliams · Accepted solution]

Hi Andrew,

There are only a few people who have install issues, so it's not a CR problem, otherwise thousands of people would be logging posts... it is an environmental issue on your PC.

As noted it's usually a dependency missing that the RDC engine needs that's missing, error handler are bad for Windows dll's. Or something CR needs is being blocked by AV or Firewall functions.

The RDC comnponent is a COM dll so that could be the problem.

Go here:

C:\Program Files (x86)\SAP BusinessObjects\InstallData\logs\2023.01.25.14.30.20

In there there is a file called setupengine.log

See if there are any errors noted with registering dll's or missing dependencies.

That would be normal for Windows to link RPT file extensions to VS since you don't have a full version of Crystal Reports installed. If you had it would start Crystal Reports Designer and open the report.

Use ProcessMonitor from Microsoft and attach the VS process to it and see what it catches when you try to open a report:

Learn.microsoft.com

https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

Process Monitor - Sysinternals - Microsoft Learn

Mar 9, 2023 ... Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. ... Its ...

It could either be a missing registry key or likely a missing dependency

Note: CR looks for registry keys, if not found it loads the defaults within it's code so a lot of keys may not be found.

Search for craxddrt.dll, should get you close....

Don

[DonWilliams]

Hi Andrew,

Error 1904 is a MSIExec error code so it's not something SAP can fix. Use Google, typically that error is due to outdated MS's installer or possibly permissions, could even be your AV software blocking registering various COM dll's. For more info use Dependency Walker on the EXE, it can sometimes indicate what is missing.

Unfortunately the error code can't drill down into dependencies, welcome to "DLL Hell", only the top layer error is reported, so likely cause is some dependency for craxddrt.dll is missing, coul dbe the VC 2015 C++ runtime.

SP 34 no longer uses VC 2005 runtime, Microsoft deprecated that version, it now requires VC 2015 or higher C++ runtime.

Also note, VS 2022 is a 64 bit interface now and so is CR for VS SP 34, there is one specifically for VS 2022:

CR for Visual Studio SP34 64b installer (VS 2022 and above)

Also, uninstall ALL CR for VS runtime as well as the EXE's.

You can't mix versions:

• Already have the SAP Crystal Reports runtime engine for .NET Framework (64-bit) 13.0.31.4010 installed.

Check my Blog I wrote for assisting upgrades:

https://blogs.sap.com/2020/10/30/upgrading-a-visual-studio-2008-2019-.net-project-with-the-latest-cr...

Don't run the MSI packages separately, the installer will ask you if you want the 32 bit MSI installed, check Yes, it is needed in VS 2022, 64 bit is the default.

Don

[andrew_hayes]

Hi Don. I uninstalled the Crystal Reports runtime for .NET Framework (64 bit), and the Crystal Reports for Visual Studio 2022 64-bit installer was able to complete without error, however there is still a problem.

Creating a new solution, I added an RPT item to it, then tried to open the item using the embedded Report Designer, and after a short delay, I got a "The specified procedure could not be found. (Exception from HRESULT: 0x8007007F)." error popup. I am running VS as ADMIN.

I'm not convinced it's not a SAP problem. With regard to the installer, surely the CR for VS installer should be checking if it has the CR for .NET already installed and uninstall it as part of the pre-requisite process, or at least warn the user they need to uninstall it if an error is thrown?

I have already installed dozens of other applications on my laptop, including VS 2022, Delphi, Office, Teams, SSMS, Oracle SQL Developer, etc... and none of them had a problem with MSIExec or anything else.

Only Crystal Reports for Visual Studio is failing to work. What makes this so special?

Strangely, if I open an RPT file directly from Explorer (the files do have the Crystal Reports icon), I get told to use Visual Studio 2010 to open RPT files. Since I've never installed a previous version of VS, I have no idea where that extension association is coming from. If the CR for VS 2022 installer did it, it's obviously wrong.