Error when importing ldif files

[Deeps]

Hi,

        I am trying to upgrade from dcm4chee-arc-light 5.21.0 to dcm4chee-arc-light 5.26.0. Getting error when trying to import 2 ldif files.

1) update-dev-5.24.0.ldif

Error while importing LDIF
 - [LDAP: error code 32 - NO_SUCH_OBJECT: failed for MessageType : MODIFY_REQUES
java.lang.Exception: [LDAP: error code 32 - NO_SUCH_OBJECT: failed for MessageType : MODIFY_REQUEST
Message ID : 226
    Modify Request
        Object : 'dcmuiPermissionName=Action - Studies - Patient,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org'
            Modification[0]
                Operation :  add
                Modification
dcmuiActionParam: unmergeorg.apache.directory.api.ldap.model.message.ModifyRequestImpl@78fa4949: Attempt to lookup non-existant entry: dcmuiPermissionName=Action - Studies - Patient,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org]
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkResponse(DirectoryApiConnectionWrapper.java:1418)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$11(DirectoryApiConnectionWrapper.java:1386)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$4.run(DirectoryApiConnectionWrapper.java:787)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1312)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkConnectionAndRunAndMonitor(DirectoryApiConnectionWrapper.java:1256)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.modifyEntry(DirectoryApiConnectionWrapper.java:809)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdifRecord(ImportLdifRunnable.java:515)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdif(ImportLdifRunnable.java:272)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.run(ImportLdifRunnable.java:218)
at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:109)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)

[LDAP: error code 32 - NO_SUCH_OBJECT: failed for MessageType : MODIFY_REQUEST
Message ID : 226
    Modify Request
        Object : 'dcmuiPermissionName=Action - Studies - Patient,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org'
            Modification[0]
                Operation :  add
                Modification
dcmuiActionParam: unmergeorg.apache.directory.api.ldap.model.message.ModifyRequestImpl@78fa4949: Attempt to lookup non-existant entry: dcmuiPermissionName=Action - Studies - Patient,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org]


2)update-config-pro-5.25.0.ldif

Error while importing LDIF
 - [LDAP: error code 16 - NO_SUCH_ATTRIBUTE: failed for MessageType : ADD_REQUES
java.lang.Exception: [LDAP: error code 16 - NO_SUCH_ATTRIBUTE: failed for MessageType : ADD_REQUEST
Message ID : 249
    Add Request :
Entry
    dn[n]: dcmuiTemplateName=MWL cd upload,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmuiCreateDialogTemplate
    dcmTag: 00400020
    dcmTag: 00400001
    dcmTag: 00400002
    dcmTag: 00400003
    dcmTag: 00400009
    dcmTag: 00400008
    dcmTag: 00080050
    dcmTag: 00401001
    dcmTag: 0020000D
    dcmuiDialog: mwl
    dcmuiTemplateName: MWL cd upload
    dcmuiTemplateDescription: MWL cd upload template
: ERR_04269 ATTRIBUTE_TYPE for OID dcmuitemplatedescription does not exist!]
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkResponse(DirectoryApiConnectionWrapper.java:1418)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$11(DirectoryApiConnectionWrapper.java:1386)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$6.run(DirectoryApiConnectionWrapper.java:1009)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1312)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkConnectionAndRunAndMonitor(DirectoryApiConnectionWrapper.java:1256)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.createEntry(DirectoryApiConnectionWrapper.java:1031)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdifRecord(ImportLdifRunnable.java:465)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdif(ImportLdifRunnable.java:272)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.run(ImportLdifRunnable.java:218)
at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:109)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)

[LDAP: error code 16 - NO_SUCH_ATTRIBUTE: failed for MessageType : ADD_REQUEST
Message ID : 249
    Add Request :
Entry
    dn[n]: dcmuiTemplateName=MWL cd upload,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmuiCreateDialogTemplate
    dcmTag: 00400020
    dcmTag: 00400001
    dcmTag: 00400002
    dcmTag: 00400003
    dcmTag: 00400009
    dcmTag: 00400008
    dcmTag: 00080050
    dcmTag: 00401001
    dcmTag: 0020000D
    dcmuiDialog: mwl
    dcmuiTemplateName: MWL cd upload
    dcmuiTemplateDescription: MWL cd upload template
: ERR_04269 ATTRIBUTE_TYPE for OID dcmuitemplatedescription does not exist!]

After configuration I tried to access dcm4chee-arc/ui2 (screenshot attached) and I am getting Internal server error. Is it because of update-dev-5.24.0.ldif and which configuration I am actually missing? How can I fix this issue?

Thanks & Regards,

Deeps.

[Vrinda Nayak]

Regarding

1) update-dev-5.24.0.ldif

dcmuiActionParam: unmergeorg.apache.directory.api.ldap.model.message.ModifyRequestImpl@78fa4949: Attempt to lookup non-existant entry: dcmuiPermissionName=Action - Studies - Patient,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org]

Seems you do not have default UI config in your setup. See point 2 in Import default configuration into LDAP Server. Import it before you run this update script.

2)update-config-pro-5.25.0.ldif

You may ignore importing this file as it is not part of open source. It got added in 5.25.0 versioned folder by accident.

In general, I have now added a link to upgrade older releases in the main Upgrade wiki page for convenience.

[Deeps]

Hi,

     I am trying to upgrade from dcm4chee-arc-light 5.21.0 to dcm4chee-arc-light 5.30.0. Faced few issues while importing the ldif files for different versions. 

1) As suggested by Vrinda, for fixing the issue while importing  update-dev-5.24.0.ldif, I deleted  dcmuiConfigName=default under dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org using Apache Directory Studio. Then imported the default-ui-config.ldif of 5.24.0 version. Since I am uploading the default-ui-config.ldif of 5.24.0 version, I deleted 2 segments from update-dev-5.24.0.ldif. The segments are:

>> dn: dcmuiPermissionName=Action - Studies - Patient,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
changetype: modify
add: dcmuiActionParam
dcmuiActionParam: unmerge

>>dn: dcmuiPermissionName=Tab - Study - Series,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
changetype: add
dcmuiPermissionName: Tab - Study - Series
dcmuiActionParam: accessible
dcmuiActionParam: visible
objectClass: dcmuiPermission
dcmAcceptedUserRole: admin
dcmAcceptedUserRole: user
dcmuiAction: tab-study-series

Is this the correct way to fix this issue?

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

2) Got issue when trying to execute update-ui-config.ldif which was under ldap/5.30.0.

Error while importing LDIF
 -  [LDAP result code 68 - entryAlreadyExists] ENTRY_ALREADY_EXISTS: failed for MessageType : ADD_REQUEST
org.apache.directory.studio.connection.core.io.StudioLdapException:  [LDAP result code 68 - entryAlreadyExists] ENTRY_ALREADY_EXISTS: failed for MessageType : ADD_REQUEST
Message ID : 40
    Add Request :
Entry
    dn[n]: dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmuiConfig
    dcmuiPersonNameFormat: {NAME-PREFIX} {GIVEN-NAME} {MIDDLE-NAME} {FAMILY-NAME} {NAME-SUFFIX}
: ERR_250_ENTRY_ALREADY_EXISTS dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org already exists!
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.toStudioLdapException(DirectoryApiConnectionWrapper.java:1350)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$2(DirectoryApiConnectionWrapper.java:1342)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$6.run(DirectoryApiConnectionWrapper.java:912)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1261)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkConnectionAndRunAndMonitor(DirectoryApiConnectionWrapper.java:1209)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.createEntry(DirectoryApiConnectionWrapper.java:924)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdifRecord(ImportLdifRunnable.java:445)

at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdif(ImportLdifRunnable.java:272)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.run(ImportLdifRunnable.java:218)
at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:109)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: org.apache.directory.api.ldap.model.exception.LdapEntryAlreadyExistsException: ENTRY_ALREADY_EXISTS: failed for MessageType : ADD_REQUEST
Message ID : 40
    Add Request :
Entry
    dn[n]: dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmuiConfig
    dcmuiPersonNameFormat: {NAME-PREFIX} {GIVEN-NAME} {MIDDLE-NAME} {FAMILY-NAME} {NAME-SUFFIX}
: ERR_250_ENTRY_ALREADY_EXISTS dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org already exists!
at org.apache.directory.api.ldap.model.message.ResultCodeEnum.processResponse(ResultCodeEnum.java:2045)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkResponse(DirectoryApiConnectionWrapper.java:1337)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$6(DirectoryApiConnectionWrapper.java:1333)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$6.run(DirectoryApiConnectionWrapper.java:908)
... 8 more

>>  The entry objectClass: dcmuiConfig was already existing under dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org

So modified the ldif file as:

version: 1

dn: dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
changetype: modify
add: dcmuiPersonNameFormat
dcmuiPersonNameFormat: {NAME-PREFIX} {GIVEN-NAME} {MIDDLE-NAME} {FAMILY-NAME} {NAME-SUFFIX}

Is it okay to add just dcmuiPersonNameFormat?

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

3) In the upgrading document, no details were given about executing the default-users.ldif of 5.30.0. Since there are additions in the users,  deleted ou=users and ou=realm-management  under dc=dcm4che,dc=org and executed default-users.ldif of 5.30.0 version.

Is there any other specific ldif file to be imported while upgrading other than given in the specific folders from ldap/5.22.0 to ldap/5.30.0?

[Vrinda Nayak]

Point 2 : Thanks for reporting, fixed in https://github.com/dcm4che/dcm4chee-arc-light/issues/4337

Point 3 : See https://github.com/dcm4che/dcm4chee-arc-light/wiki/Upgrade-on-Docker#update-ldap-configuration

As for point 1, I do not see the related reference, nor do I understand what exactly the issue is.

[Deeps]

Thank you for the response Vrinda.

Initially I tried to upgrade from dcm4chee-arc-light 5.21.0 to dcm4chee-arc-light 5.26.0. Then I got error on importing:

For this issue you gave the solution as:

Regarding

1) update-dev-5.24.0.ldif

dcmuiActionParam: unmergeorg.apache.directory.api.ldap.model.message.ModifyRequestImpl@78fa4949: Attempt to lookup non-existant entry: dcmuiPermissionName=Action - Studies - Patient,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org]

Seems you do not have default UI config in your setup. See point 2 in Import default configuration into LDAP Server. Import it before you run this update script.

=======================================================================================

In the upgrading document it is mentioned that: There are no update ldif scripts for 5.24.2. However, if UI configuration has been previously imported in archive's installation and archive is being upgraded from any version older than or equal to 5.23.3 to a newer version, then delete the UI configuration and import it again. It is a workaround for missing / incomplete update scripts concerning UI related config

So I deleted the default ui configuration and imported the default-ui-config.ldif of 5.24.0 version and then imported the upgrade scripts on top of that.

Since these below given scripts are related to the UI configuration, I deleted these from the update-dev-5.24.0.ldif (as we have already imported the  default-ui-config.ldif of 5.24.0)

>> dn: dcmuiPermissionName=Action - Studies - Patient,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
changetype: modify
add: dcmuiActionParam
dcmuiActionParam: unmerge

>>dn: dcmuiPermissionName=Tab - Study - Series,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
changetype: add
dcmuiPermissionName: Tab - Study - Series
dcmuiActionParam: accessible
dcmuiActionParam: visible
objectClass: dcmuiPermission
dcmAcceptedUserRole: admin
dcmAcceptedUserRole: user
dcmuiAction: tab-study-series

Is this the correct way of importing default-ui-config.ldif or do we need to import the default-ui-config.ldif of 5.30.0 version as we are upgrading to 5.30 now. If we are importing the default-ui-config.ldif of 5.30, whether the upgrade scripts of previous versions will give errors?

Thanks in advance.

Regards,

Deeps.

[Vrinda Nayak]

> Is this the correct way of importing default-ui-config.ldif or do we need to import the default-ui-config.ldif of 5.30.0 version as we are upgrading to 5.30 now. 

If you're on 5.30.0 and do not have UI config imported, just newly import it in your configuration. 

> If we are importing the default-ui-config.ldif of 5.30, whether the upgrade scripts of previous versions will give errors?

No - archive server side specific update scripts are independent of UI configs

[Deeps]

Thank you Vrinda. I will try this out.

[Deeps]

Hi Vrinda,

          I tried out importing the default-ui-config.ldif of 5.30.0 version. After deleting the schema entries:

dcm4chee-archive-ui
dcm4chee-archive
dcm4che
Imported these 3 ldif files and then deleted the dcmuiConfigName=default and then imported default-ui-config.ldif of 5.30.0 and then continued importing the upgrade scripts on the basis of versions. Then I got error on importing update-dev-5.23.1.ldif:

  -  [LDAP result code 32 - noSuchObject] NO_SUCH_OBJECT: failed for MessageType : MODIFY_REQUEST
org.apache.directory.studio.connection.core.io.StudioLdapException:  [LDAP result code 32 - noSuchObject] NO_SUCH_OBJECT: failed for MessageType : MODIFY_REQUEST
Message ID : 123
    Modify Request
        Object : 'dcmuiPermissionName=Action - Studies - Reject Instance,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org'
            Modification[0]
                Operation :  replace
                Modification
dcmuiAction: action-studies-instanceorg.apache.directory.api.ldap.model.message.ModifyRequestImpl@743b8189: Attempt to lookup non-existant entry: dcmuiPermissionName=Action - Studies - Reject Instance,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org

at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.toStudioLdapException(DirectoryApiConnectionWrapper.java:1350)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$2(DirectoryApiConnectionWrapper.java:1342)

at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$4.run(DirectoryApiConnectionWrapper.java:754)

at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1261)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkConnectionAndRunAndMonitor(DirectoryApiConnectionWrapper.java:1209)

at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.modifyEntry(DirectoryApiConnectionWrapper.java:766)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdifRecord(ImportLdifRunnable.java:503)

at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdif(ImportLdifRunnable.java:272)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.run(ImportLdifRunnable.java:218)
at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:109)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Caused by: org.apache.directory.api.ldap.model.exception.LdapNoSuchObjectException: NO_SUCH_OBJECT: failed for MessageType : MODIFY_REQUEST
Message ID : 123
    Modify Request
        Object : 'dcmuiPermissionName=Action - Studies - Reject Instance,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org'
            Modification[0]
                Operation :  replace
                Modification
dcmuiAction: action-studies-instanceorg.apache.directory.api.ldap.model.message.ModifyRequestImpl@743b8189: Attempt to lookup non-existant entry: dcmuiPermissionName=Action - Studies - Reject Instance,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
at org.apache.directory.api.ldap.model.message.ResultCodeEnum.processResponse(ResultCodeEnum.java:2024)

at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkResponse(DirectoryApiConnectionWrapper.java:1337)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$6(DirectoryApiConnectionWrapper.java:1333)

at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$4.run(DirectoryApiConnectionWrapper.java:750)
... 8 more

 [LDAP result code 32 - noSuchObject] NO_SUCH_OBJECT: failed for MessageType : MODIFY_REQUEST
Message ID : 123
    Modify Request
        Object : 'dcmuiPermissionName=Action - Studies - Reject Instance,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org'
            Modification[0]
                Operation :  replace
                Modification
dcmuiAction: action-studies-instanceorg.apache.directory.api.ldap.model.message.ModifyRequestImpl@743b8189: Attempt to lookup non-existant entry: dcmuiPermissionName=Action - Studies - Reject Instance,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org

====================================================================================================

Then I tried again and this time I deleted the following schema entries:

dcm4chee-archive-ui
dcm4chee-archive
dcm4che

Then imported these 3 ldif files. After this, imported upgrade scripts upto 5.23.3 version and then deleted the dcmuiConfigName=default and then imported default-ui-config.ldif of 5.30.0.After that continued importing scripts from 5.24.0 version. Then I got error on importing update-dev-5.24.1.ldif

Error while importing LDIF
 -  [LDAP result code 68 - entryAlreadyExists] ENTRY_ALREADY_EXISTS: failed for MessageType : ADD_REQUEST
org.apache.directory.studio.connection.core.io.StudioLdapException:  [LDAP result code 68 - entryAlreadyExists] ENTRY_ALREADY_EXISTS: failed for MessageType : ADD_REQUEST

Message ID : 57
    Add Request :
Entry
    dn[n]: dcmuiPermissionName=Action - Studies - Show Attributes,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmuiPermission
    dcmuiPermissionName: Action - Studies - Show Attributes
    dcmuiActionParam: visible
    dcmAcceptedUserRole: admin
    dcmAcceptedUserRole: user
    dcmuiAction: action-studies-show-attributes
: ERR_250_ENTRY_ALREADY_EXISTS dcmuiPermissionName=Action - Studies - Show Attributes,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org already exists!

at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.toStudioLdapException(DirectoryApiConnectionWrapper.java:1350)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$2(DirectoryApiConnectionWrapper.java:1342)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$6.run(DirectoryApiConnectionWrapper.java:912)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1261)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkConnectionAndRunAndMonitor(DirectoryApiConnectionWrapper.java:1209)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.createEntry(DirectoryApiConnectionWrapper.java:924)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdifRecord(ImportLdifRunnable.java:445)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdif(ImportLdifRunnable.java:272)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.run(ImportLdifRunnable.java:218)
at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:109)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: org.apache.directory.api.ldap.model.exception.LdapEntryAlreadyExistsException: ENTRY_ALREADY_EXISTS: failed for MessageType : ADD_REQUEST

Message ID : 57
    Add Request :
Entry
    dn[n]: dcmuiPermissionName=Action - Studies - Show Attributes,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmuiPermission
    dcmuiPermissionName: Action - Studies - Show Attributes
    dcmuiActionParam: visible
    dcmAcceptedUserRole: admin
    dcmAcceptedUserRole: user
    dcmuiAction: action-studies-show-attributes
: ERR_250_ENTRY_ALREADY_EXISTS dcmuiPermissionName=Action - Studies - Show Attributes,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org already exists!

at org.apache.directory.api.ldap.model.message.ResultCodeEnum.processResponse(ResultCodeEnum.java:2045)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkResponse(DirectoryApiConnectionWrapper.java:1337)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$6(DirectoryApiConnectionWrapper.java:1333)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$6.run(DirectoryApiConnectionWrapper.java:908)
... 8 more

 [LDAP result code 68 - entryAlreadyExists] ENTRY_ALREADY_EXISTS: failed for MessageType : ADD_REQUEST

Message ID : 57
    Add Request :
Entry
    dn[n]: dcmuiPermissionName=Action - Studies - Show Attributes,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmuiPermission
    dcmuiPermissionName: Action - Studies - Show Attributes
    dcmuiActionParam: visible
    dcmAcceptedUserRole: admin
    dcmAcceptedUserRole: user
    dcmuiAction: action-studies-show-attributes
: ERR_250_ENTRY_ALREADY_EXISTS dcmuiPermissionName=Action - Studies - Show Attributes,dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org already exists!

=============================================================================

Since we have imported the UI configuration of latest version, the updations in the scripts are already present in our system, right? How to solve this?

Do we need to delete the configurations for dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org in the upgrade scripts?

One more thing I wanted to ask is that in our previous version ie, 5.21 (in LDAP) under DN: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org

The attribute section contained one attribute dicomVendorData. Attaching screenshot for reference. This attribute is not present in the 5.30.0 version. Is this attribute required? How do we add this?

Thanks in advance.

Regards,

Deeps.

[Deeps]

Attaching the screenshot of dicomVendorData attribute.

[Deeps]

Hi Vrinda,

                 I tried executing the updated dcm4chee-arc-assembly/src/main/resources/ldap/5.30.0/update-ui-config.ldif

https://github.com/dcm4che/dcm4chee-arc-light/issues/4337

version: 1

dn: dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org

changetype: add
objectClass: dcmuiConfig
changetype: modify
add: dcmuiPersonNameFormat dcmuiPersonNameFormat: {NAME-PREFIX} {GIVEN-NAME} {MIDDLE-NAME} {FAMILY-NAME} {NAME-SUFFIX}

On executing this updated ldif file, I got error:

Error while importing LDIF
 -  [LDAP result code 16 - noSuchAttribute] NO_SUCH_ATTRIBUTE: failed for MessageType : ADD_REQUEST
org.apache.directory.studio.connection.core.io.StudioLdapException:  [LDAP result code 16 - noSuchAttribute] NO_SUCH_ATTRIBUTE: failed for MessageType : ADD_REQUEST
Message ID : 332

    Add Request :
Entry
    dn[n]: dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmuiConfig

    add: dcmuiPersonNameFormat
    dcmuiPersonNameFormat: {NAME-PREFIX} {GIVEN-NAME} {MIDDLE-NAME} {FAMILY-NAME} {NAME-SUFFIX}

    changetype: modify
: ERR_04269 ATTRIBUTE_TYPE for OID add does not exist!

at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.toStudioLdapException(DirectoryApiConnectionWrapper.java:1350)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$2(DirectoryApiConnectionWrapper.java:1342)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$6.run(DirectoryApiConnectionWrapper.java:912)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1261)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkConnectionAndRunAndMonitor(DirectoryApiConnectionWrapper.java:1209)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.createEntry(DirectoryApiConnectionWrapper.java:924)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdifRecord(ImportLdifRunnable.java:445)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdif(ImportLdifRunnable.java:272)
at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.run(ImportLdifRunnable.java:218)
at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:109)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Caused by: org.apache.directory.api.ldap.model.exception.LdapNoSuchAttributeException: NO_SUCH_ATTRIBUTE: failed for MessageType : ADD_REQUEST
Message ID : 332

    Add Request :
Entry
    dn[n]: dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmuiConfig

    add: dcmuiPersonNameFormat
    dcmuiPersonNameFormat: {NAME-PREFIX} {GIVEN-NAME} {MIDDLE-NAME} {FAMILY-NAME} {NAME-SUFFIX}

    changetype: modify
: ERR_04269 ATTRIBUTE_TYPE for OID add does not exist!
at org.apache.directory.api.ldap.model.message.ResultCodeEnum.processResponse(ResultCodeEnum.java:2031)

at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkResponse(DirectoryApiConnectionWrapper.java:1337)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$6(DirectoryApiConnectionWrapper.java:1333)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$6.run(DirectoryApiConnectionWrapper.java:908)
... 8 more

 [LDAP result code 16 - noSuchAttribute] NO_SUCH_ATTRIBUTE: failed for MessageType : ADD_REQUEST
Message ID : 332

    Add Request :
Entry
    dn[n]: dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmuiConfig

    add: dcmuiPersonNameFormat
    dcmuiPersonNameFormat: {NAME-PREFIX} {GIVEN-NAME} {MIDDLE-NAME} {FAMILY-NAME} {NAME-SUFFIX}

    changetype: modify
: ERR_04269 ATTRIBUTE_TYPE for OID add does not exist!

Thanks in advance.

Regards,

Deeps.

[Vrinda Nayak]

Check  if you have updated the schema for dcm4chee-archive-ui - https://github.com/dcm4che/dcm4chee-arc-light/wiki/Upgrade#update-ldap-schema

If you've never updated the vendor data and were using default and its missing now, just refer https://github.com/dcm4che/dcm4chee-arc-light/wiki/Installation#import-default-configuration-into-ldap-server and add https://github.com/dcm4che/dcm4chee-arc-light/blob/master/dcm4chee-arc-assembly/src/main/resources/ldap/add-vendor-data.ldif

[Deeps]

Thank you for the response Vrinda.

Yes, I have imported dcm4chee-archive-ui.ldif,  dcm4chee-archive.ldif  and dcm4che.ldif of 5.30 after deleting the existing 3 schemas.

 I have added the vendor data in 5.21 version and ran the upgrading steps till 5.30. Do I need to import $DCM4CHEE_ARC/ldap/add-vendor-data.ldif of 5.30 along with the upgrading scripts?

Regards,

Deeps.

[Vrinda Nayak]

No, if you already have it.

[Deeps Kiren]

Okay Vrinda, Thank you.

Regards,

Deeps.

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/2f725020-ebe9-4578-801e-978c613fab01n%40googlegroups.com.

[Vrinda Nayak]

I missed mentioning to refer last point in https://github.com/dcm4che/dcm4chee-arc-light/wiki/Upgrade#update-ldap-data

We do not have a direct "update ldif" script for updating the vendor data for the archive stylesheets that get changed between the versions. However you can update the vendor data directly using archive UI.

[Deeps Kiren]

Okay Vrinda.

Regards,

Deeps.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/d7c19fed-e2e4-4dc6-abee-3f163c2e573dn%40googlegroups.com.

[Deeps]

Hi Vrinda,

Can I edit the update-ui-config.ldif as given below?

version: 1

dn: dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org

changetype: modify
add: dcmuiPersonNameFormat
dcmuiPersonNameFormat: {NAME-PREFIX} {GIVEN-NAME} {MIDDLE-NAME} {FAMILY-NAME} {NAME-SUFFIX}

I am getting error on importing this ldif as updated in https://github.com/dcm4che/dcm4chee-arc-light/issues/4337

Error while importing LDIF
 -  [LDAP result code 16 - noSuchAttribute] NO_SUCH_ATTRIBUTE: failed for MessageType : ADD_REQUEST
org.apache.directory.studio.connection.core.io.StudioLdapException:  [LDAP result code 16 - noSuchAttribute] NO_SUCH_ATTRIBUTE: failed for MessageType : ADD_REQUEST
Message ID : 332

    Add Request :
Entry
    dn[n]: dcmuiConfigName=default,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
    objectClass: dcmuiConfig

    add: dcmuiPersonNameFormat
    dcmuiPersonNameFormat: {NAME-PREFIX} {GIVEN-NAME} {MIDDLE-NAME} {FAMILY-NAME} {NAME-SUFFIX}

    changetype: modify
: ERR_04269 ATTRIBUTE_TYPE for OID add does not exist!

Regards,

Deeps.

[Vrinda Nayak]

Seems your dcm4chee-archive-ui.schema did not get updated correctly. If you have Apache Directory Studio, check this schema using Schema Editor and delete / import again which would be easier and faster.

[Deeps]

Thank you Vrinda. I will try this.

[Deeps]

Hi Vrinda,

               I tried to check the schema using the schema editor. But couldn't view the imported schemas in schema editor (dcm4che, dcm4chee-archive, dcm4chee-archive-ui and dicom). Deleted and imported these schemas again. But still not able to view these in schema editor. Only default schemas are visible.

Attaching the screenshot.

Thanks in advance.

Regards,

Deeps.