Sessions on Synology NAS error on import
I have been pulling my hair out for days... And I have no hair :)
I have a Synology NAS DS923+ where I have stored all of my images. However, I am trying to do some reorganization of some images but am having some issues:
- I have no problem creating Catalogs and importing images. However, when I create a Session I can not import images or if I open an existing catalog or session I can not export originals to a folder on the NAS. I am the only user of the NAS. Both locally and remotely via SMB.
I can create the session just fine. However, after import I select 1 image and import.
I then get the error:
Description: Could not copy file to import destination. File was not imported.
File: /Volumes/Photography/PhotoWork/CaptureOneFiles/2013/110453.iiq
Reason: Unknown reason.
Domain: com.captureone.appcoreshared.import
Code: -1002
Any suggestions? Anyone using Synology and CaptureOne? I have been in contact with Capture One support and have done everything they suggested including deleting all of the app and reinstalling. No luck.
-
Hi Rob,
My client is experiencing exactly the same issue on 923+ running DMS 7.2.2.
Oddly enough, the error goes away if I enable AFP support (should be depreciated), it works.
The file can be read/written inside MacOS just fine so I think Capture One is somehow the culprit.
What SMB version do you have enabled on the 923+? I believe SMBv2 should be min. and v3 max.
Filip
0 -
I do have SMB set to 3 and 2 only..
0 -
Hi Rob,
You are certainly not the only one experiencing this; I have this same error and there have been posts here (e.g. Brian Creek. Post title: "Just with the most recent release I can't write to my NAS from C1, rest of my mac is not effected") about it previously. It is a royal pain. The following are work-arounds:
a) Using C1 Import and copy images to a folder that is NOT located on the NAS and then USING C1 drag/drop those images into the desired folder on the NAS.
b) Using macOS copy the images into the desired NAS folder and then using the C1 Import capability, import them choosing to leave them in their existing location.
c) As Filip suggests - use AFP instead. However, my experience is that read/write transfer speeds are a little slower than with SMB. I've also experienced several occasions where AFP mapped NAS shares (macOS 14) appear to stop responding - SMB works just fine.
I have a strong technical background having worked in IT and have spend considerable time trying to understand the root cause. I've tried SMB V1, V2, V2 with large frames and V3; I've tried enabling/disabling Transport encryption, Server signing and many of the other options available on a Synology DSM NAS. Nothing seems to work. I've also inspected firewall rules carefully to check packets are not being blocked. The legacy Unix NFS (Network File System) option also works and is an alternative to AFP, but like AFP its not as performant as SMB.
I find it interesting that when using SMB, C1 imports successfully from a flash memory card, copying files to a location on the NAS and that C1 can move files to and between folders on the NAS, delete them and even rename them indicating C1 has access permissions.
As part of my investigation I confirmed that the issue occurred with at least C1 16.2.6.7 and 16.5.1 plus also with Synology DSM 7.2.2-72806 Update 2 and Update 1.
There is something you should check tho:
- System Settings | Privacy & Security | Files & Folders | Capture One - Has permission to access Network Volumes and Removable Volumes. You may also see several other permissions such as Desktop Folder and Documents Folder - my suggestion is to enable them all. If you only see 'Full disk access' then you have granted full access using System Settings | Privacy & Security | Full Disk Access.
It 'feels' like C1 is doing something 'special' when copying files as part of an import which is triggering an interoperability issue with Synology DSM. (I've only seen this issue reported with macOS and Synology NAS units but it may occur with others too).
So, I've no solution for you I'm afraid - just welcome to the club!
Andy
0 -
Andy/all,
I also think this is somehow affected by C1 and not file/folder permissions at OS level.
I can mount the Synology network share with SMB protocol and I can read/write to files on the network share. I make sure the account that is mounting the share has read/write permissions as well.
Simple logic tells me that somehow C1 is missing permissions to read files from the share even that the app has full read/write access to the disk as set in MacOS disk permissions.
I don't want to use AFP protocol since it is depreciated by Apple and it is slower. Oddly it works though even though we have seen some issues as well.
There is not firewall in between the client and the NAS share.
The saga continues...
Filip
0
Post is closed for comments.
Comments
4 comments