ETO Deployment Configurator 2017 fails to configure deployment

ETO Deployment Configurator 2017 fails to configure deployment

AndrewPotachits
Enthusiast Enthusiast
793 Views
2 Replies
Message 1 of 3

ETO Deployment Configurator 2017 fails to configure deployment

AndrewPotachits
Enthusiast
Enthusiast

I'm trying to build an OEM package for our customer, I'm using this instruction.

 

However on step 3 I'm having error "Exception during build. See Intent.log for details.

 

In the Intent.log I don't see any details:

 

util.dc    TRACE 2017-10-03 10:36:03.2408 10528 DeployConfig.Initialize 
ic.settng  TRACE 2017-10-03 10:36:03.2568 10528 Loading settings from 'C:\Program Files\Autodesk\Inventor ETO 2017\Bin' 
util.dc    TRACE 2017-10-03 10:36:03.3238 10528 UpdateOEMProperties 
util.dc    TRACE 2017-10-03 10:36:03.3358 10528   OEM_ProductName = Catalyst 
util.dc    TRACE 2017-10-03 10:36:03.3358 10528   OEM_Manufacturer = Oldcastle Precast 
util.dc    TRACE 2017-10-03 10:36:03.3358 10528   OEM_Language = English 
util.dc    TRACE 2017-10-03 10:36:03.3588 10528   OEM_Platform = x64 
util.dc    TRACE 2017-10-03 10:36:03.3662 10528   OEM_ResultPath = C:\AdminImage\outputPackage 
util.dc    TRACE 2017-10-03 10:36:03.3778 10528 UpdateFromDeployment 
util.dc    TRACE 2017-10-03 10:36:27.4576 10528 Starting Build 
util.dc    DEBUG 2017-10-03 10:36:27.4576 10528 Exception during build.  See Intent.log for details. 
util.dc    DEBUG 2017-10-03 10:36:27.4716 10528 bad result=0 

Is there any way to resolve this error?

 

Andrew.

Reply
Reply
0 Likes
Accepted solutions (1)
794 Views
2 Replies
Replies (2)
Message 2 of 3

AlexKorzun
Autodesk
Autodesk
Accepted solution

For the curious folks: you have to run Deployment Configurator as Administrator.

We are looking to eliminate this requirement in the next release.

Thank you,




Alex Korzun
Inventor-Revit Interop / Inventor-Fusion Interop / Inventor ETO
Autodesk, Inc.

Reply
Reply
Message 3 of 3

Anonymous
Not applicable

I have ran the deployment configurator as admin and it still fails to create deployment. I am using ETO 2018. I did not have this issue prior to switching over to 2018. 

Reply
Reply
0 Likes