Revit 2016 error: an unnamed file contains an incorrect path

[mark.pritchard]

Hi all,

I have been looking through the forums about this error and so far all I can find is related to systems or assemblies, however I have been getting this same error when I try to sync to central.

Some background: I am working on a large project and currently we have about 20 models all linked into each other. We are using Revit 2016 and we have all of our Revit models hosted on Revit server.

Currently each model has its own specific sheets and then the models are all linked into our SHEET model which is used to produce the cover page and drawing index sheet for each package of drawings.

Recently, I have been getting this error message quite a lot when I try to sync this sheet model. I update the linked files, reload them, and then when I sync, I get the error. It doesn't happen often, but recently it has happened twice within the span of 4 days.

The workaround that I have been doing is to save the local file and close it, then reopen with Audit checked - when I try to open it detached I get the same error. Then I have to "save as" and give it a different name. Close the file, open it again, this time detached (as it allows me to) and then I can save over the original file.

Has anyone else seen this happen when trying to sync and how have you resolved it? Does anyone know what causes this error to appear?

Any feedback would be greatly appreciated.

Many thanks.

[jdtull]

Same thing's been happening to me.  Project is hosted on the Revit Server, try to sync, and get the same message.  We have to do the same workaround here - doesn't look like anyone is aware of why this happening... otherwise Autodesk would have responded by now.

[mark.pritchard]

Yes I agree, we would have heard soemthing by now.

I have been looking at the various links within my model and their path lengths however, but as I mentioned in my first post, the longest length is 98 characters.  Someone recently mentioned to me that if there is an AutoCAD drawing, for example, linked into another model that is then linked into my model, this could be the path that is being read as well.  So nested links could be causing the error.  However when I looked into this, the longest path I could find was 176 characters - well short of the 256 max length that Autodesk told me.

I'm still not convinced that the path length is the cause.  I have not had the error come up again since posting my original comment, so it's just a waiting game now.

[Anonymous]

Has anyone ever resolved this error? I'm getting this same error for the first time.

[mark.pritchard]

NO, I have not seen any other resolutions, apart from the fix that we mentioned in the posts above

[thomaskoruga]

Hello there,

we are currently experiencing the same issue, it seems that it happens randomly when the file path exceeds or comes close to 255 characters. We are using Revit Server 2017.

The immediate fix (atleast a fix which works for us) is saving the file locally, opening the local file and synchronizing the local file with the central file.

Another seemingly more permanant fix is changing either the file path to a shorter one or changing the affected users username in Revit to something shorter.

Hope this helps,
Thomas Koruga

[mark.pritchard]

Hi Thomas,
We have been doing the same fix that you mentioned.  We have also shortened the path to the model location, but the problem is with nested links and trying to find which one is the offending link.  I have been using the Revit Express Tools, "Import & Link Manager" plug in to help find files with long paths.

Mark

[Anonymous]

I am having the same error with one of my users...

But here's the catch. It's on C4R (using Revit 2017), not on a Revit Server.

Two of my users and I are all able to sync without issue, but 1 user in particular is receiving that error when they try.

Her Autodesk ID is a lot shorter than mine, so as for filename lengths I don't think that's the issue.

Anyone else encountered this problem on C4R?

[thomaskoruga]

Hey there Matthew,

thats quite a interesting issue you have.

Would you be able to provide a journal file from the affected computer and from one of the "working" computers? Than we could take a look at it and try to figure out whats the issue.

Workflow to obtain the journal files: Replicate the issue on the affected computer, after that close Revit and get the latest journal file from %LOCALAPPDATA%\Autodesk\Revit\Autodesk Revit 2017\Journals. Do the same thing on the working compute. Then you have the two journal files. Ideally name one of them "not_working_journal" and the other one "working_journal" to avoid any confusion.

Greetings, Thomas

p.s. If there is any sensitive Information in the files you can open them with notepad and replace information you don't want to share with XXX.

[Darin_HDR]

I just had this happen to me. I was going to comment on it in this post, but when I went to log in to type a response to this forum I could not. The reason I quickly discovered is my email address associated with my account had been changed to an old one. That is another topic as to why that may have happened (as I did not change it). However, when I changed it back, I was able to sync again using C4R. The short of it is, an email change associated with my account resulted in me receiving this same error message. Not to say that is the cause for everyone, but maybe someone who someday reads this thread.

[Anonymous]

Hi Thomas

I managed to solve the issue . Fortunately the user hadn't done too much work from previous sync, so I closed Revit and went in and cleared the Collaboration Cache folder associated with that project.

When the model re-cached and opened the sync functionality was restored.

I'm still not sure what the root cause was. As SOA_Arch mentioned it could have been due to email address association. Although in this case the user had been able to sync. hadn't closed Revit or the model, and suddenly, approximately 2 hrs after their last sync, the error popped up.

Anyway, I will keep and eye out and report again if the situation repeats itself.

Thanks again

Matt

[TBruntz1]

We just had this happen in Revit 2017.2.3 where we had a central model living on Revit Server 2017 and we were referencing .rvt files that were on a Windows server.  We narrowed the problem down to the Windows server path being too long.  We ended up moving the files to Revit server to fix the issue.  The alternative would have been to put them in a windows share that had a shorter path.  I hope that helps others having the same issue!

[Anonymous]

Just found out a user name change will do this too. Found out because for no reason at all, Autodesk changed my email address associated with the account (when I first posted). Then today did the same thing with my username (notice the username change, that is because my old username is "unavailable" after it defaulted to my email address). I want to scream at Autodesk but will refrain from doing it here in all caps.

[Anonymous]

I had this error and stumbled across this thread with the same problem.  I got this error because I removed the pathing to where I print PDF's to. I was able to fix it by reprinting the page and putting in an actual path, if you leave the path empty it defaults to where your revit is installed to and gives you this error. You don't have to actually PDF the page, just route where to send it and hit cancel.

[Anonymous]

Thank you, signing in and signing out fixed my problem.

[odb_vla]

I just experienced same issue.  rknutson suggestion works perfectly.  Just try to reprint with default settings with specified path. Thank you

[bzhang6NMAK]

Thanks so much for the tip! It's exactly what happened to me that caused the error message. The difference is I didn't manually changed the pdf printing path before the error occurred. I simply changed the pdf printing path from a long server folder address to my local document folder. And this solves the problem.