CODEWITHSUNDEEP
autodesk-forge
Chris Acheson
Chris Acheson

Reputation: 19

Erratic behaviour during translation

We are experiencing erratic translation behaviour, and have been now for a few days. Some examples:

We can translate a small number of assemblies successfully, which indicates it is not a problem with our code. Below is a typical manifest that we are getting from these errors.It's a step file that was exported from Inventor 2016. It successfully translates and is viewable within A360 but not with the Forge APIs.

{
 "type": "manifest",
 "hasThumbnail": "false",
 "status": "failed",
 "progress": "complete",
 "region": "US",
 "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6Y2Fkc2hhcmUtZGV2LWJ1Y2tldC9TaGFmdC5zdHA",
 "version": "1.0",
 "derivatives": [
   {
     "name": "Shaft.stp",
     "hasThumbnail": "false",
     "status": "failed",
     "progress": "complete",
     "messages": [
       {
         "type": "error",
         "code": "ATF-1025",
         "message": [
           "The file: {0} is corrupt or invalid.",
           "C:\\worker\\viewing-atf-lmv\\tmp\\job-1\\6\\Shaft.stp"
         ]
       },
       {
         "type": "error",
         "message": "Possibly recoverable warning exit code from extractor: -536870943",
         "code": "TranslationWorker-RecoverableInternalFailure"
       }
     ],
     "outputType": "svf"
   }
 ]
}

Upvotes: 1

Views: 218

Answers (1)

L. Silverio
L. Silverio

Reputation: 13

I had almost the same problem with this exact message. In my case, the cause of the problem was that the stream of the file i was uploading wasn't on it's beggining, so i just did a fileStream.Seek(0, SeekOrigin.Begin); and then it worked for me.

Upvotes: 1

Related Questions