Pages locks up editing NAS Based File

VikingOSX - Please reply only if you have an answer that can solve the problem.

I'll respect your time if you'll respect mine. Telling me to use local files (or iCloud files), which I already know works is just a waste of both of our time.

Since you brought it up, where is it that Apple said that Pages and Numbers are only intended for files on the HFS+ Boot system?

For everyone else, more on my original question:

For years I have been using NAS Drives. The Ready NAS NV+ was purchased with one of the Mac mini's in 2009 and Pages never had a glitch. It was replaced simply for speed improvement as we purchased better cameras. The QNAP is four months old, and worked perfectly until just a week or so ago. The same problem exists on two mac mini's and a mac book air.

Files transfer to and from the NAS drive work fine as long as I don't open a pages document also on the NAS. That will kill the transfer and lock up pages in one step.

It appears to be an issue with either the network or a change in how Pages handles network drives. I also noticed that the Finder no longer maps directly to the "folders" on the drives or to the drive itself. I must now open the finder, select network, select the AFP drive and then select the shared folder.

Another note: One of the Mac Mini's will no longer connect to the main WiFi, only the 5Ghz WiFi that was originally set up for the Skybell. This all started happening at the same time.

If anyone knows what may be causing this issue or have similar problems so I can troubleshoot faster please chime in.

One Final note, just discovered, was an update from 4.2.2 to 4.2.3 for the Qnap firmware. A ticket has been opened there and I will post if a fix comes from that end.

Thank you for keeping responses related to problems related to Pages and Numbers working with files on NAS drives.

Asking questions is fine, that helps move the process forward, posting for the sake of posting is disrespectful and only self serving to get more "points". I agree that most replies are just taking space.

I don't think drive format is the issue with a NAS but...

The QNAP is a 451+ NAS running firmware 4.2.3 with Seagate NV8000 drives (on approved list).

Drives are formatted automatically, and Qnap doesn't say how in the manual or in the system information that I can find.

All three macs running OS X 10.12.3

All Pages Versions are 6.0.5 build (4052)

All Numbers Versions are 4.0.5 (4052)

Again all of this worked up until about two weeks ago. At that time two things occurred. The Airport Express v2 was upgraded to 7.7.8 and the two Airport Express V1 were upgraded to 7.6.8.

The Airport Express V2 is running dual NAT and is directly connected to the cable modem

The first Airport Express V1 is in bridge mode and extends the wireless network

The second Airport Express V1 is in bridge mode with WiFi Off.

The setup was working just fine for several months. I did not reformat the drives, and will not waste time on that discussion.

After doing a lot more digging, the issue is a long ongoing one with Apple and AFP updates. We had the same problem with the Ready NAS NV+ and the Buffalo Terrastation before it. I had fixed it so long ago on the Ready NAS NV+ and stopped doing updates. I probably should have left the QNAP on 4.2.2.

Simply turning off AFP and switching to SMB allows me to open a file on the NAS edit it and save it back to the NAS

The benefit lost by turning off AFP is the NAS no longer acts as a Time Machine disc for backup nor will it save versions.

I have put in a support call to QNAP to see if they have a solution since it was working and I don't see any Apple updates that have taken effect recently.

Peter, you must really like to type about nothing. If you don't have a NAS, specifically a QNAP NAS and don't understand the issues, please find another thread to post on. Re-directing the conversation to irrelevant areas doesn't help me or anyone else with this issue.

This isn't a final fix, but this is one that works for most NAS drives having issues with AFP to keep you working, and is essentially what I was hoping to find or get when I started the thread.

Temp fix is to turn off AFP, turn on SMB (or CFIS depending on your NAS) and use the NAS with a single server protocol only until you find the exact culprit causing the NAS to slow down.

Drive formatting issues are for USB connected drives. A USB connected drive is not a NAS.

The crash report file from Pages indicates that pages is waiting for a response from the NAS after writing the temp file and locks up attempting to close the file and replace the original (or create the newer version).

An email from Netgear in 2013 had me turn off AFP and use CFIS only. By the time the patch came out my NV+ was outdated and couldn't take the patch. Hence the reason for the QNAP.

When (If?) QNAP has a better solution that returns AFP to working order, I will reply to this.

The fix is in - QNAP updated the Firmware to 4.2.4 and all is well.

While there has been a lot of hot air spit out on this thread, I think that most people will see a problem with Pages and Word and not relate it to AFP or the firmware on their NAS drive so I am posting the symptom and solution in the same place.

If you have a similar issue, try opening files and saving with AFP off, and use SMB. Apple does play nice with SMB but as many noticed in this and other threads, that kills the ability to save versions and Time Machine functionality.

Contrary to many posts, NAS drives do work great even if they aren't from Apple. This is my third.

For those of us with multiple apple devices and way over 10TB of stored photos and videos, a NAS is the only way to go. Read the iCloud EULA, if they lose your data it's not their problem. If the internet provider goes down, I can still work. Yes temp file selection is a bit of a challenge from time to time, and with personal DNS access to remote into my NAS or desktop mac, it is much better.

A USB drive attached to the AirPort Extreme doesn't do it. I want RAID because I have had drives go bad and haven't lost any data yet.

So you're blowing your hot air horn here again?

I believe I had a legitimate question.

You offered no answers.

I found a "patch fix" on another thread and reposted for others to find and hopefully help them.

QNAP offered a Firmware patch that solved it and I also posted that here hopefully to help others.

If I found those answers or you offered them, I would appreciate it. Otherwise, enjoy gloating over your points somewhere else please.

Peter - is there something wrong asking a question in this forum hoping someone actually had the same problem and found a solution?

If Qnap offers a fix I will post here for others to benefit,