Panic error when running AttachmentAriver

[EWA]

 

I'm setting up Attachment Archiver but getting panic error  .

 

I tried changing the folder location then running the default setting just (just adding the instance and API) but still the same.

 

{
    "InstanceID": "xxxxx"
    , "APIKeys": [
        "xxxxxxxxxxxxxxx"
    ]
    , "AttachmentFolder": "C:/Temp/"
}

 

[SamS]

Hi @EWA,

I'll hopefully have time to look at the attachment archiver tomorrow - as there is another issue reported:

BUT you might want to try with the parameter: -call="SR00486747"

[EWA]

thanks, still doesn't work I'm afraid adding the ""

[SamS]

Hi @EWA,

I am not able to recreate your issue - i.e. does not see the command line options as a hurdle.

Could you please provide the contents of the .log file? It might suggest a networking/permissions issue.

[EWA]

2024/10/29 11:22:30 [DEBUG] ---- Hornbill Request Attachment Download and Removal Utility v1.2.1 ----
2024/10/29 11:22:30 [DEBUG] Flag - Config File conf.json
2024/10/29 11:22:30 [DEBUG] Flag - Dry Run false
2024/10/29 11:22:30 [DEBUG] Loading Config File: C:\Attachement Archiver/conf.json
2024/10/29 11:22:30 Checking API Keys
2024/10/29 11:22:30 Checking API Key : xxxxxxxxxxxxxxxxxxxxxxxxxxxx

 

It stops on the API key

I have created the API under my account and set up the rules below:

 

data:queryExec
data:entityAttachBrowse
data:entityAttachFile
data:entityAttachRemove
system:pingCheck
apps/com.hornbill.servicemanager/Requests:updateReqTimeline

[SamS]

Hi @EWA,

Where the utility is panic'ing is indeed the first place where a network connection is being made.

If you guys are using a proxy server, you will need to use HTTP_PROXY And HTTPS_PROXY environment settings.

Also, there is a new version out of the utility which I would recommend you use. It will not be solving this networking issue, but it will actually find downloads (v1.2.1 regrettably skipped that step).

[EWA]

I got it worked. can it only copy files onto a local driver?