Import instances from DCM4CHEE 2 to ARC failed with restful service

[Lucas Sousa]

I'm trying to import instances from my old archive using IMPORT-RS but I keep getting the same error: 

Response Internal Server Error caused by java.lang.IllegalArgumentException: Illegal character in path at index 0: DICMUL�OBUI1.2.840.10008.5.1.4.1.1.1UI81.2.392.200036.9125.9.0.2049141748.252201692.2201912959UI1.2.840.10008.1.2.4.70UI1.2.40.0.13.1.1.1SHdcm4che-1.4.3CS

Already try with several different dicom files from my company and no luck, I've made a simple bash script to import the files:

#!/bin/bash

source=/dicom/
curl_bin=/usr/local/bin/curl

for f in $(find $source-type f); do
        echo "File: $f"
        $curl_bin -X 'POST' \
        'http://192.168.0.84:8080/dcm4chee-arc/aets/mobilemed/rs/instances/storage/migrate' \
        -H 'Accept: application/dicom+xml' \
        -H 'Content-Type: text/*' \
        --data-binary @$f \
        --output -
done

I've also try running directly from the command line as stated in the article: Import Instances on Storage · dcm4che/dcm4chee-arc-light Wiki · GitHub, same error, I really don't know which character is causing the problem, I'm going to attach a sample file I'm trying to send.

[Vrinda Nayak]

What is the configuration of migrate Storage Descriptor?

[Lucas Sousa]

Hello, Vrinda

I'll attach the screenshots from the configuration of the storage descriptor.

[ty...@anzer.com]

Is there solution? I am trying to use article https://github.com/dcm4che/dcm4chee-arc-light/wiki/Import-Instances-on-Storage and getting similar error 

Illegal character in opaque part at index 2: C:\PACSHIST\FS1\HISTORY\2.DCM

where C:\PACSHIST\FS1\HISTORY\2.DCM is dicom file I am trying to create a reference in dcm4chee arc light.

I am using Windows server 2019,  dcm4chee-arc-5.20.0 with sql server

[Vrinda Nayak]

Used your storage descriptor config and sample DICOM file to match with configured pathFormat in dockerized archive setup and successfully imported the file. See attached zipped file with docker-compose / configuration and other settings and match it with yours, as I do not know if you've started archive using manual / dockerized setup.