Deployment for Navis Freedom 2018 Fails!

mdhutchinson
Advisor

Deployment for Navis Freedom 2018 Fails!

mdhutchinson
Advisor
Advisor

I have made multiple attempts at downloading and building a deployment of Navisworks Freedom 2018 and have about exhausted the possible combinations.

 

  1. Download from  https://www.autodesk.com/products/navisworks/3d-viewers
  2. Virtual Agent Download.
  3. Locate / launch resulting install folder on C drive.
  4. Locate on my D drive.
  5. Locate on a different computer.

Every time I get the same error. See attached log file and image.

I've done this for every year since 2010... but now if fails.

 

Why... is the install media have a flaw in it... perhaps I need edit an ini file?

 

2017-07-28_11-55-49.png

 

 

Reply
617 Views
2 Replies
Replies (2)

natasha.l
Alumni
Alumni

Hello @mdhutchinson,

 

Is this issue specifically happening only on this computer or did you try to create the deployment on another Admin computer? 

 

 

0 Likes

mdhutchinson
Advisor
Advisor

The deployment I am wanting to create is/will be on the same network server I have used for all our deployments since probably the year 2012 or 2014.

 

After I fill in Administrative Image Deployment Name, Path, Installation Settings fields, Accepting the License Agreement, doing Next and deselecting Autodesk Desktop App, the error pops immediately after clicking on the Create button... (only the folder got created - but no content inside the folder)

 

... but, you have got to be kidding me...  walking through the steps to verify what I just typed out in the sentence above... the deployment proceeded as it should as if I had made the same error all the other 7 or 8 times. ?????

 

... waiting for finish.  Done.

 

What might have I done to cause the same identical error +or-8 times downloading with different methods and running from multiple drives/computers before?

 

The only thing I can think of is for this time is that I had changed the folder name/deployment name (partly from a miss-typing). Don't know... maybe the Deployment Name and the Folder name were identical in prior attempts. Folder name was NavFree, and Deployment Name was NavFree . 

 

Would that have triggered a bug in the software????

 

 

0 Likes