Issues With Reconnecting Library to Referenced Files

I'm hoping somebody may be able to shed some light on very strange behavior I'm currently experiencing with Aperture. Before I continue let me say ahead of time that I've already run a Repair Permissions, Repair Database and a complete Rebuild Database on the Library. That said here is what's happening.
My workflow consists of Importing all images via Aperture, as referenced files, on to a small, external hard drive. When I return to my studio I manually copy the folder of images, from the small external drive, over to my desktop hard drive. The next step is to Import the Field Library to my desktop MAIN library. Once the Field Library is Imported into the MAIN Desktop library I then highlight all the images and select File>Locate Referenced Files. Though I've done this hundreds of times in the past, it's currently not working on some files. Here's where the very strange behavior comes in.
When the Locae Referenced Files window comes up I see the image in the top pane that I want to reconnect. In the bottom pain I navigate to the drive the image now lives on, I find it and it too appears in the bottom window. So far all seems to be fine, except when I tried reconnecting, Aperture went through the process but didn't actually reconnect. I retried several times but after the first try to reconnect the Reconnect & Reconnect All buttons is grayed out.
Ok, so what the heck is going on? I start reviewing the Metadata of each image while still in the Locate Referenced Files window. The file numbers are exactly the same but the time stamp on each image is different. Why I have no idea. I plug in the original mini field drive with all the images that Aperture Imported to check the Metadata on the field drive. Sure enough it's identical to the Metadata on the Desktop drive which means it's different from the Aperture Library on the orignal drive Apertue saved it to as well. But what's even more interesting is that the minute the mini hard drive is plugged in, Aperture sees it and reconnects the images automatically, even though the potential issue of the metadata timestamp being different is the same on both the mini field drive and my desktop drive.
In summary, when Aperture wouldn't connect the images that were on the desktop drive I thought I found the reason; a discrepancy in Metadata. But when the original drive was plugged in, the same files had the same discrepancies yet Aperture found them fine.
None of this would be a probelm if Aperture had the ability to FORCE RECONNECT. The images are exactly the same except for some minor metadata descrepencies that I have no idea how they got changed and I really don't care about. But............. how the heck am I going to get these fiels reconnected without a Force REconnect option. Any ideas out there?

William is right - use the provided tools.
. Never once could it not find the images once I took it and showed the exact path to where the images were newly located. So what happens if that drive ever fails completely and I have to replace it with a totally new backup?
There must be something wrong with your external drive, if reconnect is not working. I had never, ever trouble to reconnect the originals after copying or cloning a drive, when I restored a mac from my backup.
Check the filesystem on your field drive, if the file system is MacOS Extended (Journaled).

Similar Messages

Masters in Library vs Referenced files

As I play around more with Aperture today I have another question this time regarding files. What are the pro's/con's of importing masters into the library vs referencing files in the library. I am leaning towards importing masters into Aperture rather than reference because 1)makes it easier to manage photos; 2)easier to backup photo's.
Those that have used Aperture for sometime what method do you use - masters in the library or reference? What are the reasons?
If I have my/a library stored on the external drive what issues will I have if the external drive is not connected to the Macbook?

all you really need to know ...
http://www.bagelturf.com/aparticles/ref/index.html
i also highly suggest that you get this book:
http://www.amazon.com/Apple-Pro-Training-Aperture-1-5/dp/0321496620
it is a tutorial, not a manual ... that is where the value is ...
i personally use a managed library ... why, i like the clean neatness of the package ... and sticking them in a package does not worry me at all ... i have several vaults that i keep around ...
with referenced to work on a external you need to make sure that your external is connected ... browse thru this forum and notice how many issues with ref'd images not reconnecting ... to me managed is easier ... but to others, not so much ...

Backing up library and referenced files

I download my images to an external F800 hard drive and organize them in folders labeled with the dates in which the download took place.
I manage them in aperture as referenced files.
I just got a second external hard drive for back up purposes. What is the best way to back up my library and referenced files?. My external hard drive allows daisy-chaining.
Sorry if this is too simple a question, but before doing something wrong I rather ask.
thanks for the patience and will to reply,
best
Mauricio

Backup the Aperture Library to your new drive using Aperture's Vault feature. Backup the folders of Masters by Finder-copying the folders to the new drive immediately after the folders are created. That should be a nice clean workflow.
Don't forget some type of off site backup to deal with the possibility of fire or theft.
-Allen Wicks

I'm having a huge issue with itunes locating my missing files..and it's too many for me to locate 1 by 1..It says I'm missing over 3,00 songs and They are all in my music folder..What can I do to fix this issue?

I'm having a huge issue with itunes locating my missing files..and it's too many for me to locate 1 by 1..It says I'm missing over 3,000 songs and They are all in my music folder..What can I do to fix this issue? I've looked at all the tutorials on youtube and none of it works. I recently got a new computer and I Back-Up all my music and itunes playlist and I import it on my new computer with the new itunes and I go to play a few songs, it says I'm missing them I locate a few but it's still like 3,000 missing and again they are all on the computer and in one folder..Please Help !

I did that and nothing changed half my songs still have examination marks beside them
I also just tried dragging my folder of music int he playlist and it duplicated all of my songs? My playlist was at 5k now it's at 10k becuz of 3 duplicates of songs. Is there a way to delete multiple duplicate files?

I got the following for Adobe Reader that there was an issue with it. C:\Program Files (x86)\Adobe\Reader 11.0\Reader\NPSWF32.dll file How do I fix this? Thanks.

How can I fix this problem. I got the following for Adobe Reader that there was an issue with it. C:\Program Files (x86)\Adobe\Reader 11.0\Reader\NPSWF32.dll file

Try uninstalling using http://labs.adobe.com/downloads/acrobatcleaner.html then reinstall.

RC 8.6 Issues with Nikon D810 NEF RAW files

RC 8.6 does not correctly process Nikon D810 NEF RAW files. See the following blog article for some details:
Nikon D810 vs D800E ISO Comparison

This is very helpful. My current workflow, until ACR 8.6 and LR fully support the Nikon D810, are to use the DNG converter and import the resulting D810 DNG files into my LR catalog.
I have not yet tried this (traveling right now), but I assume I can still make a custom profile using the X-Rite ColorChecker Passport and it's associated software for my D810 using the RC 8.6 DNG files. This is my normal workflow for all of my other cameras in LR, but the process is direct from native RAW and not DNG (to produce the custom profile).
Sent from my iPad
On Jul 28, 2014, at 6:51 PM, "max.wendt" <[email protected]> wrote:
RC 8.6 Issues with Nikon D810 NEF RAW files
created by max.wendt in Adobe Camera Raw - View the full discussion
Until Lightroom gets D810 support, you will need to use the ACR plugin in order to see the profiles. The DNG Converter always uses Adobe Standard, and embeds it into the DNG. Lightroom 5.5 doesn't have the D810 profiles.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image athttps://forums.adobe.com/message/6592335#6592335
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: [https://forums.adobe.com/message/6592335#6592335]
To unsubscribe from this thread, please visit the message page at [https://forums.adobe.com/message/6592335#6592335]. In the Actions box on the right, click theStop Email Notifications link.
Start a new discussion in Adobe Camera Raw by email or at Adobe Community
For more information about maintaining your forum email notifications please go tohttp://forums.adobe.com/thread/416458?tstart=0.

How do I stop Aperture consistently crashing when attempting to reconnect a few referenced files?

Has anyone else run into this? It's driving me nuts.
Many months ago I had Aperture move my referenced photos to a larger external hard drive. I just discovered recently that there's a small handful of images that it still thinks are on the old hard drive (even though it successfully moved the original files to the new hard drive, oddly). The full sized previews and all the meta data are still there in Aperture but it regards the photos as offline.
So I select a few (<10) of the affected images, select the "Locate referenced files" option in the File menu, to get the "Referenced files in selection" window. I click on the new hard drive name in the lower panel and Aperture instantly displays the same photo on the new hard drive. I can arrow down through the ten or so images in the top panel and Aperture instantly displays all of them on the external hard drive.
So I press "Reconnect all" and Wham! Aperture crashes. Consistently.
It sometimes works with a single image, but not yet more than once before it crashes.
Aperture has also been driving my nuts with the spinning ball since Mountain Lion and the latest update. (My hardware may be getting a bit out of date for this now, although it was working fine before--it's the fastest late 2009 13" MacBook Pro with 8 GB of RAM.) I've already tried repairing the library (Aperture forces me to do this after a about three of the abovecrashes). I've rebuilt the whole library (twice now). I've deleted the Aperture preferences and relaunched. I've deleted the Aperture application and reinstalled it from the AppStore.
Any ideas on what I can try next? Thanks!
Here's the first lines of the crash report that Apple generates:
Process:         Aperture [29772]
Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier:      com.apple.Aperture
Version:         3.4.1 (3.4.1)
Build Info:      Aperture-301039000000000~2
App Item ID:     408981426
App External ID: 11130653
Code Type:       X86-64 (Native)
Parent Process: launchd [177]
User ID:         501
Date/Time:       2012-10-25 08:47:06.464 +1300
OS Version:      Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report:          122141 sec
Crashes Since Last Report:           9
Per-App Interval Since Last Report: 102826 sec
Per-App Crashes Since Last Report:   8
Anonymous UUID:                      C8AB497A-18DB-3A43-8663-4B28960DFA6E
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Application Specific Information:
objc_msgSend() selector name: dealloc
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib                         0x00007fff897cf250 objc_msgSend + 16
1   com.apple.Aperture                      0x0000000106f2ce46 0x106e03000 + 1220166
2   com.apple.Aperture                      0x0000000106f2cf32 0x106e03000 + 1220402
3   com.apple.AppKit                        0x00007fff91a15ce6 -[_NSBrowserMatrixColumnViewController reloadData] + 587
4   com.apple.AppKit                        0x00007fff91a02e23 -[NSBrowser _matrixBasedReloadColumn:] + 199
5   libdispatch.dylib                       0x00007fff8b431f01 _dispatch_call_block_and_release + 15
6   libdispatch.dylib                       0x00007fff8b42e0b6 _dispatch_client_callout + 8
7   libdispatch.dylib                       0x00007fff8b4330c8 _dispatch_main_queue_callback_4CF + 275
8   com.apple.CoreFoundation                0x00007fff899b30fe __CFRunLoopRun + 1614
9   com.apple.CoreFoundation                0x00007fff899b26b2 CFRunLoopRunSpecific + 290
10 com.apple.HIToolbox                     0x00007fff8df760a4 RunCurrentEventLoopInMode + 209
11 com.apple.HIToolbox                     0x00007fff8df75e42 ReceiveNextEventCommon + 356
12 com.apple.HIToolbox                     0x00007fff8df75cd3 BlockUntilNextEventMatchingListInMode + 62
13 com.apple.AppKit                        0x00007fff9178b613 _DPSNextEvent + 685
14 com.apple.AppKit                        0x00007fff9178aed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
15 com.apple.Aperture                      0x000000010727700d 0x106e03000 + 4669453
16 com.apple.AppKit                        0x00007fff919d5709 -[NSApplication _realDoModalLoop:peek:] + 485
17 com.apple.AppKit                        0x00007fff919d59ce -[NSApplication runModalForWindow:] + 120
18 com.apple.Aperture                      0x0000000106f7fcb3 0x106e03000 + 1559731
19 com.apple.Aperture                      0x0000000106e4b0b5 0x106e03000 + 295093
20 com.apple.AppKit                        0x00007fff9187ba59 -[NSApplication sendAction:to:from:] + 342
21 com.apple.prokit                        0x000000010831f10c -[NSProApplication sendAction:to:from:] + 101
22 com.apple.Aperture                      0x00000001072780bf 0x106e03000 + 4673727
23 com.apple.AppKit                        0x00007fff919b144c -[NSMenuItem _corePerformAction] + 406
24 com.apple.AppKit                        0x00007fff919b113a -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 133
25 com.apple.AppKit                        0x00007fff9169e46f -[NSMenu _internalPerformActionForItemAtIndex:] + 36
26 com.apple.AppKit                        0x00007fff9169e2f7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135
27 com.apple.AppKit                        0x00007fff919aa245 NSSLMMenuEventHandler + 342
28 com.apple.HIToolbox                     0x00007fff8df4ef0a DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1206

Has anyone else run into this? It's driving me nuts.
Many months ago I had Aperture move my referenced photos to a larger external hard drive. I just discovered recently that there's a small handful of images that it still thinks are on the old hard drive (even though it successfully moved the original files to the new hard drive, oddly). The full sized previews and all the meta data are still there in Aperture but it regards the photos as offline.
So I select a few (<10) of the affected images, select the "Locate referenced files" option in the File menu, to get the "Referenced files in selection" window. I click on the new hard drive name in the lower panel and Aperture instantly displays the same photo on the new hard drive. I can arrow down through the ten or so images in the top panel and Aperture instantly displays all of them on the external hard drive.
So I press "Reconnect all" and Wham! Aperture crashes. Consistently.
It sometimes works with a single image, but not yet more than once before it crashes.
Aperture has also been driving my nuts with the spinning ball since Mountain Lion and the latest update. (My hardware may be getting a bit out of date for this now, although it was working fine before--it's the fastest late 2009 13" MacBook Pro with 8 GB of RAM.) I've already tried repairing the library (Aperture forces me to do this after a about three of the abovecrashes). I've rebuilt the whole library (twice now). I've deleted the Aperture preferences and relaunched. I've deleted the Aperture application and reinstalled it from the AppStore.
Any ideas on what I can try next? Thanks!
Here's the first lines of the crash report that Apple generates:
Process:         Aperture [29772]
Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier:      com.apple.Aperture
Version:         3.4.1 (3.4.1)
Build Info:      Aperture-301039000000000~2
App Item ID:     408981426
App External ID: 11130653
Code Type:       X86-64 (Native)
Parent Process: launchd [177]
User ID:         501
Date/Time:       2012-10-25 08:47:06.464 +1300
OS Version:      Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report:          122141 sec
Crashes Since Last Report:           9
Per-App Interval Since Last Report: 102826 sec
Per-App Crashes Since Last Report:   8
Anonymous UUID:                      C8AB497A-18DB-3A43-8663-4B28960DFA6E
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Application Specific Information:
objc_msgSend() selector name: dealloc
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib                         0x00007fff897cf250 objc_msgSend + 16
1   com.apple.Aperture                      0x0000000106f2ce46 0x106e03000 + 1220166
2   com.apple.Aperture                      0x0000000106f2cf32 0x106e03000 + 1220402
3   com.apple.AppKit                        0x00007fff91a15ce6 -[_NSBrowserMatrixColumnViewController reloadData] + 587
4   com.apple.AppKit                        0x00007fff91a02e23 -[NSBrowser _matrixBasedReloadColumn:] + 199
5   libdispatch.dylib                       0x00007fff8b431f01 _dispatch_call_block_and_release + 15
6   libdispatch.dylib                       0x00007fff8b42e0b6 _dispatch_client_callout + 8
7   libdispatch.dylib                       0x00007fff8b4330c8 _dispatch_main_queue_callback_4CF + 275
8   com.apple.CoreFoundation                0x00007fff899b30fe __CFRunLoopRun + 1614
9   com.apple.CoreFoundation                0x00007fff899b26b2 CFRunLoopRunSpecific + 290
10 com.apple.HIToolbox                     0x00007fff8df760a4 RunCurrentEventLoopInMode + 209
11 com.apple.HIToolbox                     0x00007fff8df75e42 ReceiveNextEventCommon + 356
12 com.apple.HIToolbox                     0x00007fff8df75cd3 BlockUntilNextEventMatchingListInMode + 62
13 com.apple.AppKit                        0x00007fff9178b613 _DPSNextEvent + 685
14 com.apple.AppKit                        0x00007fff9178aed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
15 com.apple.Aperture                      0x000000010727700d 0x106e03000 + 4669453
16 com.apple.AppKit                        0x00007fff919d5709 -[NSApplication _realDoModalLoop:peek:] + 485
17 com.apple.AppKit                        0x00007fff919d59ce -[NSApplication runModalForWindow:] + 120
18 com.apple.Aperture                      0x0000000106f7fcb3 0x106e03000 + 1559731
19 com.apple.Aperture                      0x0000000106e4b0b5 0x106e03000 + 295093
20 com.apple.AppKit                        0x00007fff9187ba59 -[NSApplication sendAction:to:from:] + 342
21 com.apple.prokit                        0x000000010831f10c -[NSProApplication sendAction:to:from:] + 101
22 com.apple.Aperture                      0x00000001072780bf 0x106e03000 + 4673727
23 com.apple.AppKit                        0x00007fff919b144c -[NSMenuItem _corePerformAction] + 406
24 com.apple.AppKit                        0x00007fff919b113a -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 133
25 com.apple.AppKit                        0x00007fff9169e46f -[NSMenu _internalPerformActionForItemAtIndex:] + 36
26 com.apple.AppKit                        0x00007fff9169e2f7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135
27 com.apple.AppKit                        0x00007fff919aa245 NSSLMMenuEventHandler + 342
28 com.apple.HIToolbox                     0x00007fff8df4ef0a DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1206

Masters in Aperture Library Using Referenced Files

I use a MBP with an SSD to hold my Aperture 3 library.
I use a G-RAID to store my images and use Referenced Files.
All was good until yesterday, I deleted my Thumbnails to recreate them and remove the orphans.
After restarting Aperture and the processing time to recreate the Thumbnails (AP.Minis, Ap.Thumbnails, and AP.Tinies) I noticed my AP library was huge.
After inspecting the contents, there is now 65Gb worth of Masters, why would these be there since I use Referenced files and why would they have just now shown up after rebuilding my Thumbnails?

Remember:
-- A RAW file cannot be edited. It can only be written in a camera (or scanner, etc.) To be seen, it must be read through a RAW developer. The RAW developer (or converter, if you prefer) can apply changes to the bitstream (called "adjustments" in Aperture) but those changes always live in a separate file, called a "version" in Aperture. EVERY master image file in Aperture has at least one version file. The two are combined, in real time, every time you see a file. Thus questions about the Aperture library becoming corrupted are a bit moot - if you lose your library you will lose your edits. The only way to "save" edits to a RAW file is either adjust it in Aperture (or Lightroom) and let the program combine the two, or convert the file to an industry standard format, like TIFF or JPEG.
-- Aperture uses a "non-destructive" workflow. This means that it never really edits ANY file - not even a JPEG. This avoids the problem of recompressing JPEGS each time they are opened and close. So even JPEGS remain unaltered with your "edits" or "adjustments" being stored in one or more versions.
The only time you need to "save" a file in Aperture is when you need a new file in a specific format to give to someone. Until then, Aperture happily keeps track of your original images (managed or referenced) and the corresponding "edits" which it stores in a version linked to the original image file.
There are many reasons to prefer managed over referenced or vice versa, but fears of database integrity should not be one of them. You are making a lot of work for yourself - put the Aperture Vault on your server and/or use Time Machine. "Exporting" is a terrible way to try to make backups - it will take forever and you will end up with files scattered all over the place, defeating the purpose for which you bought Aperture in the first place.
Hope this helps.
DiploStrat

Issues with attaching an Adobe Story File to a clip in PPCC

Hi,
I read through a lot of stuff and watched a couple videos but still have an issue with the attachment.
What I do is I go into the Metadata and assign my scene number (3.01). I export the script as a .astx. File/right click, attach story file-> select the file go back to metadata and it tells me nothing found. This is really frustrating what's wrong with it?

Worked this one out, I had the bullet set on file and not staging

Issue with the storage check if files are uploaded...

There is an issue with (photo) updloads to SkyDrive filling the temporary items. When I started to upload photos to Skydrive, I had about 2.4 GB free space on my Lumia 820 and after a while the whole memory was full. I uploaded successfully about 600MB of photos, but the same time the phone filled the temporary items to 2.4GB and thus went to full stop with all memory gone. And I haven't had any success of freeing up the temporary items.
Basically, whatever I upload to the Skydrive it goes to the temp files and that cannot be cleared using Storage check option.
Can you please help me on this?

cjlim wrote:
No worries with the 925. It comes with at least 16gb internal storage. Have a good holiday.
16GB without a micro-SD card slot isn't enough for many users especially those who have a large music collection. (Note: Cloud storage is NOT equivalent to local storage). In any case 16GB will only postpone but not get rid of the problem of the 'Other' folder.

Are there any compatibility issues with Mavericks and EMC Celerra File shares, particularly with the SMB protocols?

Our company uses a EMC Celerra file share, but most of our users are Windows based. We have a small production department of 7 macs. Starting with Snow Leopard, we noticed some issues with SMB. We were able to resolve those issues, but had to wait to upgrade to Lion because there were additional SMB or permissions concerns with the Celerra file share and Lion. Now, we are again waiting to upgrade to Mavricks because of the way it handles user permissions. Does anyone using Mavericks now also connect to a EMC Celerra file share? Thanks!

Our company uses a EMC Celerra file share, but most of our users are Windows based. We have a small production department of 7 macs. Starting with Snow Leopard, we noticed some issues with SMB. We were able to resolve those issues, but had to wait to upgrade to Lion because there were additional SMB or permissions concerns with the Celerra file share and Lion. Now, we are again waiting to upgrade to Mavricks because of the way it handles user permissions. Does anyone using Mavericks now also connect to a EMC Celerra file share? Thanks!

FDM: Issues with importing mapping using excel files

Hi All,
I am trying to map ICP Entries using an excel file.
I have made 2 mapping (explicit) entries, manually and exported it in Excel and then added all the Mappings in the same file, in proper format. when I am importing, I am not getting any error but the mapping is not getting updated and the new entries are also not getting added. so Ideally no Change in the tDatamap table.
Environment details: FDM Version 11.1.1.3 is getting used. Target App is Essbase 11.1.1.3. able to connect to Essbase, no issues with connectivity.
Has anyone face this issue.

The section of the admin guide I reference will tell you how to create a properly formatted excel workbook. Import XLS will work if the excel workbook is set up properly. The import XLS functionality will not change existing records, only add new ones.
Your template requires that the first cell is the table name. The second row is the table field names and rows 3 through X are the values to be inserted into the table. The named range beginning with UPS needs to highlight all of these rows and columns.
Quite honestly, if you take the time to review the admin guide, I'm sure you'll find the answer that you need. Please understand that, like you, most of us that post on this board are consultants. We share knowledge to help the community better utilize the product. It's frustrating to hear that none of the answers that I previously provided you were at all helpful.
Edited by: TonyScalese on Nov 30, 2010 3:23 PM

Issue with InDesign cs5 and network files.

On Mavericks having issues with InDesign CS5. When trying to open a file from an smb netwrok drive it goes into Not responding.
have tested InDesign working correctly with local files.
have tried removing, SING folder. tried reinstalling.
all updates on OS and adobe InDesign have been installed.
any suggestions would be appreciated.

CS5 is unsupported under Mavericks.
Unfortunately, you’re pretty much on your own here.

Issues with rights on a specific file

Hi,
Given this details: a folder called \\netshare\Temp where a user doesn't have any rights, I put a file called test.txt and give full rights on this file, I instructed the user to access it by directly by copy and paste
the UNC: \\netshare\Temp\test.txt, the file is opening, but the user cant save it.
Client OS is Windows 7.
I want to avoid giving rights on the folder itself.
Is there any workaround?
Thanks,

Hi,
I have done a test on my pc and use the same settings with yours. Then I opened the test.txt file and modify the content, after that, I could save the test.txt file. Please confirm the user configures the group policy “Bypass traverse checking”.
For more detailed information, you could refer to the article below:
Bypass traverse checking
http://technet.microsoft.com/en-us/library/cc739389(v=ws.10).aspx
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Hi,
Thanks for your kind response. The thing is that the issue is on a network share sitting on a NAS. So is not a windows PC or Server.
Is there anything else i could do?
Thanks,

Security Issues with SMB affect MS Office files being slow from Network locations

On our windows 7 machines our users our having slowness issue opening Office files from a network location
This slowness only affect domain users. Domain admins have no slowness issues.
Make changes to trusted documents ro trusted location. Trust network location has no affect.
If I disable SMB them domain users can open Office files from network location with no slowness.
Any ideas?

Hi Navar,
There has been a lot of discussions about the performance impact of SMB.
When SMB is enabled, communications to and from Windows clients will experience a significant impact on performance, which affects both the clients and the server. This is kind of by design.
More reference:
http://technet.microsoft.com/en-us/library/jj852239(v=ws.10).aspx
So if you have identified that SMB is causing the performance issues, you can disable SMB on any of your Windows clients that do not require protection.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Issues With Reconnecting Library to Referenced Files

Similar Messages

Maybe you are looking for