Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

The "500" error appears when user saving "MARC Bib" record from "Derive" window.

Description

Overview: The "500 - Internal Server Error" appears when user click on the "Save & close" button in deriving window of "MARC Bibliographic" record.
The issue is reproduced not each time.
Steps to Reproduce:

  1. Log into Nolana BF FOLIO environment as User with the following permissions:
    Inventory: All permissions
    quickMARC: Derive new MARC bibliographic record
    quickMARC: View, edit MARC bibliographic record

  2. Go to "Inventory" app.

  3. Open any "Instance" record (with source = "MARC") in the third pane.

  4. Click on the "Actions">>"Derive new MARC bibliographic record".

  5. Click on the "Save & close" button.

Expected Results: The new "Instance" record with source "MARC" successfully saved.
Actual Results:
1) from UI side: the error toast notification is being displayed with the following message: "Record not saved: Communication problem with server. Please try again."
2) from Back-end side: the POST request if failed with the following error: "HTTP 500 Internal Server Error. If the issue persists, please report it to EBSCO Connect."
Additional Information: See attached screenshots.
See logs in the attachments.
Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

TestRail: Results

Activity

Show:

Kateryna Senchenko March 6, 2023 at 2:45 PM

Hi , I linked a spike to work out a solution to allow the R/W split of the DB. Thank you

Martin Tran January 20, 2023 at 10:45 PM

I don't think it's a data synchronization issue because if it was so, other Data Import workflows that are processed via mod-data-import or even other workflows like Check in Check out would have been affected by the synchronization.  I'd recommend creating another story to debug this issue deep in the code all the way down to RMB to see what is wrong. I'm willing to work with Folijet to troubleshoot this problem.

Kateryna Senchenko November 28, 2022 at 4:28 PM

Hi , no bugfix is needed. I added a release not for Nolana https://folio-org.atlassian.net/wiki/display/REL/Nolana+%28R3+2022%29+Release+Notes. Thank you!

Ann-Marie Breaux November 28, 2022 at 7:46 AM

- do we need a bugfix, or is this just a setting that needs to be updated in Nolana SRM? If just a setting, then please make sure there is a note in Nolana release notes, so that the proper thing is done during upgrade from MG to Nolana. We can talk about it or look at it together later this week if necessary.

Roman Chernetskyi November 25, 2022 at 2:51 PM

Reason for the bug is a new feature about adding read-only DB, sometimes read-only instance do not synchronise with the default one, so we decided to turn off this feature for srm

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Folijet

Parent

Release

Nolana (R3 2022)

RCA Group

Not a bug

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created November 16, 2022 at 11:45 AM
Updated May 22, 2024 at 11:53 AM
Resolved November 28, 2022 at 7:46 AM
TestRail: Cases
TestRail: Runs