Can not save, "The system cannot find the file specified"

[Tik-Tak]

Originally Posted by sjl501

Thanks for posting. I'll give this a try -- and will forward to Synology.

Did you manage to get it work with the instructions I provided? Any update from Synology?

[sjl501]

Unfortunately, I think the steps you've listed are over my head. I was not able to follow them all the way through (especially for fear of disrupting my work environment and causing downtime).

More importantly, if this is something Synology needs to fix, I felt it was important to submit it to them. When I first brought up the topic to them, I was connected with a VERY helpful tech who went above and beyond to understand the problem. This time I was not very lucky, and I got only standard troubleshooting responses--they said anything beyond that was an Avid problem. (And of course I never did get any help from Avid--not one single response.) I'm afraid it's one of those situations where both manufacturers are going to blame each other, and the problem isn't widespread enough for them to look into it any further.

Meanwhile, I have spent a few hundred dollars and a handful of hours to make my environment work for me, although it is less convenient now--more of a workaround than a real working solution. But I'm not sure what more I can do. If more people chime in on this thread, or start their own threads, maybe this issue will get more attention from Avid. What we really need is for senior engineers at both Avid and Synology to have a conversation about it, but I would be fooling myself if I thought I could make that happen...

[PatSab]

Hi All,

Our broadcasting company uses many Protools V12 system on PC (win7 64bits) and synology NAS.

From the DSM 6.23 update we noticed that only certain NAS no longer worked with Protools.
- DSM 6.2.3 with Marvell Armada processor - XP MV 78230 - DS214 +
- DSM 6.2.3 with Marvell Armada processor - 388 88F6828 - DS416J
- DSM 6.2.3 with ANAPURNALABS ALPINE AL212 processor - DS416
A downgrade to version 6.1.7 allowed reworking normally.

On the other hand, the NAS equipped with DSM 6.2.3 and INTEL CELERON N3160 processor - DS716 + did not have any problems.

We have blocked problematic updates while we wait for Synology to fix these bugs.

[sjl501]

Thanks PatSab.

I am running DSM 6.2.3-25426 Update 2, MARVELL Kirkwood 88F6282, DS212+

Have you been in contact with Synology, and believe that they are aware of the problem and working to fix it?

[Tik-Tak]

We use DS418 with Realtek RTD1296 processor and have the issue.

Originally Posted by PatSab

Hi All,

Our broadcasting company uses many Protools V12 system on PC (win7 64bits) and synology NAS.

From the DSM 6.23 update we noticed that only certain NAS no longer worked with Protools.
- DSM 6.2.3 with Marvell Armada processor - XP MV 78230 - DS214 +
- DSM 6.2.3 with Marvell Armada processor - 388 88F6828 - DS416J
- DSM 6.2.3 with ANAPURNALABS ALPINE AL212 processor - DS416
A downgrade to version 6.1.7 allowed reworking normally.

On the other hand, the NAS equipped with DSM 6.2.3 and INTEL CELERON N3160 processor - DS716 + did not have any problems.

We have blocked problematic updates while we wait for Synology to fix these bugs.

[PatSab]

Originally Posted by sjl501

Thanks PatSab.

I am running DSM 6.2.3-25426 Update 2, MARVELL Kirkwood 88F6282, DS212+

Have you been in contact with Synology, and believe that they are aware of the problem and working to fix it?

No, I am not in contact with Synology ... not too much time to deal with it.
I'm waiting for a major update to see if the problem persists ...

[Christopotamus]

I have a fix that works for me, but these forums are terrible and are not letting me reply with the actual details.


I created a script that changes some SMB config and the issue went away for me on DSM 6.2.3.


Here's a google doc with instructions:


https://docs.google.com/document/d/1...it?usp=sharing


I reached out to Synology and they're only interested in troubleshooting by jumping through hoops so I give up on working with them.

[Christopotamus]

All of this is explained in the google doc I linked above, but I figured a way around the forum's filtering of my post:


Go to the Task Scheduler on the NAS and create a Triggered Task -> User Defined Script with the following settings and contents:


Give the task any name you’d like, such as “Fix Pro Tools Saving”
User should be set to “root”
Event should be set to “Boot-up”
Enabled should be checked.


Click on the “Task Settings” tab and paste in the following script:


Note: Replace "FORBIDDEN_WORD" with "sh" - no quotes

#!/bin/FORBIDDEN_WORD


 # Stop Samba
/usr/syno/sbin/synoservicecfg --stop samba


 # Create the new conf file

 echo "vfs objects = fruit
fruit:aapl = yes
fruit:encoding = native
fruit:locking = none
fruit:metadata = stream
fruit:resource = file" >> /var/tmp/nginx/smb.netbios.aliases.conf


# Start Samba
/usr/syno/sbin/synoservicecfg --start samba

Save this task.


You may click the task and press the “Run” button in the DSM, or simply reboot the NAS. Once the task has been run or the NAS has finished rebooting, you should be able to save your protools sessions.


If this doesn’t work for you I’d be happy to help troubleshoot further.

[prosndeng]

Same here, do you have any update about the issue from Avid or Synology ?

[Jasonfortheworld]

Just wanted to thank Christopotamus for the fix he supplies above . It worked like a charm for me on my DS1817. Now here's hoping that a patch can be made by either company to get things rolling again without this fix.