Crystal Reports will not Export follow GS2022 Upgrade

[du5tin]

We are experiencing a weird issue where Crystal Reports will not export properly. They fail with the message: 

Export report request failed - Failed to export report, Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=4.0.4.1, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. ... (03/21/2023 13:28:35)

We have opened a ticket with support already but wanted to see if anyone else is seeing this issue. The report was made a while ago using Crystal Reports 2013 but I cannot see how that would impact the system. THis looks more like a .NET framework incompatibility to me. 

Operating System: Windows Server 2016

Things we have tried:

- repairing Geo SCADA install

- reinstalling the Crystal Reports runtimes

- installing windows updates and restarting

I'm thinking we need to reinstall .NET framework 4.8 and possibly .NET 3.5 and then try reinstalling the whole thing from the ground up again. Just weird. Open to suggestions and ideas. 

Driver Log file contents: 

21-MAR-2023 19:10:45.612 [RPT1] OpenReport( OUT: 0x00000000 )
21-MAR-2023 19:10:45.612 [RPT1] SetLogOnInfo( IN: DSN "Geo SCADA Expert", User "" ) for "Pembina.~Reports.Daily Injection Well Report" [CCrystalReport,729873]
21-MAR-2023 19:10:45.698 [RPT1] SetLogOnInfo( OUT: 0x00000000 )
21-MAR-2023 19:10:45.698 [RPT1] Refresh( IN: ) for "Pembina.~Reports.Daily Injection Well Report" [CCrystalReport,729873]
21-MAR-2023 19:10:45.728 [RPT1] Refresh( OUT: 0x00000000 )
21-MAR-2023 19:10:45.728 [RPT1] ExportOptions( IN: ) for "Pembina.~Reports.Daily Injection Well Report" [CCrystalReport,729873]
21-MAR-2023 19:10:45.734 [RPT1] ExportOptions( OUT: 0x00000000 )
21-MAR-2023 19:10:45.734 [RPT1] Export( IN: ) for "Pembina.~Reports.Daily Injection Well Report" [CCrystalReport,729873]
21-MAR-2023 19:10:50.729 [RPT1] Error at line 702, file D:\AzAgent\agent\_work\13\s\Drivers\CrystalReports\DriverCrystalReports\DrvCrystalThread.cpp
  Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=4.0.4.1, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
  80131040 -> Unknown Error 0x80131040
  Failed to export ("Pembina.~Reports.Daily Injection Well Report" [CCrystalReport,729873])
21-MAR-2023 19:10:50.729 [RPT1] Export( OUT: 0x80131040 )
21-MAR-2023 19:10:50.815 [Main] Received reply (Failed 0x400000D) to Export Report request (Id:1) for "Pembina.~Reports.Daily Injection Well Report"

[AndrewScott · Accepted solution]

This issue relates to the version of the "System.Runtime.CompilerServices.Unsafe" assembly that is installed. GS 2022 installs version 6.0.0.0, but Crystal Reports wants the older version 4.0.4.1.

It appears this issue only effects exporting reports in certain formats / destinations (e.g. email), as most don't use this particular assembly so aren't effected.

Creating the following file (on the main server) and restarting the Crystal Reports driver should workaround this issue until it can be fixed:

C:\Program Files\Schneider Electric\ClearSCADA\DriverCrystalReports.exe.config

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.1.1" newVersion="4.0.1.1" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Threading.Tasks.Extensions" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.2.0.1" newVersion="4.2.0.1" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Text.Encodings.Web" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.ValueTuple" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Text.Json" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.6" newVersion="6.0.0.6" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.Bcl.AsyncInterfaces" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

[du5tin · Accepted solution]

Thanks Andrew! This put us in the right direction. We tried out the xml you provided and it got rid of the error we were having but then we were presented with a similar error with System.Memory. We ended up figuring out which version of that ships with GS2022 and updated the file. New code below: 

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.1.2" newVersion="4.0.1.1" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Threading.Tasks.Extensions" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.2.0.1" newVersion="4.2.0.1" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Text.Encodings.Web" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.ValueTuple" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Text.Json" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.6" newVersion="6.0.0.6" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.Bcl.AsyncInterfaces" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

[AndrewScott]

No problem. I've corrected the mistake in my original solution with the "System.Memory" version. I was adapting the solution from the upcoming GS 2023 and missed this difference in GS 2022.

[DougIv]

Andrew, I am having the same issue after updating to GS2021 Sept 2023 update.  I tried the work around above but it still does not work.  Any Suggestions?

[AndrewScott]

@DougIv The assembly redirections in DriverCrystalReports.exe.config above are for GSE 2022 so may require changes for GSE 2021.

Which assembly and version are you seeing give a mismatch error?

Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=4.0.4.1, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.

[Sophia.He]

Hi @AndrewScott, we also ran into the same problem after upgrading to GSE2023, 

Error at line 688, file D:\AzAgent\agent_work\22\s\Drivers\CrystalReports\DriverCrystalReports\DrvCrystalThread.cpp
Could not load file or assembly 'Microsoft.Kiota.Abstractions, Version=1.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
80131040 -> Unknown Error 0x80131040

We tried adding the following workaround, and it works.     

<dependentAssembly>
        <assemblyIdentity name="Microsoft.Kiota.Abstractions" publicKeyToken="31bf3856ad364e35" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-1.5.0.0" newVersion="1.6.1.0" />
      </dependentAssembly>

Thanks.

[JChamberlain1]

@AndrewScott \ @sbeadle any plans for this issue to be fixed in an update or be added to the known issues list?

[AndrewScott]

@JChamberlain1 this issue has been fixed in 6.84 (GSE 2021), 6.85 (GSE 2022) and 6.86 (GSE 2023) and the fix will be available in the upcoming June 2024 releases of Geo SCADA.

[sbeadle]

Information added to this KB page:

https://community.se.com/t5/Geo-SCADA-Knowledge-Base/Monthly-Release-Known-Issues/ba-p/278395

The files per version are included in a zip attached to that page.

Steve