You didn't allow Tunespan to access to all necessary locations - bringing NAS media files to SSD

David Hobbs shared this problem 6 years ago
Solved

I followed the default "allow access" but all of my iTunes media was stored on a NAS (I set this up in my Windows PC days), and I'm trying to bring some of them back to my internal SSD for when I am away from home.


Tunespan came up with an Allow Access message once which was for the NAS not the Macintosh HD.


Now I don't get asked to allow access, but it always gives me the message "You didn't allow Tunespan to access to all necessary locations" and I don't get the opportunity to change it.


I am however, allowed to span a file FROM the Macintosh HD TO the NAS and then restore it back again. It just won't let me span files that have not been on the Macintosh HD. Can I use Tunespan to bring these back?

Comments (13)

photo
1

Thanks for getting in touch. I'm sorry you've run into an issue.


You can reset TuneSpan's file access by holding down the Control and Command keys while TuneSpan loads. If you miss holding the keys down on launch, you can hold them when you select Reload TuneSpan from the File menu.


When file access is cleared in the first seconds of loading, you'll see the puff-of-smoke cursor, but that's the only UI feedback.


Once file access is cleared, TuneSpan will ask for fresh access on the next reattempt.


If should ask for access twice, once to the NAS and once on your internal drive. If anything looks weird, please take screenshots so I can see what's going on to help.

photo
1

I followed this process and reset the file access to no avail. :(


It asked for access twice, and it did not matter whether I chose the root directory of the NAS or the iTunes directory = same result.


BTW, when I held down Control and Command on and Reloaded Tunespan or even just restarted Tunespan, I didn't get the puff of smoke and it only asked me once. So I rebooted the Mac and repeated the test so that it asked me twice to grant access.

photo
1

Maybe it is making a sad comment on my choice in music, LOL. But it does it for all tracks...

photo
1

Hmmm, strange, looks like we'll need to dig a bit deeper.


Just to be sure... you clicked "Allow Access" on both of these sheets without selecting any folders in the list, right?


To pursue this further, I may need to send you a testing version that can log all the paths that TuneSpan is requesting access to, and what paths it got access to so we can find the discrepancy.

photo
1

Actually, in the mean time, you could give TuneSpan access to all your files at once, then you should be able to span tracks.


To do this, hold down the Option key as you open the File menu, and you'll see an "Allow Access to All Files..." menu item, select it and you'll be prompted allow access to the root of your internal drive.


Granting that access will give access to all external drives and everything so it should avoid this issue. Before you do that, you may want to clear access once more so whatever paths TuneSpan already has access to don't interfere with anything.

photo
1

Thanks for the reply.


Correct, I clicked "Allow Access" on both of these sheets without selecting any folders in the list.


I also cleared access and tried the "Allow Access to All Files..." menu item, and allowed access to the root of your internal drive. (i.e. did not select any folders).


Both tests gave the same results.


But I'm puzzled because they seem to refer to granting access to the internal drive and not the external NAS drive.


Clearly TuneSpan has read access to the NAS since it can restore a file previously spanned to the NAS.

photo
1

Hmm, so after you cleared access and allowed access to all files TuneSpan still said that you hadn't allowed access to all locations in the span results in the same way as before?


Looks like I'll need to send you a testing version so we can see some extra logging to figure out what exactly is going on.


I don't think I'll have to time to do that until tomorrow or the next day though. I'm very sorry about this hassle.

photo
1

OK, thanks. Sorry it is an unusual use case. Will wait for your reply. In the meantime, iTunes can play from the NAS while I am connected...

photo
1

I may have found a workaround for if you can't fix it.


If I move all of the media files to my Lacie external HDD (or Macintosh HD SSD) manually, delete/disconnect from the NAS, and then let iTunes locate the missing files TuneSpan will consider the Lacie as the "home" location and then let me span and restore wherever I want. iTunes almost locates all of the files so it may not be too bad. But not the way it is supposed to work...


Is there any reason why TuneSpan would prefer the "home" location of the files on the Macintosh HD or the Lacie?

photo
1

I'm very sorry I haven't gotten back to you yet. I've been busy with other stuff the past few days.


TuneSpan shouldn't care where your files original location is. It doesn't matter to the code one bit.


It sounds to me like this may actually be a permissions issue with the NAS on your end.


What are the permission on your NAS? Does it ever require authentication to copy files to or from the NAS?

photo
1

I'm pretty sure I have read/write access to all folders when I am logged in. All other applications that I have tested can read and write to the NAS folders. Indeed TuneSpan can write span files to it and then span them to another location (i.e. I can copy a new media file from Macintosh HD to NAS to Lacie.

photo
1

Interesting. Well, I've made a lot of changes in TuneSpan. It would probably be good to check if my latest testing version doesn't solve this problem before we go digging further to find the issue.


Would you mind emailing me so that I can send you a testing build?


http://contact.tunespan.com

photo
1

I'm very pleased to say that TuneSpan 1.2 is now available on the Mac App Store which solves this issue, and adds many new features.


http://mas.tunespan.com