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

100 Views

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].