I am having an issue with our revit files and how it is accessing the central file. Every time that I (along with others in my office) go to open the central file to create a new local file we receive an error that the central file has been copied or moved (see first image). The file has not been moved or changed so we do not understand why we are getting the message.
We have found that if we go through our PC to the network location, we receive the error (image 2). This is how we have always accessed these files. However if we go through the network location the file will open up normally. See image 3.
The files are at the same location and we cannot figure how to get the computer to understand that it is the same location, or at minimum go back to understanding that when access the file through our PC (i.e. the 2nd image) that we no longer get the error message.
Gelöst! Gehe zur Lösung
Gelöst von trunyan. Gehe zur Lösung
Try re-setting up your Central. Open the file as Detached with preserved Worksets, save in desired location as Central.
Why is it happening and how do I correct it? Creating new centrals for hundreds of projects is cumbersome not to mention that there are sometimes errors when creating new centrals which can potentially lose work. I want to fix the issue and understand why it is happening not put a band-aid on the problem.
Revit reads the EXACT file location path, so make sure everyone has the drive mapped on the same letter. From you image #2, everyone should have that Project (P:) drive mapped on the P: letter.
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
We did and still do have it mapped the same way. For this particular project I was the only one on the file, no one else accessed it. Then one day, it gave me the error. We do not have a new server and I have no clue what could have changed (on purpose or accident). I can only assume it may be something our I.T. guy did but no one has moved the file and everyone is having issues.
Everyone has always accessed their files by going to my computer and then selecting the network drive, in this particular case labeled P drive. No one has ever had to go the back route through the network mapping location.
Just a side comment. I checked the collaborate button and went to show history. The history shows 2 users, both are me, however it appears that my username now has the @email... added to the end of my user name. After a quick search online I think it is related to autodesk 360 and its change of user name input. I don't know if this has any bearing on the subject, just thought I would list it.
keep in mind that either user would still have linked it through the mapped drive and not through the network drive path.
Revit looks at the (UNC) address
Definition of: UNC. UNC. (Universal Naming Convention) A standard for identifying servers, printers and other resources in a network, which originated in the Unix community. A UNC path uses double slashes or backslashes to precede the name of the computer. ... \\servername\path DOS/Windows.
somewhere along the line users are losing this connection and that is why it seems to keep getting lost as far as revit knows.
maybe your IT guy can work through this
if the username becomes an issue (someone actually working in the central file) that might be something to look for too.
I was able to find a similar link based off of the UNC information. https://forums.autodesk.com/t5/revit-collaboration-forum/central-files-and-unc-paths/td-p/5526398 however there was a comment about correcting it back to revit 2014. Did That information ever get resolved by autodesk?
Whereas Revit appeared to be able to identify both the mapped drive and and the UNC location as being the same location. Then something changed.
Could it possibly be a windows updated on our server or something along those lines that could cause the issue?
Interesting page. This point from Steve Stafford struck me as possibly having a bearing on your situation -
To go on to your query about the latest and greatest re this concern, you may be able to get more information on the Revit Collaboration forum.
at this point I wouldn't rule out too many things
we ran into an issue a few years ago that turned out to be a hardware issue
10/100 switch was in the mix of a gigabit switch once the switch was upgraded issue went away.
windows updates, the same build number for all revit users all play a role.
I too saw that comment while doing research online on the subject. However, I have a single file that has been created and ONLY accessed by myself. I have only accessed the file from one computer so there is not a possibility of things being changed from a user perspective.
Day in, day out the file is accessed the exact same way by the same person, in this case, myself. Generically, I create a new local about once a week to keep things refreshed and to minimize errors in the file (at least that is my understanding). Then one day, errors start happening in the entire office. We did not get a new server so we can rule that out, however I don't know what updates may have been installed.
I appreciate the link to the other comment however I don't think it applies in this situation.
Pick a method of how to connect to the location and make sure everyone is using the same method.
I suggest keeping your Projects (P:) method and make sure everyone is setup that way.
We did keep to the same method, everyone was using the mapped drive. Then something changed (what I am trying to ascertain) and the only way to access the file is through the network folders or saving the file as a new central. From a user perspective nothing changed on our end. For hundreds of projects and multiple employees saving as a new central it is not something that is easily done.
Did IT change hard drives on you? That will cause the issue that you are experiencing.
Have had it happen to me quite a few times.
Not to my knowledge, however I am checking just to make sure. Keep in mind I can still access the exact same file without errors by going through the network path versus mapped drive.
So we found the issue and cause of the problem or should I say my I.T. guy solved the issue. We found that when the I.T. pushed out a security setting through GFI essentials it changed the host name for how the drives were mapped.
The revised structure had the IP address as the mapping structure (mapping image) whereas the original did not. Once the I.T. guy noted that he pushed out a new setting to change the mapped drives to coincide with the original naming structure versus the IP address.(Revised image)
so it was UNC vs Network path good catch IT guy
Yes it was the UNC / network path but not something a user did. We were trying to figure out what changed since there was no new equipment. With that in mind, if someone has to replace a server is there a way to name the new server correctly that we would not have to update central locations?
to my knowledge no
we went through this exercise a few years ago we had to rebuild all the models with the new server UNC path.
now we use Revit Servers for all our projects
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.