Bad Escape

59 views
Skip to first unread message

Richard Urban

unread,
May 9, 2022, 10:29:58 AM5/9/22
to droid-list
Hi all,

I have a DROID profile created on a Windows 2012 server that fails on export on the. server.  I pulled it over to my local Mac and the latest version, which opens properly and allows me to explore the profiled files.  However, when I try to export, I get a "java.lang.illegalArgumentException: Bad Escape."

I haven't found an explicit reference that this is a DROID-specific error. Any other suggestions for troubleshooting?  

Thanks,
Richard J. Urban, MLIS, PhD
Digital Asset Manager & Strategist | Rakow Research Library
Corning Museum of Glass

Matt Palmer

unread,
May 10, 2022, 3:50:03 AM5/10/22
to droid-list
Hi,

From a Github search, there's no string matching "Bad Escape" in the droid code base.


This is probably the result of a URL encoding/decoding issue.  DROID does encode file paths as URLs, so it can point to files nested inside archive files.   I suspect that some filename on the system has something in it that's causing the URL encoding/decoding to break for some reason, although I don't know that for sure.

Do you have logs of the actual error - this would provide some context for where the problem is occurring.  Note - I'm not part of the National Archives, just someone who has worked on DROID for many years.

Regards,

Matt.

Richard Urban

unread,
May 11, 2022, 8:59:21 AM5/11/22
to droid-list
Thanks Matt,

I seem to have gotten around this by filtering to only include specific MIME types that I'm concerned with.  Now onto the next problem...the export csv seems to consistently tap out at 100K...

Richard

kathryn phelps

unread,
May 19, 2022, 1:14:20 PM5/19/22
to droid-list
Hi , apologies for not getting back to you sooner. Is the problem still occurring? Please can you confirm The OS (Windows?) and whether you are using the gui version? It sounds like some sort of memory problem.  

Sincerely,

Kathryn (PRONOM team member).

Urban, Richard

unread,
May 20, 2022, 10:06:44 AM5/20/22
to droid...@googlegroups.com

Hi Kathryn,

 

I’m running this on a Windows 2012 R2 server, but I’m more of a Mac/Linux fella.  I had brought the completed .droid report over to OSX 12.0.1 (on a M1 chip).  I am profiling a drive with approx. 25Tb of files.

 

However, since writing in I may have figured out what was causing this.  I went back and threw a few other things at this and all the methods failed – from Karen’s Directory Printer to a simple DIR /B.  This drive is used for both digitization workflows and as a staging area for the backup of other media.  Some of the things that were added recently appear to exceed the allowable path length in Windows 2012.  There are deeply nested directories and some folders that have been used to leave notes/metadata about their content.

e.g.

 

My current workaround is to break this into smaller DROID profiles that circumvent the directories causing problems. I’ve been able to create profiles of everything else until I can talk to the stakeholders about the items that are causing problems.

 

At least…this is my working theory that’s allowed me to get unstuck.

 

Cheers,

Richard J. Urban, MLIS, PhD | Digital Asset Manager & Strategist | Digital Initiatives Department | Rakow Research Library
The Corning Museum of Glass | 5  Museum Way | Corning, NY 14830
m: 607.368.4331|  e: urb...@cmog.orgcmog.org

Follow us: Facebook | Twitter | Instagram 
We inspire people to see glass in a new light.

Pronouns: he/him/his

--
You received this message because you are subscribed to a topic in the Google Groups "droid-list" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/droid-list/jL5mUaRQ0VQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to droid-list+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/droid-list/0457bd83-83f2-4657-9436-65601db1f6f2n%40googlegroups.com.

kathryn phelps

unread,
May 23, 2022, 6:41:22 AM5/23/22
to droid-list
Hi Richard, ahh yes, the headache of long filepaths in Windows. Very glad to hear you have found a workaround for now. We were able to change the limit on our WIndows machines, so they could handle long filepaths- I don't know if you've tried that?
Reply all
Reply to author
Forward
0 new messages