Global Data Management Forum

 View Only
  • 1.  IBM.EntityFrameworkCore .NET 8

    Posted Fri April 05, 2024 10:43 AM

    We are using the following packages, and ran into this error. The application that encountered this error is a .NET worker service running on a Windows Server 2019. It is running as a Windows service.

    Is this a known issue? Or is there a way to configure the connection to get around this error?

    Packages used:

    •  <PackageReference Include="IBM.EntityFrameworkCore" Version="8.0.0.100" />
    •  <PackageReference Include="Net.IBM.Data.Db2" Version="8.0.0.100">

    Exception:

    CoreCLR Version: 8.0.123.58001
    .NET Version: 8.0.1
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
    Stack:
       at IBM.Data.Db2.UnsafeNativeMethods+DB232.SQLFreeConnAttribsADONET(DB2SQLGetConnAttribsADONETParams ByRef)
       at IBM.Data.Db2.UnsafeNativeMethods+DB232.SQLFreeConnAttribsADONET(DB2SQLGetConnAttribsADONETParams ByRef)
       at IBM.Data.Db2.ConnSettingsFromXmlConfig.Dispose()
       at IBM.Data.Db2.DB2ConnPool.ReplaceConnectionStringParms(IBM.Data.Db2.DB2Connection, System.String, DB2ConnSettings ByRef, DB2ConnSettingsInternal ByRef, Boolean, Boolean)
       at IBM.Data.Db2.DB2Connection.set_ConnectionString(System.String)
       at IBM.Data.Db2.DB2Connection..ctor(System.String)
       at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.get_DbConnection()



    ------------------------------
    Matthew Severson
    ------------------------------


  • 2.  RE: IBM.EntityFrameworkCore .NET 8

    Posted Mon April 08, 2024 07:04 AM

    Hi Matthew,

    Would you try with latest package that is IBM.EntityFrameworkCore version 8.0.0.200 ?



    ------------------------------
    Archana Soni
    ------------------------------



  • 3.  RE: IBM.EntityFrameworkCore .NET 8

    Posted Mon April 08, 2024 09:17 AM

    Hi Archana,

    Yes, we will give that a try. 

    Was this a known issue that was fixed in the latest version, or were there any known issues with the 8.0.0.100 version? I see that it was removed from nuget.org. 



    ------------------------------
    Thank you,
    Matthew Severson
    ------------------------------