Did you know that in Windows Vista you can quickly copy the file name and path of a file, and put it into the Clipboard as text? Simply:

  1. Select the file in Explorer
  2. Hold ‘Shift’ and right-click
  3. Choose the ‘Copy as Path’ option

You can then use this to ‘paste’ into a hyperlink, for example, in Outlook. I found this at http://www.watchingthenet.com/copy-file-name-and-path-as-text-in-vista.html

We use a Netgear ReadyNAS Duo as our fileserver. Recently we started to experience some annoying and disturbing error messages, such as:

  • Access to {path}{CentralFileName}-backupeperms.dat was denied
  • Encountered a hardware I/O error while accessing {path}{CentralFileName}-backuprequests.dat
  • An unknown error occurred while accessing {path}{CentralFileName}.rvt

This resulted in some loss of work and lots of annoyance.
I discussed the issue with our local reseller and they basically recommended I stop using the NAS and use a different share. But I didn’t want to do that! However, it did seem likely that the problem was with the NAS. I played around with some settings in the NAS setup…and I think I found the answer. It was to do with ‘oplocks’. I needed to disable the oplocks for the share, and the problem went away! How do you do it?

  1. In the Netgear ReadyNAS Duo ‘Frontview’ administration page, go to the ‘Shares’ page.
  2. Go to the ‘Share Options’ for the share you are using to store Revit Central Files.
  3. Scroll down the bottom to ‘Opportunistic Locking’ and disable the ‘Enable oplocks for this share’ tick box.

What are ‘oplocks’? According to the utility:
Opportunistic locking (oplocks) can enhance CIFS performance by allowing files residing on this ReadyNAS to be cached locally on the Windows client, eliminating network latency when files are repeatedly accessed.
This definition indicates that oplocks could certainly have caused this issue. Since disabling the option, we have experienced none of the aforementioned errors.
Have you experienced this problem? If so, I hope my solution helped you.
Also, it looks like I haven’t been the only one with an issue like this:
“Specific applications known to exhibit this behavior include Solidworks and AutoDesk Revit, as demonstrated by your experience.”

EDIT Associated issue may result in error such as:
This issue was with a user not being able to write to a particular file that Revit uses to maintain the state of the central file.