Page 1 of 1
Error adding file to SQL transaction
Posted: Mon Aug 26, 2013 3:54 pm
by MatthewThorn
Hi, getting a rather non-descript error dialog when scanning files:
"Error adding file to SQL transaction: Illegal characters in path."
The folders I am scanning are smb shares mapped to windows drives, ie X:\ & Y:\
Unfortunately I have no further information available as to the paths in question.
Any ideas?
Regards
Matt
Re: Error adding file to SQL transaction
Posted: Mon Aug 26, 2013 8:22 pm
by DigitalVolcano
Can you try this:
In More Options->Scanning uncheck the 'Ignore extentions when comparing file names' option and see if this fixes it. This routine may be failing on your samba paths.
Re: Error adding file to SQL transaction
Posted: Fri Aug 30, 2013 7:46 am
by MatthewThorn
Thanks, this has stopped the message.
I wasn't comparing file-names in my search, so I cant see how it matters whether extensions are included or not when comparing files.
Also this was during the discovery phase, which I aborted given the number of errors I was getting rather than the comparison phase.
Re: Error adding file to SQL transaction
Posted: Fri Aug 30, 2013 11:09 am
by DigitalVolcano
It's failing when hitting some non-standard file names while creating the list of files. The routine has been fixed and will be in update version 3.2.1.
Thanks!
Re: Error adding file to SQL transaction
Posted: Tue Sep 03, 2013 9:05 am
by MatthewThorn
It's happening again, I'm pretty sure with ignore extensions unckecked, though far less often.
One pattern I have noticed, after accessing a folder including "$" (dollar symbol) within the path name I get the message. I presume this is an example of non-standard filenames?
Is there any way to open a second instance of DC, or any other way, so I can double-check that setting for you, while running a scan?
Re: Error adding file to SQL transaction
Posted: Tue Sep 03, 2013 10:38 am
by DigitalVolcano
I've tested with a $ symbol and it seems ok - a dollar is a legitimate system in Windows file paths. Have you got an example of a full path/filename that is causing trouble?
There will be a new release today - let's see if it fixes things. thanks!