File Not Found Exception After Uninstalling .msm And Reinstalling .msi

[Former Member]

Hello,

We have two applications that originally used the redistributable merge modules (CrystalReportsRedist2005_x86.msm) as per the Business Objects guidelines for Crystal Reports for .NET Framework 2.0.

Several workstations were selected for user acceptance testing. Both applications were deployed to the UAT workstations.

When Application-A was uninstalled, Application-B (same dependencies, same deployment scenario) began throwing the error shown in Listing -1 below.

We uninstalled both applications. We then prepped the workstations with the redistributable msi package (CRRedist2005_x86.msi) and removed the merge modules from the application deployment.

We also expanded the user acceptance testing pool to include additional workstations that did not have either application deployed using the merge modules.

During testing weu2019ve found that work stations that originally received the merge module installation now throw the error shown in Listing -1 below. Workstations that did not receive the merge module installation work fine.

Our questions:

1) Why is this occurring?

2) How can we resolve the issue without reimaging the worktations?

Listing - 1

Error Message: Could not load file or assembly 'CrystalDecisions.Shared, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.

Error Type: System.IO.FileNotFoundException

Base Exception: System.IO.FileNotFoundException: Could not load file or assembly 'CrystalDecisions.Shared, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.

File name: 'CrystalDecisions.Shared, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304'

at Reports.pt_PtfViewer..ctor(Int32 batchKey)

at UserInterface.frmProvTrackerMain._ViewPtf_Click(Object sender, EventArgs e)

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

[former_member183750 · Accepted solution]

Not sure what this would be happening, but the 1st thing to look for is the CrystalDecisions.Shared.dll Version=10.2.3600.0 in GAC. I suspect that for some reason it will not be there. Also, check the directory structure for c:\program files\Business Objects\2.7\bin. See if this exists and if the CR runtime files are in the bin directory.

Ludek

[Former Member · Accepted solution]

Hello,

Thank you for your suggestions. We have check the 7 workstations that are in question:

All workstations have a GAC record for CrystalDecisions.Shared v10.2.3600.0

The CR Runtime files are not in the C:\Program Files\Business Objects\2.7\bin directory, they are located in the C:\Program Files\Common Files\Business Objects\2.7\Bin directory.

There does not appear to be a C:\Program Files\Business Objects\2.7\bin directory, but there is a C:\Program Files\Business Objects\Crystal Reports for .NET Framework 2.0 (x86) directory.

The only item in the C:\Program Files\Business Objects\Crystal Reports for .NET Framework 2.0 (x86) directory is atl80.dll

Are there registry settings that might be artifacts from previous versions that might be re-directing runtime calls?

[former_member183750 · Accepted solution]

Are there registry settings that might be artifacts from previous versions that might be re-directing runtime calls?

- not that I'm aware of.

It may be worthwhile to see at where the app is looking for the assemblies. Process Monitor, available from here:

http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx

will create log files for you. Search the log for issues locating or loading of the assemblies.

Ludek

[former_member11696]

To fix the problem re-install the app missing the parts will resolve the problem. We are fixing this in CR 2008 but will not be fixing this in older versions. It's an MSI issue.

[Former Member]

This issue is not resolved.

We could not determine what the root cause of the issue was. We solved the problem by re-imaging the workstations and migrating the application to CR 10.5. This is not truly an acceptable solution to the issue.

Has anyone come up with additional suggestions?