Dicom horos viewer does not save in the dcm4chee pacs.

[pepe....@gmail.com]

Hello.

I have used dcm4chee-arc-psql:5.34.0-secure

I send from the machine "de803" with horos to the machine "pacs" with dcm4chee.

Log wildfly:

------------------

2025-07-22 02:10:33,877 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/100.121.80.93,port=58464,localport=11112]
2025-07-22 02:10:33,915 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-5) DCM4CHEE<-de803(1) >> A-ASSOCIATE-RQ
2025-07-22 02:10:33,934 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-5) DCM4CHEE<-de803(1) << A-ASSOCIATE-AC
2025-07-22 02:10:34,095 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-5) DCM4CHEE<-de803(1) >> 1:C-STORE-RQ[pcid=213, prior=2
  cuid=1.2.840.10008.5.1.4.1.1.6.1 - Ultrasound Image Storage
  iuid=1.3.76.2.3.3.474985436.19378.3.3.1.20250616175347286 - ?
  tsuid=1.2.840.10008.1.2.1 - Explicit VR Little Endian]
2025-07-22 02:10:40,245 INFO  [org.dcm4chee.arc.coerce.impl.MergeAttributesCoercionProcessor] (EE-ManagedExecutorService-default-Thread-5) Merge Attributes using ArchiveAttributeCoercion2[cn=SupplementIssuerOfPatientID, priority=0, DIMSE=C_STORE_RQ, role=SCU, cuids=[], conditions={IssuerOfPatientID!=.+}, uri=merge-attrs:, description=null, onFailure=RETHROW, sufficient=false, attributeUpdatePolicy=MERGE, mergeAttributes=[IssuerOfPatientID=DCM4CHEE.{PatientName,hash}.{PatientBirthDate,hash}], deviceCoercionParam=null, otherCoercionParams={}]
2025-07-22 02:10:40,387 WARN  [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EE-ManagedExecutorService-default-Thread-5) SQL Error: 0, SQLState: 42703
2025-07-22 02:10:40,388 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EE-ManagedExecutorService-default-Thread-5) ERROR: column s1_0.metadata_update_load_objects does not exist
  Position: 550
2025-07-22 02:10:40,425 ERROR [org.jboss.as.ejb3.invocation] (EE-ManagedExecutorService-default-Thread-5) WFLYEJB0034: Jakarta Enterprise Beans Invocation failed on component StoreServiceEJB for method public org.dcm4chee.arc.store.impl.UpdateDBResult org.dcm4chee.arc.store.impl.StoreServiceEJB.updateDB(org.dcm4chee.arc.store.StoreContext,org.dcm4chee.arc.store.impl.UpdateDBResult) throws org.dcm4che3.net.service.DicomServiceException: jakarta.ejb.EJBException: org.hibernate.exception.SQLGrammarException: JDBC exception executing SQL [select s1_0.pk,s1_0.access_control_id,s1_0.dicomattrs_fk,ab3_0.pk,ab3_0.attrs,s1_0.body_part,s1_0.completeness,s1_0.compress_failures,s1_0.compress_params,s1_0.compress_time,s1_0.compress_tsuid,s1_0.created_time,s1_0.expiration_date,s1_0.expiration_exporter_id,s1_0.expiration_state,s1_0.ext_retrieve_aet,s1_0.failed_retrieves,s1_0.stgver_failures,s1_0.inst_purge_state,s1_0.inst_purge_time,s1_0.inst_code_fk,s1_0.institution,s1_0.department,s1_0.dept_code_fk,s1_0.laterality,s1_0.metadata_fk,s1_0.metadata_update_time,s1_0.metadata_update_failures,s1_0.metadata_update_load_objects,s1_0.modality,s1_0.modified_time,s1_0.pps_cuid,s1_0.pps_iuid,s1_0.pps_start_date,s1_0.pps_start_time,ppn1_0.pk,ppn1_0.alphabetic_name,ppn1_0.ideographic_name,ppn1_0.phonetic_name,s1_0.receiving_aet,s1_0.receiving_hl7_app,s1_0.receiving_hl7_facility,s1_0.receiving_pres_addr,s1_0.rejection_state,s1_0.sending_aet,s1_0.sending_hl7_app,s1_0.sending_hl7_facility,s1_0.sending_pres_addr,s1_0.series_custom1,s1_0.series_custom2,s1_0.series_custom3,s1_0.series_desc,s1_0.series_iuid,s1_0.series_no,s1_0.series_size,s1_0.sop_cuid,s1_0.station_name,s1_0.stgver_time,s1_0.study_fk,s2_0.pk,s2_0.access_control_id,s2_0.access_time,s2_0.accession_no,s2_0.accno_entity_id,s2_0.accno_entity_uid,s2_0.accno_entity_uid_type,s2_0.admission_id,s2_0.admid_entity_id,s2_0.admid_entity_uid,s2_0.admid_entity_uid_type,s2_0.dicomattrs_fk,ab2_0.pk,ab2_0.attrs,s2_0.completeness,s2_0.created_time,s2_0.study_deleting,s2_0.expiration_date,s2_0.expiration_exporter_id,s2_0.expiration_state,s2_0.ext_retrieve_aet,s2_0.failed_retrieves,s2_0.modified_time,s2_0.patient_fk,p1_0.pk,p1_0.dicomattrs_fk,ab1_0.pk,ab1_0.attrs,p1_0.created_time,p1_0.failed_verifications,p1_0.merge_fk,p1_0.num_studies,p1_0.pat_birthdate,p1_0.pat_custom1,p1_0.pat_custom2,p1_0.pat_custom3,pn1_0.pk,pn1_0.alphabetic_name,pn1_0.ideographic_name,pn1_0.phonetic_name,p1_0.pat_sex,p1_0.resp_person_fk,p1_0.updated_time,p1_0.verification_status,p1_0.verification_time,p1_0.version,rpn1_0.pk,rpn1_0.alphabetic_name,rpn1_0.ideographic_name,rpn1_0.phonetic_name,s2_0.rejection_state,s2_0.study_size,s2_0.storage_ids,s2_0.study_custom1,s2_0.study_custom2,s2_0.study_custom3,s2_0.study_date,s2_0.study_desc,s2_0.study_id,s2_0.study_iuid,s2_0.study_time,s2_0.updated_time,s2_0.version,s1_0.tsuid,s1_0.updated_time,s1_0.version from series s1_0 join study s2_0 on s2_0.pk=s1_0.study_fk join patient p1_0 on p1_0.pk=s2_0.patient_fk left join person_name pn1_0 on pn1_0.pk=p1_0.pat_name_fk join dicomattrs ab1_0 on ab1_0.pk=p1_0.dicomattrs_fk left join person_name rpn1_0 on rpn1_0.pk=s2_0.ref_phys_name_fk join dicomattrs ab2_0 on ab2_0.pk=s2_0.dicomattrs_fk left join person_name ppn1_0 on ppn1_0.pk=s1_0.perf_phys_name_fk join dicomattrs ab3_0 on ab3_0.pk=s1_0.dicomattrs_fk where s2_0.study_iuid=? and s1_0.series_iuid=?] [ERROR: column s1_0.metadata_update_load_objects does not exist
  Position: 550] [n/a]
at org.jbos...@36.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:251)
at org.jbos...@36.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:373)

How do I fix it?
Thanks.

[pepe....@gmail.com]

I have done it with Docker

[Hubert Wozinski]

Hello,
I’ve encountered an issue with your database, specifically with the series table. Arc-light is unable to find the metadata_update_load_objects column. Could you please verify whether this column exists in your database schema?
According to the documentation, it was introduced in version 5.34 of arc-light.

Best regards,
HW

[pepe....@gmail.com]

Hello
Thanks for helping me.
The column doesn't exist.
What can I do?

[pepe....@gmail.com]

I've already fixed it.
I deleted the tables and recreated them.
Resource:
https://github.com/dcm4che-dockerfiles/postgres-dcm4chee/tree/master/sql