topic Re: "Failed to translate" in BIM 360 Support Forum

"Failed to translate"

Chad-Smith — Wed, 16 May 2018 00:34:31 GMT

Came across a translation error today. Pressing 'Update to Latest' kept telling me that I had no Sets.

Yet, in Revit using the publish through Manage Cloud Models worked.

So while I don't have an issue anymore, I thought I might flag it as something to maybe investigate.

Re: "Failed to translate"

martyn_messerli — Wed, 16 May 2018 07:42:10 GMT

Hi Chad,

thanks for reporting this issue. We apprechiate those reports which helps us to make the whole process more robust. I'll go through the logs and see whether I can trace down the problem and try to figure what we can improve.

It can happen from time to time that the overal translation (generating all the derivatives required for the web) either fail in the backend or the Design Collaboration specific translations fail (generating viewer data for an improved experiance). If there is no real problem with Revit file, the issue can be resolved by publishing the data again.

Regards

Martyn

Re: "Failed to translate"

martyn_messerli — Fri, 18 May 2018 09:41:20 GMT

Small heads-up,

To narrow down where the error happens (DC or Docs), you can check whether you can see the models within the document version on Docs. If you cannot see the content, e.g no version number is shown for the document in docs or no derivatives are shown when you select the document, then the translation of BIM360 Docs failed.

If the you can see all the derivatives in BIM360 Docs, we have to check the logs for Design Collaboration Services to figure what the problem is.
Just in case you run again into this problem.

We have a ticket in our backend to look into one of the crashes related to links. Not sure whether this is related to your problem.

Martyn

Re: "Failed to translate"

Anonymous — Fri, 18 May 2018 15:24:58 GMT

I have seen this error (Failed to translate) when we change set names in Revit and publish to BIM 360 Design.

See my post 'Design Collaboration breaks...' for some detail.

In our case, publishing the file again to BIM 360 Design has no effect. Changing the set names back to their original names will restore the file.

Re: "Failed to translate"

Anonymous — Thu, 01 Nov 2018 18:27:22 GMT

not solved!

Re: "Failed to translate"

Anonymous — Thu, 01 Nov 2018 18:30:12 GMT

did not work.

Re: "Failed to translate"

martin — Fri, 02 Nov 2018 20:31:34 GMT

Martyn,

I've run across this same issue. When posting to BIM 360 I get the file in the Document Managment portion but nothing shows up in the Design Collaboration side. Is this an issue that has yet to be resolved or is there a technical support contact that I can get in contact with to help resolve the issue with this process. We are currently testing the BIM 360 platform to see if want to go ahead with it, but need some assurances that this type of thing has some resolve.

Regards,

Martin

Re: "Failed to translate"

martyn_messerli — Fri, 11 Jan 2019 14:47:58 GMT

@martin When you say "nothing shows up" do you see the error from this topic (Failed to translate)? If not, then this is maybe another problem. Be also aware, that it takes a moment to finish all process and prepare date for the web application.

It can always happen that a translation fails due some backend issues. In most cases publishing again can solve the problem. If not then this needs investigation for the given case, which can differ to other occurence.

Betreff: "Failed to translate"

asWAPL9 — Mon, 21 Mar 2022 08:50:38 GMT

@martyn_messerli the last thread here is from 2019 however we have this problem in ACC Collaborate Pro. re-publishing the model solved it.