We are having problems with clients that have both iMIS 15.2 and ACCPAC (financial package) installed on workstations.  Following the upgrade of iMIS from 10.6 to 15.2, some machines were having problems runnig custom Crystal Reports, with a message reading "iMIS Crystal Runtime Error. Unable to load report." Standard Crystal Reports were running fine, and we narrowed it down to a known issue with multiple copies of the crpe32.dll.  ASI/iMIS community advice is to delete or rename this file in every location except the one in C:\Program Files (x86)\Common Files\Crystal Decisions\2.0.

This was fine, until the users with ACCPAC tried running custom Crystal Reports from ACCPAC.  They recieved an error message in ACCPAC and their ACCPAC consultant advised a fix.  After that fix, there were additional copies of the crpe32.dll on the workstation and the iMIS custom Crystal Reports were generating the same error as originally!

We've narrowed this down to the copy of the file in C:\Windows\System32.  If it is present, the ACCPAC reports work and the iMIS ones do not.  If it is not present, the iMIS reports work and the ACCPAC ones do not.  It does only appear to be affecting custom reports in each application, of which there are more in iMIS, but the cheque print from ACCPAC is a custom report.

ASI Tech Support has suggested a workaround that involves staff doing remote desktop for one of the applications, at least for printing, but I am reluctant to offer this as a solution.  Both staff are heavy users of both applications. The other workaround that I can think of is to provide DOS batch files to rename the dll as required, or perhaps something more complicated that launches each application in turn with the file present or absent as required (renaming the file while the applications are already open has no effect).

Does anyone have a solution to this problem?