IV 2016 SDK install error - serious error installing DeveloperTools.msi from SDK

[Anonymous]

Hi,

everytime I try to install the DeveloperTools.msi from the SDK of Inventor 2016, I got this serious error:

"A script required for this install to complete could not be run." - see screenshot 1.

Right before the error occurs, I see a command window popping up with "C:\Users\<Username>\AppData\Local\Temp\UpdateTypeLibPath.exe" - see screenshot 2.

I tried this on 2 workstations, both with the same result: the DeveloperTools could not be installed.

The UserTools.msi installs fine everytime.

The workstations are configured as follows:

- Windows 7 x64 (german)

- Office 2010 (german)

- Visual Basic 2010 Express (german)

- Inventor 2016 (english with additional german language pack)

All components are fully updated.

Any hints???

Kind regards

[Anonymous]

I'm having the same issue but using Windows 10. Sounds like the problem is not related with the OS.

[Anonymous]

SAME PROBLEM WINDOWS 8.1.  THE DEVELOPERTOOLS.MSI MUST BE INCOMPLETE, CAN WE DOWNLOAD IT SOMEWHERE ELSE?

[Anonymous]

Dirty trick but it works, when you get the OK button that complains about a script.  Goto the DeveloperTools.msi folder, copy all of the new folders to a different location.  Then press ok.  It will delete the originals, but you have a copy.  Or get the ORCA MSI editor from microsoft windows SDK, and crack that installer open (what a complex setup inside) and change its settings to fit your needs (which is Autodesk's job so good luck with that!).

[Anonymous]

Any thing new for this topic?

I got problem for compatiable inventor 2013 with Visual Stodio 2012. I very hardly get updated to Inventor 2016.  Then I got this same problem, so still can not get developtools...

[Anonymous]

No, I still have no solution seen yet...

Seems that Autodesk don't want that anyone develop for Inventor 2016... !!!???

I develop AddIns since Inventor 10, 11, 2008, 2009, and so on, never got such problem.

No support from you, Autodesk!?

I'm very disappointed about that!!!

[nate_webers]

I am also having the same issue and get this message when I try to install developertools.msi in Inventor 2016:

[Anonymous]

Yep, thats exactly it.  Again my work around was to steal the files it wrote while it was in the middle of installing them.  And Yes, Shame on Autodesk for this very common in the community error, and missing script on an installer that doesn't need to be so complicated.

[nate_webers]

Yes, I saw your earlier post and did that myself.

[YuhanZhang]

I tried to reproduce it here with couple of my machines but they all succeed, I noticed that the failure you see is about running the "C:\Users\<Username>\AppData\Local\Temp\UpdateType​LibPath.exe", I guess the point maybe that you can't run it in that location. Can you help to check that you have admin account but not standard user logged in, and turn the UAC(User Account Control) off, then try to install the DeveloperTools.msi again to see if it works? I am not sure if there are any group policy are set in your machines that will block you to run an Exe from that location, if the failure still happens can you ask your IT to help?

Hope this helps.

[Anonymous]

Hi,

thanks for your answer so far!

Here are our configuration:

- Windows 7 Pro x64

- no domain, only stand alone workstations with NAS

- no group policies set, untouched standard Windows installation

- the users accounts are of type "administrator", not "standard user"

- UAC is turned on - I will try that with UAC off later and report the result

"DeveloperTools.msi" asks for rights after launching, so it should have the necessary rights, even with UAC on I think.

The main clue for that this is a fault of Autodesks Installer is, that the "DeveloperTools.msi" from Inventor 2015 and earlier are worked fine on exactly the same configuration!

Kind regards

[YuhanZhang]

Thanks for your info, please let me if turning UAC off helps there. I will commpare the installer from Inv2016 with that from Inv2015 to check if I can fix it here.

[Anonymous]

Hi,

in our lunch break I could test now with UAC off on our workstations.

As I thought, it doesn't matter. The error still occurs.

Would you please post the "DeveloperTools.msi", that you could successfully installed!?

So we could compare it with the file, that we have.

Maybe that already solves our problem...

Kind regards

[nate_webers]

With my computer, I am the administrator.  The MSI file fails in the same way regardless of where I run it from.

[kmiller]

I am having the same problems.  Just tried it this morning.  I am administrator on my machine. I do not believe any of our group policy's prohibit me from running the exe from that location although I never did get the second command prompt window that the initial post showed.  Just the general message about the Windows Installer package not being able to run script required for completion.

- UAC is on - 1 "notch" above off. 

- Win 7 64-bit Pro - SP1

- VS Express 2012

- Visual Basic 2010 Express

- Office 2007

- Inventor 2016 w/ Updates (From Product Design Suite Premium)

- Whole other slue of Autodesk Products (Revit, Vault Basic, AutoCAD, Design Review, DWG True View)

[YuhanZhang]

My colleague helped to identify where the problem is, seems the point is the KB3072630(please let me if your windows has not this update yet, that maybe a different issue), this update changes the Windows Installer privilege that causes the installer DeveloperTools.msi fails to call the Exe (C:\Users\[username]\AppData\Local\Temp\UpdateTypeLibPath.exe), I will check how to fix this issue for next release, but for current build we can use below workaround:

1. Uninstall the  KB3072630 from your windows first.

2. Install the DeveloperTools.msi.

3. Re-install the  KB3072630. 

Another workaround is to just disable the  KB3072630 first and then enable it after installing the  DeveloperTools.msi, below are the steps:

1. Download the attached zip file, unzip it and double click the KB3072630Disabled.reg to register a key to registry, you can also manually create the key in the registry.

2. Install the  DeveloperTools.msi, after installation(there should be no the failure dialog during installation) you should manually run the C:\Users\[username]\AppData\Local\Temp\UpdateTypeLibPath.exe once. This is becase even the failuredialog is suppressed but the DeveloperTools.msi still can't execute the Exe. To check if the Exe is run successfully you can check the file C:\Users\Public\Documents\Autodesk\Inventor 2016\SDK\DeveloperTools\Include\InventorUtils.h, it should have a full path for the RxInventor.tlb like in below picture:

3. Double click the KB3072630Enabled.reg to remove the key that created in step 1. 

The KB3072630 was published on July 14, 2015, but on my machines I don't have this update:(, so I did not reproduce the problem. Hope this workaround works for you for now, if any more problems please let me know.

[YuhanZhang]

Please try the workaround I replied to i25506. And let me if any more issues.

[YuhanZhang]

Please try the workaround I replied to i25506, and let me if any more issues.

[Anonymous]

Hi,

thanks for your help with the KB3072630 workaround!

The KB3072630 is installed on all of our workstations.

I tried both workarounds, both with the same following result:

- the "DeveloperTools.msi" installation runs to the end with no errors

- but the "InventorUtils.h" doesn't have the full path to the "RxInventor.tlb" type lib  - the code line is still:

#import "RxInventor.tlb" no_namespace named_guids raw_dispinterfaces raw_method_prefix("") high_method_prefix("Method") \
    rename("DeleteFile", "APIDeleteFile"), rename("CopyFile", "APICopyFile"), rename("MoveFile", "APIMoveFile") \
    rename("SetEnvironmentVariable", "APISetEnvironmentVariable")

With both workarounds you have to run "C:\Users\[username]\AppData\Local\Temp\UpdateTypeLibPath.exe" "as administrator" before you close the "DeveloperTools.msi" installer!

Then you get the full path set in "InventorUtils.h" like:

#import "C:\\Program Files\\Autodesk\\Inventor 2016\\Bin\\RxInventor.tlb" no_namespace named_guids raw_dispinterfaces raw_method_prefix("") high_method_prefix("Method") \
    rename("DeleteFile", "APIDeleteFile"), rename("CopyFile", "APICopyFile"), rename("MoveFile", "APIMoveFile") \
    rename("SetEnvironmentVariable", "APISetEnvironmentVariable")

The KB3072630 windows update is a important security update, not an optional update. So I wonder that anyone could not have it...

Kind regards

[nate_webers]

I haven't had time to examine the effects, but I tried option two... the one that has the different registry keys.  I was able to get DeveloperTools.msi to run fine without any error message.

However, it would be better to have an MSI solution that didn't require the developer to hack their registry or uninstal a Windows hot fix in order to work properly.