Skipped files due to no access

Marks shared this problem 4 years ago
In Progress

I try to move files from my data disc to a network drive and tunespan asks me to access the files from my data disk which is granted by me. Nevertheless it tries to perform the action and states "skipped files due to no access".


I have no special access restrictions done > where is the problem?

Comments (27)

photo
1

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


If you try the span again, does it ask for access again?


Be sure to not select any folders in the Allow Access sheet, the correct location will be selected when TuneSpan presents the sheet.


Also, if you open the Console application and searching for "TuneSpan". You should see a log in there at says "Inaccessible Location: [/Some/Path/]"


Would you mind sending over a screenshot of what you see in the Console application, as well as a screenshot of the Allow Access sheet in TuneSpan?

photo
1

I try to attach the screenshot, here is the paste of the Conole Log


16.10.14 14:29:48.791 WindowServer[107]: disable_update_timeout: UI updates were forcibly disabled by application "TuneSpan" for over 1.00 seconds. Server has re-enabled them.


16.10.14 14:29:48.981 WindowServer[107]: common_reenable_update: UI updates were finally reenabled by application "TuneSpan" after 1.19 seconds (server forcibly re-enabled them after 1.00 seconds)


16.10.14 14:29:56.234 WindowServer[107]: disable_update_timeout: UI updates were forcibly disabled by application "TuneSpan" for over 1.00 seconds. Server has re-enabled them.


16.10.14 14:29:56.329 WindowServer[107]: common_reenable_update: UI updates were finally reenabled by application "TuneSpan" after 1.10 seconds (server forcibly re-enabled them after 1.00 seconds)


16.10.14 14:29:56.747 TuneSpan[4170]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.


16.10.14 14:30:02.522 TuneSpan[4170]: sandbox extension creation failed: permissions error for path: [/Volumes/MacData/]


16.10.14 14:30:02.523 TuneSpan[4170]: sandbox extension creation failed: permissions error for path: [/Volumes/MacData]


16.10.14 14:30:02.524 TuneSpan[4170]: __CFPasteboardCreateSandboxExtensionDataFromCFData : failed to obtain sandbox extension data for url [file:///Volumes/MacData]


16.10.14 14:30:02.716 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.716 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.753 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.753 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.756 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.756 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.772 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.772 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.822 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.822 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.826 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.827 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.828 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.828 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.832 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.832 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.833 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.834 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.892 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.892 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.893 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.894 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.947 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.947 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:02.993 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:02.993 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.010 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.011 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.012 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.012 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.017 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.017 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.017 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.018 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.038 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.038 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.038 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.039 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.050 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.051 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.051 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.051 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.070 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.071 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.071 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.071 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.121 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.122 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.172 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.172 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.222 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.223 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.273 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.274 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.321 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.322 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.360 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.360 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:03.362 TuneSpan[4170]: Failed to obtain a valid sandbox extension for item: [789514] of flavor: [dyn.ah62d4rv4gu8y6y4grf0gn5xbrzw1gydcr7u1e3cytf2gn] from the pasteboard. Because the sandbox extension was still being set.


16.10.14 14:30:03.362 TuneSpan[4170]: Failed to get a sandbox extensions for itemIdentifier (789514). The data for the sandbox extension was still proxy data


16.10.14 14:30:12.836 TuneSpan[4170]: Starting span with 2 tracks...


16.10.14 14:30:13.977 TuneSpan[4170]: Inaccessible Location: '/volumes/macdata/users' (r1 w0)


16.10.14 14:30:14.752 TuneSpan[4170]: Finished spanning 2 tracks (149.3 MB) in 1 second: 2 tracks skipped


16.10.14 14:30:15.576 TuneSpan[4170]: shouldPresentNotification


photo
1

Thanks for sending all this.


So TuneSpan specifically wants access to "/volumes/macdata/users".


But, I'm not seeing that folder in the Previously Accessed Locations. Having access to the whole "MacData" drive should suffice, but depending on how the permissions are set up, that may not be the case.


When TuneSpan prompts you to Allow Access, is it for the Users folder, or for the root of the drive?


Also, if you highlight MacData in the File Access list to view the Read/Write status, it is listed as both Readable and Writable?

photo
1

I think it is for the Users Folder not the whole drive but I also added the whole drive (both my system drive and my data drive) which din't work. One thing to add: I have my users folder as a symbolic link on a seperate partition (screeenshot added). Thats all german cause my mac is german but you should be able to see the case.

photo
1

Another thing: When I allow access to all files for the whole drive (MacSys) (via TuneSpan Menu) it is marked only readable > how do i get this to readable AND writeable! With MacData its both readable and writeable

photo
1

Interesting... So TuneSpan is requesting access to the /Volumes/MacData/Users/ folder, but then there's a symbolic link within there that's pointing to your local drive, which TuneSpan doesn't have access to.


That's an interesting edge case that I'll need to look into and think about more.


In the mean time, please try first clearing all file access, and then after all access is cleared, use the "Allow Access to All Files..." menu item to grant access to the root of your local drive, MacSys in this case.


With access to that location (and only that location), I believe the span should work.


But, please let me know if that's not the case.

photo
1

think its the opposite way. I guess I already tried that (can't try it now as I don't have access to the new spanned location), with both MacSys and MacData but with MacSys TuneSpan only gets Read Access and no write Access. With MacData both. Maybe thats also the issue that it has the read/write permission only on the symbolic link (destination) and not the origin... Is there a way how I can grant Read and Write access to a Location, as I only have a "grant access" button not specifying whether it can be read and/or write....

photo
1

Before we continue investigating other things, I'd really like to know how things go with all access cleared, and then only access granted to the root of your local drive.


Please let me know how that goes when you can test a span.


There's no way to force TuneSpan to get Write access, after you grant TuneSpan access to a location, the read/write access should be dictated by the file system.

photo
1

all cleared and access given to sys and data. results see attachment

photo
1

I see what you're saying, but that's not a guarantee that the span won't work. In fact it's normal for OS X to have restricted access to the root of the local drive, but the subfolders will have normal writable access.


Please try the span with ONLY access granted to MacSys, you should not grant access to MacData for this test that I'm wanting to do.


After you grant access to only MacSys, the span should work without asking for anymore access. But please let me know what you see.


If TuneSpan asks for any more access, please grab a screenshot of the Allow Access sheet, and if the span fails or skips, please grab a screenshot of the results.

photo
1

Ok, so I tried again. 1) Cleared all accesses 2) Grant Access to Sys 3) Spanned to a test-folder on macdata 4) Failed with same error message


Tested again with the following 1) Cleared 2) No Grants given 3) Spanned to test-folder 4) Allowed access to drive requested by TuneSpan (see attachment) 4) Failed again.


photo
1

I was actually hoping to see the whole allow access sheet to see what was selected as the actual location, not just the button which is static.


But, if it didn't work in any of these scenarios, the issue is most likely a true problem with your permissions on the file system (TuneSpan will only get the user level permission) or it's something weird caused by the symlink.


Can you do some tests to see whether you can span directly to a different location on both MacSys and MacData to rule out either a permissions issue or a symlink issue? Hopefully we can find a span that works and work our way back from there to see what's different.

photo
1

Sorry it's late, I missed that you spanned to a test folder. That folder didn't involve a symlink, right?


If not, this looks like a problem with the permissions on your drive.

photo
1

Yes, the original location (also with the itunes metadata) is still on the symlink and the new testfolder is without a symlink.

photo
1

maybe thats the problem? that tunespan is not allowed to manipulate the original itunes metadata?

photo
1

Haven't hear anything after my last statement

photo
1

Sorry, I've been busy the past few days.


Granting access to the root of your main drive gives full file access to all locations, including external drives.


If the span didn't work with full access, the next thing to investigate is your drives permissions.


So far, this has the signs of a permissions issue, not necessarily a TuneSpan issue.

photo
1

This answer doesn't help me at all. It leave me alone with a problem that your software is designed to solve. Either I get clear advice on what to do or otherwise I want my money back > if I don't receive any help with something that TuneSpan is supposed to do. I expect a solution that works within the next 3 business days.

photo
1

I understand you're frustrated, and I'm sorry this doesn't have an obvious fix.


With these kinds of problems, we need to work together to figure it out and solve it.


The problem is either because of the symlink, or because of permissions that need to be changed.


I've outlined how to narrow that down on your end in a previous message.


You're not alone, I'm here to help, but I can't do it all.


I would still like to see more detailed screenshots. Specifically a screenshot of the full Allow Access sheet so I can see what exact location is being presented by the open panel. Whether or not the symlink is being resolved by the open panel may be part of the problem.


But, since a span without a symlink also didn't work, that makes it seem like something else may be going on as well.


Also, screenshots of the Span Results when you span to a location with no symlink, as well as with the symlink would be helpful to understand the situation.


I'd recommend trying to find some test span that can work so we gave some starting point and isolate the drives or scenarios that aren't working... Have you tried spanning to the Desktop? Do you have other drives to test with?

photo
1

What else can I provide to help in solving this issue? I thought I provided all screenshots etc. Well, I tried it with Schreibtisch (i.e. Desktop) after having cleared all accesses which brings the following screen and again - no result.

photo
1

What is the path listed if you open up that dropdown menu in the top middle of the open sheet that says "Users"?


I'm curious if that path is on MacData or MacSys because of the symlink.


So all of your files currently reside somewhere within "markus" folder? That would mean that we're having a problem with the permissions (or TuneSpan getting access) at the source location, not at the destination span location.


I'm sorry that you have to work with me on this, I appreciate your patience. This is just a special case because of how you have your files set up that TuneSpan may not be handling properly. Not something I can replicate on my system.


I'm curious if this wouldn't be an issue if TuneSpan was requesting access to the "markus" folder instead of the "Users" folder. I'll look into the code that chooses access locations and see if I can do a special catch to not ask for access to a "Users" folder directly and always go one more level in.

photo
1

Yes, everything is under markus. Users resides on MacSys, whereas Markus (below Users) is the symlink to MacData. Unfortunately you don't see the path in the dropbox nevertheless I include a screenshot. I already stated before I think its a problem in accessing the Original file or even the iTunes MetaData via write access.


photo
1

Thanks, I think I'm understanding your setup better now. But just to make sure...


The path in the open panel "/Volumes/MacData/Users/" is the actual file location? The symlink is on MacSys, pointing to MacData?


I'll take a moment to make a change to the file access path requesting code and may have a testing version for you to try out. I'll let you know shortly.

photo
1

Here is my MacSys Users (German "Benutzer") Structure, everything on MacSys but markus being the symlink.

photo
1

Alright, I've made a tweak in TuneSpan to never choose a base path that's a "Users" folder. It will always go one more level in to a specific user folder if it can.


Please email me directly with the form at http://contact.tunespan.com or with one of the links from the app so that I can send you this testing version.


I can't guarantee that it will fix the issue. But it'll be important to rule that out as the cause of this problem.

photo
1

Form submitted.

photo
1

Markus has reported this issue is solved by TuneSpan choosing the actual user folder (in this case, the "markus" folder) instead of the "Users" folder.


This turned out not to have to do with the symbolic link, or any issue with permissions in any of the other folders. It's normal for the "Users" folder to have limited permissions, and TuneSpan should never need to choose it as an access location. Now, TuneSpan will always choose a folder level deeper than a "Users" folder for a base access path in a setup like this.


This fix will be in the next minor update to TuneSpan. For now, I'm marking this problem as "In progress" and I'll post back here when the update is officially released.