Issue saving/opening central model in LAN

[arq_42]

In the office, we have a local NAS where we store all our central or single-user files.
We can access the NAS through Windows Explorer via \NAS\Files\... or through a fake hard drive called S:\
We all have the same letter assigned to that fake drive.

Today, trying to create a new model, we created the file, colaborate, etc, and saved it as central in S:\...file.rvt.
When opening it from another PC, to create the first local file, we accessed it via S:\...file.rvt, and the "Create local file" option is grayed out.

When opening, Revit gives the error "The central file has been copied or moved from \NAS...File.rvt to S:\...File.rvt"

If we access it from the second PC via \NAS, it opens without problems, but the question is: Why does this happen if both have accessed it via S:\?

[RSomppi]

Using the NAS may have been a bad choice.

[SteveKStafford · Accepted solution]

The way each user's PC is mapped to the shared resource matters to Revit. For example, if one user is mapped via UNC format and another is mapped using the IP address. Revit "sees" that as different because the actual full path description IS different. You must make sure everyone is mapped to where the project files are located in exactly the same way otherwise this will continue to happen.

[TripleM-Dev.net · Accepted solution]

As far as I'm aware Revit's central file will always use the network direct path (\NASxx\...) if it's created on a Mapped drive (S:\ in this case)

If a user only has access to the model thruw S:\ but not from \NASxx\ Revit will use the S:\ drive and will give the warning of the moved central.

Make sure all stations only have S:\ access and not \NASxx\ itself, or ensure all also have access to \NASxx\

You can check this in the "Sync with settings" of a valid local from which path the central should have access from.

Opening it from S:\ shouldn't be a problem as long as the actual saved path in the central is also accessable.

- Michel

[arq_42]

---

@RSomppi  ha escrito:

Using the NAS may have been a bad choice.

---

I know, but these are decisions that come "from above," and there's no way to convince them otherwise.

@SteveKStafford @TripleM-Dev.net 

What you're saying makes sense, because yesterday, while running tests (creating new centrals on different PCs, and through different routes), we managed to identify the PCs with the problem, and they happen to be the last ones the new IT guy configured.

Time to call him and have him check it out, thanks!

[SteveKStafford]

Yes the path that Revit reports when you use Synchronize with Central and Modify Settings must be identical for each PC that will access that project's models. That means whatever process the IT people are using to map shared resources to each PC in your organization must be configured exactly the same. When Revit sees a different path it regards that file as a local file trying to access the actual central file instead.

[Simon_Weel]

Using the NAS may have been a bad choice.

I think I disagree with AI 🙂 From the client side, there's no difference between a Window Share or a NAS share, especially since most NAS'es can use SMB. So as long as you make a local connection to your NAS, there should be no problem.