Crystal Reports for VS 2010 Installation failure on Windows 7

[former_member703598]

I am receiving the 1904 error durring the install of the latest build.  I verified that .net 4 extended is installed as well as the Microsoft Visual C++ 2005 Redistributable.  I am at a loss of what else to try at this point.  Any ideas would be appreciated.

The error message is attached..

[former_member183750 · Accepted solution]

Make sure you are using SP 3 for Crystal Reports for Visual Studio 2010

- Ludek

[former_member703598]

Sorry.  I didn't explain it correctly.  The installation error occurs during the runtime installation.  I am using 13.0.2 for the install version.

[former_member183750]

Yup. That is what I understood. Do hit on the link I provided and try the SP3 runtime please.

- Ludek

[former_member703598]

I am using the 13.0.2 files that are posted in the link with the same issue.  I was able to install on a Windows 7 toshiba computer but when I try on two Windows 7 Dell desktop computers I get the same exact error.  Are there some other dependancys that are missing that the files can't be registered?

[former_member183750]

No additional dependencies that I am aware of. However, the full message should be something like:

Error 1904. Module C:\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dtsagent.dll failed to register. HRESULT -1073741819. Contact your support personnel.

This may be on a number of files, or just one (e.g.; dtsagent.dll). In your case, is it one file that fails (if so, which file), or a number of files?

- Ludek

[former_member703598]

The first file that fails has the following error message:

Error 1904. Module C:\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\commonobjmodel.dll failed to register. HRESULT -2147023898. Contact your support personnel.  If I click ignore, many more files have the same error.

[former_member183750]

Try the following:

1. Search your system for all instances of cryptocme2.dll. 
2. Rename cryptocme2.dll files you find to something like *.org 
   1. Do NOT rename the cryptocme2.dll files you find the in the subdirectories of C:\Program Files (x86)\SAP BusinessObjects
3. Install the Crystal Reports runtime (CRRuntime_32bit_13_0.msi). 
4. Rename cryptocme2.org files back to cryptocme2.dll.

- Ludek

[former_member703598]

I found that there were two instances of the file.  One for adobe reader and one for DameWare.  The installation worked when they were renamed.  Once they were restored, I received a COM error 800703E6.  I saw in the forum from 2010 that this was a result of the conflict of the file.  Is there a fix for this?

[former_member183750]

There was a fix - for Computer Associates as CA had / has(?) the path to the dll in system environment variables. I am not familiar with DameWare so no idea how they implement the access to the dll.

- Ludek

[former_member703598]

The crystal reports throws the COM error not the DameWare.  It seems to me that crystal reports doesn't know the correct file path.   Is there an environment variable in Crystal to point to the correct path?

[former_member183750]

Understood. However, in the case of CA, the issue was that the path was in the system variable. As I understand it, a big no, no with today's Operating Systems. And as a matter of fact, last I heard CA actually modified their load of the dll so that there is no need for a system var for them. E.g.; CR will use it's own version of the dll - unless some other app forces a load from else where. By renaming the dll and then successfully installing CR, you proved that the issue is not with Crystal Reports. Another way of looking at this is to use the Modulesutility and see where the dll is loading from. For CRVS2010 it should be:

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

- Ludek

[former_member188030]

Could you check the CLSID for which the COM error is being thrown?

Once the DLL is identified, check if it is properly registered in the win registry. May be comparing the folder structure in the win reg of the faulty machine with some other working machine would help identify if it is registered preprly.

Then reregister the DLL.

- Bhushan.

[former_member183750]

It's a bunch of dlls Bhushan. Which is typical with 1904 error. I believe there is a KB that lists most of them, but that does not help in this case.

- Ludek