Open Closed

Hangfire Error After Upgrade to V8.2.0 #7581


User avatar
0
sukhdeep.dhillon created
  • ABP Framework version: v8.2.0
  • UI Type: Angular
  • Database System: EF Core (SQL Server)

Hi, after upgrading to V8.2.0, getting the following error

I tried the solution from the other issue (https://abp.io/support/questions/7551/HANGFIRE-WORKERJOB-REGISTRATION-PROBLEMS-ON-ABP-820), but getting compile time error onRecurring.AddOrUpdatemethod


12 Answer(s)
  • User Avatar
    0
    liangshiwei created
    Support Team Fullstack Developer

    Hi,

    You can solve this problem by simply changing the field length.

  • User Avatar
    0
    sukhdeep.dhillon created

    Hi,

    I have to manually change to all the environments and tomorrow if we delete and recreate the database, we will have the same problem again.

    are you going to provide any permanent fix in the coming patches ?

  • User Avatar
    0
    liangshiwei created
    Support Team Fullstack Developer

    Hi,

    yes, we will fix it in the next patch version

  • User Avatar
    0
    sukhdeep.dhillon created

    Hi, I have changed the size from 100 to 255 as you can see in the following screenshot

    but now I'm getting another following error

  • User Avatar
    0
    liangshiwei created
    Support Team Fullstack Developer

    hi

    https://abp.io/support/questions/7458/Abp-820-Hangfire-errror-with-redis-db#answer-3a1392c1-9efc-888a-acae-14a9415640ce

  • User Avatar
    0
    sukhdeep.dhillon created

    now app is working but in the console, I can see the following error:

  • User Avatar
    0
    liangshiwei created
    Support Team Fullstack Developer

    I could not reproduce the problem.

  • User Avatar
    0
    sukhdeep.dhillon created

    Hi,

    as you asked me to change the size of the column.

    I did the following:

    • drop the primary key constraint
    • change the size
    • recreate the primary key

    after doing this, I was getting the error "Violation of Primary Key constraint and cannot add duplicate entry"

    but if I create the primary key constraint with this flag IGNORE_DUP_KEY = ON, then I'm not getting an error.

    let me know if this is okay for now because as you said in the next patch it will be resolved

  • User Avatar
    0
    liangshiwei created
    Support Team Fullstack Developer

    HI,

    You can try removing those records from the database and restarting your application.

    By the way, we will release the new patch version today; you can wait for it.

  • User Avatar
    0
    sukhdeep.dhillon created

    I tried removing those records but had the same issue. but if I create the primary key constraint with this flag IGNORE_DUP_KEY = ON, then I'm not getting an error.

    anyway, I will wait for your patch to be release today.

  • User Avatar
    0
    liangshiwei created
    Support Team Fullstack Developer

    okay : )

  • User Avatar
    0
    sukhdeep.dhillon created

    thanks, the issue is fixed with the new patch

    but FYI,, abp update command was not updating the backend projects, I had to manually type abp update --version 8.2.1

Made with ❤️ on ABP v9.1.0-preview. Updated on November 11, 2024, 11:11